--- 1/draft-ietf-idr-large-community-08.txt	2016-11-21 13:13:07.509773624 -0800
+++ 2/draft-ietf-idr-large-community-09.txt	2016-11-21 13:13:07.525773788 -0800
@@ -1,25 +1,25 @@
 
 IDR                                                        J. Heitz, Ed.
 Internet-Draft                                                     Cisco
 Intended status: Standards Track                        J. Snijders, Ed.
-Expires: May 18, 2017                                                NTT
+Expires: May 25, 2017                                                NTT
                                                                 K. Patel
                                                                   Arrcus
                                                              I. Bagdonas
                                                                  Equinix
                                                              N. Hilliard
                                                                     INEX
-                                                       November 14, 2016
+                                                       November 21, 2016
 
                          BGP Large Communities
-                   draft-ietf-idr-large-community-08
+                   draft-ietf-idr-large-community-09
 
 Abstract
 
    This document describes the BGP Large Communities attribute, an
    extension to BGP-4.  This attribute provides a mechanism to signal
    opaque information within separate namespaces to aid in routing
    management.  The attribute is suitable for use with four-octet
    Autonomous System Numbers.
 
 Requirements Language
@@ -36,21 +36,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 http://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 May 18, 2017.
+   This Internet-Draft will expire on May 25, 2017.
 
 Copyright Notice
 
    Copyright (c) 2016 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
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -62,21 +62,21 @@
 
 Table of Contents
 
    1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
    2.  BGP Large Communities Attribute . . . . . . . . . . . . . . .   3
    3.  Aggregation . . . . . . . . . . . . . . . . . . . . . . . . .   4
    4.  Canonical Representation  . . . . . . . . . . . . . . . . . .   4
    5.  Reserved BGP Large Community values . . . . . . . . . . . . .   4
    6.  Error Handling  . . . . . . . . . . . . . . . . . . . . . . .   5
    7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
-   8.  Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION   5
+   8.  Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION   6
    9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
    10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   6
    11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
    12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
      12.1.  Normative References . . . . . . . . . . . . . . . . . .   7
      12.2.  Informative References . . . . . . . . . . . . . . . . .   8
      12.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .   8
    Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8
 
 1.  Introduction
@@ -189,20 +189,23 @@
    used if there is a future need for them.
 
 6.  Error Handling
 
    The error handling of BGP Large Communities is as follows:
 
    o  A BGP Large Communities attribute SHALL be considered malformed if
       the length of the BGP Large Communities Attribute value, expressed
       in octets, is not a non-zero multiple of 12.
 
+   o  A BGP Large Communities attribute SHALL NOT be considered
+      malformed due solely to presence of duplicate community values.
+
    o  A BGP UPDATE message with a malformed BGP Large Communities
       attribute SHALL be handled using the approach of "treat-as-
       withdraw" as described in section 2 [RFC7606].
 
    The BGP Large Communities Global Administrator field MAY contain any
    value, and a BGP Large Communities attribute MUST NOT be considered
    malformed if the Global Administrator field contains an unallocated,
    unassigned or reserved ASN or is set to one of the reserved BGP Large
    Community values defined in Section 5.