-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think this is better discussed in 6man.
"The use of the symbol "::" MUST be used to its maximum capability." means, you have to represent an address as 2001:db8::1 and not 2001:db8:0:0:0:0:0:1 :: instead of 0:0:0:0:0:0:0:0 I didn't quite understand what you mean here though. > However, RFC 2373 states that "::" corresponds to the unspecified addresses > XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX BTW, 2373 is obsoleted by 4291 Regards, Seiichi - -------- Original Message -------- Subject: RFC 5292 Comment Date: Thu, 14 Oct 2010 15:01:11 +0200 From: Test <[email protected]> To: [email protected], [email protected] Sirs, Thanks for your work on IPv6 addresses and operational problems. We need to get this right to avoid all sorts of nasty bugs. I have come across a particular problem whilst writing and testing IPv6 library routines that is not addressed in your paper: the handling of the literal address "::" Taking your interpretation from section 4.2 of RFC 5952 "The use of the symbol "::" MUST be used to its maximum capability." then my conclusion is that the literal address "::" == /^::$/ in regular expression format, should correspond to the all zeros address 0000:0000:0000:0000:0000:0000:0000:0000 (reverse of address compression = address expansion. it has to be a transparent 2 way process without loss of information) However, RFC 2373 states that "::" corresponds to the unspecified addresses XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX Why is this important to understand? An often used shorthand for the default route in IPv6 notation seems to be use of the prefix "::/0" I was testing my own perl prefix creation libraries, which tested whether the first portion of the prefix was a valid IPv6 address and it failed on the case "::/0". The PERL library Regexp-IPv6 does not seem to recognize that "::" is a valid address corresponding to the all zeros IPv6 address, because of this fuzzy definition. Hoping you can clarify which is the correct interpretation of "::", and possibly add a section on "Handling Eight 16-Bit 0 Fields" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAky3l7QACgkQcrhTYfxyMkLNdwCcDFUxXRmHOgUgWU8M7VLvU1Y1 mdkAn0WfEquXKqW7PbBK32/Tti4/5oec =PPUG -----END PGP SIGNATURE----- -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
