--- 1/draft-ietf-grow-wkc-behavior-07.txt	2019-06-13 09:15:30.560794330 -0700
+++ 2/draft-ietf-grow-wkc-behavior-08.txt	2019-06-13 09:15:31.580820046 -0700
@@ -1,23 +1,23 @@
 
 Network Working Group                                     J. Borkenhagen
 Internet-Draft                                                      AT&T
 Updates: 1997 (if approved)                                      R. Bush
 Intended status: Standards Track                            IIJ & Arrcus
-Expires: December 12, 2019                                     R. Bonica
+Expires: December 15, 2019                                     R. Bonica
                                                         Juniper Networks
                                                             S. Bayraktar
                                                            Cisco Systems
-                                                           June 10, 2019
+                                                           June 13, 2019
 
                   Well-Known Community Policy Behavior
-                    draft-ietf-grow-wkc-behavior-07
+                    draft-ietf-grow-wkc-behavior-08
 
 Abstract
 
    Well-Known BGP Communities are manipulated differently across various
    current implementations; resulting in difficulties for operators.
    Network operators should deploy consistent community handling across
    their networks while taking the inconsistent behaviors from the
    various BGP implementations into consideration..  This document
    recommends specific actions to limit future inconsistency, namely BGP
    implementors must not create further inconsistencies from this point
@@ -38,21 +38,21 @@
 
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
-   This Internet-Draft will expire on December 12, 2019.
+   This Internet-Draft will expire on December 15, 2019.
 
 Copyright Notice
 
    Copyright (c) 2019 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -190,31 +190,31 @@
    is not formally a Well-Known Community as it is not in [IANA-WKC];
    but 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."
 
 5.  Note for Those Writing RFCs for New Community-Like Attributes
 
    When establishing new [RFC1997]-like attributes (large communities,
    wide communities, etc.), RFC authors should state explicitly how the
-   > new attribute is to be handled.
+   new attribute is to be handled.
 
 6.  Action Items
 
    Network operators are encouraged to limit their use of the "set"
    directive (within reason), to improve consistency across platforms.
 
    Unfortunately, it would be operationally disruptive for vendors to
    change their current implementations.
 
-   Vendors SHOULD clearly document the behavior of "set" directive in
+   Vendors MUST clearly document the behavior of "set" directive in
    their implementations.
 
    Vendors MUST ensure that their implementations' "set" directive
    treatment of any specific community does not change if/when that
    community becomes a new Well-Known Community through future
    standardization.  For most implementations, this means that the "set"
    directive MUST continue to remove the community; for those
    implementations where the "set" directive removes no communities,
    that behavior MUST continue.