Re: routing around Sprint's depeering damage

• From: Larry Sheldon
• Date: Sun Nov 02 10:51:39 2008

• List-archive: <http://mailman.nanog.org/pipermail/nanog>
• List-help: <mailto:[email protected]?subject=help>
• List-id: North American Network Operators Group <nanog.nanog.org>
• List-post: <mailto:[email protected]>
• List-subscribe: <http://mailman.nanog.org/mailman/listinfo/nanog>, <mailto:[email protected]?subject=subscribe>
• List-unsubscribe: <http://mailman.nanog.org/mailman/listinfo/nanog>, <mailto:[email protected]?subject=unsubscribe>

If things were truly operating as designed the internet would be able to automatically route around this depeering..the problem is not only do these two depeer but they also totally block any other traffic coming in from the other side. This is not how things should be done..disconnect the peering but let the traffic get automatically route around the disruption as it should.

• References:
  • routing around Sprint's depeering damage Dave Blaine
  • Re: routing around Sprint's depeering damage Larry Sheldon
  • Re: routing around Sprint's depeering damage Marc Farnum Rendino
  • RE: routing around Sprint's depeering damage James Jun
  • Re: routing around Sprint's depeering damage William Warren

• Prev by Date: Re: routing around Sprint's depeering damage
• Next by Date: Re: routing around Sprint's depeering damage
• Date Index
• Thread Index
• Author Index
• Historical