--- 1/draft-ietf-idr-as4octet-extcomm-generic-subtype-00.txt	2009-10-26 23:12:11.000000000 +0100
+++ 2/draft-ietf-idr-as4octet-extcomm-generic-subtype-01.txt	2009-10-26 23:12:11.000000000 +0100
@@ -1,20 +1,20 @@
 
 Network Working Group                                             D. Rao
 Internet-Draft                                              P. Mohapatra
 Intended status: Standards Track                           Cisco Systems
-Expires: July 30, 2009                                           J. Haas
+Expires: April 29, 2010                                          J. Haas
                                                           Arbor Networks
-                                                        January 26, 2009
+                                                        October 26, 2009
 
    Generic Subtype for BGP Four-octet AS specific extended community
-         draft-ietf-idr-as4octet-extcomm-generic-subtype-00.txt
+         draft-ietf-idr-as4octet-extcomm-generic-subtype-01.txt
 
 Status of this Memo
 
    This Internet-Draft is submitted to IETF in full conformance with the
    provisions of BCP 78 and BCP 79.
 
    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.
@@ -23,33 +23,32 @@
    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."
 
    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt.
 
    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.
 
-   This Internet-Draft will expire on July 30, 2009.
+   This Internet-Draft will expire on April 29, 2010.
 
 Copyright Notice
 
    Copyright (c) 2009 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
-   carefully, as they describe your rights and restrictions with respect
-   to this document.
+   Provisions Relating to IETF Documents in effect on the date of
+   publication of this document (http://trustee.ietf.org/license-info).
+   Please review these documents carefully, as they describe your rights
+   and restrictions with respect to this document.
 
 Abstract
 
    Maintaining the current best practices with communities, ISPs and
    enterprises that are assigned a 4-octet AS number may want the BGP
    UPDATE messages they receive from their customers or peers to include
    a 4-octet AS specific extended community.  This document defines a
    new sub-type within the four-octet AS specific extended community to
    facilitate this practice.
 
@@ -176,22 +175,22 @@
 
 6.  Security Considerations
 
    There are no additional security risks introduced by this design.
 
 7.  Normative References
 
    [I-D.ietf-l3vpn-as4octet-ext-community]
               Rekhter, Y., Sangli, S., and D. Tappan, "Four-octet AS
               Specific BGP Extended Community",
-              draft-ietf-l3vpn-as4octet-ext-community-02 (work in
-              progress), November 2008.
+              draft-ietf-l3vpn-as4octet-ext-community-03 (work in
+              progress), March 2009.
 
    [RFC1997]  Chandrasekeran, R., Traina, P., and T. Li, "BGP
               Communities Attribute", RFC 1997, August 1996.
 
    [RFC1998]  Chen, E. and T. Bates, "An Application of the BGP
               Community Attribute in Multi-home Routing", RFC 1998,
               August 1996.
 
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119, March 1997.