[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

routing around Sprint's depeering damage

Subject: routing around Sprint's depeering damage
From: fw at deneb.enyo.de (Florian Weimer)
Date: Sun, 02 Nov 2008 16:40:00 +0100
In-reply-to: <[email protected]> (Seth Mattinen's message of "Sun, 02 Nov 2008 01:28:51 -0700")
References: <[email protected]> <[email protected]>

* 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:
- routing around Sprint's depeering damage
  - From: eugen at imacandi.net (Eugeniu Patrascu)

References:
- routing around Sprint's depeering damage
  - From: dfblaine at gmail.com (Dave Blaine)
- routing around Sprint's depeering damage
  - From: sethm at rollernet.us (Seth Mattinen)

Prev by Date: routing around Sprint's depeering damage
Next by Date: routing around Sprint's depeering damage
Previous by thread: routing around Sprint's depeering damage
Next by thread: routing around Sprint's depeering damage
Index(es):
- Date
- Thread