|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Tue, 29 May 2007 14:49:44 +0100 From: "Alexander Harrowell" <a.harrowell@gmail.com> To: "Iljitsch van Beijnum" <iljitsch@muada.com> Cc: "Donald Stahl" <don@calis.blacksun.org>, "John Curran" <jcurran@istaff.org>, nanog@nanog.org In-Reply-To: <F7A0B3D8-9E34-4560-9C0B-BFCF13730270@muada.com> Errors-To: owner-nanog@merit.edu On 5/29/07, Iljitsch van Beijnum <iljitsch@muada.com> wrote: > > On 29-mei-2007, at 15:21, Donald Stahl wrote: > > 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? > > You mean other than setting it up once, forgetting about it and then > calling the support line when it stops working? Don't forget that > changing mail settings isn't something you'll want to do too often > (speaking as the owner of an IPv6 mail server and a mail client that > won't fall back to IPv4 when IPv6 is present but doesn't work). > Isn't his point that y! could offer IPv6 e-mail in parallel to the existing IPv4 service, putting the IPv6 machines in a subdomain ipv6.yahoo.com, so that end users and networks who want to do it can do so without bothering the others?
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |