Skip to content

Conversation

ton31337
Copy link
Member

No description provided.

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>
…ities

Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
@frrbot frrbot bot added bgp tests Topotests, make check, etc labels Jan 21, 2025
@riw777 riw777 self-requested a review January 28, 2025 15:41
Copy link
Member

@riw777 riw777 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good ... waiting on freeze

@ton31337
Copy link
Member Author

@Mergifyio backport stable/10.2 stable/10.1 stable/10.0

Copy link

mergify bot commented Jan 30, 2025

backport stable/10.2 stable/10.1 stable/10.0

✅ Backports have been created

@riw777 riw777 merged commit e6228f7 into FRRouting:master Feb 4, 2025
18 checks passed
riw777 added a commit that referenced this pull request Feb 4, 2025
bgpd: Send non-transitive extended communities from/to OAD peers (backport #17896)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants