On Fri, 31 Jan 2003 [EMAIL PROTECTED] wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IP Version 6 Working Group Working Group of the
>IETF.
>
> Title : IPv6 Global Unicast Address Format for the 2000::/3
> Prefix
> Author(s) : R. Hinden, S. Deering
> Filename : draft-ietf-ipv6-unicast-aggr-v2-00.txt
> Pages : 4
> Date : 2003-1-30
>
> This document defines the unicast address format for the 2000::/3
> (001 binary) prefix. The address format defined in this document is
> consistent with RFC1883 'Internet Protocol, Version 6 (IPv6)
> Specification' and RFCXXXX 'IP Version 6 Addressing Architecture'.
> This documented replaces RFC2374 'An IPv6 Aggregatable Global Unicast
> Address Format'. RFC2374 will become historic.
Comments:
draft-ietf-ipv6-unicast-aggr-v2-00.txt
==> how did the first draft suddently jump to a w.g. document? I don't
recall this question being raised, unless it was years ago (or I've missed
something). Not that I disagree with (most of) the contents, but some
parts at least seem to be questionable.
This document defines the unicast address format for the 2000::/3
(001 binary) prefix. The address format defined in this document is
consistent with RFC1883 "Internet Protocol, Version 6 (IPv6)
Specification"
==> s/1883/2460/
The specific format of global unicast address under the 2000::/3
prefix is:
| 3 | n bits | 61-n bits | 64 bits |
+---+--------------------+-----------+----------------------------+
|001| routing prefix | subnet ID | interface ID |
+---+--------------------+-----------+----------------------------+
==> I guess this is another part which some folks will just ignore .. but
no matter.
3.0 IANA Considerations
The following prefix is reserved for use in documentation and MUST
NOT be assigned to any operational IPv6 nodes:
2000:0001::/32
==> I do not understand why this reservation has been made; I see zero
technical reason for it -- and it would prevent the use of the full
2000::/16 for something else.
I'd rather reserve a documentation prefix somewhere else, and in some
other, _separate_ internet-draft.
5.0 References
==> split the references.
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
