<div dir="ltr">How much is ARIN going to get from the next round of IANA returned space distribution? It's more than a /16, isn't it?<div><br></div><div>-Scott</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 8, 2015 at 5:33 PM, David Farmer <span dir="ltr"><<a href="mailto:farmer@umn.edu" target="_blank">farmer@umn.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Now that we are on the other side of the Holidays, I would like to prompt a little more discussion of this Draft Policy.<br>
<br>
On PPML, there have been 2 clear statements of support, no opposition, a proposal to modify the policy text, primarily consisting of editorial changes for the broader section 4.4, and significant side discussion not directly related to the policy itself.<br>
<br>
As shepherd, I anticipate this policy going to the PPC in San Antonio at NANOG next month in its current state as a Draft policy. Then subsequent to and based on feedback from San Antonio, maybe making some minor changes, advancing this policy to Recommended Draft policy prior to the PPM in San Francisco in April. Assuming no opposition develops against the proposal.<br>
<br>
On the current trajectory for this proposal implementation is likely sometime in June, its entirely possible that the ARIN Free Pool would have run out before implementation of this policy can take place. There are several options to deal with this issue;<br>
<br>
1. Advance the policy to Recommended Draft prior to the PPC in San<br>
Antonio, moving likely implementation to sometime in April.<br>
<br>
2. Request that the Board instruct ARIN Staff to reserve a /16 in<br>
anticipation of this policy, imminently. With this option a<br>
reservation could reasonably occur in February or March with<br>
policy implementation on its current trajectory, likely June.<br>
<br>
3. Stay on the current trajectory, get IPv4 address space for the<br>
policy from returned or recovered space address space, and what<br>
little if any space is the the ARIN Free Pool at implementation,<br>
likely June. Its not likely there will be a single contiguous<br>
block, likely a hodgepodge of smaller blocks, and it may take a<br>
while to collect a /16 for the reservation.<br>
<br>
4. Do nothing, let events overtake the policy if they do, maybe<br>
abandoning the policy for lack of IPv4 address space late in the<br>
process.<br>
<br>
There are likely other variations on these themes.<br>
<br>
Regarding option #1: It might be possible to advance this proposal as-is to Recommended Draft prior to the PPC in San Antonio, at the January AC meeting. However, in order to justify recommending this to the AC, I will need to see significantly more support for this policy on PPML prior to the next AC meeting in two weeks. Even then it is likely not possible to advance the proposal prior to the PPC in San Antonio at this point, its less than a month away.<br>
<br>
I will raise option #2 with the AC at our meeting in two weeks. However, for this options to even be considered, I'm quite sure that both the AC and the Board will want to see significant community support on PPML before they would moving forward with such an option.<br>
<br>
I am interested to hear the community's opinions on the issue of this policy and the timing of ARIN Free Pool run out. Do you support any of the above options? Some other option?<br>
<br>
So, if you support this policy, and particularly if you think this policy should go to the PPC at NANOG in San Antonio in February as Recommended Draft policy please speak up ASAP.<br>
<br>
Do you have comments on or support the alternate text proposed in the email at this link?<br>
<a href="http://lists.arin.net/pipermail/arin-ppml/2014-December/029565.html" target="_blank">http://lists.arin.net/<u></u>pipermail/arin-ppml/2014-<u></u>December/029565.html</a><br>
<br>
Finally, if anyone opposes this policy it is important to speak up, as at this point no one has expressed any opposition to the policy at all.<br>
<br>
Thanks and I look forward to your comments.<div class="HOEnZb"><div class="h5"><br>
<br>
On 11/25/14 14:35 , ARIN wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 20 November 2014 the ARIN Advisory Council (AC) accepted<br>
"ARIN-prop-213 Modification to CI Pool Size per Section 4.4" as a Draft<br>
Policy.<br>
<br>
Draft Policy ARIN-2014-21 is below and can be found at:<br>
<a href="https://www.arin.net/policy/proposals/2014_21.html" target="_blank">https://www.arin.net/policy/<u></u>proposals/2014_21.html</a><br>
<br>
You are encouraged to discuss the merits and your concerns of Draft<br>
Policy 2014-21 on the Public Policy Mailing List.<br>
<br>
The AC will evaluate the discussion in order to assess the conformance<br>
of this draft policy with ARIN's Principles of Internet Number Resource<br>
Policy as stated in the PDP. Specifically, these principles are:<br>
<br>
* Enabling Fair and Impartial Number Resource Administration<br>
* Technically Sound<br>
* Supported by the Community<br>
<br>
The ARIN Policy Development Process (PDP) can be found at:<br>
<a href="https://www.arin.net/policy/pdp.html" target="_blank">https://www.arin.net/policy/<u></u>pdp.html</a><br>
<br>
Draft Policies and Proposals under discussion can be found at:<br>
<a href="https://www.arin.net/policy/proposals/index.html" target="_blank">https://www.arin.net/policy/<u></u>proposals/index.html</a><br>
<br>
Regards,<br>
<br>
Communications and Member Services<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
## * ##<br>
<br>
<br>
Draft Policy ARIN-2014-21<br>
Modification to CI Pool Size per Section 4.4<br>
<br>
Date: 25 November 2014<br>
<br>
Problem Statement:<br>
<br>
At the time that this section of policy was written, IXP growth in North<br>
America was stagnant. Efforts of late have increased significantly<br>
within the IXP standards and other communities to improve critical<br>
infrastructure in North America. This effort is paying dividends and we<br>
project that a /16 will not be enough to continue to improve global<br>
interconnect conditions and support needed IXP CI infrastructure.<br>
<br>
Policy statement:<br>
<br>
Change to text in section 4.4 Micro Allocations:<br>
<br>
Current text:<br>
<br>
ARIN will place an equivalent of a /16 of IPv4 address space in a<br>
reserve for Critical Infrastructure, as defined in section 4.4. If at<br>
the end of the policy term there is unused address space remaining in<br>
this pool, ARIN staff is authorized to utilize this space in a manner<br>
consistent with community expectations.<br>
<br>
Proposed text to replace current text entirely:<br>
<br>
ARIN will place an equivalent of a /15 of IPv4 address space in a<br>
reserve for Critical Infrastructure, as defined in section 4.4.<br>
<br>
Timetable for implementation: Immediate<br>
</blockquote>
<br>
<br></div></div><span class="im HOEnZb">
-- <br>
==============================<u></u>==================<br>
David Farmer Email: <a href="mailto:farmer@umn.edu" target="_blank">farmer@umn.edu</a><br>
Office of Information Technology<br>
University of Minnesota<br>
2218 University Ave SE Phone: <a href="tel:1-612-626-0815" value="+16126260815" target="_blank">1-612-626-0815</a><br>
Minneapolis, MN 55414-3029 Cell: <a href="tel:1-612-812-9952" value="+16128129952" target="_blank">1-612-812-9952</a><br>
==============================<u></u>==================<br></span><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/<u></u>listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</div></div></blockquote></div><br></div>