Canarie / 2001:410::/32 (Was: Filters) (fwd)

[Bernhard Schmidt]

Hi,

> Thanks to Jeroen's fine forensic work, looks like some AS's are having
> some problems between each other.  Of course, none of this would have
> been noticed had my prospective peering with sixxs.net not been tested
> first with a simple traceroute.
> 
> In short, I cannot reach 2001:838:1:1:210:dcff:fe20:7c7c from, for
> example, 2001:410:9000:127::10.

Canarie seems to be a downstream of Abilene. Abilene seems to have a
funny routing policy, to say the least. When looking at the paths of the
Canarie prefix

http://www.sixxs.net/tools/grh/lg/?find=2001:410::/32

or the Viagenie one

http://www.sixxs.net/tools/grh/lg/?find=2001:468::/32

I'm not able to make out an upstream. The international connectivity
seems to be mostly done by sending those routes to other NRENs in the
APNIC region and then sent to some "strategic" routeswappers (AS6939 for
example). Inbound routes to Abilene are strange as well, for a newly
advertised prefix Abilene sees

11537 17579 9270 7660 2500 1273 680 12816

Europe - Asia - America

Abilene seems to take what they get (even if it doesn't make sense at
all) and trust the forces of routeswap to get their own prefixes
visible. This mostly works (with long paths, in special occasions
several times around the globe), but sometimes doesn't. The prefix I'm
talking about above had a loooong path from Abilene through es.net this
noon, with es.net happily advertising but then sending "destination
unreachable" for every packet following that path.

Those who are downstream customers of the few ASNs peering with Abilene
(GBLX, Verio, ISC) can be happy here, for all others the available paths
are pure crap.

I can't currently see any decent service provided by Abilene. GEANT
being the european REN isn't that much better.

Bernhard