Trouble reaching whois.ripe.net and www.ietf.org

[Stig Venaas]

I'm getting fed up with this broken routing... We can't reach either of 
whois.ripe.net or www.ietf.org at the moment.

whois.ripe.net has address 2001:610:240:0:193::202. We get this as a /42 
prefix via GEANT, Level 3, and Tiscali:

*> 2001:610:240::/42
                     2001:948:0:F042::1
                                                            0 2603 20965 
3356 3257 3333 i

Our best connectivity to RIPE would probably be via SURFnet from which 
we get 2001:610::/32, but we end up using this more specific. Not only
is the path in-optimal, but it appears to stop in level3's network.

For www.ietf.org, the prefix 2001:503:C779::/48 is used and the story
is similar. We get an in-optimal path, and it again seems to stop in
level3.

*> 2001:503:C779::/48
                     2001:948:0:F042::1
                                                            0 2603 20965 
3356 30071 7786 i

Use of these longer prefixes for critical infrastructure seems like a 
bad idea to me. Due to many people filtering these, the paths are at 
best in-optimal, and in this case not working at all.

I assume you guys see similar things?

Stig