<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 20/Jun/20 17:12, Robert Raszuk
wrote:<br>
<br>
</div>
<blockquote type="cite"
cite="mid:CAOj+MMERSsgW5Bn7E0ktc94AhqTHaVemcjKAmABAiuJfBc6Acg@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote"><br>
<div>MPLS is not flow driven. I sent some mail about it but
perhaps it bounced. </div>
<div><br>
</div>
<div>MPLS LDP or L3VPNs was NEVER flow driven. </div>
<div><br>
</div>
<div>Since day one till today it was and still is purely
destination based. </div>
<div><br>
</div>
<div>Transport is using LSP to egress PE (dst IP). </div>
<div><br>
</div>
<div>L3VPNs are using either per dst prefix, or per CE or per
VRF labels. No implementation does anything upon "flow
detection" - to prepare any nested labels. Even in FIBs all
information is preprogrammed in hierarchical fashion well
before any flow packet arrives. <br>
</div>
</div>
</div>
</blockquote>
<br>
If you really don't like LDP or RSVP-TE, you can statically assign
labels and manually configure FEC's across your entire backbone. If
trading state for administration is your thing, of course :-).<br>
<br>
Mark.<br>
</body>
</html>