Hi, some quick comments on this draft, thanks.
Brian Dickson wrote:
(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.
Use of term 'autoconf' (like in 'autoconf bit', 'the rfcs for autoconf',
'autoconf-specific behaviour', etc) are confusing to a AUTOCONF WG
member who also reads it as address autoconfiguration tools for mobile
ad-hoc networks. I'd suggest expanding completely the term 'autoconf'
to what you/authors really meant to say.
This draft's section 4.1.1 may list RFC5072's section 4.1 ("IP Version 6
over PPP"), as a potential impact to existing RFCs.
later on draft says:
OR-ing the prefix with the modified hardware address (e.g.
EUI-48/MAC-48 with left-padded zeros)
How about when the hardware address is 48bit but its uniqueness not
guaranteed, because not in the IEEE space. That is the case for USB
48bit 'MAC' address decided solely by software, not standardized. There
are other virtual interfaces as well.
I feel the need for that 70th bit 'u'...
PD is, however, usable by routers in RA announcements, which can then
be used by autoconfiguration.
You mean RFC4191 "Default Router Preferences and More-Specific Routes
[in RAs]"? Or something else?
Thanks,
Alex
Enjoy,
Brian Dickson
------------------------------------------------------------------------
Subject: New Version Notification for
draft-dickson-v6man-new-autoconf-00 From: IETF I-D Submission Tool
<[EMAIL PROTECTED]> Date: Thu, 04 Oct 2007 19:20:10 -0400 To:
[EMAIL PROTECTED]
To: [EMAIL PROTECTED] CC:
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.
------------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list [email protected] Administrative
Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
