Date: Tue, 18 Nov 1997 12:41:14 +0100 (MET) From: =?iso-8859-1?Q?Martin_J=2E_D=FCrst?= <email@example.com> cc: firstname.lastname@example.org Subject: Re: IPv6 addresses within URLs In-Reply-To: <346A11C1.20463C40@parc.xerox.com> Message-ID: <Pine.SUN.3.96.971118123545.282Gemail@example.com> On Wed, 12 Nov 1997, Larry Masinter wrote: > draft-ietf-ipngwg-aaaa-00.txt > > proposes another method which would work for including IPv6 addresses: > > An IPv6 address is represented as a name in the IP6.INT domain by a > sequence of nibbles separated by dots with the suffix ".IP6.INT". The > sequence of nibbles is encoded in reverse order, i.e. the low-order > nibble is encoded first, followed by the next low-order nibble and so > on. Each nibble is represented by a hexadecimal digit. For example, > the inverse lookup domain name corresponding to the address > > 4321:0:1:7:3:4:567:89ab > > would be > > b.a.188.8.131.52.184.108.40.206.0.0.3.0.0.0.7.0.0.0.1.0.0.0.0.0.0.0.1.2.3.4.IP6.INT. If that was 89ab.5220.127.116.11.1.0.4321.something it would look okay, but as above it's definitely too lengthy. I agree with many of the points John Klensin has mentionned. For "addresses will frequently change", however, I guess (without much in-depth knowledge) that while some addresses will indeed change very frequently, others might me much more stable and long-term, especially for example the addresses of some DNS servers,... And it's these that have the greatest chance of being used in URLs. Regards, Martin.