New ID: Special Use IPv4 Addresses
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.
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.
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.
participants (2)
-
Jonathan Heinlein -
Sean Donelan