[132346] in North American Network Operators' Group
Re: IPv6
daemon@ATHENA.MIT.EDU (Matthew Petach)
Sun Nov 21 18:06:06 2010
In-Reply-To: <5A6D953473350C4B9995546AFE9939EE0B14CACE@RWC-EX1.corp.seven.com>
Date: Sun, 21 Nov 2010 15:06:01 -0800
From: Matthew Petach <mpetach@netflight.com>
To: George Bonser <gbonser@seven.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Sun, Nov 21, 2010 at 2:05 PM, George Bonser <gbonser@seven.com> wrote:
>>
>> Well,
>>
>> ipv6.ycpi.ops.yahoo.net has IPv6 address 2a00:1288:f006:1fe::1000
>> ipv6.ycpi.ops.yahoo.net has IPv6 address 2001:4998:f00b:1fe::1000
>> ipv6.ycpi.ops.yahoo.net has IPv6 address 2001:4998:f011:1fe::1000
>>
>> In my bgp I see only the first address, I don't see any path to two
>> others. Do you have the route to them?
>>
>
> I see two of them directly from yahoo : 2001:4998::/32 (that covers the
> last two IPs) but the first one comes to me via HE (2a00:1288::/32)
>
> You think many people are going to type the "v6" part of the URL
> considering most people when they get v6 won't even know if they have it
> or not?
Until all the routing kinks being mentioned are all worked, out, it's
probably somewhat intentional that the namespace is being
kept separate, so that v6-aware techies can help diagnose/debug
routing oddities, DNS lookup issues, and other gotchas *before*
the rest of the population is subjected to it.
Matt
(speaking only for himself, at the moment)
