<p dir="ltr">I am in support of the draft policy...however, if David is correct, and I notice that John differs on that...re runout timescale, then<br>
options 3&4 do not look acceptable.</p>
<p dir="ltr">And the Dul modified text, does seem to add clarity ..certainly on my mind....But i have not seen any further comments on the modified draft.<br>
RD</p>
<div class="gmail_quote">On Jan 8, 2015 10:57 PM, <<a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send ARIN-PPML mailing list submissions to<br>
<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:arin-ppml-owner@arin.net">arin-ppml-owner@arin.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of ARIN-PPML digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Draft Policy ARIN-2014-21: Modification to CI Pool Size<br>
per Section 4.4 (David Farmer)<br>
2. Re: Draft Policy ARIN-2014-21: Modification to CI Pool Size<br>
per Section 4.4 (Scott Leibrand)<br>
3. Re: Draft Policy ARIN-2014-21: Modification to CI Pool Size<br>
per Section 4.4 (John Curran)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 08 Jan 2015 19:33:25 -0600<br>
From: David Farmer <<a href="mailto:farmer@umn.edu">farmer@umn.edu</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] Draft Policy ARIN-2014-21: Modification to CI<br>
Pool Size per Section 4.4<br>
Message-ID: <<a href="mailto:54AF2FE5.7030803@umn.edu">54AF2FE5.7030803@umn.edu</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
<br>
Now that we are on the other side of the Holidays, I would like to<br>
prompt a little more discussion of this Draft Policy.<br>
<br>
On PPML, there have been 2 clear statements of support, no opposition, a<br>
proposal to modify the policy text, primarily consisting of editorial<br>
changes for the broader section 4.4, and significant side discussion not<br>
directly related to the policy itself.<br>
<br>
As shepherd, I anticipate this policy going to the PPC in San Antonio at<br>
NANOG next month in its current state as a Draft policy. Then<br>
subsequent to and based on feedback from San Antonio, maybe making some<br>
minor changes, advancing this policy to Recommended Draft policy prior<br>
to the PPM in San Francisco in April. Assuming no opposition develops<br>
against the proposal.<br>
<br>
On the current trajectory for this proposal implementation is likely<br>
sometime in June, its entirely possible that the ARIN Free Pool would<br>
have run out before implementation of this policy can take place. There<br>
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<br>
to Recommended Draft prior to the PPC in San Antonio, at the January AC<br>
meeting. However, in order to justify recommending this to the AC, I<br>
will need to see significantly more support for this policy on PPML<br>
prior to the next AC meeting in two weeks. Even then it is likely not<br>
possible to advance the proposal prior to the PPC in San Antonio at this<br>
point, its less than a month away.<br>
<br>
I will raise option #2 with the AC at our meeting in two weeks.<br>
However, for this options to even be considered, I'm quite sure that<br>
both the AC and the Board will want to see significant community support<br>
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<br>
policy and the timing of ARIN Free Pool run out. Do you support any of<br>
the above options? Some other option?<br>
<br>
So, if you support this policy, and particularly if you think this<br>
policy should go to the PPC at NANOG in San Antonio in February as<br>
Recommended Draft policy please speak up ASAP.<br>
<br>
Do you have comments on or support the alternate text proposed in the<br>
email at this link?<br>
<a href="http://lists.arin.net/pipermail/arin-ppml/2014-December/029565.html" target="_blank">http://lists.arin.net/pipermail/arin-ppml/2014-December/029565.html</a><br>
<br>
Finally, if anyone opposes this policy it is important to speak up, as<br>
at this point no one has expressed any opposition to the policy at all.<br>
<br>
Thanks and I look forward to your comments.<br>
<br>
On 11/25/14 14:35 , ARIN wrote:<br>
> 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/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/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/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>
<br>
<br>
--<br>
================================================<br>
David Farmer Email: <a href="mailto:farmer@umn.edu">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">1-612-626-0815</a><br>
Minneapolis, MN 55414-3029 Cell: <a href="tel:1-612-812-9952" value="+16128129952">1-612-812-9952</a><br>
================================================<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 8 Jan 2015 17:50:57 -0800<br>
From: Scott Leibrand <<a href="mailto:scottleibrand@gmail.com">scottleibrand@gmail.com</a>><br>
To: David Farmer <<a href="mailto:farmer@umn.edu">farmer@umn.edu</a>><br>
Cc: ARIN-PPML List <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
Subject: Re: [arin-ppml] Draft Policy ARIN-2014-21: Modification to CI<br>
Pool Size per Section 4.4<br>
Message-ID:<br>
<CAGkMwz4EGR_YExYoUp7xxvSuQSUT40Eczzm8f5f2u9XeQs6=<a href="mailto:Gw@mail.gmail.com">Gw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
How much is ARIN going to get from the next round of IANA returned space<br>
distribution? It's more than a /16, isn't it?<br>
<br>
-Scott<br>
<br>
On Thu, Jan 8, 2015 at 5:33 PM, David Farmer <<a href="mailto:farmer@umn.edu">farmer@umn.edu</a>> wrote:<br>
<br>
> Now that we are on the other side of the Holidays, I would like to prompt<br>
> a little more discussion of this Draft Policy.<br>
><br>
> On PPML, there have been 2 clear statements of support, no opposition, a<br>
> proposal to modify the policy text, primarily consisting of editorial<br>
> changes for the broader section 4.4, and significant side discussion not<br>
> directly related to the policy itself.<br>
><br>
> As shepherd, I anticipate this policy going to the PPC in San Antonio at<br>
> NANOG next month in its current state as a Draft policy. Then subsequent<br>
> to and based on feedback from San Antonio, maybe making some minor changes,<br>
> advancing this policy to Recommended Draft policy prior to the PPM in San<br>
> Francisco in April. Assuming no opposition develops against the proposal.<br>
><br>
> On the current trajectory for this proposal implementation is likely<br>
> sometime in June, its entirely possible that the ARIN Free Pool would have<br>
> run out before implementation of this policy can take place. There are<br>
> 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<br>
> to Recommended Draft prior to the PPC in San Antonio, at the January AC<br>
> meeting. However, in order to justify recommending this to the AC, I will<br>
> need to see significantly more support for this policy on PPML prior to the<br>
> next AC meeting in two weeks. Even then it is likely not possible to<br>
> advance the proposal prior to the PPC in San Antonio at this point, its<br>
> less than a month away.<br>
><br>
> I will raise option #2 with the AC at our meeting in two weeks. However,<br>
> for this options to even be considered, I'm quite sure that both the AC and<br>
> the Board will want to see significant community support on PPML before<br>
> they would moving forward with such an option.<br>
><br>
> I am interested to hear the community's opinions on the issue of this<br>
> policy and the timing of ARIN Free Pool run out. Do you support any of the<br>
> above options? Some other option?<br>
><br>
> So, if you support this policy, and particularly if you think this policy<br>
> should go to the PPC at NANOG in San Antonio in February as Recommended<br>
> Draft policy please speak up ASAP.<br>
><br>
> Do you have comments on or support the alternate text proposed in the<br>
> email at this link?<br>
> <a href="http://lists.arin.net/pipermail/arin-ppml/2014-December/029565.html" target="_blank">http://lists.arin.net/pipermail/arin-ppml/2014-December/029565.html</a><br>
><br>
> Finally, if anyone opposes this policy it is important to speak up, as at<br>
> this point no one has expressed any opposition to the policy at all.<br>
><br>
> Thanks and I look forward to your comments.<br>
><br>
><br>
> On 11/25/14 14:35 , ARIN wrote:<br>
><br>
>> 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/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/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/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>
>><br>
><br>
><br>
> --<br>
> ================================================<br>
> David Farmer Email: <a href="mailto:farmer@umn.edu">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">1-612-626-0815</a><br>
> Minneapolis, MN 55414-3029 Cell: <a href="tel:1-612-812-9952" value="+16128129952">1-612-812-9952</a><br>
> ================================================<br>
> _______________________________________________<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">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/listinfo/arin-ppml</a><br>
> Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20150108/3c1f5196/attachment-0001.html" target="_blank">http://lists.arin.net/pipermail/arin-ppml/attachments/20150108/3c1f5196/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 9 Jan 2015 02:56:56 +0000<br>
From: John Curran <<a href="mailto:jcurran@arin.net">jcurran@arin.net</a>><br>
To: Scott Leibrand <<a href="mailto:scottleibrand@gmail.com">scottleibrand@gmail.com</a>><br>
Cc: ARIN-PPML List <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
Subject: Re: [arin-ppml] Draft Policy ARIN-2014-21: Modification to CI<br>
Pool Size per Section 4.4<br>
Message-ID: <<a href="mailto:15B8BAFA-64E6-4535-9163-529162D1736F@corp.arin.net">15B8BAFA-64E6-4535-9163-529162D1736F@corp.arin.net</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
On Jan 8, 2015, at 5:50 PM, Scott Leibrand <<a href="mailto:scottleibrand@gmail.com">scottleibrand@gmail.com</a>> wrote:<br>
><br>
> 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?<br>
<br>
Per the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA,<br>
the allocation size technically is set based on the recovered pool size at the time of<br>
the next allocation (1 March 2015). If I recall correctly, the estimate is that each RIR<br>
will receive IPv4 space equivalent to a /12 block on that date.<br>
<br>
FYI,<br>
/John<br>
<br>
John Curran<br>
President and CEO<br>
ARIN<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
ARIN-PPML mailing list<br>
<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
<br>
End of ARIN-PPML Digest, Vol 115, Issue 2<br>
*****************************************<br>
</blockquote></div>