<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 17/Jun/20 20:40, Dave Bell wrote:<br>
<br>
<br>
</div>
<blockquote type="cite"
cite="mid:CACXVQYCs6Bf5QFDL_2GicorhVx0gqp-vP2u9c2cTjGJYQuK_Rw@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<div>I don't understand the point of SRv6. What equipment can
support IPv6 routing, but can't support MPLS label
switching?</div>
</div>
</div>
</blockquote>
<br>
Indeed. <br>
<br>
Anything that can support LDPv4 today can support LDPv6, in
hardware.<br>
<br>
SRv6 and SRv6+ is a whole other issue, not to mention the amount of
work needed to write code for it.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CACXVQYCs6Bf5QFDL_2GicorhVx0gqp-vP2u9c2cTjGJYQuK_Rw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div>Not just this, but the LFA path is always the
post-convergence path. You don't get microloops.</div>
<div><br>
</div>
<div>You can implement TE on top if that is your thing. No
need to run RSVP. Another protocol you don't need to run.</div>
<div><br>
</div>
<div>You don't need to throw out all your old kit, and replace
with new in one go. You can incrementally roll it out, and
leave islands of LDP where needed. LDP-SR interworking is
pretty simple.</div>
<div><br>
</div>
<div>We are currently introducing it into our core. It will
probably be a while before we fully phase out LDP, but its
definitely on the roadmap.</div>
</div>
</div>
</blockquote>
<br>
Happy to hear, and I have nothing against your choice if you are
happy with it.<br>
<br>
But for a network that may not see the need in spending cycles doing
yet-another roll out, it tastes funny when you are forced down a new
path.<br>
<br>
Mark.<br>
</body>
</html>