On Oct 21, 2014, at 8:39 PM, Brian E Carpenter <[email protected]<mailto:[email protected]>> wrote:
6874 slightly extends the syntax in 3986, but you want to explicitly exclude that extension. So I think this would cover it: OLD: The IPv4 and IPv6 address formats supported in this query are described in section 3.2.2 of [RFC3986], as IPv4address and IPv6address ABNF definitions. Any valid IPv6 text address format [RFC4291] can be used, compressed or not compressed. The restricted rules to write a text representation of an IPv6 address [RFC5952] are not mandatory. However, the zone id [RFC4007] is not appropriate in this context and therefore prohibited. NEW: The IPv4 and IPv6 address formats supported in this query are described in section 3.2.2 of [RFC3986], as IPv4address and IPv6address ABNF definitions. Any valid IPv6 text address format [RFC4291] can be used, compressed or not compressed. The rules to write a text representation of an IPv6 address [RFC5952] are RECOMMENDED. However, the zone id [RFC4007] is not appropriate in this context and therefore the corresponding syntax extension in [RFC6874] MUST NOT be used. Thanks. That’s great. (I sort of feel obliged to apologise, since there has been confusion in this area since RFC 2732, although the root problem was the choice of the colon in both IPv6 address syntax and URI syntax.) :) It was collective oversight. Thanks for your review. This is good stuff. -andy
_______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
