I think this is a mis-use of AUTH48; the working group has considered the draft and said what it wanted to say, and at this point the RFC Editor is asking you whether they changed the intent of the draft in the editing process or whether perhaps your address has changed. Changing the draft in a substantive way is out of scope of the question you are being asked.
On Aug 4, 2010, at 1:26 PM, Seiichi Kawamura wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi > > This already came up on the list once before, > and since its in AUTH48 now, I would like to > make the changes to the document. > > Current section 4.2 has 3 parts, and the first two are > > 4.2.1. Shorten as Much as Possible > > The use of the symbol "::" MUST be used to its maximum capability. > For example, 2001:db8::0:1 is not acceptable, because the symbol "::" > could have been used to produce a shorter representation 2001:db8::1. > > 4.2.2. Handling One 16-Bit 0 Field > > The symbol "::" MUST NOT be used to shorten just one 16-bit 0 field. > For example, the representation 2001:db8:0:1:1:1:1:1 is correct, but > 2001:db8::1:1:1:1:1 is not correct. > > I would like to combine these two, and also clarify that you MUST > use "::" when there are more then two consecutive 0 fields. > The following is the text I plan to use. > > 4.2.1. When to use "::" > > If the address contains at least two consecutive 16-bit 0 fields, "::" > MUST be used to compress all consecutive 16-bit 0 fields. > The symbol "::" MUST NOT be used to shorten just one 16-bit 0 field. > For example, the representation 2001:db8:0:1:1:1:1:1 is correct, but > 2001:db8::1:1:1:1:1 is not correct. > > Please let me know by Aug 6, 2010 if you have any objections to this. > > Thanks and Regards, > Seiichi > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > > iEYEARECAAYFAkxZTlAACgkQcrhTYfxyMkLNnACfbaXV00gkSPn0ZtsLvmgONr72 > 5WIAn0zKEaW61ab/H/jSWiAT80y7ORLT > =kEsX > -----END PGP SIGNATURE----- > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > [email protected] > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- http://www.ipinc.net/IPv4.GIF -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
