<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 18/Jul/20 15:31,
<a class="moz-txt-link-abbreviated" href="mailto:adamv0025@netconsultings.com">adamv0025@netconsultings.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:113c01d65d07$cbb8f9e0$632aeda0$@netconsultings.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Well
luckily we have MEF to set expectations about ones
EPL/EVPL/EPLAN/EVPLAN performance. (and formal SLA contracts
describing every single aspect of the service and its
performance).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Anyways,
when I was designing these the back in the days when it was
cool and demand was high, customers (other carriers) were
getting MTU9100 (to fit customers MTU9000), the whole CFM
& LFM shebang (to the point made earlier in the thread
that the link should go down on both ends -like it’s the
case with a wave) and sub 50ms convergence in case something
when wrong inside our backbone. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">We
as a provider </span>got more $$$ from single investment to
our wave/fiber, but our customers could enjoy p2p links on par
with wave for less $.</p>
</div>
</blockquote>
<br>
It's probably worth noting that easily 90% of all remote peering
circuits are running over an EoMPLS service, FWIW.<br>
<br>
Mark.<br>
</body>
</html>