--- 1/draft-ietf-idr-as4bytes-02.txt	2006-02-04 23:29:09.000000000 +0100
+++ 2/draft-ietf-idr-as4bytes-03.txt	2006-02-04 23:29:09.000000000 +0100
@@ -1,19 +1,18 @@
-
 Network Working Group                                  Quaizar Vohra
 Internet Draft                                      Juniper Networks
-Expiration Date: October 2001                              Enke Chen
+Expiration Date: November 2001                             Enke Chen
 Network Working Group                         Redback Networks, Inc.
 
                BGP support for four-octet AS number space
 
-                     draft-ietf-idr-as4bytes-02.txt
+                     draft-ietf-idr-as4bytes-03.txt
 
 1. Status of this Memo
 
    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.
 
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as Internet-
    Drafts.
@@ -105,24 +104,24 @@
    A BGP speaker that supports 4-octets Autonomous System numbers may
    advertise this to its peers using the BGP Capability Advertisements.
    A BGP speaker that advertises such capability to a particular peer,
    and receives from that peer the advertisement of such capability MUST
    encode Autonomous System numbers as 4-octets entities in both the
    AS_PATH and the AGGREGATOR attributes in the updates it sends to the
    peer, and MUST assume that these attributes in the updates received
    from the peer encode Autonomous System numbers as 4-octets entities.
 
    The new attributes, NEW_AS_PATH and NEW_AGGREGATOR should not be
-   carried in the updates between NEW BGP peers. A NEW BGP speaker that
-   receives an UPDATE message from a NEW BGP speaker, with the
-   NEW_AS_PATH attribute carried in the UPDATE message must ignore the
-   attribute. The same applies to the NEW_AGGREGATOR attribute.
+   carried in the UPDATE messages between NEW BGP peers. A NEW BGP
+   speaker that receives the NEW_AS_PATH and NEW_AGGREGATOR path
+   attributes in an UPDATE message from a NEW BGP speaker should discard
+   these path attributes and continue processing the UPDATE message.
 
 4.2. Interaction between NEW and OLD BGP speaker
 
 4.2.1. BGP Peering
 
    Note that peering between a NEW BGP speaker and an OLD one is
    possible only if the NEW BGP speaker has a 2-octets AS number.
    However, this document doesn't assume that an Autonomous System with
    NEW speakers has to have a globally unique 2-octets AS number -
    AS_TRANS could be used instead (even if multiple Autonomous System
@@ -254,31 +253,31 @@
 
    In addition, this document introduces two new BGP optional transitive
    attributes. The first is the NEW_AS_PATH attribute, which preserves
    the AS path information with 4-octet AS numbers across old BGP
    speakers. The second is the NEW_AGGREGATOR attribute, which is
    similar in use to the current AGGREGATOR attribute but it carries
    4-octet AS numbers.  The Type Codes for these attributes are to be
    assigned by IANA.
 
    Finally, this document introduces a reserved 2-octets AS number -
-   AS_TRANS.  The AS number for AS_TRANS are to be assigned by the IANA.
+   AS_TRANS.  The AS number for AS_TRANS is to be assigned by the IANA.
 
 8. Security Considerations
 
    Security issues are not discussed in this document.
 
 9. Acknowledgments
 
-   The authors would like to thank Yakov Rekhter and Chaitanya
-   Kodeboyina for the numerous discussions which went into the making of
-   this draft.
+   The authors would like to thank Yakov Rekhter, Chaitanya Kodeboyina,
+   and Jeffrey Haas for the numerous discussions which went into the
+   making of this draft.
 
 10. References
 
    [BGP] Rekhter, Y., Li, T., "Border Gateway Protocol 4", draft-ietf-
    idr-bgp4-12.txt
 
    [EXT-COM] Ramachandra, S., Tappan, D., and Rekter Y. "BGP Extended
    Communities Attribute", draft-ramachandra-bgp-ext-communities-02.txt
 
    [RFC1997] Chandra, R., Traina, P. and T. Li, "BGP Communities