<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 21/Jun/20 22:21, Robert Raszuk
wrote:<br>
<br>
</div>
<blockquote type="cite"
cite="mid:CAOj+MMGcQksFkFwtRubjjn7BHchtO8FiwSG=hyAw60o0NxBoNw@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote"><br>
<div>Well this is true for one company :) Name starts with j
.... </div>
<div><br>
</div>
<div>Other company name starting with c - at least some time
back by default allocated labels for all routes in the RIB
either connected or static or sourced from IGP. Sure you
could always limit that with a knob if desired. <br>
</div>
</div>
</div>
</blockquote>
<br>
<br>
Juniper allocates labels to the Loopback only.<br>
<br>
Cisco allocates labels to all IGP and interface routes.<br>
<br>
Neither allocate labels to BGP routes for the global table.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAOj+MMGcQksFkFwtRubjjn7BHchtO8FiwSG=hyAw60o0NxBoNw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>The issue with allocating labels only for BGP next hops
is that your IP/MPLS LFA breaks (or more directly is not
possible) as you do not have a label to PQ node upon
failure. Hint: PQ node is not even running BGP :). <br>
</div>
</div>
</div>
</blockquote>
<br>
Wouldn't T-LDP fix this, since LDP LFA is a targeted session?<br>
<br>
Need to test.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAOj+MMGcQksFkFwtRubjjn7BHchtO8FiwSG=hyAw60o0NxBoNw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>Sure selective folks still count of "IGP Convergence" to
restore connectivity. But I hope those will move to much
faster connectivity restoration techniques soon. <br>
</div>
</div>
</div>
</blockquote>
<br>
We are happy :-).<br>
<br>
Mark.<br>
</body>
</html>