(Please excuse minor formatting issues and the occasional spelling
mistake - this is version 00 of the draft.)
This I-D is the one you've all been waiting for, after the "16 bits
between friends" thread.
Enjoy,
Brian Dickson
--- Begin Message ---
A new version of I-D, draft-dickson-v6man-new-autoconf-00.txt has been
successfuly submitted by Brian Dickson and posted to the IETF repository.
Filename: draft-dickson-v6man-new-autoconf
Revision: 00
Title: A New Method of Constructing Interface Identifiers for
Expanded Autoconfiguration in IPv6
Creation_date: 2007-10-04
WG ID: Independent Submission
Number_of_pages: 27
Abstract:
This Internet Draft discusses a proposed extension to the set of
Interface Identifier construction methods for 802 networks. The
purpose of this is to allow autoconf RA announcments of prefix length
other than 64 bits. It is intended to be fully backward compatible
for /64 announcements. Instead of having one Interface Identifier
construction method for all purposes, this adds an alternate method
which is only used for autoconf, and only if the prefix length is not
/64. No other IPv6 methods or protocols require modification.
However, without modification, use of prefixes other than /64 likely
won't support many IPv6 enhanced functions.
The ultimate goal it providing enough bits between the top level
allocation by Regional Internet Registristry (RIR) and the smallest
autoconfiguration allocation, to allow both external aggregation by
ISPs into one prefix, as well as internal hierarchical aggregation to
support a variety of ISP topologies and practices. Current policies
are driven from below by the current 64 bit Interface Identifier.
Only by relaxing this to 48 bits for such technologies as 802
(Ethernet), does the number of bits available reach a level deemed
"sufficient".Author's Note
This Internet Draft is intended to result in this draft or a related
draft(s) being placed on the Standards Track for 6man.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [5].
The IETF Secretariat.
--- End Message ---
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
