--- 1/draft-ietf-idr-extcomm-iana-00.txt	2013-09-30 08:14:27.354351764 -0700
+++ 2/draft-ietf-idr-extcomm-iana-01.txt	2013-09-30 08:14:27.386352583 -0700
@@ -1,22 +1,22 @@
 
 IDR Working Group                                          Eric C. Rosen
 Internet Draft                                       Cisco Systems, Inc.
 Intended Status: Standards Track
 Updates: 4360,5701                                         Yakov Rekhter
-Expires: February 22, 2014                        Juniper Networks, Inc.
+Expires: March 30, 2014                           Juniper Networks, Inc.
 
-                                                         August 22, 2013
+                                                      September 30, 2013
 
               IANA Registries for BGP Extended Communities
 
-                   draft-ietf-idr-extcomm-iana-00.txt
+                   draft-ietf-idr-extcomm-iana-01.txt
 
 Abstract
 
    This document reorganizes the IANA Registries for the type values and
    sub-type values of BGP Extended Communities attribute and the BGP
    IPv6-Address-Specific Extended Communities attribute.  This is done
    in order to remove inter-dependencies among the registries, thus
    making it easier for IANA to determine which codepoints are available
    for assignment in which registries.  This document also clarifies the
    information that must be provided to IANA when requesting an
@@ -227,31 +227,31 @@
    in an IPv6-Address-Specific Extended Community registry that is
    allocated in some other registry, it is the responsibility of the
    requester to explicitly ask this of IANA.
 
 5. IANA Considerations
 
    IANA is to replace the pre-existing BGP Extended Communities
    registries with the registries described in this section.
 
    Any Extended Community Type or Sub-type codepoints allocated by IANA
-   between the date of this document that the date at which the
+   between the date of this document and the date at which the
    registries are reorganized must also be incorporated into the new
    registry organization.  The authors will work with IANA to ensure
    that this is done correctly.
 
    The registries reproduced below do not include the "references" or
    "date" fields of the registries, because it is difficult to
    incorporate those within the 72-character line limitation of RFCs.
    The references and associated dates must be copied from the current
    registries when the new registries are introduced; the authors will
-   work with IANA to ensure this this information is carried over
+   work with IANA to ensure that this information is carried over
    correctly to the new registry organization.
 
 5.1. Registries for the TYPE Field
 
 5.1.1. Transitive Types
 
    This registry contains values of the high-order octet (the "Type
    Field") of a Transitive Extended Community.
 
 Registry Name: BGP TRANSITIVE EXTENDED COMMUNITY TYPES
@@ -525,21 +525,21 @@
 
     RANGE              REGISTRATION PROCEDURE
 
     0x00-0xBF          First Come, First Served
     0xC0-0xFF          IETF Review
 
     SUB-TYPE VALUE      NAME
 
     0x06                Flow spec traffic-rate
     0x07                Flow spec traffic-action (Use of the Value Field
-                        is defined in the "Traffic Actions Field"
+                        is defined in the "Traffic Action Field"
                         registry)
     0x08                Flow spec redirect
     0x09                Flow spec traffic-remarking
     0x0A                Layer2 Info Extended Community
 
 Note: RFC 5575 contains narrative text that declares the "Flow spec
 traffic-rate" to be non-transitive, but then assigns it a codepoint that
 indicates it to be transitive.  Addressing this error in RFC 5575 is not
 within the scope of the current document.