<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">PCRE or death. Tell me if I am wrong, but I thought PCRE was the most widely used regex lib these day anyways. I also thought it was already in Junos.<br><br><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On Aug 19, 2021, at 7:56 AM, Jeffrey Haas <jhaas@pfrc.org> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="Content-Type" content="text/html; charset=utf-8">ORFs are a challenging feature and haven't gotten a lot of deployment for a number of reasons.<div class=""><br class=""></div><div class="">At a high level, they're a very coarse filter. Since each new ORF type adds to the logical AND condition, you start having to be more and more permissive in what you permit in the policy. Since a significant amount of common ISP policies require matching things in tuples, this doesn't translate super well into many types of automatically generated ORFs.</div><div class=""><br class=""></div><div class="">The ext-community-orf feature was effectively supplanted by Rt-Constrain (RFC 4684).</div><div class=""><br class=""></div><div class="">The as-path ORF was challenging because different vendors have different ideas about what "regex" means and what the input tokens are. Consider for example Juniper vs. Cisco regex matching. The abstract fix would have been to define a regex that is for the feature. I half suspect if people pushed on this these days, they'd want PCRE. :-)</div><div class=""><br class=""></div><div class="">The RD-ORF work is part of some ongoing discussion about how to deal with VRF overwhelm (prefix-limit exceed).</div><div class=""><br class=""></div><div class="">-- Jeff (IDR co-chair)<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 18, 2021, at 1:10 PM, Douglas Fischer <<a href="mailto:fischerdouglas@gmail.com" class="">fischerdouglas@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hello!<br class=""><br class="">I also found a recent draft(expires Novembre 2021) about using Route Distinguisher as a Value on ORF.<div class=""><a href="https://datatracker.ietf.org/doc/draft-wang-idr-rd-orf/" class="">https://datatracker.ietf.org/doc/draft-wang-idr-rd-orf/</a><br class=""><br class=""><br class=""></div><div class=""><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em qua., 18 de ago. de 2021 às 11:41, Humberto Galiza <<a href="mailto:humbertogaliza@gmail.com" class="">humbertogaliza@gmail.com</a>> escreveu:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br class="">
<br class="">
Is anyone aware of any vendor that supports Outbound Route Filtering<br class="">
(ORF) based on anything other than prefix-lists?<br class="">
<br class="">
I found these two old IETF drafts (both expired :-/) which supported<br class="">
the idea of filtering based on community and as-path respectively, but<br class="">
I wasn't able to understand if they were ever discussed at the WG and<br class="">
if there was any outcome of the discussion (I suspect the authors are<br class="">
no longer even working with the mentioned companies in the drafts):<br class="">
<br class="">
- <a href="https://datatracker.ietf.org/doc/html/draft-chen-bgp-ext-community-orf-02" rel="noreferrer" target="_blank" class="">https://datatracker.ietf.org/doc/html/draft-chen-bgp-ext-community-orf-02</a><br class="">
- <a href="https://datatracker.ietf.org/doc/html/draft-ietf-idr-aspath-orf-13" rel="noreferrer" target="_blank" class="">https://datatracker.ietf.org/doc/html/draft-ietf-idr-aspath-orf-13</a><br class="">
<br class="">
Any info is very much appreciated.<br class="">
<br class="">
Thanks,<br class="">
</blockquote></div><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div dir="ltr" class="gmail_signature"><div dir="ltr" class="">Douglas Fernando Fischer<br class="">Engº de Controle e Automação<br class=""><div style="padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; text-align: left; line-height: 130%; font-family: "courier new", monospace;" class=""></div></div></div>
</div></blockquote></div><br class=""></div></div></blockquote></body></html>