North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: .ORG problems this evening
TV> Date: Thu, 18 Sep 2003 14:22:19 -0400 (EDT) TV> From: Todd Vierling TV> Sucks to be anyone trying to use the service whose routers TV> pick those nodes as the only ones available. That's the TV> fault of the implementor, not the client. Yes. TV> The major issue here is that no *gTLD*, particularly one of TV> the Big Three, should be subject to a SPOF -- even if it's TV> only a regionally visible SPOF Yes. TV> due to anycast selection. Which would be due to a broken implementation. Broken unicast is bad. Not all unicast is bad. Broken anycast is bad. Not all anycast is bad. TV> It should *always* be possible to attempt queries to more TV> than one physical location's servers for a gTLD. _Or_ guarantee that the physical location selected was indeed up. Again, it smells an awful lot like plain old multihoming... if you advertise the route, you'd better be ready to handle the traffic. (Did someone say "7007"?) TV> BGP errors happen (everyone here should be able to attest to TV> that readily), and they did. What's to stop some other TV> boneheaded DoS or oversight from causing this again? And TV> again? I've had problems with unicast when a link went down, yet the upstream continued advertising the routes. BGP stupidity happens with unicast service, too. Yes, anycast requires some additional thought and out-of-box thinking. But that doesn't make it inherently unstable. Eddy -- Brotsman & Dreger, Inc. - EverQuick Internet Division Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita _________________________________________________________________ DO NOT send mail to the following addresses : email@example.com -or- firstname.lastname@example.org -or- email@example.com Sending mail to spambait addresses is a great way to get blocked.