Apple Airport Extreme IPv6 problems?
JORDI PALET MARTINEZ
jordi.palet at consulintel.es
Mon Sep 24 10:39:17 UTC 2007
For a production service, I will never use dual naming for IPv4 and IPv6, is
ridiculous ask the users to understand if they want to use one or the other
to use a different name. For a testing, not an issue.
> De: Martin Hannigan <hannigan at gmail.com>
> Responder a: <owner-nanog at merit.edu>
> Fecha: Mon, 17 Sep 2007 13:06:25 -0400
> Para: Iljitsch van Beijnum <iljitsch at muada.com>
> CC: Barrett Lyon <blyon at blyon.com>, <nanog at merit.edu>
> Asunto: Re: Apple Airport Extreme IPv6 problems?
> On 9/15/07, Iljitsch van Beijnum <iljitsch at muada.com> wrote:
>> On 15-sep-2007, at 21:25, Barrett Lyon wrote:
>>> The other thought that occurred to me, does FF/Safari/IE have any
>>> ability to default back to v4 if v6 is not working or behaving
>>> badly? This could be a helpful transition feature but may be more
>>> trouble than it's worth.
>> Browsers are pretty good at falling back on a different address in
>> general / IPv4 in particular when the initial try doesn't work, but
>> it does take too long if the packet is silently dropped somewhere. If
>> there is an ICMP unreachable there is no real delay. Worst case is a
>> path MTU discovery black hole, then browsers generally don't fall back.
> Getting back to my original discussion with Barrett, what should we do
> about naming? I initially though that segregating v6 in a subdomain
> was a good idea, but if this is truly a migration, v4 should be the
> interface segregated.
> I have also read Jordi? saying that no dual naming should occur, but
> I think this is unrealistic. (Sorry if I misquoted you, Jordi)
>> It would be good if more ISPs deployed 6to4 gateways so the 6to4
>> experience would be better.
> We are. There are an unending supply of small details that are in the
> way at the moment. :-)
The IPv6 Portal: http://www.ipv6tf.org
Bye 6Bone. Hi, IPv6 !
This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
More information about the NANOG