<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<span style="font-size: 12pt;">I fully agree here too. That's why I proposed a "smarter" CPE to replace the standard appliances deployed on site, where the only thing changing is the configuration on the device itself, not product being handed off.</span></div>
<div class="elementToProof">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Ryan Hamel</div>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> NANOG <nanog-bounces+ryan=rkhtech.org@nanog.org> on behalf of Mark Tinka <mark@tinka.africa><br>
<b>Sent:</b> Wednesday, June 14, 2023 10:31 PM<br>
<b>To:</b> nanog@nanog.org <nanog@nanog.org><br>
<b>Subject:</b> Re: 10G CPE w/VXLAN - vendors?</font>
<div> </div>
</div>
<div>
<table border="0" cellspacing="0" cellpadding="0" align="left" width="100%">
<tbody>
<tr>
<td style="background:#ff0000; padding:5pt 2pt 5pt 2pt"></td>
<td width="100%" cellpadding="7px 6px 7px 15px" style="background:#ff000; padding:5pt 4pt 5pt 12pt; word-wrap:break-word">
<div style="color:#000000"><span style="color:#000000; font-weight:bold">Caution:</span> This is an external email and may be malicious. Please take care when clicking links or opening attachments.
</div>
</td>
</tr>
</tbody>
</table>
<br>
<div><br>
<br>
<div class="x_moz-cite-prefix">On 6/14/23 21:16, Joe Freeman wrote:<br>
<br>
</div>
<blockquote type="cite">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:Verdana}
@font-face
{}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
span.x_EmailStyle19
{font-family:"Verdana",sans-serif;
color:windowtext}
.x_MsoChpDefault
{font-size:10.0pt}
div.x_WordSection1
{}
-->
</style>
<div class="x_WordSection1">
<p class="x_MsoNormal"><span style="font-family:"Verdana",sans-serif">I think you�re probably overthinking this a bit.</span></p>
<p class="x_MsoNormal"><span style="font-family:"Verdana",sans-serif"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Verdana",sans-serif">Why do you need to extend your vxlan/evpn to the customer premise? There are a number of 1G/10G even 100G CPE demarc devices out there that push/pop tags, even q-in-q, or 802.1ad. Assuming
you have some type of aggregation node you bring these back to, tie those tags to the appropriate EVPN instance at the aggregation point. Don�t extend anything but a management tag and an S-tag essentially to the device at the customer premise.</span></p>
<p class="x_MsoNormal"><span style="font-family:"Verdana",sans-serif"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Verdana",sans-serif">You can even put that management tagged vlan in it�s own L3 segment, or a larger L3 network and impose security. This way you�re not exposing your whole service infrastructure to a bad actor
that might unplug your cpe device and plug into your network directly.</span></p>
</div>
</blockquote>
<br>
The reason customers ask that their site be part of the customer's Metro-E backbone is so that they can enjoy link redundancy without paying for it.<br>
<br>
Operators will generally have east and west links coming out of a Metro-E site. Customers who single-home into this device only have their last mile as the risk. But if the operator drops a Metro-E node into the customer's site, and cables it per standard,
the customer has the benefit of last mile redundancy, because the internal fibre/copper patch to the operator's Metro-E switch does not really count as a (risky) last mile.<br>
<br>
Sales people like to do this to engender themselves with the customer. <br>
<br>
Customers like to do this to get a free meal.<br>
<br>
Don't do it, because customer's always assume that that Metro-E node that is in their building "belongs to them".<br>
<br>
Mark.<br>
</div>
</div>
</body>
</html>