[104901] in North American Network Operators' Group
Re: New ID: Special Use IPv4 Addresses
daemon@ATHENA.MIT.EDU (Sean Donelan)
Thu May 29 19:25:50 2008
Date: Thu, 29 May 2008 19:24:40 -0400 (EDT)
From: Sean Donelan <sean@donelan.com>
To: Jonathan Heinlein <jonathanheinlein@gmail.com>
In-Reply-To: <bea7d74a0805291539p5700cbb7yed5b941c40743c0@mail.gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
The header was corrected an hour or so after my original message, and
a revised internet-draft (02) was published.
On Thu, 29 May 2008, Jonathan Heinlein wrote:
> Link change?
>
> http://www.ietf.org/internet-drafts/draft-iana-rfc3330bis-02.txt
>
> On Wed, May 28, 2008 at 3:12 PM, Sean Donelan <sean@donelan.com> wrote:
>
>>
>> http://www.ietf.org/internet-drafts/draft-iana-rfc3330bis-01.txt
>>
>> Other than a formatting error in the header ("IPv4 Multicast Guidelines")
>> instead of ("Special Use IPv4 Addresses"), the only significant change
>> appears to be removing the "Reserved" status of the old Classfull boundary
>> networks. The former boundary networks are now subject to allocation like
>> any other unicast IPv4 address space.
>>
>> Host, Router vendors and Network Operators should have already been testing
>> their equipment for proper handling (i.e. not doing anything different) of
>> these network addresses. So this ID should just be a minor IANA
>> administrative cleanup.
