[97937] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Carrier Recommendations

daemon@ATHENA.MIT.EDU (Timothy McKee)
Sat Jul 21 09:48:13 2007

In-Reply-To: <OFDB2D0C2D.C36D4B75-ON8525731C.0081A458-8525731C.00826ACC@sungard.com>
Cc: Daniel <accesss801@gmail.com>, nanog@nanog.org, owner-nanog@merit.edu
From: Timothy McKee <tim@baseworx.net>
Date: Sat, 21 Jul 2007 09:46:11 -0400
To: Keegan.Holley@sungard.com
Errors-To: owner-nanog@merit.edu



--Apple-Mail-1-559941789
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

If this is for redundancy, also keep in mind that most 'cuts' occur  
in the last mile.  Unless you are in a major facility with engineered  
entrance/egress diversity a failure will result in ALL terrestrial  
links failing.  This is a very string argument for a limited  
bandwidth satellite or EVDO backup link.  (Which one depends on many  
other factors.)

Tim McKee
VP, Network Services
SDN Global <http://www.sdnglobal.com>

On Jul 18, 2007, at 7:44 PM, Keegan.Holley@sungard.com wrote:

>
> Hi Daniel,
>
> Could you provide a little more detail as to your requirements?   
> Bandwith, applications (voice, video, etc...) number of sites, that  
> sort of thing. On the surface the first thing that comes to mind is  
> redundancy.  You are going to have outages, especially if you have  
> to go that far point to point.  The best thing would be to have a  
> second circuit with another carrier on a diverse path.  The worst  
> thing is when both the primary circuit and the backup were ordered  
> through the same carrier and both go down during the came fiber  
> cut.  Worse still is when they were ordered from two different  
> carriers but carrier B actually bought bandwidth from carrier A  
> resulting in the same outcome.
>
>
>
> Daniel <accesss801@gmail.com>
> Sent by: owner-nanog@merit.edu
> 07/16/2007 05:37 PM
>
> To
> nanog@nanog.org
> cc
> Subject
> Carrier Recommendations
>
>
>
>
>
> All,
>
> I am currently in the process of evaluating carriers for future  
> expansion into international regions, primarily Asia, Europe and  
> South America.
>
> I am comfortable with AT&T and Verizon however I would like to make  
> sure I include all the major players and would like your direct  
> feedback and commentary in regards to any of them.
>
> These are the key areas I am concerned with.
>
> Support
> Reliability
> Flexibility
> Complexity
> Coverage
>
> I am looking at two deployment options as well if anyone would like  
> to comment.
>
> 1) A single carrier for global connectivity to all sites (mpls etc)
>
> 2) A single carrier for global regional connectivity, and in  
> country/regional carriers for all local offices that funnel back to  
> regional aggregation points.
>
> Any insight would be greatly appreciated.
>
> Thanks, Daniel
>

=====
Tim McKee




--Apple-Mail-1-559941789
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">If this is for redundancy, also =
keep in mind that most 'cuts' occur in the last mile.=A0 Unless you are =
in a major facility with engineered entrance/egress diversity a failure =
will result in ALL terrestrial links failing.=A0 This is a very string =
argument for a limited bandwidth satellite or EVDO backup link.=A0 =
(Which one depends on many other factors.)<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Tim McKee</DIV><DIV>VP, =
Network Services</DIV><DIV>SDN Global &lt;<A =
href=3D"http://www.sdnglobal.com">http://www.sdnglobal.com</A>&gt;</DIV><D=
IV><BR><DIV><DIV>On Jul 18, 2007, at 7:44 PM, <A =
href=3D"mailto:Keegan.Holley@sungard.com">Keegan.Holley@sungard.com</A> =
wrote:</DIV><BR class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><BR><FONT size=3D"2" face=3D"sans-serif">Hi Daniel,</FONT> =
<BR> <BR><FONT size=3D"2" face=3D"sans-serif">Could you provide a little =
more detail as to your requirements? =A0Bandwith, applications (voice, =
video, etc...) number of sites, that sort of thing. On the surface the =
first thing that comes to mind is redundancy. =A0You are going to have =
outages, especially if you have to go that far point to point. =A0The =
best thing would be to have a second circuit with another carrier on a =
diverse path. =A0The worst thing is when both the primary circuit and =
the backup were ordered through the same carrier and both go down during =
the came fiber cut. =A0Worse still is when they were ordered from two =
different carriers but carrier B actually bought bandwidth from carrier =
A resulting in the same outcome.</FONT> <BR> <BR> <BR> <BR> <TABLE =
width=3D"100%"> <TBODY><TR valign=3D"top"><TD width=3D"40%"><FONT =
size=3D"1" face=3D"sans-serif"><B>Daniel &lt;<A =
href=3D"mailto:accesss801@gmail.com">accesss801@gmail.com</A>&gt;</B> =
</FONT> <BR><FONT size=3D"1" face=3D"sans-serif">Sent by: <A =
href=3D"mailto:owner-nanog@merit.edu">owner-nanog@merit.edu</A></FONT><P><=
FONT size=3D"1" face=3D"sans-serif">07/16/2007 05:37 PM</FONT> =
</P></TD><TD width=3D"59%"> <TABLE width=3D"100%"> <TBODY><TR =
valign=3D"top"><TD> <DIV align=3D"right"><FONT size=3D"1" =
face=3D"sans-serif">To</FONT></DIV> </TD><TD><FONT size=3D"1" =
face=3D"sans-serif"><A =
href=3D"mailto:nanog@nanog.org">nanog@nanog.org</A></FONT> </TD></TR><TR =
valign=3D"top"><TD> <DIV align=3D"right"><FONT size=3D"1" =
face=3D"sans-serif">cc</FONT></DIV> </TD><TD> </TD></TR><TR =
valign=3D"top"><TD> <DIV align=3D"right"><FONT size=3D"1" =
face=3D"sans-serif">Subject</FONT></DIV> </TD><TD><FONT size=3D"1" =
face=3D"sans-serif">Carrier =
Recommendations</FONT></TD></TR></TBODY></TABLE> <BR> <TABLE> <TBODY><TR =
valign=3D"top"><TD> </TD><TD></TD></TR></TBODY></TABLE> =
<BR></TD></TR></TBODY></TABLE> <BR> <BR> <BR><FONT size=3D"3">All,<BR> =
<BR> I am currently in the process of evaluating carriers for future =
expansion into international regions, primarily Asia, Europe and South =
America.<BR> <BR> I am comfortable with AT&amp;T and Verizon however I =
would like to make sure I include all the major players and would like =
your direct feedback and commentary in regards to any of them. <BR> <BR> =
These are the key areas I am concerned with.<BR> <BR> Support<BR> =
Reliability<BR> Flexibility<BR> Complexity<BR> Coverage<BR> <BR> I am =
looking at two deployment options as well if anyone would like to =
comment.<BR> <BR> 1) A single carrier for global connectivity to all =
sites (mpls etc)<BR> <BR> 2) A single carrier for global regional =
connectivity, and in country/regional carriers for all local offices =
that funnel back to regional aggregation points. <BR> <BR> Any insight =
would be greatly appreciated.<BR> <BR> Thanks, Daniel<BR> </FONT> =
<BR></BLOCKQUOTE></DIV><BR><DIV> <SPAN class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px 0px; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><SPAN =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; =
"><DIV>=3D=3D=3D=3D=3D</DIV><DIV>Tim<SPAN =
class=3D"Apple-converted-space">=A0</SPAN>McKee</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><BR =
class=3D"Apple-interchange-newline"></SPAN></SPAN> =
</DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-1-559941789--


home help back first fref pref prev next nref lref last post