From c3f2a06147e5158059cf55e42849c553bfa447d4 Mon Sep 17 00:00:00 2001
From: Randy Bush <randy@psg.com>
Date: Thu, 1 Mar 2018 09:22:49 +0900
Subject: [PATCH] -00 published

---
 draft-ymbk-grow-wkc-behavior.xml | 25 +++++++++++++------------
 1 file changed, 13 insertions(+), 12 deletions(-)

diff --git a/draft-ymbk-grow-wkc-behavior.xml b/draft-ymbk-grow-wkc-behavior.xml
index 5884a7b..eb0c8ee 100644
--- a/draft-ymbk-grow-wkc-behavior.xml
+++ b/draft-ymbk-grow-wkc-behavior.xml
@@ -45,17 +45,17 @@
         </address>
     </author>
 
-    <author fullname="John G. Scudder" initials="J." surname="Scudder">
-       <organization>Juniper Networks, Inc.</organization>
+    <author fullname="Ron Bonica" initials="R." surname="Bonica">
+       <organization>Juniper Networks</organization>
        <address>
           <postal>
-            <street>1133 Innovation Way</street>
-            <city>Sunnyvale</city>
-            <region>CA</region>
-            <code>94089</code>
+            <street>2251 Corporate Park Drive</street>
+            <city>Herndon</city>
+            <region>VA</region>
+            <code>20171</code>
             <country>US</country>
           </postal>
-          <email>jgs@juniper.net</email>
+          <email>rbonica@juniper.net</email>
        </address>
     </author>
     
@@ -172,9 +172,9 @@
       </texttable>
 
     <t>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.</t>
+    time 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.</t>
 
     <section anchor="ianalist" title="Note on an Inconsistency">
 
@@ -214,8 +214,9 @@
     inclusion in this document, especially if their behavior differs
     from the examples described.</t>
 
-    <t>Vendors MUST NOT create additional communities that the command
-    to "set" the community would not modify.</t>
+    <t>For new well-known communities specified (after this draft),
+    vendors MUST treat "community set" command to mean “remove all
+    other communities, Well-Known or otherwise."</t>
     
     </section>