From 05ae8218fa6ade2335958a3448a77dfa900ab7e6 Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Mon, 12 Feb 2018 08:21:53 +0900 Subject: [PATCH] section on xr/iana inconsistency --- draft-ymbk-grow-wkc-behavior.xml | 56 +++++++++++++++++++++++--------- 1 file changed, 41 insertions(+), 15 deletions(-) diff --git a/draft-ymbk-grow-wkc-behavior.xml b/draft-ymbk-grow-wkc-behavior.xml index 7d6bb72..5884a7b 100644 --- a/draft-ymbk-grow-wkc-behavior.xml +++ b/draft-ymbk-grow-wkc-behavior.xml @@ -59,7 +59,7 @@ - + Cisco Systems
@@ -69,7 +69,7 @@ 95134 United States of America - dward@cisco.com + serpil@cisco.com
@@ -128,18 +128,18 @@ 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 a "set community" - directive that operators use to mean "remove any/all communities - present on the update received from the neighbor, and apply this - set of communities instead." + 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."
Vendor implementations differ in the treatment of certain - Well-Known communities when modified using the "set community" - directive. Some replace all communities including the Well-Known + Well-Known communities when modified using the syntax to "set" the + community. Some replace all communities including the Well-Known ones with the new set, while others replace all non-Well-Known Communities but do not modify any Well-Known Communities that are present. @@ -152,7 +152,7 @@
- In Juniper Networks' JunOS, "set community" removes all received + In Juniper Networks' JunOS, "community set" removes all received communities, Well-Known or otherwise. In Cisco Systems' IOS-XR, "set community" removes all received @@ -171,10 +171,28 @@ Communities not removed by Cisco IOS/XR - IOS-XR does allow Well-Known communities to be removed one at a - time (with a tweezers) by explicit policy; for example, "delete - community accept-own". Operators are advised to consult IOS-XR - documentation and/or Cisco Systems support for full details. + IOS-XR does allow Well-Known communities to be removed one at a + time (with a tweezers) by explicit policy; for example, "delete + community accept-own". Operators are advised to consult IOS-XR + documentation and/or Cisco Systems support for full details. + +
+ + The IANA publishes a list of Well-Known Communities . + + IOS-XR's set of well-known communities that "set community" + will not overwrite diverges from IANA's list. Quite a few + well-known communities from IANA's list do not receive special + treatment in IOS-XR, and at least one specific community on + IOS-XR's special treatment list (internet == 0:0) is not really + on IANA's list -- it's taken from the "Reserved" range + [0x00000000-0x0000FFFF]. + + This merely notes an inconsistency. It is not a plea to + 'protect' the entire IANA list from "set community." + +
@@ -196,8 +214,8 @@ inclusion in this document, especially if their behavior differs from the examples described. - Vendors MUST NOT create additional communities that the "set - community" directive would not modify. + Vendors MUST NOT create additional communities that the command + to "set" the community would not modify.
@@ -223,6 +241,14 @@ + + + IANA Well-Known Comunities + + + + +