Hi,
On 01/06/2025 09:56, Job Snijders wrote:
Please read the document with fresh eyes and tell us whether the
structure of the document in the right direction!
This document aims to do two things:
- Stop the use of Extended communities for signalling Route Server
policy
- Scrubbing of L3VPN Extended communities on Route Servers
The phrasing "avoid the use of BGP Extended Communities" does not make
this sufficiently clear. A casual reader may still think the intent is
to scrub all Extended communities, until reading the "Recommendation"
section. I think the two goals should be pointed out explicitly in the
Abstract and Introduction.
Alternatively, given that the two goals are orthogonal and mixing them
leads to confusion, the following could be done:
- Remove the L3VPN scrubbing recommendation from this document
- Create a second draft with the L3VPN scrubbing recommendation, and
perhaps scrubbing of a few other Extended Community Sub-Types on
Route Servers.
For the L3VPN scrubbing, I think this needs to update RFC7947, section
2.2.4, since this states "Transitive as well as non-transitive
Communities attributes [..] SHOULD NOT be modified, processed, or removed".
Some text corrections in the "Background" section:
"The practise [..]" -> "The practice"
"Classic BGP communities" -> "standard BGP communities" (to be
consistent with section 5 and RFC7948)
"With a total space of 12 octets divided into 3 separate fields,
signalling between 2-octet ASNs and 4-octet ASNs, or 4-octet ASNs and
4-octet ASNs, making the use of BGP Extended Communities redundant."
->
"With a total space of 12 octets divided into 3 separate fields,
signalling between 2-octet ASNs and 4-octet ASNs, or 4-octet ASNs and
4-octet ASNs is possible, making the use of BGP Extended Communities
redundant."
"(Classic, Large, and Extended)" -> "(standard, Large, and Extended)"
"Routing Policies" -> "routing policies"
Kind regards,
Martin
_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]
