|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical 6bone space used still in the free (www.ietf.org over IPv6 broken) (Was: why same names, was Re: NANOG 40 agenda posted)
[let me whine again about this one more time... *sigh*]
[guilty parties in cc + public ml's so that every body sees again that
this is being sent to you so that you can't deny it... *sigh again*]
Iljitsch van Beijnum wrote:
>
> On 30-mei-2007, at 13:23, Nathan Ward wrote:
>
>>> I can't seem to reach www.ietf.org over IPv6 these days and I have to
>>> wait 10 seconds before I fall back to IPv4.
[..]
> I think what's going on is that packets from www.ietf.org don't make it
> back to my ISP. A ping6 or traceroute6 doesn't show any ICMP errors and
> TCP sessions don't connect so it's not a PMTUD problem. So it's an
> actual timeout.
I also just started noticing this, that is, that it does not work. And
there is a very simple explanation for this: 6bone space.
As a lot of people might recall, the 6bone was shutdown on 6/6/6.
Still there are folks who are definitely not running anything
operational or who care at all about the state of their network, if
they did they would not be using it now would they?
As this is what I found on the way from $US -> $IE
7 2001:470:0:1f::2 112.131 ms 108.949 ms 108.316 ms
8 2001:470:0:9::2 109.864 ms 112.767 ms 111.586 ms
9 3ffe:80a::c 111.118 ms 86.010 ms 86.648 ms
10 2001:450:2001:1000:0:670:1708:1225 193.914 ms 194.640 ms 194.976 ms
And what do we see: 6bone space and still in use.
As a lot of places correctly filter it out, the PMTU's get dropped, as
they are supposed to be dropped.
The whois.6bone.net registry is fun of course:
inet6num: 3FFE:800::/24
netname: ISI-LAP
descr: Harry Try IPv6
country: CA
Fortunately it still also has:
ipv6-site: ISI-LAP
origin: AS4554
descr: LAP-EXCHANGE
Los Angeles
country: US
Which matches what GRH has on list for it: Bill.
Now I have a very very very simple question:
Can you folks finally, a year after the 6bone was supposed to be
completely gone, renumber from out that 6bone address space that you
are not supposed to use anymore?
That most likely will resolve the issues that a lot of people are
seeing. Or should there be another 6/6/7 date which states that
de-peering networks which are still announcing/forwarding 6bone space
should become into effect?
Of course, Neustar, who are hosting www.ietf.org, might also want to
look for a couple of extra transit providers who can provide them with
real connectivity to the rest of the world.
Thank you, I sincerely hope that this matter will finally be resolved.
Greets,
Jeroen
Attachment:
signature.asc
|