On Wed, Jan 06, 2010 at 05:35:21PM +0100, Dan Wing wrote: > > My main interest is textual comparability of addresses coming from > > potentially many different sources. If I can compare addresses safely > > only if I know some context information communicated out of band or I > > have to configure all sources to produce the same, I feel somewhat > > uneasy. My preference thus is 1), I might be OK with 2) if the > > frequency of the introduction of new WKPs is very small. > > BEHAVE is introducing both (1) a WKP which embeds the IPv4 address > in the last 32 bits and (2) allowing networks to use their own 96-bit > prefix and embed the IPv4 address in the last 32 bits. > > Your proposal would prohibit (2) from displaying the IPv4 address in > dotted decimal, because of a fear the parsed IPv6 address might be > seen or used on another network. > > Personally, I find this useful. If I'm on my home network and somebody > sends me a trace with their IPv6 prefix and some dotted-decimal displayed > in the last 32 bits, I know immediately that their tool (running on their > network) believed -- through whatever means -- that the last 32 bits > was an IPv4 address.
My concern are tools/applications generating different textual representations of the same addresses because of different contextual information they have. This then requires smart tools that can normalize things in order to make comparisons easy. Avoiding the need of special tools to enable comparisons of IPv6 addresses I think was one of the motivations behind this work. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
