]> git.puffer.fish Git - matthieu/frr.git/commit
bgpd: Send non-transitive extended communities from/to OAD peers
authorDonatas Abraitis <donatas@opensourcerouting.org>
Tue, 21 Jan 2025 19:17:39 +0000 (21:17 +0200)
committerMergify <37929162+mergify[bot]@users.noreply.github.com>
Tue, 4 Feb 2025 16:43:35 +0000 (16:43 +0000)
commita73b0f88c7715bfcf5dc8ffd46d2fd0bbc9a8aff
tree431eb7900da83d9a14397fedaecbc7da469a4307
parentc28079c9db210e69cb39d083a4f0f87ba5ed7628
bgpd: Send non-transitive extended communities from/to OAD peers

draft-uttaro-idr-bgp-oad says:

Extended communities which are non-transitive across an AS boundary MAY be
advertised over an EBGP-OAD session if allowed by explicit policy configuration.
If allowed, all the members of the OAD SHOULD be configured to use the same
criteria.
For example, the Origin Validation State Extended Community, defined as
non-transitive in [RFC8097], can be advertised to peers in the same OAD.

Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
(cherry picked from commit f2759c46ceda2a5f13b40213381baf71997b6b87)

# Conflicts:
# bgpd/bgp_route.c
bgpd/bgp_route.c