<html>
<head>
</head>
<body>
<div style="color: black;">
<div style="color: black;">
<p style="margin: 0 0 1em 0; color: black;">+Thomas to be on track.</p>
</div>
<div style="color: black;">
<p
style="color: black; font-size: 10pt; font-family: Arial, sans-serif; margin: 10pt 0;">Le
18 mars 2017 06:19:47 Vivek Venkatraman <vivek@cumulusnetworks.com> a
écrit :</p>
<blockquote type="cite" class="gmail_quote"
style="margin: 0 0 0 0.75ex; border-left: 1px solid #808080; padding-left: 0.75ex;">
<div dir="ltr">This is correct. By definition, if a router is the
penultimate hop, it means the actual egress is downstream and has signaled
(advertised) an implicit-null label to this router. The router doing the
PHP knows the next hop to forward to (the egress) without doing any
additional lookup.<div><br></div><div>This behavior should already be
supported.</div><div><br></div><div>What is not supported (if I remember
right) is the ability on the egress to terminate a label and perform a
(route) lookup. That is needed to really be able to support any L2/L3 VPN
service properly.</div></div><div class="gmail_extra"><br><div
class="gmail_quote">On Thu, Mar 16, 2017 at 10:45 AM, Jeff Tantsura <span
dir="ltr"><<a href="mailto:jefftant@gmail.com"
target="_blank">jefftant@gmail.com</a>></span> wrote:<br><blockquote
class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Donald,<br>
<br>
Wrt PHP, this is incorrect, PHP node MUST not perform IP lookup, or in fact
any lookup after POP. In most cases (labeled services, L2/L3 VPN)
there's another label(s) in the stack, looking it up would be fatal.<br>
<br>
Regards,<br>
Jeff<br>
<br>
> On Mar 15, 2017, at 08:05, Donald Sharp <<a
href="mailto:sharpd@cumulusnetworks.com">sharpd@cumulusnetworks.com</a>>
wrote:<br>
><br>
> David/Roopa -<br>
><br>
> Olivier asked me about these two issues yesterday in the FRR Technical<br>
> Meeting. I just wanted to make sure I didn't loose track of these<br>
> questions that he had:<br>
><br>
> 1) More than 2 labels in the kernel at a time, when will this be<br>
> allowed in the kernel?<br>
><br>
> -> David is currently working on this issue. When he is done it<br>
> will be upstreamed. So soonish(tm).<br>
><br>
> 2) PenUltimate Hop Popping:<br>
><br>
> I know this issue is not trivial to solve. In fact, once the POP<br>
> instruction perform, the packet must re-enter in the IP packet<br>
> processing to determine what action must apply. A possible solution<br>
> would be to process this packet as a new incoming IP packet when<br>
> output interface is the loopback disregarding the IP address value.<br>
> But, this issue is less urgent than the first one. Our OSPF Segment<br>
> Routing implementation could announce if the router works in<br>
> PenUltimate Hop Poping mode or not. So, for the moment, the option is<br>
> force to yes.<br>
><br>
> thanks!<br>
><br>
> donald<br>
><br>
> ______________________________<wbr>_________________<br>
> frr mailing list<br>
> <a href="mailto:frr@lists.nox.tf">frr@lists.nox.tf</a><br>
> <a href="https://lists.nox.tf/listinfo/frr" rel="noreferrer"
target="_blank">https://lists.nox.tf/listinfo/<wbr>frr</a><br>
<br>
______________________________<wbr>_________________<br>
frr mailing list<br>
<a href="mailto:frr@lists.nox.tf">frr@lists.nox.tf</a><br>
<a href="https://lists.nox.tf/listinfo/frr" rel="noreferrer"
target="_blank">https://lists.nox.tf/listinfo/<wbr>frr</a><br>
</blockquote></div><br></div>
_______________________________________________<br>
frr mailing list<br>
<a class="aqm-autolink aqm-autowrap"
href="mailto:frr%40lists.nox.tf">frr@lists.nox.tf</a><br>
<a class="aqm-autolink aqm-autowrap"
href="https://lists.nox.tf/listinfo/frr">https://lists.nox.tf/listinfo/frr</a><br>
</blockquote>
</div>
</div>
</body>
</html>