<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Merci Colonel!!<BR> <BR>
> Date: Fri, 24 Dec 2010 11:06:30 +0200<BR>> From: rpd-request@afrinic.net<BR>> Subject: rpd Digest, Vol 52, Issue 3<BR>> To: rpd@afrinic.net<BR>> <BR>> Send rpd mailing list submissions to<BR>> rpd@afrinic.net<BR>> <BR>> To subscribe or unsubscribe via the World Wide Web, visit<BR>> https://lists.afrinic.net/mailman/listinfo.cgi/rpd<BR>> or, via email, send a message with subject or body 'help' to<BR>> rpd-request@afrinic.net<BR>> <BR>> You can reach the person managing the list at<BR>> rpd-owner@afrinic.net<BR>> <BR>> When replying, please edit your Subject line so it is more specific<BR>> than "Re: Contents of rpd digest..."<BR>> <BR>> <BR>> Today's Topics:<BR>> <BR>> 1. e-mail (Fran?ois OUEDRAOGO)<BR>> 2. AfriNIC to assign AS Numbers from a common 32-bit pool.<BR>> (Ernest - (AfriNIC))<BR>> 3. Re: Comments about AFPUB-2010-GEN-005 (Dr Paulos Nyirenda)<BR>> 4. Re: Comments about AFPUB-2010-GEN-005 (Owen DeLong)<BR>> 5. Re: Comments about AFPUB-2010-GEN-005 (Walubengo J)<BR>> 6. Re: Comments about AFPUB-2010-GEN-005 (Ademola Osindero)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Fri, 17 Dec 2010 19:00:09 +0000<BR>> From: Fran?ois OUEDRAOGO <ouedraogo.francois@gmail.com><BR>> Subject: [AfriNIC-rpd] e-mail<BR>> To: rpd@afrinic.net<BR>> Message-ID:<BR>> <AANLkTimY0rVwjy1C=2Shoz_bdUbc8jEVKSbh4iNyDXB5@mail.gmail.com><BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> <BR>> ouedraogo.francois@gmail.com<BR>> <BR>> -- <BR>> *<BR>> ================================================================================================================<BR>> ==============*<BR>> <BR>> François Ouédraogo<BR>> Colonel<BR>> <BR>> Directeur des Transmissions et de l'Informatique<BR>> Gendarmerie Nationale<BR>> Aide de Camp du Président de l'Assemblée Nationale<BR>> <BR>> Tel. mob: (226) 70200914<BR>> (226) 76200914<BR>> (226) 78200914<BR>> Tel. bur: (226) 50318015<BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: https://lists.afrinic.net/pipermail/rpd/attachments/20101217/d104bf99/attachment-0001.htm<BR>> <BR>> ------------------------------<BR>> <BR>> Message: 2<BR>> Date: Mon, 20 Dec 2010 14:16:42 +0300<BR>> From: "Ernest - (AfriNIC)" <ernest@afrinic.net><BR>> Subject: [AfriNIC-rpd] AfriNIC to assign AS Numbers from a common<BR>> 32-bit pool.<BR>> To: announce@afrinic.net<BR>> Message-ID: <4D0F3B1A.2050900@afrinic.net><BR>> Content-Type: text/plain; charset=ISO-8859-1<BR>> <BR>> Dear Colleagues,<BR>> <BR>> According to the "IANA Policy for Allocation of ASN Blocks to the<BR>> Regional Internet Registries (RIRs)" -<BR>> http://www.afrinic.net/docs/policies/AFPUB-2008-ASN-001.htm , IANA<BR>> will cease to make any distinction between 16 and 32-bit only<BR>> ASN blocks on 31 December 2010 when making allocations to RIRs.<BR>> <BR>> After this date, the RIRs will assign AS Numbers from an<BR>> undifferentiated 32-bit ASN allocation pool.<BR>> <BR>> Consequently, for any entity requesting an ASN, AfriNIC will cease<BR>> to present the ability to opt for a 16- or 32-bit ASN, and will<BR>> start issuing ASNs from a common 32-bit pool.<BR>> <BR>> We therefore urge all IP network operators to ensure that their<BR>> routing infrastructure is 32-bit ASN compatible.<BR>> <BR>> Kind regards,<BR>> <BR>> Ernest Byaruhanga.<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 3<BR>> Date: Thu, 23 Dec 2010 16:07:19 +0200<BR>> From: "Dr Paulos Nyirenda" <paulos@sdnp.org.mw><BR>> Subject: Re: [AfriNIC-rpd] Comments about AFPUB-2010-GEN-005<BR>> To: Nii Narku Quaynor <quaynor@ghana.com>, rpd@afrinic.net<BR>> Message-ID: <4D135797.18560.16404C7@paulos.sdnp.org.mw><BR>> Content-Type: text/plain; charset=US-ASCII<BR>> <BR>> <BR>> Experience on the AfriNIC PDP-MG shows that conflict among chairs of the PDP process has <BR>> occurred often in the last three years, making this a very meaningful and pertinent <BR>> issue. <BR>> <BR>> This has been the case at face to face public policy meetings as well as during PDP-MG <BR>> internal meetings. It has been observed before that AFPUB-2010-GEN-005 has a major <BR>> problem in that it has two co-chairs (even number) which will result in many hanging <BR>> decisions very often. <BR>> <BR>> One way to the resolve this is to revise AFPUB-2010-GEN-005 so that number of co-chairs <BR>> should have been odd.<BR>> <BR>> When analysing such conflicts, it will be necessary to include consideration of conflicts <BR>> of interest in policy development such as the case where one of the PDP co-chairs is an <BR>> author of a policy under consideration as it unfortunately happened in the development of <BR>> AFPUB-2010-GEN-005.<BR>> <BR>> Regards,<BR>> <BR>> Paulos<BR>> ======================<BR>> Dr Paulos B Nyirenda<BR>> NIC.MW & .mw ccTLD<BR>> http://www.registrar.mw<BR>> <BR>> <BR>> On 15 Dec 2010 at 12:42, Nii Narku Quaynor wrote:<BR>> > <BR>> > On Dec 15, 2010, at 2:12 AM, sm+afrinic@elandsys.com wrote:<BR>> ><BR>> > > AFPUB-2010-GEN-005 does not discuss about the question of conflict between the two<BR>> > > Chairs. I suggest that the Chairs ask the community for comments to get a better<BR>> > > perspective of the problem. The Chairs bear the responsibility to make the process <BR>> > > work and to ensure that their decisions have the consensus of the community.<BR>> > <BR>> > <BR>> > normally, Chairs are looking for consensus so conflict would not be so meaningful<BR>> > Nii_______________________________________________<BR>> > rpd mailing list<BR>> > rpd@afrinic.net<BR>> > https://lists.afrinic.net/mailman/listinfo.cgi/rpd<BR>> <BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 4<BR>> Date: Thu, 23 Dec 2010 07:23:51 -0800<BR>> From: Owen DeLong <owen@delong.com><BR>> Subject: Re: [AfriNIC-rpd] Comments about AFPUB-2010-GEN-005<BR>> To: paulos@sdnp.org.mw<BR>> Cc: rpd@afrinic.net<BR>> Message-ID: <A7DFC173-08D7-4106-B61F-F0D9B7641206@delong.com><BR>> Content-Type: text/plain; charset=us-ascii<BR>> <BR>> If there is conflict between two chairs, that would seem to indicate a lack of consensus.<BR>> <BR>> If there is not consensus, the policy proposal should not move forward.<BR>> <BR>> Since that is what happens if the chairs don't agree, this does not seem problematic to me.<BR>> <BR>> Having said that, I don't think an odd number of co-chairs is a bad idea.<BR>> <BR>> Owen<BR>> <BR>> On Dec 23, 2010, at 6:07 AM, Dr Paulos Nyirenda wrote:<BR>> <BR>> > <BR>> > Experience on the AfriNIC PDP-MG shows that conflict among chairs of the PDP process has <BR>> > occurred often in the last three years, making this a very meaningful and pertinent <BR>> > issue. <BR>> > <BR>> > This has been the case at face to face public policy meetings as well as during PDP-MG <BR>> > internal meetings. It has been observed before that AFPUB-2010-GEN-005 has a major <BR>> > problem in that it has two co-chairs (even number) which will result in many hanging <BR>> > decisions very often. <BR>> > <BR>> > One way to the resolve this is to revise AFPUB-2010-GEN-005 so that number of co-chairs <BR>> > should have been odd.<BR>> > <BR>> > When analysing such conflicts, it will be necessary to include consideration of conflicts <BR>> > of interest in policy development such as the case where one of the PDP co-chairs is an <BR>> > author of a policy under consideration as it unfortunately happened in the development of <BR>> > AFPUB-2010-GEN-005.<BR>> > <BR>> > Regards,<BR>> > <BR>> > Paulos<BR>> > ======================<BR>> > Dr Paulos B Nyirenda<BR>> > NIC.MW & .mw ccTLD<BR>> > http://www.registrar.mw<BR>> > <BR>> > <BR>> > On 15 Dec 2010 at 12:42, Nii Narku Quaynor wrote:<BR>> >> <BR>> >> On Dec 15, 2010, at 2:12 AM, sm+afrinic@elandsys.com wrote:<BR>> >> <BR>> >>> AFPUB-2010-GEN-005 does not discuss about the question of conflict between the two<BR>> >>> Chairs. I suggest that the Chairs ask the community for comments to get a better<BR>> >>> perspective of the problem. The Chairs bear the responsibility to make the process <BR>> >>> work and to ensure that their decisions have the consensus of the community.<BR>> >> <BR>> >> <BR>> >> normally, Chairs are looking for consensus so conflict would not be so meaningful<BR>> >> Nii_______________________________________________<BR>> >> rpd mailing list<BR>> >> rpd@afrinic.net<BR>> >> https://lists.afrinic.net/mailman/listinfo.cgi/rpd<BR>> > <BR>> > <BR>> > _______________________________________________<BR>> > rpd mailing list<BR>> > rpd@afrinic.net<BR>> > https://lists.afrinic.net/mailman/listinfo.cgi/rpd<BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 5<BR>> Date: Fri, 24 Dec 2010 00:41:38 -0800 (PST)<BR>> From: Walubengo J <jwalu@yahoo.com><BR>> Subject: Re: [AfriNIC-rpd] Comments about AFPUB-2010-GEN-005<BR>> To: Nii Narku Quaynor <quaynor@ghana.com>, rpd@afrinic.net,<BR>> paulos@sdnp.org.mw<BR>> Message-ID: <327390.81023.qm@web57808.mail.re3.yahoo.com><BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> <BR>> my earlier undestanding behind the need to have 2chairs for the PDP was that they could act as "alternate" to avoid the occurence of "no chair" present as it happened in Afrinic-11 in Senegal.<BR>> <BR>> However, during the last policy meeting in SA (Afrinic-13), it occured to me that BOTH Chairs are actually expected to be present and managing the Policy discussion - thus creating a real potential for deadlocks (as Dr. Paulos describes here).<BR>> <BR>> One quick way to resolve the potential for deadlocks while simultaneously eliminating the potential for "absent chair" is to designate a "lead" Chair for each Policy meeting on a rotational basis. Since we have 2 policy meetings per year, and 2 chairs, the lead chair in a previous policy meeting becomes the secondary chair in the subsequent meeting and both act as Backup for each other i.e. in the event a lead chair cant make it for the meeting the secondary chair simply takes over. Also this means that the lead chair for that period/session has the final say - in the event of conflict or need to break a tie (within the Chairmanship).<BR>> <BR>> regards.<BR>> walu.<BR>> <BR>> <BR>> <BR>> <BR>> On Thu, 12/23/10, Dr Paulos Nyirenda <paulos@sdnp.org.mw> wrote:<BR>> <BR>> From: Dr Paulos Nyirenda <paulos@sdnp.org.mw><BR>> Subject: Re: [AfriNIC-rpd] Comments about AFPUB-2010-GEN-005<BR>> To: "Nii Narku Quaynor" <quaynor@ghana.com>, rpd@afrinic.net<BR>> Date: Thursday, December 23, 2010, 5:07 PM<BR>> <BR>> <BR>> Experience on the AfriNIC PDP-MG shows that conflict among chairs of the PDP process has <BR>> occurred often in the last three years, making this a very meaningful and pertinent <BR>> issue. <BR>> <BR>> This has been the case at face to face public policy meetings as well as during PDP-MG <BR>> internal meetings. It has been observed before that AFPUB-2010-GEN-005 has a major <BR>> problem in that it has two co-chairs (even number) which will result in many hanging <BR>> decisions very often. <BR>> <BR>> One way to the resolve this is to revise AFPUB-2010-GEN-005 so that number of co-chairs <BR>> should have been odd.<BR>> <BR>> When analysing such conflicts, it will be necessary to include consideration of conflicts <BR>> of interest in policy development such as the case where one of the PDP co-chairs is an <BR>> author of a policy under consideration as it unfortunately happened in the development of <BR>> AFPUB-2010-GEN-005.<BR>> <BR>> Regards,<BR>> <BR>> Paulos<BR>> ======================<BR>> Dr Paulos B Nyirenda<BR>> NIC.MW & .mw ccTLD<BR>> http://www.registrar.mw<BR>> <BR>> <BR>> On 15 Dec 2010 at 12:42, Nii Narku Quaynor wrote:<BR>> > <BR>> > On Dec 15, 2010, at 2:12 AM, sm+afrinic@elandsys.com wrote:<BR>> ><BR>> > > AFPUB-2010-GEN-005 does not discuss about the question of conflict between the two<BR>> > > Chairs. I suggest that the Chairs ask the community for comments to get a better<BR>> > > perspective of the problem. The Chairs bear the responsibility to make the process <BR>> > > work and to ensure that their decisions have the consensus of the community.<BR>> > <BR>> > <BR>> > normally, Chairs are looking for consensus so conflict would not be so meaningful<BR>> > Nii_______________________________________________<BR>> > rpd mailing list<BR>> > rpd@afrinic.net<BR>> > https://lists.afrinic.net/mailman/listinfo.cgi/rpd<BR>> <BR>> <BR>> _______________________________________________<BR>> rpd mailing list<BR>> rpd@afrinic.net<BR>> https://lists.afrinic.net/mailman/listinfo.cgi/rpd<BR>> <BR>> <BR>> <BR>> <BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: https://lists.afrinic.net/pipermail/rpd/attachments/20101224/85ac34b6/attachment-0001.htm<BR>> <BR>> ------------------------------<BR>> <BR>> Message: 6<BR>> Date: Fri, 24 Dec 2010 10:04:36 +0100<BR>> From: Ademola Osindero <ademola@ng.lopworks.com><BR>> Subject: Re: [AfriNIC-rpd] Comments about AFPUB-2010-GEN-005<BR>> To: Walubengo J <jwalu@yahoo.com><BR>> Cc: rpd@afrinic.net<BR>> Message-ID: <13B68F0C-6C6A-45CF-8184-DDCF56B9B27B@ng.lopworks.com><BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> Dear,<BR>> <BR>> It is interesting to read this and see the huge potential issues with overcomplicating things. Things can just be made simple - One Chair and one or many vice chairs or co-chairs. The Chair takes a lead at all times and can designate co-chairs or vice-chairs to preside over select Policy discussions. And in the absence of a Chair, a co-chair will stand in. There must be one clear lead at all times.<BR>> <BR>> Regards,<BR>> Ademola Osindero<BR>> <BR>> CEO/Consulting Director<BR>> Lopworks Limited<BR>> 29 Ago Palace Way,<BR>> Okota, Isolo,<BR>> Lagos, Nigeria<BR>> <BR>> Mob: +234 805 809 7820<BR>> Tel: +234 1 877 5289<BR>> Email: ademola@ng.lopworks.com<BR>> <BR>> <BR>> On 24 Dec 2010, at 09:41, Walubengo J wrote:<BR>> <BR>> > my earlier undestanding behind the need to have 2chairs for the PDP was that they could act as "alternate" to avoid the occurence of "no chair" present as it happened in Afrinic-11 in Senegal.<BR>> > <BR>> > However, during the last policy meeting in SA (Afrinic-13), it occured to me that BOTH Chairs are actually expected to be present and managing the Policy discussion - thus creating a real potential for deadlocks (as Dr. Paulos describes here).<BR>> > <BR>> > One quick way to resolve the potential for deadlocks while simultaneously eliminating the potential for "absent chair" is to designate a "lead" Chair for each Policy meeting on a rotational basis. Since we have 2 policy meetings per year, and 2 chairs, the lead chair in a previous policy meeting becomes the secondary chair in the subsequent meeting and both act as Backup for each other i.e. in the event a lead chair cant make it for the meeting the secondary chair simply takes over. Also this means that the lead chair for that period/session has the final say - in the event of conflict or need to break a tie (within the Chairmanship).<BR>> > <BR>> > regards.<BR>> > walu.<BR>> > <BR>> > <BR>> > <BR>> > <BR>> > On Thu, 12/23/10, Dr Paulos Nyirenda <paulos@sdnp.org.mw> wrote:<BR>> > <BR>> > From: Dr Paulos Nyirenda <paulos@sdnp.org.mw><BR>> > Subject: Re: [AfriNIC-rpd] Comments about AFPUB-2010-GEN-005<BR>> > To: "Nii Narku Quaynor" <quaynor@ghana.com>, rpd@afrinic.net<BR>> > Date: Thursday, December 23, 2010, 5:07 PM<BR>> > <BR>> > <BR>> > Experience on the AfriNIC PDP-MG shows that conflict among chairs of the PDP process has <BR>> > occurred often in the last three years, making this a very meaningful and pertinent <BR>> > issue. <BR>> > <BR>> > This has been the case at face to face public policy meetings as well as during PDP-MG <BR>> > internal meetings. It has been observed before that AFPUB-2010-GEN-005 has a major <BR>> > problem in that it has two co-chairs (even number) which will result in many hanging <BR>> > decisions very often. <BR>> > <BR>> > One way to the resolve this is to revise AFPUB-2010-GEN-005 so that number of co-chairs <BR>> > should have been odd.<BR>> > <BR>> > When analysing such conflicts, it will be necessary to include consideration of conflicts <BR>> > of interest in policy development such as the case where one of the PDP co-chairs is an <BR>> > author of a policy under consideration as it unfortunately happened in the development of <BR>> > AFPUB-2010-GEN-005.<BR>> > <BR>> > Regards,<BR>> > <BR>> > Paulos<BR>> > ======================<BR>> > Dr Paulos B Nyirenda<BR>> > NIC.MW & .mw ccTLD<BR>> > http://www.registrar.mw<BR>> > <BR>> > <BR>> > On 15 Dec 2010 at 12:42, Nii Narku Quaynor wrote:<BR>> > > <BR>> > > On Dec 15, 2010, at 2:12 AM, sm+afrinic@elandsys.com wrote:<BR>> > ><BR>> > > > AFPUB-2010-GEN-005 does not discuss about the question of conflict between the two<BR>> > > > Chairs. I suggest that the Chairs ask the community for comments to get a better<BR>> > > > perspective of the problem. The Chairs bear the responsibility to make the process <BR>> > > > work and to ensure that their decisions have the consensus of the community.<BR>> > > <BR>> > > <BR>> > > normally, Chairs are looking for consensus so conflict would not be so meaningful<BR>> > > Nii_______________________________________________<BR>> > > rpd mailing list<BR>> > > rpd@afrinic.net<BR>> > > https://lists.afrinic.net/mailman/listinfo.cgi/rpd<BR>> > <BR>> > <BR>> > _______________________________________________<BR>> > rpd mailing list<BR>> > rpd@afrinic.net<BR>> > https://lists.afrinic.net/mailman/listinfo.cgi/rpd<BR>> > <BR>> > _______________________________________________<BR>> > rpd mailing list<BR>> > rpd@afrinic.net<BR>> > https://lists.afrinic.net/mailman/listinfo.cgi/rpd<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: https://lists.afrinic.net/pipermail/rpd/attachments/20101224/3d4174cb/attachment.htm<BR>> <BR>> ------------------------------<BR>> <BR>> _______________________________________________<BR>> rpd mailing list<BR>> rpd@afrinic.net<BR>> https://lists.afrinic.net/mailman/listinfo.cgi/rpd<BR>> <BR>> <BR>> End of rpd Digest, Vol 52, Issue 3<BR>> **********************************<BR> </body>
</html>