[96929] in North American Network Operators' Group
Re: NANOG 40 agenda posted
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Tue May 29 15:37:21 2007
To: Donald Stahl <don@calis.blacksun.org>
Cc: John Curran <jcurran@istaff.org>, nanog@nanog.org
In-Reply-To: Your message of "Tue, 29 May 2007 09:21:49 EDT."
<20070529091737.K13003@calis.blacksun.org>
From: Valdis.Kletnieks@vt.edu
Date: Tue, 29 May 2007 13:30:40 -0400
Errors-To: owner-nanog@merit.edu
--==_Exmh_1180459840_5909P
Content-Type: text/plain; charset=us-ascii
On Tue, 29 May 2007 09:21:49 EDT, Donald Stahl said:
> So many people seem to be obsessed with getting the end users connected
> via IPv6 but there is no point in doing so until the content is reachable.
> The built in tunneling in Windows could be a problem so let's start by
> using different dns names for IPv6 enabled servers- mail.ipv6.yahoo.com or
> whatever. Can anyone think of a reason that a separate hostname for IPv6
> services might cause problems or otherwise impact normal IPv4 users?
How do you get mail.ipv6.yahoo.com to actually get *used*, when your average
user doesn't know where they set 'mail.yahoo.com' in their PC's configuration,
and either don't understand why sometimes's it's foo.com and sometimes it's
www.foo.com, or don't even bother, they just type 'foo' into the address bar
and let the browser add www. and .com, or they go to google and enter 'foo'
and hit "I feel lucky"?
You're basically stuck that you have to provide one name with both ann A and
an AAAA record, or your support desk staff will mutiny.
--==_Exmh_1180459840_5909P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001
iD8DBQFGXGNAcC3lWbTT17ARAt2ZAKDtnTtLvjJvpIVQhCYDrVuY1fdYTACdEcVY
LrTdgeUbGCj2rAliXSWMN9M=
=rL5V
-----END PGP SIGNATURE-----
--==_Exmh_1180459840_5909P--
