[99313] in North American Network Operators' Group
Re: Apple Airport Extreme IPv6 problems?
daemon@ATHENA.MIT.EDU (John Curran)
Mon Sep 17 17:24:53 2007
In-Reply-To: <2d106eb50709171006u64dcd4cmf087d63820b10936@mail.gmail.com>
Date: Mon, 17 Sep 2007 17:15:38 -0400
To: "Martin Hannigan" <hannigan@gmail.com>
From: John Curran <jcurran@mail.com>
Cc: nanog@merit.edu
Errors-To: owner-nanog@merit.edu
At 1:06 PM -0400 9/17/07, Martin Hannigan wrote:
>
>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.
RFC 4472 has an excellent discussion of the topic, and while pointing
out that your mileage may vary, it recommends the AAAA on the same
name only when:
" 1. The address is assigned to the interface on the node.
2. The address is configured on the interface.
3. The interface is on a link that is connected to the IPv6
infrastructure.
In addition, if the AAAA record is added for the node, instead of
service as recommended, all the services of the node should be IPv6-
enabled prior to adding the resource record. "
Not a problem for names which are single services (www.foo.com),
but caution is required when the name has multiple services running.
/John
