From c325b189f56a779bb97911c689af0d2e7dab2718 Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Wed, 29 May 2019 22:13:41 -0700 Subject: [PATCH] jay's review --- draft-ietf-grow-wkc-behavior.xml | 15 ++++----------- 1 file changed, 4 insertions(+), 11 deletions(-) diff --git a/draft-ietf-grow-wkc-behavior.xml b/draft-ietf-grow-wkc-behavior.xml index c492514..15cad5b 100644 --- a/draft-ietf-grow-wkc-behavior.xml +++ b/draft-ietf-grow-wkc-behavior.xml @@ -83,7 +83,7 @@ community handling across their networks, taking the inconsistent behaviors from the various BGP implementations they operate into consideration. This document recommends specific actions to limit - future inconsistency, namely BGP implementors should not create + future inconsistency, namely BGP implementors must not create further inconsistencies from this point forward. @@ -236,11 +236,9 @@
- Care should be taken when establishing new -like attributes (large communities, wide - communities, etc.), RFCs MUST make clear how the new community - attribute is to to be handled, avoiding repeating - inconsistencies. + > When establishing new [RFC1997]-like attributes (large + communities, wide communities, etc.), RFC authors should state + explicitly how the > new attribute is to be handled.
@@ -271,11 +269,6 @@ a neighbor ASN, the operator should confirm with that neighbor how the community will be treated. - Network operators are encouraged to limit their use of the "set" - directive (within reason), to improve the readability of their - configurations and hopefully to achieve behavioral consistency - across platforms. -