<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>++1<br><br>Serge ILUNGA KABWIKA<div>Skype: sergekbk</div><div>Cell: +243814443160</div></div><div><br>Le 6 nov. 2014 à 17:18, nico tshintu <<a href="mailto:bakajika@yahoo.fr">bakajika@yahoo.fr</a>> a écrit :<br><br></div><blockquote type="cite"><div><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1415271945193_78588">Hello All,</div><div id="yui_3_16_0_1_1415271945193_79085"><br></div><div id="yui_3_16_0_1_1415271945193_79084">I support this proposal</div><div id="yui_3_16_0_1_1415271945193_78586"> </div><div id="yui_3_16_0_1_1415271945193_78390" class="signature"><br>Nico TSHINTU BAKAJIKA <br>Tél: 243 818149372</div> <div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"> <font face="Arial" size="2"> Le Mardi 4 novembre 2014 9h19, Fiona Asonga <<a href="mailto:tespok@tespok.co.ke">tespok@tespok.co.ke</a>> a écrit :<br> </font> </div> <br><br> <div class="y_msg_container">Hallo All<br clear="none"><br clear="none">Based on our experience at KIXP and growth strategy moving forward. I support the proposal as it allows room for the IXPs to grow with minimum challenges on management of their allocation space.<br clear="none"><br clear="none">Kind regards<br clear="none"><br clear="none">Fiona Asonga <br clear="none"><br clear="none">Chief Executive Officer <br clear="none"><br clear="none">Telecommunications Service Providers Association of Kenya/ Kenya Internet Exchange Point <br clear="none"><br clear="none">Member Strategic Committee of the Africa Computer Emergency Response Team <br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none">NRO Number Council <a shape="rect" href="http://www.nro.net/about/number-council.html" target="_blank">http://www.nro.net/about/number-council.html </a><br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none">ASO Address Council <a shape="rect" href="http://aso.icann.org/ac/" target="_blank">http://aso.icann.org/ac/ </a><br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none">14 th Floor, Bruce House <br clear="none"><br clear="none">Standard Street <br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none">Tel: +254 20 2245 036 <br clear="none"><br clear="none">Cell: +254 721 713 504 <br clear="none"><br clear="none">Website: <a href="http://www.tespok.or.ke">www.tespok.or.ke</a> <br clear="none">----- Original Message -----<br clear="none">From: "Frank Habicht" <<a shape="rect" ymailto="mailto:geier@geier.ne.tz" href="mailto:geier@geier.ne.tz">geier@geier.ne.tz</a>><br clear="none">To: "rpd" <<a shape="rect" ymailto="mailto:rpd@afrinic.net" href="mailto:rpd@afrinic.net">rpd@afrinic.net</a>><br clear="none">Cc: "Nishal Goburdhan" <<a shape="rect" ymailto="mailto:nishal@ispa.org.za" href="mailto:nishal@ispa.org.za">nishal@ispa.org.za</a>><br clear="none">Sent: Wednesday, October 29, 2014 7:31:37 PM<br clear="none">Subject: [rpd] proposed policy: reservation of resources for IXPs<br clear="none"><br clear="none">Hello all,<br clear="none"><br clear="none">please find this proposed policy, which we (3 co-authors) have submitted to<br clear="none">the pdpwg last week:<br clear="none"><br clear="none">Resource Reservation for Internet Exchange Points<br clear="none"><br clear="none">Author(s):<br clear="none">a) Frank Habicht, Tanzania Internet Exchange<br clear="none">b) Michuki Mwangi, Internet Society/KIXP<br clear="none">c) Nishal Goburdhan, Packet Clearing House/JINX<br clear="none"><br clear="none">1) Summary of the Problem being addressed by this proposal<br clear="none"><br clear="none">This policy reserves IPv4 and 2-byte ASNs resources for public Internet<br clear="none">Exchange Points (IXPs) in the African region, ensuring that there would be<br clear="none">discrete IPv4 resources to allow the establishment and growth of future IXPs.<br clear="none"><br clear="none"><br clear="none">2) Summary of How this Proposal Addresses the Problem<br clear="none"><br clear="none">This policy requests AfriNIC to reserve, and publish IPv4 resources, and<br clear="none">2-byte ASNs for use by IXPs only.<br clear="none"><br clear="none"><br clear="none">3) Proposal<br clear="none"><br clear="none">3.1 Introduction<br clear="none"><br clear="none">It is widely considered that Internet Exchange Points (IXPs) are one of the<br clear="none">critical elements needed for Internet economies to develop. Africa is still<br clear="none">in the process of developing these, and is, at the same time, faced with<br clear="none">the imminent exhaustion of its IPv4 resources. Not having IPv4 addresses to<br clear="none">grow, or start new, IXPs would create unnecessary and unneeded routing<br clear="none">complexity for Internet connected networks, looking to peer at IXPs to<br clear="none">further their network scope. AfriNIC already has an existing policy to make<br clear="none">allocations to IXPs [1], but that policy does not specifically reserve IPV4<br clear="none">space to ensure that there will be such, for future IXPs to grow and<br clear="none">develop. Additionally, this policy reserves a set of 2-byte ASNs for use by<br clear="none">IXPs for use at IXP BGP Route Servers.<br clear="none"><br clear="none"><br clear="none">3.2 Distinction between IXP peering and management networks<br clear="none"><br clear="none">We distinguish between two kinds of IP address resources needed and used at<br clear="none">IXPs. An IXP peering LAN is the contiguous network address block that the<br clear="none">IXP would use to assign unique IP addresses to each peering member, for<br clear="none">each peering participant to exchange network traffic across the shared<br clear="none">peering infrastructure. Best practice has the IXP peering LAN *not* being<br clear="none">visible in a view of the global routing table, among other things to reduce<br clear="none">the attack vectors for ISP border routers via the IXP.<br clear="none"><br clear="none">>From a network identification, monitoring and analysis perspective, it is<br clear="none">thus desirable, that the "peering LAN" space be provided from a contiguous<br clear="none">block. The IXP management LAN is the management network that the IXP uses<br clear="none">to provision services at the IXP, like monitoring, statistics, mail, ticket<br clear="none">systems, provisioning of transit to DNS Roots, etc.<br clear="none"><br clear="none">Management networks, are meant to be reachable globally, for instance to<br clear="none">publish data and allow remote access for common good network infrastructure<br clear="none">(such as root and TLD DNS servers) and research projects.<br clear="none"><br clear="none"><br clear="none">3.3 BGP Route Servers use<br clear="none"><br clear="none">Typically IXPs use BGP route servers to help manage peering sessions<br clear="none">between different participants. The route servers implement IXP routing<br clear="none">policy in the form of BGP communities, typically in the form of A:B, where<br clear="none">A,B represent A=IXP BGP route server and B=participant ASN. Current BGP<br clear="none">implementations utilise 6 bytes for the extended community attribute<br clear="none">[RFC5668]. Therefore, an IXP with a 4-byte ASN in use at its route server<br clear="none">would not be able to successfully implement the A:B BGP community mapping,<br clear="none">if an IXP participant has a 4-byte ASN. This situation is likely to be<br clear="none">experienced by more IXPs, as additional 4-byte ASNs are allocated through<br clear="none">the current AfriNIC process.<br clear="none"><br clear="none">If, IXP route server communities include the IXP ASN and the peer's ASN<br clear="none">(expected to be 4-byte), and a total of only 6 bytes are available, it<br clear="none">follows that IXP route servers ASN could not be longer than a 2-byte ASN.<br clear="none"><br clear="none"><br clear="none">3.4 Proposal<br clear="none"><br clear="none">To ensure that there are sufficient resources for IXPs to develop, this<br clear="none">policy proposes that AfriNIC reserve IPv4 addresses for IXP peering LANs<br clear="none">out of an address block marked particularly, and exclusively, for IXP<br clear="none">peering LAN use. Assignments for IXP peering LANs must be from one<br clear="none">dedicated block, published as such by AfriNIC. Assignments for IXP<br clear="none">management addresses should NOT be provided from the same block as the IXP<br clear="none">peering LANs.<br clear="none"><br clear="none">It is proposed that a /16 block be reserved for future requirements for IXP<br clear="none">peering LANs in the AfriNIC service region, and that AfriNIC publish this<br clear="none">block as such.<br clear="none"><br clear="none">It is further proposed to reserve the equivalent of an additional /16 block<br clear="none">for IXP management prefixes, separate from the peering LANs. It is proposed<br clear="none">that AfriNIC reserves a block of 2-byte ASNs for use in BGP route servers<br clear="none">at IXPs in the AfriNIC service region.<br clear="none"><br clear="none">The number of ASNs to be reserved should be the larger of 114, or half of<br clear="none">the remaining 2-byte ASNs within AfriNIC's block at the date of<br clear="none">ratification of this policy.<br clear="none"><br clear="none">AfriNIC will allocate these resources on a first come first served basis.<br clear="none"><br clear="none"><br clear="none">3.5 Evaluation criteria<br clear="none"><br clear="none">This policy does not suggest new evaluation criteria for what determines a<br clear="none">valid IXP.<br clear="none"><br clear="none"><br clear="none">4.0 References<br clear="none"><br clear="none">[1] AfriNIC Policy for End User Assignments - AFPUB-2006-GEN-001<br clear="none"><a shape="rect" href="http://afrinic.net/en/library/policies/127-afpub-2006-gen-001" target="_blank">http://afrinic.net/en/library/policies/127-afpub-2006-gen-001 </a>Sections 5)<br clear="none">and 6)<br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none">Note: proposal also available at<br clear="none"><a shape="rect" href="http://www.afrinic.net/en/community/policy-development/policy-proposals/1231-resource-reservation-for-internet-exchange-points" target="_blank">http://www.afrinic.net/en/community/policy-development/policy-proposals/1231-resource-reservation-for-internet-exchange-points</a><br clear="none"><br clear="none"><br clear="none">Regards,<br clear="none">Frank<br clear="none">_______________________________________________<br clear="none">rpd mailing list<br clear="none"><a shape="rect" ymailto="mailto:rpd@afrinic.net" href="mailto:rpd@afrinic.net">rpd@afrinic.net</a><br clear="none"><a shape="rect" href="https://lists.afrinic.net/mailman/listinfo.cgi/rpd" target="_blank">https://lists.afrinic.net/mailman/listinfo.cgi/rpd</a><div class="yqt7460953340" id="yqtfd88757"><br clear="none">_______________________________________________<br clear="none">rpd mailing list<br clear="none"><a shape="rect" ymailto="mailto:rpd@afrinic.net" href="mailto:rpd@afrinic.net">rpd@afrinic.net</a><br clear="none"><a shape="rect" href="https://lists.afrinic.net/mailman/listinfo.cgi/rpd" target="_blank">https://lists.afrinic.net/mailman/listinfo.cgi/rpd</a><br clear="none"></div><br><br></div> </div> </div> </div> </div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>rpd mailing list</span><br><span><a href="mailto:rpd@afrinic.net">rpd@afrinic.net</a></span><br><span><a href="https://lists.afrinic.net/mailman/listinfo.cgi/rpd">https://lists.afrinic.net/mailman/listinfo.cgi/rpd</a></span><br></div></blockquote></body></html>