<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Consolas;
color:#1F497D;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=FR link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-family:Consolas;color:#1F497D'>Thank you Walu for your very clear explanation and Thanks Adamou for Its question.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:Consolas;color:#1F497D'>Best regards.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:Consolas;color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De :</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> rpd-bounces@afrinic.net [mailto:rpd-bounces@afrinic.net] <b>De la part de</b> Walubengo J<br><b>Envoyé :</b> mercredi 22 février 2012 18:57<br><b>À :</b> rpd@afrinic.net; Nacer Adamou Saidou<br><b>Objet :</b> Re: [AfriNIC-rpd] Call for policy proposals and/or issues on AfriNIC PDP for AfriNIC-16<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0><tr><td valign=top style='padding:0cm 0cm 0cm 0cm'><p class=MsoNormal>@ Adamou,<br><br>in practice Policies tend to have either a global or regional objective - by design.. E.g Policy describing the minimum block of IPs for distribution in Africa is so local that it need not be the same as that of Europe. A globally oriented policy maybe like a Policy attempt to describe what to do with legacy IPs in light of the diminishing IPv4 - trying to do this locally is possibly, but doing it globally is better (and more effective).<br><br>So in my view, if a global policy has been rejected - it makes no sense trying to accept it locally/regionally since it's original intention must have been "global" - by design. And I think this make our work easier - just add one clause in the existing PDP framework to simply "park" locally created global policies that failed to meet global acceptance.<br><br>walu.<br><br>--- On <b>Wed, 2/22/12, Nacer Adamou Saidou <i><adamou.nacer@gmail.com></i></b> wrote:<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><br>From: Nacer Adamou Saidou <adamou.nacer@gmail.com><br>Subject: Re: [AfriNIC-rpd] Call for policy proposals and/or issues on AfriNIC PDP for AfriNIC-16<br>To: rpd@afrinic.net<br>Date: Wednesday, February 22, 2012, 11:18 AM<o:p></o:p></p><div><p class=MsoNormal>-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>Hi all,<br>I really need to understand what problem we are trying to solve. For me,<br>if a policy is approved ifrom the AfriNIC community, that means that<br>that policy is the answer to an issue from the AfriNIC community, issue<br>that may not appears the same way in other communities.<br>So why do we want to treat differently globally approved policies from<br>those approved only by our community? What added value can we expect<br>from that?<br><br>Regards<br><br>Le 21/02/2012 19:49, Badru Ntege a écrit :<br>> Could it be that if it is not accepted in all regions it ceases to be a<br>> global policy and reverts to a regional policy. <br>> <br>> Or do we need a policy to handle this situation ?? <br>> <br>> maybe the policy should return to the PDP for review <br>> <br>> how is this handled in other regions ?? <br>> <br>>> -----Original Message-----<br>>> From: <a href="/mc/compose?to=rpd-bounces@afrinic.net">rpd-bounces@afrinic.net</a> [mailto:<a href="/mc/compose?to=rpd-bounces@afrinic.net">rpd-bounces@afrinic.net</a>] On Behalf<br>>> Of McTim<br>>> Sent: Tuesday, February 21, 2012 6:22 PM<br>>> To: Douglas Onyango<br>>> Cc: <a href="/mc/compose?to=rpd@afrinic.net">rpd@afrinic.net</a><br>>> Subject: Re: [AfriNIC-rpd] Call for policy proposals and/or issues on<br>> AfriNIC<br>>> PDP for AfriNIC-16<br>>><br>>> Hi Douglas,<br>>><br>>> On 2/21/12, Douglas Onyango <<a href="/mc/compose?to=ondouglas@gmail.com">ondouglas@gmail.com</a>> wrote:<br>>>> Paulos et al,<br>>>> I think there is a unique issue with the way our current PDP treats<br>>>> global policies after they get "approved" in our region and fail in<br>>>> other regions.<br>>>><br>>>> (afrinic.net/docs/policies/AFPUB-2009-v4-002.htm) is a prime example<br>>>> of what I am talking about. This Policy is marked "abandoned" on the<br>>>> ASO website (aso.icann.org/global-policy-proposals), but continues to<br>>>> have the status of "Approved" on the AfriNIC website.<br>>>><br>>><br>>> Probably because we approved it? ;-)<br>>><br>>>> I think that we should find away of resting these Global policies in a<br>>>> way that conforms to the Global PDP<br>>>><br>>>> A sample solution could be for the policy's status to change to<br>>>> "Expired" or something else if the Global status of the policy move in<br>>>> the "rejected" or "abandoned" direction.<br>>><br>>> "something else" I think, as policy proposals expire if they are not<br>> approved.<br>>><br>>><br>>> So we need to find a word that means "approved in region but not globally<br>>> accepted".<br>>><br>>> I admit that word is not coming to mind immediately ;-/<br>>><br>>>><br>>>> I haven't thought this through, but since you asked for suggestions<br>>>> and the like, I thought i would start this discussion.<br>>><br>>><br>>> Thanks!<br>>><br>>> --<br>>> Cheers,<br>>><br>>> McTim<br>>> "A name indicates what we seek. An address indicates where it is. A route<br>>> indicates how we get there." Jon Postel<br>>> _______________________________________________<br>>> rpd mailing list<br>>> <a href="/mc/compose?to=rpd@afrinic.net">rpd@afrinic.net</a><br>>> <a href="https://lists.afrinic.net/mailman/listinfo.cgi/rpd" target="_blank">https://lists.afrinic.net/mailman/listinfo.cgi/rpd</a><br>> <br>> _______________________________________________<br>> rpd mailing list<br>> <a href="/mc/compose?to=rpd@afrinic.net">rpd@afrinic.net</a><br>> <a href="https://lists.afrinic.net/mailman/listinfo.cgi/rpd" target="_blank">https://lists.afrinic.net/mailman/listinfo.cgi/rpd</a><br><br>- -- <br>Nacer Adamou Saïdou<br>LPC-1 Certified Engineer<br>Wave: <a href="/mc/compose?to=nacerix@waveinabox.net">nacerix@waveinabox.net</a><br>Blog: <a href="http://nacerix.blogspot.com" target="_blank">http://nacerix.blogspot.com</a><br>Twitter: nacerix<br>Identi.ca: nacerix<br><a href="http://paper.li/nacerix" target="_blank">http://paper.li/nacerix</a><br><a href="http://netvibes.net/nacerix" target="_blank">http://netvibes.net/nacerix</a><br><a href="https://launchpad.net/%7Eadamou-nacer" target="_blank">https://launchpad.net/~adamou-nacer</a><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.10 (GNU/Linux)<br><br>iQEcBAEBAgAGBQJPRKTkAAoJELZpU0pKyeBuq70H/Rhop6oSesL3ltzAjvupGlYJ<br>ntu1s2UF2EWiGd/IR2J4HKSIIsI/KOGRGuiCKjA7zqtnVjaw8l3T/KgteE0a7ZOl<br>BOGKRMUnn8gZ2Z2ZJJiawgQVwuTRwVSeHwcCYk3lOw38mYHraIQn1+Ro1Mi7Pkj9<br>nIX2ysBUt1OpAnvklKkNDnGu0PC9bDc88XyD7qyLytszGyzxcVmJggWrG/HeGtYG<br>pxxXbqrxhwu0MOH0yJYKh62tKMpdAnjfeUBZy/629PLHQFUB2KJtjuv6JpS15VFj<br>L+INFHJqlzVKAz69IYqOeI4Fjf53z7LmwezmT87TmLdTHqdyRU/an7PEn3bv+Ok=<br>=5W/s<br>-----END PGP SIGNATURE-----<br>_______________________________________________<br>rpd mailing list<br><a href="/mc/compose?to=rpd@afrinic.net">rpd@afrinic.net</a><br><a href="https://lists.afrinic.net/mailman/listinfo.cgi/rpd" target="_blank">https://lists.afrinic.net/mailman/listinfo.cgi/rpd</a><o:p></o:p></p></div></td></tr></table><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div></body></html>