Re: routing around Sprint's depeering damage

• From: Florian Weimer
• Date: Sun Nov 02 10:41:21 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>

* Seth Mattinen:

> 4. Multihome.

Or get upstream from someone who does, and who is small enough to be
able to get additional upstream upon short notice.  I know that this
solution isn't always cost-effective. 8-/

(Multihoming alone isn't a solution because it's hard to figure out
how independent your peering partners are.)

• Follow-Ups:
  • Re: routing around Sprint's depeering damage Eugeniu Patrascu

• References:
  • routing around Sprint's depeering damage Dave Blaine
  • Re: routing around Sprint's depeering damage Seth Mattinen

• 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