[151306] in North American Network Operators' Group
Re: shared address space... a reality!
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Thu Mar 15 11:39:08 2012
In-Reply-To: <86B7574E-7917-45C0-8B79-F5EE8C969C79@corp.arin.net>
Date: Thu, 15 Mar 2012 11:38:03 -0400
From: Christopher Morrow <morrowc.lists@gmail.com>
To: John Curran <jcurran@arin.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Thu, Mar 15, 2012 at 11:34 AM, John Curran <jcurran@arin.net> wrote:
> On Mar 14, 2012, at 6:54 PM, Christopher Morrow wrote:
>>
>> thanks! history is important here.
>
reading this this morning, my comment sounds more flippant than I
meant. I really did mean that getting the details right was important.
> Policy proposals for "specialized technical allocations"
> are best considered by the IETF. =A0ARIN was aware of the
> RFC 2860 (the MOU between ICANN and the IAB) which said
> as much, and once we confirmed this understanding with
> the IAB, ARIN directed the community to make use of the
> IETF process to develop an appropriate RFC for an IANA
> assignment.
>
> ARIN was notified by the IANA that the RFC was approved
> and was asked if we could assign sufficient resources to
> them for this purpose. =A0The ARIN Board approved assigning
> back to the IANA a /10 block out of one of the /8's we
> received from them in 2010. =A0The IANA registry has been
> now updated accordingly: http://www.iana.org/assignments/ipv4-address-spa=
ce/ipv4-address-space.xml#note5
>
> Thanks! (and hope this clarifies things)
does, thanks!
>
> John Curran
> President and CEO
> ARIN
>
>
>
>
>
>
>
