Routing to ARIN from Teleglobe (2001:5a0::/32)

nenad pudar nenad.pudar at gmail.com
Sun Feb 11 23:18:30 CET 2007


I did not realize how many e-mails was exchanged on this subject.
Ross we do not peer with OCCAID
You are sourced from your /32 network that is why you see occaid gw.
I do not know whether C&W and Tisacali leaking the OCCAID routes or that is
done on purpose ("kind of semi-transit" solution )

For Teleglobe solution seems to be peering with OCCAID (I will talk to
peering comity about this )
Besides that both OCCAID and  Arin (multi homing) should be provide better
routing especially having in mind the number of important ipv6 networks
connected to their network .

nenad



On 2/11/07, Ross West <ipv6-ops at inet6.ca> wrote:
>
>
> Sunday, February 11, 2007, 11:44:51 AM, ipv6-ops at inet6.ca wrote:
>
> >>> OCCAID can't reach Teleglobe as it isn't in their routing tables.
>
> > Teleglobe can't reach OCCAID, OCCAID can't reach Teleglobe.  Hmm.  Maybe
> > they should peer?
>
> Actually, if I can add a bit to this argument as a transit customer of
> Teleglobe:
>
> traceroute6 to www.arin.net (2001:500:4:1::80) from 2610:38:1::e, 64 hops
> max, 1                                                  2 byte packets
> 1 (as7781)  2610:38:1::d  1.786 ms  1.773 ms  1.764 ms
> 2 (as6453) tunnel13.6bb1.nyy-newyork.ipv6.teleglobe.net  21.269 ms  21.342ms
> 20.930 m                                                  s
> 3 (as6453) if-15-0.mcore4.nqt-newyork.ipv6.teleglobe.net  21.275 ms
> 21.363 ms  21.263                                                   ms
> 4 (as6453) 2001:5a0:600:200::6  26.847 ms  26.770 ms  26.713 ms
> 5 (as6453) 2001:5a0:600::5  26.972 ms  26.449 ms  26.916 ms
> 6 (as30071) equi6ix-ash.ipv6.us.occaid.net  36.349 ms  36.828 ms  36.535ms
> 7 (as30071) arin-gw1.customer.occaid.net  36.697 ms  37.032 ms  36.697 ms
> 8  * * *
>
> Teleglobe/Occaid does have peering - and has had it for a while.
>
> But my return route (from as30071 according to grh) is via Sprint
> (as6175), and since 2001:5a0::/32 isn't in grh for Occaid, I'd
> probably suspect that the route announcements at Equinix is one way
> (teleglobe sees occaid, but occaid doesn't see teleglobe).
>
>
> Cheers,
>   Ross.
>
> --
> Ross West - doin' ipv6 in Canada.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20070211/26ec0716/attachment.htm>


More information about the ipv6-ops mailing list