A study on community-triggered updates in BGP

[Maria Matějka]

Hello!

If I read your paper correctly, I assume that this is just a feature of the BGP itself. To make it clear: I read that in some cases when a link inside one AS goes down, a route is reannounced with the same AS path but different communities because of e.g. some internal tagging which you call duplicate. Please correct me if I'm wrong.

This is definitely something for the admin of that AS whether they want to share such an information outside or not. We can't say from a global perspective whether they shall or shan't reannounce that route. They may want to, they may not want to reannounce. It depends on lots of things. 

So from my perspective, as a developer of BIRD, this is a matter of configuration. If some of your routers do some tagging, it's your configuration as well as the configuration of the outbound router where you can strip these tags if you want.

BIRD shall be never smarter than its user.

There is also another thing that in case of egress filtering, BIRD may send a duplicate announcement if it is not sure about the contents of the previous route. From my point of view, it is a tradeoff. We save memory by not keeping the Adj-RIB-Out by default. This can be switched on by the "export table on" setting in the appropriate bgp channel with the cost of some memory overhead.

I hope I've answered you well, feel free to discuss or correct me if I misunderstood anything. 

Thank you for the research. BTW, do you have an estimation on how frequently does it happen? 

Maria


On October 17, 2020 1:43:54 AM GMT+02:00, Thomas Krenc <tkrenc at nps.edu> wrote:
>Dear BIRD users and developers,
>
>As a team of researchers from NPS and TU Berlin, we are investigating
>the impact of BGP community attributes on the update behavior between
>ASes.
>
>We find that when a route is associated with multiple distinct
>community
>attributes it does not only lead to multiple announcement at the
>tagging
>AS, but also at neighboring ASes, if communities are not filtered
>properly. This behavior is wide-spread.
>
>In order to better understand our observations, we have performed a
>series of laboratory experiments using Cisco IOS, Junos OS, as well as
>the BIRD daemon.
>
>We find that - by default - all routers generate announcements with
>changing community attributes, even when other attributes do not
>change.
>In addition, when communities are filtered at egress, Cisco und BIRD
>send duplicate announcements (Juniper does not).
>
>    Is this side-effect known to the BIRD community and would you
>consider it a bug or a feature?
>
>Since our findings are limited to observations in public data as well
>as
>few router implementations, we would like to share our research and
>kindly ask you to have a look at:
>
>    https://www.cmand.org/communityexploration/
>
>There, we provide some resources documenting our research, as well as
>open questions. We greatly appreciate any feedback and insights you can
>offer. Also, please don't hesitate to contact us directly:
>
>    communityexploration AT cmand DOT org
>
>best regards
>
>Thomas Krenc
>Postdoctoral Researcher
>Naval Postgraduate School

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20201017/6da9263c/attachment.htm>