[96947] in North American Network Operators' Group
Re: why same names, was Re: NANOG 40 agenda posted
daemon@ATHENA.MIT.EDU (David Conrad)
Tue May 29 17:54:30 2007
In-Reply-To: <a06230902c28201c8b71b@[10.31.32.75]>
Cc: Nanog <nanog@nanog.org>
From: David Conrad <drc@virtualized.org>
Date: Tue, 29 May 2007 12:01:36 -0700
To: Edward Lewis <Ed.Lewis@neustar.biz>
Errors-To: owner-nanog@merit.edu
Ed,
On May 29, 2007, at 9:22 AM, Edward Lewis wrote:
> First - "the way you ask for names" is not different at the
> application level, it is different in the "layer" in which you find
> where to shoot packets.
Right. The problem is, the methodology by which you shoot packets
may or may not work.
> If the user types in the domain label (like "nanog") and the
> application then adds on TLDs and such, the application would have
> to try the likely set of IPv6 labels to pre-pend.
What a horrible idea. Applications automatically pre- or appending
crap to domain name labels shouldn't be done, period.
> As far as any other encoding of the name, whether IPv6 is working
> is something that the encoder cannot know as the code will probably
> be run from different points of the collective IP4 and IP6 network.
Exactly. And since it is impossible to know whether or not there is
actual IPv6 connectivity to a site that is advertising AAAA records,
you get into situations where you get a connection attempt, timeout,
retry, etc., resulting in people getting directives like the one Leo
pointed to.
The IPv6 Internet is a different network than the IPv4 Internet.
Same names invites confusion and unhappiness.
Rgds,
-drc
