<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 http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:321012979;
mso-list-type:hybrid;
mso-list-template-ids:-119127554 1865035836 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-upper;
mso-level-text:"%1\.\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1549338422;
mso-list-type:hybrid;
mso-list-template-ids:-1090605856 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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=EN-US link=blue vlink=purple style='WORD-WRAP: break-word'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As I’ve stated in previous emails, I still believe that we
should probably stay in line with what the other regions are doing here in
order to avoid complications and different filtering systems globally to make
the P.I space work.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>That is, a single block out of which allocations of /48 are made
as a minimum. That way, a single prefix list could be applied on an ISP’s
bgp peers that basically says (cisco syntax here, though its simply an
illustration of principle)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Permit aaaa:aaaa::/yy le 48<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>permit xxxx:xxxx::/yy le 48 <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>permit zzzz:zzzz::/yy le 48<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>permit ::/0 le 32<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Where A X and Z are the pre-defined P.I blocks from the various
regions, everything else that’s in the tables that smaller in size than a
/32 gets dumped. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If we then decide to allocate these /48s on /44 boundaries so
that organizations can grow (/44 being what I would consider a reasonable
boundary for growth of individual companies) it would allow for companies to
grow and add more /48s without growing the routing table because the blocks
would be contiguous. If AfriNIC were to allocate a /28 for this purpose it
allows for 2^16 (65536) P.I /44 blocks, which should last a fairly long time, and
if it becomes necessary to grow this, its just a matter of adding another /28
prefix to the prefix list to expand the P.I space. We could even allocate
that /28 on a /26 boundary for safety!<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This at the end of the day covers most of the aspects,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>A.)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It provides P.I space (which there seems to be consensus on from
what I’m reading)<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>B.)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It provides enough space that the blocks can be expanded for
institutions who have P.I space up to a /44, which, providing institutions are
using a /48 per physical site would give them up to 16 physical sites (as an
example, they could break /48s across multiple physical sites as well)<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>C.)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It provides enough space for the allocations of these P.I blocks
without needing extensive filter lists on routers for the P.I prefix blocks and
allows for the differentiation of P.I blocks versus P.A blocks by simply
looking at the block the space was assigned out of. (This becomes even more
obvious an advantage if the P.I allocation block is initially published on a
/28 boundary but with a /26 reserved by AfriNIC incase of need)<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>D.)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In the case of point B.) due to the fact that sites can grow
their blocks on a contiguous basis, it prevents massive growth in the routing
table<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Just my thoughts, curious to hear what the disagreements with
this are.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Andrew Alston<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>TENET – Chief Technology Officer<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> rpd-bounces@afrinic.net
[mailto:rpd-bounces@afrinic.net] <b>On Behalf Of </b>Hytham EL Nakhal<br>
<b>Sent:</b> Tuesday, March 13, 2007 6:55 PM<br>
<b>To:</b> AfriNIC Resource Policy Discussion List<br>
<b>Subject:</b> RE: [AfriNIC-rpd] Re: [resource-policy] AfriNIC Policy
Proposal: IPv6ProviderIndependent (PI) Assignment for End-Sites<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div id=idOWAReplyText47537>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif"'>Dear Vincent,</span><o:p></o:p></p>
</div>
<p><span style='font-family:"Arial","sans-serif"'>I'd like to discuss
something may be get benefits of all suggestions regarding PI assignment, What
about dedicating a /32 for PI assignments, and each PI is /48 , so we have 2 to
the power 16 PI assignments (i.e. 65536 /48 PI blocks). AfriNIC provide services
for Africa Continent which contains about 55 countries. So if we divide PI
blocks equally over countries we find that each country will have more than
1190 PI blocks, "Is it enough for each country" ? to know the answer
we can have a look on the number of IPv4 PI assignments for each country in
database (keeping in mind that /48 IPv6 block has addresses more more than /24
IPv4). </span><o:p></o:p></p>
<p><span style='font-family:"Arial","sans-serif"'>Then we can make all /48 PI
assignments from a dedicated /32 block and in same time we can arrange for a
serial /48 blocks for each country and inside each country we can keep a guard
band for each PI assignment in case of future growth. </span><o:p></o:p></p>
<p> <o:p></o:p></p>
<p><span style='font-family:"Arial","sans-serif"'>Thanks,</span><o:p></o:p></p>
<p><span style='font-family:"Arial","sans-serif"'>Haitham..</span><o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> rpd-bounces@afrinic.net on behalf of
Vincent Ngundi<br>
<b>Sent:</b> Tue 3/13/2007 3:51 PM<br>
<b>To:</b> Resource Policy Discussion List<br>
<b>Cc:</b> AfriNIC Policy Working Group List<br>
<b>Subject:</b> [AfriNIC-rpd] Re: [resource-policy] AfriNIC Policy Proposal:
IPv6ProviderIndependent (PI) Assignment for End-Sites</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Hi All, <o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Below is a summary of the above policy as per the
discussions we have had so far.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><b>So far, we have the following arguments:</b><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>(a) Andrew Levin <span class=apple-tab-span> </span>(30.01.2007)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>proposed that we should not assign prefixes < /48 due to
concerns about the global routing table<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>(b) Frank Habitcht <span class=apple-tab-span> </span>(30.01.2007)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>was in agreement that there was need for PI assignments <
/48 especially in the case of IXP's since the prefix would not appear in the
global routing table.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>(c) Mark Elkins<span class=apple-tab-span> </span>(01.02.2007)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Suggested that each /48 assignment should be made from a
unique /32 (which should be preserved to accommodate growth)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><b>From the above points:</b><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>(b) above seems to have outweighed (a) above and as such we
should allow for the assignment prefixes < /48 as per the draft.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>as for (c) above, organisations which require >= /32
should become an LIR.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>In conclusion, it seems that the draft policy should remain
as it is.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><b>Currently statistics:</b><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>* Yea (those in support of the policy)<span
class=apple-tab-span> </span>:<span class=apple-tab-span> </span>6<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>* Nay (those _not in support of the policy)<span
class=apple-tab-span> </span>:<span class=apple-tab-span> </span>1<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Finally, I wish to encourage more members of the community
to give their views on this policy, or at least indicate whether they are in
favour of it or not.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Abuja is only 5 weeks away!<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>-v<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>On Jan 30, 2007, at 11:22 AM, Andrew Alston wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>Hi Vincent,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>I’m ok with all of this except for the following:</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>*
The intial provider independent assignment size to an end-site should be a /48,
or a shorter/longer prefix if the end-site can justify it.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt'>I’m happy with /48s, I’m even happier with
bigger blocks, but there should *<b>NEVER</b>* be a situation where the block
is smaller than this in the global routing tables. If the blocks can ever
be smaller than /48 in size it is going to create major BGP filtering
headaches.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt'>Can this wording be clarified?</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt'>Many Thanks</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt'>Andrew Alston</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt'>TENET – Chief Technology Officer</span><o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal>_______________________________________________<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>resource-policy mailing list<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><a href="mailto:resource-policy@afrinic.net">resource-policy@afrinic.net</a><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><a
href="https://lists.afrinic.net/mailman/listinfo.cgi/resource-policy">https://lists.afrinic.net/mailman/listinfo.cgi/resource-policy</a><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>