[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
How to choose a transport(terrestrial/subsea)
- Subject: How to choose a transport(terrestrial/subsea)
- From: alfie at fdx.services (Alfie Pates)
- Date: Wed, 02 Jan 2019 17:14:16 +0000
- In-reply-to: <1070675904.7469.1545939242369.JavaMail.mhammett@ThunderFuck>
- References: <CA+LTh5XNVZSs00BCpngcPSMfo67O-=CsCEsH7HvPJbvYBGHWrA@mail.gmail.com> <[email protected]> <805398887.1927.1544870668800.JavaMail.mhammett@ThunderFuck> <[email protected]> <782357206.2397.1544892820238.JavaMail.mhammett@ThunderFuck> <[email protected]> <788457847.2761.1544902202755.JavaMail.mhammett@ThunderFuck> <CA+LTh5X-jhb1+0nENKEvGk=drVf4Sa_GH4_52w2P7O1A1OFuqQ@mail.gmail.com> <1070675904.7469.1545939242369.JavaMail.mhammett@ThunderFuck>
I'm of the opinion that, if you need resiliency, you should order
explicitly diverse circuits from a primary provider and then a secondary
circuit from a second vendor.
Ultimately, If you want contractually-enforced physical diversity then
the best options will be single-vendor solutions: Obviously you also
want to avoid an unknown single-vendor single-point-of-failure, hence
the secondary provider. Having two vendors is usually a less than
optimal solution since neither has visibility into the others' network
to ensure the physical diversity required for a truly resilient service:
what happens if an undersea cable is cut, etc?
The cost of such solutions is often unpleasant to justify, mind.
~a
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190102/d78b5990/attachment.html>