Trouble reaching whois.ripe.net and www.ietf.org
Marc.Williams at neustar.biz
Tue Oct 17 16:33:41 CEST 2006
Alexander / Stig,
Currently, access to www.ietf.org is via a single tunnel from
OCCAID in Ashburn, VA. Are you aware of any carrier out there who
would be willing and well equiped to provide redundant access to IETF
for cases like this? Perhaps we could have supressed advertisement of
our prefixes toward the trouble.
> -----Original Message-----
> ipv6-ops-bounces+wan.engineering=neustar.biz at lists.cluenet.de
> [mailto:ipv6-ops-bounces+wan.engineering=neustar.biz at lists.clu
enet.de] On Behalf Of Alexander Koch
> Sent: Tuesday, October 17, 2006 10:13 AM
> To: Stig Venaas
> Cc: ipv6-ops at lists.cluenet.de
> Subject: Re: Trouble reaching whois.ripe.net and www.ietf.org
> is GEANT peering with anyone at all except for the few
> transits they have? Sure, their customers, but unless they
> really peer I would say kick them, too. I know some
> disclaimers here, so I better shut up now.
> Also happy to do native v6 with 2603 at Netnod GE-A/B if you
> are there, piece of cake it seems to me. Ignore the GEANT bit
> there, it sucks anyway (scnr). YMMV.
> Also L3 will be much more native soon, that should also just fix it.
> preferring the practical approach
> On Tue, 17 October 2006 09:59:52 +0200, Stig Venaas wrote:
> > whois.ripe.net has address 2001:610:240:0:193::202. We get
> this as a
> > /42 prefix via GEANT, Level 3, and Tiscali:
More information about the ipv6-ops