Peering with Level3

[brad]

I had e-mailed this to ipv6@, peering@ and noc@ and usually any of my e-mails regarding an issue tend to get a reasonably quick response of some kind but I haven't had any response regarding this...

Could HE look into establishing some IPv6 peering with Level3? I know it might be difficult, but that's based on their IPv4 peering. v6 is a totally different ball game, who knows..

Code Select Expand


$ traceroute6 2001:16b0::1
traceroute6 to 2001:16b0::1 (2001:16b0::1) from
2001:470:b01e:3:216:41ff:fe17:6933, 64 hops max, 12 byte packets
1  2001:470:b01e:3::2  0.487 ms  0.344 ms  0.282 ms
2  2001:470:1c:8e::1  23.954 ms  24.683 ms  23.633 ms
3  gige-g2-5.core1.tor1.he.net  23.435 ms  23.961 ms  25.102 ms
4  10gigabitethernet1-2.core1.nyc5.he.net  40.235 ms  41.399 ms  40.612 ms
5  10gigabitethernet1-4.core1.nyc1.he.net  39.691 ms  40.817 ms  47.577 ms
6  10gigabitethernet1-1.core1.nyc4.he.net  43.704 ms  39.715 ms  40.189 ms
7  2001:470:0:10e::1  102.222 ms  102.862 ms  101.027 ms
8  10gigabitethernet1-3.core1.pao1.he.net  109.065 ms  111.681 ms  109.887 ms
9  plt6-gate0.iij-america.net  109.87 ms  109.583 ms  109.622 ms
10  plt001bb00.iij.net  110.412 ms  109.767 ms  110.64 ms
11  sjc002bb01.iij.net  110.967 ms  110.804 ms  110.776 ms
12  sjc002ix02.iij.net  112.218 ms sjc002ix02.iij.net  111.175 ms
sjc002ix02.iij.net  197.004 ms
13  tu-601.sar1.London1.Level3.net  213.805 ms  221.001 ms  214.557 ms
14  tu-613.sar1.Amsterdam1.Level3.net  223.765 ms  220.451 ms  220.745 ms
15  2001:1900:5:2::e2  247.648 ms  246.936 ms  245.046 ms
16  2001:1900:5:2::e2  3245.13 ms !A  3249.24 ms !A  3245.21 ms !A


Code Select Expand


$ traceroute6 2a00:d40::1 
traceroute6 to 2a00:d40::1 (2a00:d40::1) from
2001:470:b01e:3:216:41ff:fe17:6933, 64 hops max, 12 byte packets
1  2001:470:b01e:3::2  0.69 ms  0.349 ms  0.283 ms
2  2001:470:1c:8e::1  24.539 ms  23.912 ms  24.224 ms
3  gige-g2-5.core1.tor1.he.net  23.914 ms  24.229 ms  27.14 ms
4  10gigabitethernet1-2.core1.nyc5.he.net  39.514 ms  40.345 ms  40.035 ms
5  10gigabitethernet1-4.core1.nyc1.he.net  39.83 ms  70.718 ms  41.801 ms
6  2001:458:26:2::200  41.286 ms  40.256 ms  41.18 ms
7  nyc002bb01.iij.net  40.451 ms  41.593 ms  40.702 ms
8  sjc002bb01.iij.net  120.433 ms  145.189 ms  115.756 ms
9  sjc002ix02.iij.net  117.934 ms sjc002ix02.iij.net  116.061 ms  116.482 ms
10  tu-601.sar1.Amsterdam1.Level3.net  218.092 ms  219.29 ms  218.821 ms
11  tu-607.sar1.London1.Level3.net  221.666 ms  224.437 ms  218.303 ms
12  * * *


[comptech]

IPv6 Peering with Level3 would be awesome, here is from Dallas Level3 Router to Chicago HE Tunnel server.  Dallas > Paris > London > Amsterdam > London > NYC > Chicago

Code Select Expand

Show Level 3 (Dallas, TX (IPv6)) Traceroute to 2001:470:0:6E::2

 1 tu-635.sar1.Washington1.Level3.net (2001:1900:4:1::D) 32 msec 36 msec 36 msec
 2 2001:1900:6:1::9 108 msec 108 msec 112 msec
 3 2001:7F8:4::CB9:1 108 msec 112 msec 160 msec
 4 xe-10-3-0.fra20.ip6.tinet.net (2001:668:0:2::1:1241) 124 msec 184 msec
   xe-8-3-0.lon20.ip6.tinet.net (2001:668:0:2::1:1651) 112 msec
 5 de-cix.he.net (2001:7F8::1B1B:0:1) 272 msec
   xe-9-3-0.fra20.ip6.tinet.net (2001:668:0:2::1:1231) 136 msec
   de-cix.he.net (2001:7F8::1B1B:0:1) 272 msec
 6 de-cix.he.net (2001:7F8::1B1B:0:1) 272 msec
   10gigabitethernet1-4.core1.ams1.he.net (2001:470:0:47::1) 272 msec 272 msec
 7 10gigabitethernet1-4.core1.ams1.he.net (2001:470:0:47::1) 272 msec
   10gigabitethernet1-4.core1.lon1.he.net (2001:470:0:3F::1) 272 msec 272 msec
 8 10gigabitethernet1-4.core1.lon1.he.net (2001:470:0:3F::1) 272 msec 272 msec 272 msec
 9 10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3E::1) 276 msec
   10gigabitethernet1-2.core1.chi1.he.net (2001:470:0:4E::1) 292 msec 296 msec
10 10gigabitethernet1-2.core1.chi1.he.net (2001:470:0:4E::1) 300 msec 300 msec 300 msec
11 1g-bge0.tserv9.chi1.ipv6.he.net (2001:470:0:6E::2) 296 msec 292 msec 292 msec


IPv4 Peering would be awesome too.  28ms extra isn't that bad though. 
From Level3 Chicago to tserv9.chi1.ipv6.he.net.  Chicago > NYC > Chicago

Code Select Expand

Show Level 3 (Chicago, IL) Traceroute to 209.51.181.2

  1 ae-13-51.car3.Chicago1.Level3.net (4.68.101.7) 0 msec
    ae-13-55.car3.Chicago1.Level3.net (4.68.101.135) 0 msec
    ae-23-54.car3.Chicago1.Level3.net (4.68.101.103) 4 msec
  2 glbx-level3-te.Chicago1.level3.net (4.68.110.194) 0 msec 0 msec 0 msec
  3 HURRICANE-ELECTRIC-LLC-Ashburn.TenGigabitEthernet4-4.ar3.DCA3.gblx.net (64.214.121.170) [AS3549 {GBLX}] 24 msec 20 msec 20 msec
  4 10gigabitethernet1-2.core1.nyc4.he.net (72.52.92.85) [AS6939 {HURRICANE}] 28 msec 28 msec 28 msec
  5 10gigabitethernet1-2.core1.chi1.he.net (72.52.92.102) [AS6939 {HURRICANE}] 32 msec 28 msec 28 msec
  6 tserv9.chi1.ipv6.he.net (209.51.181.2) [AS6939 {HURRICANE}] 24 msec 28 msec 28 msec



[mleber]

Please retest. ;)

[brad]

Please retest. ;)

Wow. Peering with Leve3 before Cogent *draw drops* heh. I see there is now peering in San Jose/Chicago/New York. Are you guys going to attempt to turn up peering at other locations such as Los Angeles/Dallas/Atlanta or European cities like London/Amsterdam/Frankfurt?

[mtindle]

We can't comment on future peering until they're in place.  However, if you have a specific routing you're interested in, please post some traceroutes.  We can look into them and discuss other peering locations with our peers.