Experiences with IPv6 peering?

[Jon Harald Bøvre]

Trace through Tata (AS6453) OK

traceroute6 2001:550:2:49::1:2
traceroute to 2001:550:2:49::1:2 (2001:550:2:49::1:2) from 
2a02:270:ff:2::150, 30 hops max, 16 byte packets
  1  2a02:270:ff:2::1 (2a02:270:ff:2::1)  0.988 ms  0.781 ms  0.722 ms
  2  Vl3255.ocjha2-520-060.as41572.net (2a02:270:0:4::23)  3.031 ms  
2.83 ms  2.903 ms
  3  Vl1505.ocjha2-520-070.as41572.net (2a02:270:0:2::4)  2.994 ms  2.82 
ms  2.801 ms
  4  Vl1506.ooe121-520-070.as41572.net (2a02:270:0:2::)  2.898 ms  2.802 
ms  2.833 ms
  5  ix-0-2.core2.OS1-Oslo.ipv6.as6453.net (2001:5a0:2c00::c)  3.035 ms  
2.808 ms  2.829 ms
  6  if-xe-10-3-0.0.tcore2.AV2-Amsterdam.ipv6.as6453.net 
(2a01:3e0:ff40:200::1d)  37.308 ms  38.087 ms  38.941ms
  7  if-0-1-0.3223.mcore3.LDN-London.ipv6.as6453.net 
(2a01:3e0:ff40:200::e)  53.441 ms  54.378 ms  54.239 ms
  8  2001:5a0:c00:600::1 (2001:5a0:c00:600::1)  55.789 ms  53.947 ms  
54.419 ms
  9  2001:5a0:c00:600::12 (2001:5a0:c00:600::12)  69.461 ms  56.665 ms  
72.217 ms
10  te0-3-0-4.ccr21.bos01.atlas.cogentco.com (::ffff:154.54.30.129)  
167.092 ms  159.673 ms  156.189 ms
11  te0-5-0-5.mpd22.ord01.atlas.cogentco.com (::ffff:154.54.42.249)  
156.854 ms  157.16 ms  157.771 ms
12  te0-3-0-1.mpd22.mci01.atlas.cogentco.com (::ffff:154.54.7.165)  
159.069 ms  161.986 ms  163.53 ms
13  te3-3.mpd01.dfw01.atlas.cogentco.com (::ffff:154.54.5.157)  164.954 
ms  168.536 ms  166.772 ms
14  te2-8.mpd01.dfw03.atlas.cogentco.com (::ffff:154.54.7.38)  167.393 
ms  166.665 ms  165.043 ms
15  2001:550:2:49::1:1 (2001:550:2:49::1:1)  163.373 ms  165.523 ms  
166.128 ms
16  2001:550:2:49::1:2 (2001:550:2:49::1:2)  167.6 ms  164.642 ms  
164.503 ms

Cogent not one of our transits.
Experience with Cogent: 2 years ago, negotiating new transit provider: 
Me Asking for IPv6. Answer: No, still many years before IPv6 will be 
implemented. Easy choice: Cogent, not an option for us.


Jon Harald Bovre
www.as41572.net


On 02.03.2011 17:27, Chase Venters wrote:
> I recently acquired my first native IPv6 address space for our 
> organization in the hopes that we could take a stab at participating 
> in World IPv6 day. Cogent provided the address space on connectivity 
> they provide us at the Dallas Infomart.
>
> The first thing I tried to do was to ping some of my addresses on 
> Hurricane Electric's tunnelbroker, which I use at home. "No Route". 
> Then I found this:
>
> http://ipv6.he.net/bgpview/24h_history/COGC-6NET-0001.html
>
> I contacted Hurricane Electric, who informed me that Cogent doesn't 
> have a path to them.
>
> The thought of being the "IPv6 engineer" in our firm and thusly being 
> the only one who wouldn't be able to access our site on world IPv6 day 
> is silly, but if I started putting in AAAA records that's just what 
> would happen.
>
> Is this par for the course with IPv6 peering? What kind of improvement 
> are we likely to see between now and June?
>
> We don't have any DNS magic like Google does (to try and hand out 
> AAAAs only to known good peers). We're using Dynect for DNS... they 
> support IPv6 but I don't think they have anything like Google's split 
> view technique implemented.
>
> If I publish AAAA records on World IPv6 day, will I just be cutting 
> off some IPv6 users from our site? (Never mind the 0.1% of IPv6-broken 
> users)
>
> I should point out that I'm not trying to point the finger at 
> Cogent... to their credit, our other provider advertises IPv6 but 
> their sales people inform me it's only available on an optical GigE 
> handoff and won't be available on smaller circuits until at least 
> 60-90 days. The Cogent program is specifically labelled "Beta" and we 
> had no problems participating.
>
> PS: If anyone is curious to ping me on Cogent, try 2001:550:2:49::1:2.
>
> Thanks,
> Chase
>
> -- 
> *Chase Venters*
> Exceleron Software
> +1-972-852-2718

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20110302/9c307f87/attachment.htm>