[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: quality of v6 connections [Re: unmanaged scope comments]

At 16:54 +0300 9/24/02, Pekka Savola wrote:

6bone is what we have.

Saying it is not "ipv6 internet" won't change the truth, unfortunately.
We have a small, with a couple of million potential users, native IPv6
network in Europe too, called 6NET, but I wouldn't go as far as calling
that "ipv6 internet" either.

One must either acknowledge that or live in a dream world thinking we have
good connections, "ipv6 internet" is doing well etc.

And how we can fix that?  Start building real v6 connections and start
ignoring 6bone.  But there is no IPv6 internet other than 6bone yet.
Sorry.
There is perhaps something in between:

[cookiemonster:~] owens% traceroute6 hammer.uoregon.edu
traceroute6 to hammer.uoregon.edu (2001:468:d01:dc::80df:dc1d) from 2001:468:901:1:203:93ff:fed6:dfcc, 30 hops max, 12 byte packets
1 c7206-ge0-0.nysernet.net 1.291 ms 0.484 ms 0.503 ms
2 nyc-m20-nnsyr.nysernet.net 13.811 ms 13.981 ms 13.925 ms
3 roc-m10-nyc-m20.nysernet.net 21.467 ms 21.235 ms 20.965 ms
4 buf-m20-roc-m10.nysernet.net 23.047 ms 22.945 ms 22.881 ms
5 clev-nysernet.abilene.ucaid.edu 27.226 ms 27.581 ms 27.362 ms
6 ipls-clev.abilene.ucaid.edu 33.778 ms 33.685 ms 33.449 ms
7 kscy-ipls.abilene.ucaid.edu 42.633 ms 42.661 ms 43.221 ms
8 kscy-dnvr.abilene.ucaid.edu 54.519 ms 53.815 ms 53.663 ms
9 snva-dnvr.abilene.ucaid.edu 78.355 ms 78.035 ms 79.221 ms
10 2001:468:ff:b4d::2 92.055 ms * 91.137 ms
11 2001:468:d3f:1::2 91.39 ms 91.674 ms 91.789 ms
12 hammer.ipv6.uoregon.edu 92.268 ms 91.678 ms 91.538 ms

[cookiemonster:~] owens% traceroute hammer.uoregon.edu
traceroute to hammer.uoregon.edu (128.223.220.29), 30 hops max, 40 byte packets
1 c7206-1.nysernet.org (199.109.32.254) 0.92 ms 0.836 ms 0.476 ms
2 199.109.5.86 (199.109.5.86) 13.738 ms 13.693 ms 13.754 ms
3 roc-m10-nyc-m20.nysernet.net (199.109.5.53) 21.355 ms 22.949 ms 20.973 ms
4 buf-m20-roc-m10.nysernet.net (199.109.6.2) 22.692 ms 23.851 ms 23.228 ms
5 abilene-clev-buf-m20.nysernet.net (199.109.2.2) 27.101 ms 26.637 ms 27.035 ms
6 ipls-clev.abilene.ucaid.edu (198.32.8.25) 33.208 ms 33.272 ms 33.877 ms
7 kscy-ipls.abilene.ucaid.edu (198.32.8.5) 42.53 ms 42.008 ms 42.355 ms
8 dnvr-kscy.abilene.ucaid.edu (198.32.8.13) 53.762 ms 53.011 ms 53.15 ms
9 pos-6-3.core0.eug.oregon-gigapop.net (198.32.163.13) 86.98 ms 86.256 ms 90.283 ms
10 uo-0.eug.oregon-gigapop.net (198.32.163.147) 86.877 ms 84.327 ms 85.403 ms
11 ge-1-1.uonet2-gw.uoregon.edu (128.223.2.2) 85.201 ms 84.273 ms 86.951 ms
12 hammer.uoregon.edu (128.223.220.29) 85.456 ms 84.671 ms 86.446 ms

The reason those traceroutes look so similar is that they're both native paths from Syracuse, NY (central NY state) to Eugene, OR. There's a slight difference at the far end because UO is dual connected to Abilene, and the BGP config is slightly different for v4 and v6. But they're basically the same path, over the same equipment, all running dual-stack and native.

Of course other R&E networks have had native v6 capabilities for quite some time, too. One thing that stands out for me with respect to this path is that it crosses five ASes and all the participants are running released code on standard hardware, routing IPv4 and IPv6 with the same boxes. And for most of us that means all the boxes - we have no IPv4-only routers any more. I'm not sure how many other networks are doing that (if you are, I'd like to compare notes ;).

Of course, NYSERNet, the Oregon GigaPoP and Abilene are not the 'real internet', where 'real internet' = 'commercial DFZ providers'. But we definitely aren't the 6Bone either.

Bill.