Re: Transit SLA
"Jere Retzer" <[email protected]> Thu, 17 Jul 2003 11:33:54 -0700
| Newsgroups | gmane.org.operators.rep |
|---|---|
| Message-ID | <[email protected]> |
This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_AAF48E07.98FB9D28 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Thanks for the excellent comments Dave. Very helpful. Dave Siegel wrote:=20 >>The only real con is that smaller exchange points just don't offer enough business opportunities to justify the CapEx and circuit cost to be present at the facility. Of course this is relevant to Global Crossing. Other companies may have different minimum=20 POP requirements and may be willing to tolerate support situations that don't work well for a larger carrier. Would you consider delivering transit across the exchange switch fabric? = In particular, for exchanges distributed in multiple metro data center = locations would you consider delivering transit from a data center where = you have a presence to a data center where the customer has a presence = using a dedicated (Global Crossing-Customer) exchange VLAN? What sorts of = issues/parameters enter into this decision from your perspective? The SLA = (see below) seems like it may enter into this question. I obtained an SLA from a large ISP. It has an exceptions clause, I suspect = like most that says the customer will not receive credit for any failure = or deficiency caused by "circumstances beyond (the ISP's) control," = including "unavailability of or interruption or delay in telecommunications= or third party services." Just like any telecommunications service, you = obvously cannot be held responsible for problems caused by a third party = not under your control. If you meet a customer in a third party data = center/POP, for example there is always a possibility the air conditioning = will fail or that someone will be clumsy in the common fiber meet-me room = and mangle your cross connect. You would normally, I think start counting = your performance for SLA purposes at the point where you hand the = circuit/data stream off from equipment you own/lease/operate to the = customer or a third party such as a local phone company or an exchange. = Does this make sense? From this perspective, would an EP be any different = than any other third party service provider? Thanks again for your help. Jere --=_AAF48E07.98FB9D28 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Description: HTML <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"= > <META content=3D"MSHTML 5.50.4727.700" name=3DGENERATOR></HEAD> <BODY style=3D"MARGIN-TOP: 2px; FONT: 12pt Verdana; MARGIN-LEFT: 2px"> <DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px">Thanks for the excellent = comments=20 Dave. Very helpful.</DIV> <DIV> </DIV> <DIV>Dave Siegel wrote: <BR><BR>>>The only real con is that = smaller=20 exchange points just don't offer<BR>enough business opportunities to = justify the=20 CapEx and circuit<BR>cost to be present at the facility. Of course = this is=20 relevant<BR>to Global Crossing. Other companies may have different = minimum=20 <BR>POP requirements and may be willing to tolerate support situations<BR>t= hat=20 don't work well for a larger carrier.</DIV> <DIV> </DIV> <DIV>Would you consider delivering transit across the exchange switch = fabric? In=20 particular, for exchanges distributed in multiple metro data center = locations=20 would you consider delivering transit from a data center where = you=20 have a presence to a data center where the customer has a=20 presence using a dedicated (Global=20 Crossing-Customer) exchange VLAN? What sorts of issues/parameters= =20 enter into this decision from your perspective? The SLA (see below) = seems=20 like it may enter into this question.</DIV> <DIV> </DIV> <DIV>I obtained an SLA from a large ISP. It has an exceptions = clause,=20 I suspect like most that says the customer will not receive credit for = any=20 failure or deficiency caused by "circumstances beyond (the ISP's) = control,"=20 including "unavailability of or interruption or delay in telecommunications= or=20 third party services." Just like any telecommunications service, you = obvously=20 cannot be held responsible for problems caused by a third party not under = your=20 control. If you meet a customer in a third party data center/POP, for = example=20 there is always a possibility the air conditioning will fail or that = someone=20 will be clumsy in the common fiber meet-me room and mangle your cross = connect.=20 You would normally, I think start counting your performance for = SLA=20 purposes at the point where you hand the circuit/data stream off from = equipment=20 you own/lease/operate to the customer or a third party such as a local = phone=20 company or an exchange. Does this make sense? From this perspective, would = an EP=20 be any different than any other third party service provider?</DIV> <DIV> </DIV> <DIV>Thanks again for your help.</DIV> <DIV> </DIV> <DIV>Jere<BR></DIV></BODY></HTML> --=_AAF48E07.98FB9D28--