[ppml] IPv6 assignment - proposal for change to nrpm

[Brian Dickson]

Leo Bicknell wrote:
> In a message written on Mon, Oct 22, 2007 at 09:31:36AM -0400, Azinger, Marla wrote:
>   
>> 3177 is a recommendation from 2001 and not a standar of any kind.
>>     
>
> I'm afraid many people are not looking at the right RFC's and/or
> considering what all needs to be changed if the /64 boundary is to
> be updated.  I'm fairly sure this is not an exhaustive list, /64
> is referenced in many locations in different IPv6 RFC's, many of
> which are standards track.
>
> * http://www.faqs.org/rfcs/rfc2373.html
>   "IP Version 6 Addressing Architecture"
>   Status: Standards Track
>
>   Section 2.5.1: "Interface IDs are required to be 64 bits long..."
>
>   Section 2.5.7: Aggregatable Global Unicast Addresses
>
>   Section 2.5.8: Local-Use IPv6 Unicast Addresses
>
>   
RFC 2373 was obsoleted by 3531 which was obsoleted by 4291.
2.5.8 is gone, but AGUA is still roughly the same (all but 000 require 
use of EUI-64 modified), and ditto 2.5.1
> * http://www.faqs.org/rfcs/rfc2374.html
>   "An IPv6 Aggregatable Global Unicast Address Format"
>   Status: Standards Track
>
>   Section 3.1 makes it clear the lower 64 bits are an interface
>   identifier for 
>
>   I also point out section 3.4 makes a recomendation we continue to use
>   a slow start method:
>
>     It is recommended that
>     organizations assigning NLA address space use "slow start" allocation
>     procedures similar to [RFC2050].
>
>   
2374 was obsoleted by 3587.
> * http://www.faqs.org/rfcs/rfc2450.html
>   "Proposed TLA and NLA Assignment Rule"
>   Status: Informational
>
>   Section 3: IPv6 Aggregatable Global Unicast Address Format
>
>   
This bit was itself in RFC 2374, which was obsoleted by RFC 3587.
> * http://www.faqs.org/rfcs/rfc2460.html
>   "Internet Protocol, Version 6 (IPv6) Specification"
>   Status: Standards Track
>
>   Section 3: Specifically referrs to 2373 (ADDRARCH)
>   
4291  obsoletes 3531 which obsoleted 2373.

(I don't know why 2460 hasn't been updated with the new references...)
> * http://www.rfc-editor.org/rfc/rfc3177.txt
>   "IAB/IESG Recommendations on IPv6 Address Allocations to Sites"
>   Status: Informational
>
>   Section 3: Recomendations
>   
This was informational only, from 2001, and IMHO no longer as relevant 
as it once was.

So, by my count, that is 4291 and 3587.

My IETF draft also lists 2464 (Ethernet),  4941 (privacy), and 4862 
(autoconfiguration).
Most other IPv6 RFCs inherit from those few, and mostly the choice is 
rather axiomatic.
Two small changes, basically, in a backward-compatible
manner, is meant to be as minimally-disruptive as is possible.
(Think surgery to remove a burst appendix or inflamed tonsils.)

Anyone interested can see the draft at:
http://www.ietf.org/internet-drafts/draft-dickson-v6man-new-autoconf-00.txt

My draft even includes the necessary patch for Linux, about 17 lines in 
total, mostly the result
of the necesssary line length provisions for an RFC. (It was 10 lines 
originally.)

Brian