diff options
| author | Donatas Abraitis <donatas@opensourcerouting.org> | 2025-01-21 21:17:39 +0200 |
|---|---|---|
| committer | Mergify <37929162+mergify[bot]@users.noreply.github.com> | 2025-02-04 16:43:35 +0000 |
| commit | a73b0f88c7715bfcf5dc8ffd46d2fd0bbc9a8aff (patch) | |
| tree | 431eb7900da83d9a14397fedaecbc7da469a4307 /lib/id_alloc.c | |
| parent | c28079c9db210e69cb39d083a4f0f87ba5ed7628 (diff) | |
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
Diffstat (limited to 'lib/id_alloc.c')
0 files changed, 0 insertions, 0 deletions