[arin-ppml] ARIN-prop-154 Shared Space for IPv4 Address Extension (w/IETF considerations)

Owen DeLong owen at delong.com
Tue Jul 5 15:55:37 EDT 2011

On Jul 4, 2011, at 11:37 AM, John Curran wrote:

> On Jul 4, 2011, at 8:14 PM, William Herrin wrote:
>> On Mon, Jul 4, 2011 at 12:20 PM, John Curran <jcurran at arin.net> wrote:
>>> On Jul 4, 2011, at 12:26 PM, William Herrin wrote:
>>>> Yes, I understand your interpretation of the matter. You recommend we
>>>> punt back to the IETF and let them run with the ball for a while. And
>>>> if someone else would like to write a proposal that ARIN play lap dog
>>>> to the IETF on prop 2011-5, I'm sure I can find it within myself not
>>>> to invent process grounds for objecting.
>>> Bill - RFC2860 indicates that the IETF should establish the criteria
>>> and procedures for a reservation of the type proposed in Draft Policy
>>> 2011-5.
>> John,
>> Prop 154 indicates the same. That's what makes it different from
>> 2011-5. But 154 also facilitates ARIN constituents' operation for the
>> three years it's going to take the IETF to work through the
>> procedures.
> ARIN-prop-154 directs ARIN to perform that allocation, whereas RFC 2860
> indicates that should be performed by the IANA in accordance with the 
> criteria and procedures established by the IETF.

I read 154 differently. To me, 154 directs ARIN to set aside a /10
reservation to be subsequently allocated, but, does not allocate it until
the IETF addresses the situation and publishes an appropriate RFC.

It specifically discourages ARIN constituents from using the address space
until such time as the IETF publishes an RFC and ARIN completes the


More information about the ARIN-PPML mailing list