http://www.dot-biz.com/IPv4/Tutorial
C@t-32-BitOID:UnirVerse0QQQQGGGWWWXXXXX32-Bit Managed Address0000000000000000 Jim Fleming http://www.ddj.com/articles/search/search.cgi?q=fleming Oct93: The C+@ Programming Language ----- Original Message ----- From: "Bob Hinden" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, November 28, 2001 9:52 AM Subject: Request to Advance "IP Version 6 Addressing Architecture" > Erik, Thomas, > > The chairs of the IP Next Generation working group, on behalf of the > working group, request that the following document be published as an Draft > Standard: > > Title : IP Version 6 Addressing Architecture > Author(s) : B. Hinden, S. Deering > Filename : draft-ietf-ipngwg-addr-arch-v3-07.txt > Pages : 27 > Date : 27-Nov-01 > > A working group last call for this document was completed on August 31, > 2001. The -07 version of the draft resolves issues raised during the > working group last call and subsequent discussion. A summary of the > comments received on the mailing list and their disposition is attached. > > This document will obsolete RFC2373. Changes from RFC2373 are listed in > Appendix B. > > Bob Hinden / Steve Deering > IPng Working Group Co-Chairs > > > ------------------------------------------------------------------------ > > COMMENT 1: Suggestion that it isn't good practice to talk about assigning > multicast address to an interface because it may confuse people and they > might be assigned directly to interfaces (e.g., via ifconfig command). > > Text will be changed to clarify this issue. > > > COMMENT 2: Questioned whether the IPv6 addresses with embedded IPv4 address > should be included in the document. > > This was discussed at the interim meeting in Seattle and there was a > consensus to keep the mapped and compatible address in this > document. Other types of transition addresses can be defined in other > documents. > > > COMMENT 3: Suggestion that the anycast usage scenarios in the document are > very router centric and restrictions for router only usage be eased. > > The current text will be revised to clarify that other anycast usage is > possible, but that new uses need to be specified. > > > COMMENT 4: Suggestion that there be more clarification on the differences > between interface, link, and node in section 2.7 on multicast addresses. > > Will add a summary description of the multicast scope values to the document. > > > COMMENT 5: Questioned the removal of the format prefix (FP) and detailed FP > table, and instead only listing the exceptions to global unicast. > > This issue was discussed on the mailing list and there was a consensus that > the current text is appropriate. The resulting behavior of treating the > address space as global unicast, except for the listed exceptions, is correct. > > > COMMENT 6: Suggestion to reserve some part of the IPv6 and have it's usage > be unspecified. > > The discussion on the mailing concluded was this was not a good idea. Past > experience with IPv4 indicated that it becomes very hard to utilize > "unspecified" address space in the future. > > > COMMENT 7: Suggestion to move IANA considerations to a numbered section > instead of an appendix to make clearer it is normative. > > Document will be updated to make the IANA consideration a numbered section. > > -------------------------------------------------------------------------- > > -------------------------------------------------------------------- > 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] > -------------------------------------------------------------------- > -------------------------------------------------------------------- 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] --------------------------------------------------------------------
