<p dir="ltr">Hi Kivuva,</p>
<p dir="ltr">The process to updating/creating existing/new policies of our region is documented in the AfriNIC policy development process.</p>
<p dir="ltr"><a href="http://www.afrinic.net/en/community/policy-development">http://www.afrinic.net/en/community/policy-development</a></p>
<p dir="ltr">Regards<br>
Sent from my Asus Zenfone2<br>
Kindly excuse brevity and typos.</p>
<div class="gmail_quote">On 13 Sep 2015 13:41, "Mwendwa Kivuva" <<a href="mailto:Kivuva@transworldafrica.com">Kivuva@transworldafrica.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Thanks Seun.</p>
<p dir="ltr">It seems after APNIC and RIPE-NCC change their policy to remove the multihoming requirement for ASN request, the only region to remain with this policy will be AFRINIC. Is there any process to align our policy with the other 4 RIRs? Is it necessary to follow suite?</p>
<p dir="ltr">Regards</p>
<div class="gmail_quote">On Sep 13, 2015 10:02 AM, "Seun Ojedeji" <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hello,</p>
<p dir="ltr">This apnic policy proposal is currently in what we know as "last call" in AfriNIC. It proposes to remove multihoming requirement for ASN request. This is currently required for our region.</p>
<p dir="ltr">Regards</p>
<p dir="ltr">Sent from my Asus Zenfone2<br>
Kindly excuse brevity and typos.</p>
<div class="gmail_quote">---------- Forwarded message ----------<br>From: "Masato Yamanishi" <<a href="mailto:myamanis@gmail.com" target="_blank">myamanis@gmail.com</a>><br>Date: 12 Sep 2015 16:27<br>Subject: [sig-policy] Final Comment Period for prop-114: Modification in the ASN eligibility criteria<br>To: "<a href="mailto:sig-policy@lists.apnic.net" target="_blank">sig-policy@lists.apnic.net</a>" <<a href="mailto:sig-policy@lists.apnic.net" target="_blank">sig-policy@lists.apnic.net</a>><br>Cc: <br><br type="attribution"><div dir="ltr"><span style="font-size:14px">Dear colleagues</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">Version 3 of prop-114: Modification in the ASN eligibility criteria,</span><br style="font-size:14px"><span style="font-size:14px">reached consensus at the APNIC 40 Open Policy Meeting and later at the</span><br style="font-size:14px"><span style="font-size:14px">APNIC Member Meeting (AMM).</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">This proposal will now move to the next step in the APNIC Policy</span><br style="font-size:14px"><span style="font-size:14px">Development Process and is being returned to the Policy SIG mailing list</span><br style="font-size:14px"><span style="font-size:14px">for the final Comment Period.</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">At the end of this period the Policy SIG Chairs will evaluate comments</span><br style="font-size:14px"><span style="font-size:14px">made and determine if the consensus reached at APNIC 40 still holds. The</span><br style="font-size:14px"><span style="font-size:14px">Chairs may extend the Comment Period to a maximum of eight (8) weeks to</span><br style="font-size:14px"><span style="font-size:14px">allow further discussion.</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">If consensus holds, the Chair of the Policy SIG will ask the Executive</span><br style="font-size:14px"><span style="font-size:14px">Council to endorse the proposal for implementation.</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px"> - Send all comments and questions to: <sig-policy at apnic dot net></span><br style="font-size:14px"><span style="font-size:14px"> - Deadline for comments: 23:59 (UTC +10) Sunday, 11 October 2015</span><br style="font-size:14px"><br style="font-size:14px"><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">Proposal details</span><br style="font-size:14px"><span style="font-size:14px">----------------</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">This is a proposal changes the criteria for AS number requests from</span><br style="font-size:14px"><span style="font-size:14px">end-user organizations considering multihoming.</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">Proposal details, including the full text of the proposal, history, and</span><br style="font-size:14px"><span style="font-size:14px">links to the APNIC 40 meeting archive, are available at:</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px"> </span><a href="http://www.apnic.net/policy/proposals/prop-114" rel="noreferrer" style="font-size:14px" target="_blank">http://www.apnic.net/policy/proposals/prop-114</a><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">Regards</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">Masato and Sumon</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">------------------------------</span><span style="font-size:14px">-----------------------------</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">prop-114-v003: Modification in the ASN eligibility criteria</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">------------------------------</span><span style="font-size:14px">-----------------------------</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">Proposer: Aftab Siddiqui</span><br style="font-size:14px"><span style="font-size:14px"> </span><a href="mailto:aftab.siddiqui@gmail.com" style="font-size:14px" target="_blank">aftab.siddiqui@gmail.com</a><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px"> Skeeve Stevens</span><br style="font-size:14px"><span style="font-size:14px"> </span><a href="mailto:skeeve@eintellegonetworks.com" style="font-size:14px" target="_blank">skeeve@eintellegonetworks.com</a><br style="font-size:14px"><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">1. Problem statement</span><br style="font-size:14px"><span style="font-size:14px">--------------------</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px"> The current ASN assignment policy states two eligibility criteria and</span><br style="font-size:14px"><span style="font-size:14px"> that both criteria should be fulfilled in order to obtain an ASN. The</span><br style="font-size:14px"><span style="font-size:14px"> policy seems to imply that both requirements i.e. multi-homing and</span><br style="font-size:14px"><span style="font-size:14px"> clearly defined single routing policy must be met simultaneously,</span><br style="font-size:14px"><span style="font-size:14px"> this has created much confusion in interpreting the policy.</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px"> As a result organizations have either provided incorrect information</span><br style="font-size:14px"><span style="font-size:14px"> to get the ASN or barred themselves from applying where they still</span><br style="font-size:14px"><span style="font-size:14px"> have a valid justification for obtaining an ASN.</span><br style="font-size:14px"><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">2. Objective of policy change</span><br style="font-size:14px"><span style="font-size:14px">-----------------------------</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px"> In order to make the policy guidelines simpler we are proposing to</span><br style="font-size:14px"><span style="font-size:14px"> modify the text describing the eligibility criteria for ASN</span><br style="font-size:14px"><span style="font-size:14px"> assignment by providing alternate criteria to obtaining an ASN.</span><br style="font-size:14px"><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">3. Situation in other regions</span><br style="font-size:14px"><span style="font-size:14px">-----------------------------</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">ARIN:</span><br style="font-size:14px"><span style="font-size:14px"> It is not mandatory but optional to be multi-homed in order get ASN</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">RIPE:</span><br style="font-size:14px"><span style="font-size:14px"> Policy to remove multi-homing requirement is currently in discussion</span><br style="font-size:14px"><span style="font-size:14px"> and the current phase ends 12 February 2015 (awaiting Chair decision)</span><br style="font-size:14px"><span style="font-size:14px"> Policy - </span><a href="https://www.ripe.net/ripe/policies/proposals/2014-03" rel="noreferrer" style="font-size:14px" target="_blank">https://www.ripe.net/ripe/policies/proposals/2014-03</a><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">LACNIC:</span><br style="font-size:14px"><span style="font-size:14px"> Only inter-connect is mandatory not multi-homing</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">AFRINIC:</span><br style="font-size:14px"><span style="font-size:14px"> It is mandatory to be multi-homed in order to get ASN.</span><br style="font-size:14px"><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">4. Proposed policy solution</span><br style="font-size:14px"><span style="font-size:14px">---------------------------</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">An organisation is eligible for an ASN assignment if:</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px"> - they are currently multi-homed, OR</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px"> - have previous allocated provider independent address space by</span><br style="font-size:14px"><span style="font-size:14px"> APNIC, AND intend to multi-home in the future</span><br style="font-size:14px"><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">5. Advantages / Disadvantages</span><br style="font-size:14px"><span style="font-size:14px">-----------------------------</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">Advantages:</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px"> By adding the additional criteria of Guidelines managed by APNIC</span><br style="font-size:14px"><span style="font-size:14px"> Secretariat, this would enable the Secretariat to make decisions</span><br style="font-size:14px"><span style="font-size:14px"> based on common or rare use cases, but that may still be a valid</span><br style="font-size:14px"><span style="font-size:14px"> request.</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">Disadvantages:</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px"> It may be perceived that this policy would enable members to obtain</span><br style="font-size:14px"><span style="font-size:14px"> ASN’s more easily, and in return cause faster consumption of ASN’s</span><br style="font-size:14px"><span style="font-size:14px"> in the region. Given the relative ease of obtaining an ASN with</span><br style="font-size:14px"><span style="font-size:14px"> ‘work around’ methods, we do not perceive this will actually have</span><br style="font-size:14px"><span style="font-size:14px"> any effect.</span><br style="font-size:14px"><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px">6. Impact on resource holders</span><br style="font-size:14px"><span style="font-size:14px">-----------------------------</span><br style="font-size:14px"><br style="font-size:14px"><span style="font-size:14px"> No impact on existing resource holders.</span><br style="font-size:14px"><br style="font-size:14px"></div>
<br>* sig-policy: APNIC SIG on resource management policy *<br>
_______________________________________________<br>
sig-policy mailing list<br>
<a href="mailto:sig-policy@lists.apnic.net" target="_blank">sig-policy@lists.apnic.net</a><br>
<a href="http://mailman.apnic.net/mailman/listinfo/sig-policy" rel="noreferrer" target="_blank">http://mailman.apnic.net/mailman/listinfo/sig-policy</a><br>
<br></div>
<br>_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
<br></blockquote></div>
</blockquote></div>