<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 12/Dec/18 09:32, Andrew Alston
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:77F09551-C6DF-44BE-B54D-3DF61AA87383@liquidtelecom.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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Yeah – I get
that – but to what advantage is what Im trying to
understand.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">SR-MPLS vs
SRv6 – the only difference between the two is that in one
case you are using a label stack on the outside of the
packet – in the other you are encoding in EH. If you encode
in EH – you introduce packets with variable length headers
that create ASIC issues and other issues – vs – simply
handling a label stack.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Everything
else – the rsvp-te, the ldp, all that other crap –
disappears both ways – so why would anyone want to switch
the labels to EH – whats the rationale behind it – that’s
what I don’t understand</span></p>
</div>
</blockquote>
<br>
The claim is that since the EH being used in SRv6, you can have
128-bit sized SID's, while with SR-MPLS, you have just 32-bit sized
SID's.<br>
<br>
The extra "space" means that you can now do more things with SRv6
than just routing, e.g., the first 64 bits would be used for
routing, then next 32 bits used to impose some action on the
traffic, and the final 32 bits used to include some additional
information. In summary, the claim if you can add more "network
programmability (yuck!)" into the deployment.<br>
<br>
Mark.<br>
</body>
</html>