On Tue, Dec 12, 2017 at 06:47:44PM +0100, Pier Carlo Chiodi wrote: > Hello, > > while I was running some tests on BIRD 2.0.0 I've noticed that the > handling of RFC8097 extended communities is different from 1.6.3. > The results I get follow: > > - when 1.6.3 is used on the route server, BIRD treats the community > strictly according to RFC4360: > > If a route has a non-transitivity extended community, then before > advertising the route across the Autonomous System boundary the > community SHOULD be removed from the route. > > - when 2.0.0 is used, the community is treated accordingly to > draft-ietf-sidrops-route-server-rpki-light-02 and is propagated to the > client.
Hi Thanks for report, this seems like a bug. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
