discuss on draft-ietf-ipv6-unicast-aggr-v2

[Thomas Narten <narten@us.ibm.com>]

Hi Allison.

It is a feature that chairs/authors now go to ID tracker to see what
is up with a document, before we've necessarily even closed the
loop. Then they send mail to the ADs.  Kind of forces the issue
sometimes. :-)

In this case, Bob Hinden is already asking what your discuss is about,
which isn't written down yet. Can you please clarify:

a) are you asking removal of all of section 3?

b) removal of all of Section 3, except the following:

> 3.0 Address Format
> 
>    The general format for IPv6 global unicast addresses as defined in
>    "IP Version 6 Addressing Architecture" [ARCH] is as follows:
> 
> 
>       |         n bits          |   m bits  |       128-n-m bits         |
>       +-------------------------+-----------+----------------------------+
>       | global routing prefix   | subnet ID |       interface ID         |
>       +-------------------------+-----------+----------------------------+
> 
>    where the global routing prefix is a (typically hierarchically-
>    structured) value assigned to a site (a cluster of subnets/links),
>    the subnet ID is an identifier of a subnet within the site, and the
>    interface ID is as defined in section 2.5.1 of [ARCH].

c) something else?

I'd be OK with b), as it pretty narrowly restates what's in addr
arch. There might me more pushback from the author/WG if we argue the
entire section should go.

The part I think is the most in need of being deleted is:

>    [ARCH] also requires that all unicast addresses, except those that
>    start with binary value 000, have Interface IDs that are 64 bits long
>    and to be constructed in Modified EUI-64 format.  The format of
>    global unicast address in this case is:
> 
>       |         n bits          | 64-n bits |       64 bits              |
>       +-------------------------+-----------+----------------------------+
>       | global routing prefix   | subnet ID |       interface ID         |
>       +-------------------------+-----------+----------------------------+
> 
>    where the routing prefix is a value assigned to identify a site (a
>    cluster of subnets/links), the subnet ID is an identifier of a subnet
>    within the site, and the interface ID is in modified EUI-64 format as
>    defined in [ARCH].
> 
>    An example of the resulting format of global unicast address under
>    the 2000::/3 prefix that is currently being delegated by the IANA and
>    consistent with the recommendations in RFC3177 is:
> 
>       | 3 |     45 bits         |  16 bits  |       64 bits              |
>       +---+---------------------+-----------+----------------------------+
>       |001|global routing prefix| subnet ID |       interface ID         |
>       +---+---------------------+-----------+----------------------------+
> 

which is I suspect that part that got you attention.

Thomas