North American Network Operators Group
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Historical
Re: IPv6 internet broken, Verizon route prefix length policy
- From: Seth Mattinen
- Date: Mon Oct 12 21:22:30 2009
Owen DeLong wrote:
> From where I sit, it looks like:
>
> a.root-servers.net has IPv6 address 2001:503:ba3e::2:30
> BGP routing table entry for 2001:503:ba3e::/48
>
> f.root-servers.net has IPv6 address 2001:500:2f::f
> BGP routing table entry for 2001:500:2f::/48
>
> h.root-servers.net has IPv6 address 2001:500:1::803f:235
> BGP routing table entry for 2001:500:1::/48
>
> j.root-servers.net has IPv6 address 2001:503:c27::2:30
> BGP routing table entry for 2001:503:c27::/48
>
> k.root-servers.net has IPv6 address 2001:7fd::1
> BGP routing table entry for 2001:7fd::/32
>
> l.root-servers.net has IPv6 address 2001:500:3::42
> BGP routing table entry for 2001:500:3::/48
>
> m.root-servers.net has IPv6 address 2001:dc3::35
> BGP routing table entry for 2001:dc3::/32
>
>
> b.root-servers.net has no AAAA record
> c.root-servers.net has no AAAA record
> d.root-servers.net has no AAAA record
> e.root-servers.net has no AAAA record
> g.root-servers.net has no AAAA record
> i.root-servers.net has no AAAA record
>
>
> So... Likely, Verizon customers can reach k and m root servers via IPv6
> and not the others.
>
I can see the /48's out of 2001 in Verizon's table.
~Seth
|
