Greetings. I do not believe 6bone space has anything
to do with it. 3ffe:80a::/64 is still being used by
PAIX in Palo Alto. However, we should be filtering
6bone space. So were only using it until all peers are
moved off of 6bone space. Unfortunately, moving those
peers and getting rid of our remaining overlay routers
is about has hard to do as dislodging an Alabama tick.
In general, I had no problems reaching www.ietf.org from
pretty much anywhere in our network. The one exception
was a single overlay router located at AMS-IX IPV6. I
have a number of usual suspect bugs that I checked out, but
I could still not reach www.ietf.org. I changed routing
policy to learn 2610:A0::/32 from AS3257, which is directly
connected to us on AMS-IX. I still could not ping it.
However, I could ping www.ietf.org from all other locations
despite the fact the path had to go through the same router.
The scope of my policy change was global. So the entire network
prefered that path through the Amsterdam router.
However, I have seen stranger stuff with IPv6. If you could
send me a traceroute and show me where its dieing, I can
do some more poking around. If your going through that particular
overlay router, I'll just reboot tonight. The traceroute I
see in the forwarded message appears to be going to HEAnet,
www.ietf.org. So I would like to see what a traceroute looks
like.
spowell(_at_)ar2(_dot_)pao2> traceroute 2610:A0:C779:B::D1AD:35B4
traceroute6 to 2610:A0:C779:B::D1AD:35B4 (2610:a0:c779:b::d1ad:35b4) from
2001:450:2001:1000:0:670:1708:219, 30 hops max, 12 byte packets
1 2001:450:1:2000::c (2001:450:1:2000::c) 50.432 ms 60.226 ms 50.749 ms
2 2001:450:1:2000::c (2001:450:1:2000::c) 50.581 ms 50.368 ms 50.771 ms
3 2001:450:1:1::29 (2001:450:1:1::29) 50.355 ms 50.593 ms 50.444 ms
4 GBLX-v6-CHI1.cr1.ord1.us.occaid.net (2001:4830:ff:1010::3549) 64.120 ms
55.993 ms 54.963 ms
5 ge-0-1-0.cr1.iad1.us.occaid.net (2001:4830:ff:f151::2) 111.167 ms 81.835
ms 80.415 ms
6 unassigned.in6.twdx.net (2001:4830:e6:d::2) 84.715 ms 88.792 ms 91.223 ms
7 stsc350a-eth3c0.va.neustar.com (2610:a0:c779::fe) 88.154 ms 85.269 ms
84.699 ms
8 www.ietf.ORG (2610:a0:c779:b::d1ad:35b4) 97.191 ms 86.825 ms 86.173 ms
[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
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf