|
RE: IETF: v6 works, v4 is broken
2003-03-18 02:39:56
Pekka Savola wrote:
On Mon, 17 Mar 2003, Aaron Falk wrote:
Tom Marshall wrote:
I have found that IPv6 seems to have a much longer round
trip delay than
IPv4 for just about every site that I have tried. For
example, pinging
www.rfc-editor.org from here gives me this:
IPv6: rtt min/avg/max/mdev = 589.174/678.001/1109.953/117.776 ms
IPv4: rtt min/avg/max/mdev = 8.346/48.524/130.290/37.593 ms
See note to ietf list from yesterday that IPv6 routes all
go to Europe
before going anywhere else. :(
Better so than going to Japan first as the last time ;-)
Wow, I didn't know yet that postel.org & rfc-editor did IPv6.
Good thing :)
Albeit a bit on the slow side from europe:
jeroen(_at_)purgatory:~$ traceroute6 www.rfc-editor.org
traceroute to www.rfc-editor.org (3ffe:801:1000:0:2d0:b7ff:c0de:3) from
3ffe:8114:2000:240:290:27ff:fe24:c19f, 30 hops max, 16 byte packets
1 gw-20.ams-02.nl.sixxs.net (3ffe:8114:1000::26) 19.811 ms 19.93 ms
20.14 ms
2 Amsterdam.core.ipv6.intouch.net (2001:6e0::2) 19.367 ms 20.136 ms
20.228 ms
3 3ffe:800::fffb:0:0:5 (3ffe:800::fffb:0:0:5) 181.746 ms * 181.91 ms
4 3ffe:801:1000:0:2d0:b7ff:c0de:3 (3ffe:801:1000:0:2d0:b7ff:c0de:3)
182.807 ms 183.276 ms 182.283 ms
Then again the v4 path is imho even a bit worse:
jeroen(_at_)purgatory:~$ traceroute www.rfc-editor.org
traceroute to www.rfc-editor.org (128.9.160.27), 64 hops max, 40 byte
packets
1 gw-64-92.sms-1.ams-tel.cistron.net (195.64.92.1) 18 ms 18 ms 18
ms
2 ve10.rtr-1.ams-tel.cistron.net (62.216.31.1) 18 ms 19 ms 18 ms
3 ge10-0.mpr1.ams1.nl.mfnx.net (193.148.15.122) 17 ms 17 ms 20 ms
4 pos2-0.cr2.ams2.nl.mfnx.net (208.184.231.254) 19 ms 18 ms 18 ms
5 pos3-0.cr1.ams2.nl.mfnx.net (64.125.31.169) 18 ms 18 ms 18 ms
6 so-4-2-0.cr2.lhr3.uk.mfnx.net (208.184.231.45) 28 ms 29 ms 29 ms
7 so-7-0-0.cr2.lga1.us.mfnx.net (64.125.31.182) 102 ms 101 ms 101
ms
8 so-1-0-0.cr1.lga1.us.mfnx.net (208.185.0.233) 102 ms 102 ms 101
ms
9 so-1-0-0.cr1.iad1.us.mfnx.net (208.184.233.61) 105 ms 106 ms 106
ms
10 so-3-0-0.mpr1.iad5.us.mfnx.net (216.200.127.10) 105 ms 105 ms
so-0-0-0.mpr1.iad5.us.mfnx.net (216.200.127.17) 105 ms
11 64.124.112.29.cogentco.com (64.124.112.29) 106 ms 106 ms 105 ms
12 p15-0.core02.dca01.atlas.cogentco.com (66.28.4.22) 107 ms 106 ms
106 ms
13 p14-0.core01.atl01.atlas.cogentco.com (66.28.4.161) 232 ms 321 ms
239 ms
14 p15-0.core01.jax01.atlas.cogentco.com (66.28.4.137) 124 ms 123 ms
124 ms
15 p14-0.core01.mco01.atlas.cogentco.com (66.28.4.153) 128 ms 127 ms
127 ms
16 p14-0.core01.tpa01.atlas.cogentco.com (66.28.4.142) 128 ms 129 ms
128 ms
17 p5-0.core01.iah01.atlas.cogentco.com (66.28.4.45) 144 ms 144 ms
143 ms
18 p14-0.core01.san01.atlas.cogentco.com (66.28.4.6) 183 ms 181 ms
182 ms
19 p4-0.core01.lax01.atlas.cogentco.com (66.28.4.77) 182 ms 181 ms
180 ms
20 p6-0.core01.lax04.atlas.cogentco.com (66.28.4.202) 182 ms 182 ms
182 ms
21 38.118.132.98 (38.118.132.98) 182 ms 182 ms 182 ms
22 lngw2-isi-1-atm.ln.net (130.152.180.22) 183 ms 182 ms 182 ms
23 boreas.isi.edu (128.9.160.161) 183 ms * 182 ms
Looks like we are routed all over the US for that host ;)
But it's good to see that it works, IMHO all the important (ietf etc)
hosts
should already have been doing IPv6 for quite some time, but:
www.ietf.org AAAA record currently not present
ops.ietf.org AAAA record currently not present
ietf.org MX 10 ietf-mx.ietf.org
ietf.org MX 20 odin.ietf.org
ietf-mx.ietf.org AAAA record currently not present
odin.ietf.org AAAA record currently not present
Greets,
Jeroen
|
|