Hello Nigel, you can always store this information to custom attributes which are faster than communities, auto-ignored on export and can't leak to your peers.
BTW that guide looks quite outdated (regarding e.g. the support of autoreload) and will be even more outdated with BIRD 3 optimized import tables and selective autoreload. Noting that we shall look into updating this guide. Maria On 27 April 2024 05:05:35 CEST, Nigel Kukard via Bird-users <bird-users@network.cz> wrote: >Hi all, > >I was busy reading https://bgpfilterguide.nlnog.net/guides/reject_invalids/ >and noticed the following text... > >Note: REALLY DONT store the validation state inside a bgp_community or >bgp_large_community or bgp_ext_community variables. It can cause CPU & memory >overload resulting in convergence performance issues. > >I was wondering if this is still an issue and if it would still be a bad idea >to indicate that RPKI was VALID using communities on multiple full BGP feeds? > >Is anyone doing this at present? are you seeing significant load? > >Kind Regards >Nigel > -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
