diff --git a/draft-ymbk-grow-wkc-behavior.xml b/draft-ymbk-grow-wkc-behavior.xml index de60ce6..0c715a1 100644 --- a/draft-ymbk-grow-wkc-behavior.xml +++ b/draft-ymbk-grow-wkc-behavior.xml @@ -11,7 +11,7 @@ - + @@ -117,23 +117,32 @@ -
- - says: +
+ + says: - "A BGP speaker receiving a route with the COMMUNITIES path - attribute may modify this attribute according to the local - policy." + "A BGP speaker receiving a route with the COMMUNITIES path + attribute may modify this attribute according to the local + policy." - One common operational need is to add or remove one or more - communities to the current set. Another common need is to replace - all received communities with a new set as defined by policy. All - BGP policy implementations we know of provide syntax to "set" a - community that operators use to mean "remove any/all - communities present on the update received from the neighbor, and - apply this set of communities instead." + A basic operational need is to add or remove one or more + communities to the received set. Another common need is to replace + all received communities with a new set. To simplify the second + case, most BGP policy implementations provide syntax to "set" + community that operators use to mean "remove any/all communities + present on the update received from the neighbor, and apply this set + of communities instead." -
+ Some prefer to write explicit policy to delete unwanted + communities rather than using "set;" i.e. using a "delete community + *:*" and then "add community x:y ..." configuration statements in an + attempt to replace all received communities. The same community + manipulation policy differences described in the following section + exist in both "set" and "delete community *:*" syntax. For + simplicity, the remainder of this document refers only to the "set" + behaviors. + +
@@ -182,8 +191,8 @@ In Huawei's VRP product, "community set" removes all received communities, well-Known or otherwise. - In OpenBSD's OpenBGPD, "community set" removes no communities, - well-Known or otherwise. + In OpenBSD's OpenBGPD, "set community" does not remove any + communities, well-Known or otherwise.