<div dir="ltr">Thanks Jeffrey!<br><br>Well, I invested 15 minutes passing my eyes on the IDR list archive Joel mentioned(scary!).<br>You were very concise describing aaaall that discussion in such polide way.<br><br>I agree that without combining prefix-list and as-path, the effectiveness of ORF, considering its initial purpose, the pros and cons does not pay themselves.<br><br><br>But (there is always a but), I was imagining a different use for ext-community-orf !<div><br></div><div>Considering scenarios like:<br> -
Route-Servers of big IXPs, now days with almost 200K routes.<br> - Transit providers sending its own point of view of DFZ with almos 900K routes.<br>On both cases, informative communities are an excelente way to decide "what is good for my ASN, and what is not".</div><div><br>Yes, I know that is possible to filter based on that after receiving those routes.<br><div>But it takes computational effort on both sides to do that.<br>And I imagine that comparing to AS-Path Regex, the needed computational effort and the complexity of the logics to do filtering based on community-list are much smaller.<br></div><div><br></div><br>So, if I could say:<br> "Hey Mr. Route-Server... how are you?<br> Could you please not send-me the routes that are tagged with the community <RS-ASN:xyz>?<br> And after that, send-me just the routes that are tagged with the community <RS-ASN:abc>?"<br>In a Route-Server context, beyond reduce the number of BGP Messages that would be great for the CPU/Memory consumption both, RS and RS-Client.</div><div><br><div>Or, in a Transit context...<br>1 - Customer opens a ticket with support team to set the export filter to send only default-route.<br>2 - Customer, 5 days later, opens a ticket with support team re-adjust the export filter, now sending full-routing.<br></div><div>3 - Customer, on next month, opens another ticket with support team to send only the cone at right of the ASN of ITP.<br>With a good and public informative communities policy and ext-community-orf, the transit customer could change what his router will receive from the BGP transit Peer, depending only on himself.</div><div><br><br>Well... I don't really know how complex is to deal with that again on a WG.<br>But I would like to see that.<br><br><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em qua., 18 de ago. de 2021 às 20:11, Jeffrey Haas <<a href="mailto:jhaas@pfrc.org">jhaas@pfrc.org</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">ORFs are a challenging feature and haven't gotten a lot of deployment for a number of reasons.<div><br></div><div>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><br></div><div>The ext-community-orf feature was effectively supplanted by Rt-Constrain (RFC 4684).</div><div><br></div><div>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><br></div><div>The RD-ORF work is part of some ongoing discussion about how to deal with VRF overwhelm (prefix-limit exceed).</div><div><br></div><div>-- Jeff (IDR co-chair)<br><div><br><blockquote type="cite"><div>On Aug 18, 2021, at 1:10 PM, Douglas Fischer <<a href="mailto:fischerdouglas@gmail.com" target="_blank">fischerdouglas@gmail.com</a>> wrote:</div><br><div><div dir="ltr">Hello!<br><br>I also found a recent draft(expires Novembre 2021) about using Route Distinguisher as a Value on ORF.<div><a href="https://datatracker.ietf.org/doc/draft-wang-idr-rd-orf/" target="_blank">https://datatracker.ietf.org/doc/draft-wang-idr-rd-orf/</a><br><br><br></div><div><br></div></div><br><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" target="_blank">humbertogaliza@gmail.com</a>> escreveu:<br></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>
<br>
Is anyone aware of any vendor that supports Outbound Route Filtering<br>
(ORF) based on anything other than prefix-lists?<br>
<br>
I found these two old IETF drafts (both expired :-/) which supported<br>
the idea of filtering based on community and as-path respectively, but<br>
I wasn't able to understand if they were ever discussed at the WG and<br>
if there was any outcome of the discussion (I suspect the authors are<br>
no longer even working with the mentioned companies in the drafts):<br>
<br>
- <a href="https://datatracker.ietf.org/doc/html/draft-chen-bgp-ext-community-orf-02" rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/html/draft-chen-bgp-ext-community-orf-02</a><br>
- <a href="https://datatracker.ietf.org/doc/html/draft-ietf-idr-aspath-orf-13" rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/html/draft-ietf-idr-aspath-orf-13</a><br>
<br>
Any info is very much appreciated.<br>
<br>
Thanks,<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr">Douglas Fernando Fischer<br>Engº de Controle e Automação<br><div style="padding:0px;margin-left:0px;margin-top:0px;overflow:hidden;text-align:left;line-height:130%;font-family:"courier new",monospace"></div></div></div>
</div></blockquote></div><br></div></div></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Douglas Fernando Fischer<br>Engº de Controle e Automação<br><div style="padding:0px;margin-left:0px;margin-top:0px;overflow:hidden;color:black;text-align:left;line-height:130%;font-family:"courier new",monospace"></div></div></div>