On Tue, 4 Mar 2003, Bob Hinden wrote:
> I think the new draft resolves issues raised during the last call.  Changes 
> to the document include:
> 
>   - Generalize the scope of the document to cover more than the 2000::/3
>     prefix.  This includes changing the title and introduction text.
>   - Added a new section that describes in more detail why the TLA/NLA structure
>     is being made historic.
>   - Including an example of the address format that is consistent with
>     the recommendations in RFC3177.
>   - Added Erik Nordmark as an author (note this is not shown in the
>     ID announcement).
>   - Clarified normative and non-normative references.
>   - Various small improvements to the text.
> 
> I think the consensus of the discussion was to advance this document as in 
> Informational RFC instead of to Proposed Standard.  I believe it is now 
> ready to be sent to the IESG.


One substantial point I'd like to see more discussion on is whether folks
feel that "Address Format" section, mainly restating what addr-arch-v3-11
says on 64 bit IID's, seems like the right thing to do in this document?

I think this point was brought up by at least Thomas Narten and others, 
but I don't remember whether a closure was reached.

So, I believe everything starting from:

   [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:
[...]

should be removed, if not the whole section.

I can live with this but IMO putting 64-bit-interface-ID thing which is 
rather controversial still in too many documents seems like something to 
be careful about.

How do others feel?




Below are a few very minor editorial nits:

INTERNET-DRAFT                                         R. Hinden, Nokia
February 26, 2003                                     S. Deering, Cisco
                                                       E. Nordmark, Sun

==> the header should probably say IPv6 working group.

   unassigned parts of the IPv6 address space to the purpose of Global
   Unicast as well.

==> "to the purpose of" ?  Sounds awkward, especially "to"?
==> "Global Unicast" capitalized looks funny, as if it was somehow a 
special term.

   Non-Normative

==> better named Informative, I guess?

   [ARCH]    Hinden, R., "IP Version 6 Addressing Architecture",
             Internet Draft, <draft-ietf-ipngwg-addr-arch-v3-11.txt>,
             October 2002.

==> Forgot Steve from the author list :-)

6.0 Security Considerations

==> I believe Sec Cons is typically up, before references but YMMV.

-- 
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]
--------------------------------------------------------------------

Reply via email to