--- 1/draft-ietf-grow-va-auto-01.txt	2010-08-31 15:12:39.000000000 +0200
+++ 2/draft-ietf-grow-va-auto-02.txt	2010-08-31 15:12:39.000000000 +0200
@@ -1,64 +1,57 @@
 
 Network Working Group                                         P. Francis
 Internet-Draft                                                   MPI-SWS
 Intended status: Informational                                     X. Xu
-Expires: September 9, 2010                                        Huawei
+Expires: March 4, 2011                                            Huawei
                                                               H. Ballani
                                                               Cornell U.
                                                                   D. Jen
                                                                     UCLA
                                                                R. Raszuk
                                                                    Cisco
                                                                 L. Zhang
                                                                     UCLA
-                                                           March 8, 2010
+                                                         August 31, 2010
 
                Auto-Configuration in Virtual Aggregation
-                     draft-ietf-grow-va-auto-01.txt
+                     draft-ietf-grow-va-auto-02.txt
 
 Abstract
 
    Virtual Aggregation as specified in [I-D.ietf-grow-va] requires
    configuration of a static "VP-List" on all routers.  The VP-List
    allows routers to know which prefixes may or may not be FIB-
    installed.  This draft specified an optional method of determining
    this that requires far less configuration.  Specifically, it requires
    the configuration of a "VP-Range" in ASBRs connected to transit and
    peer ISPs.  An Extended Communities Attribute is used to convey to
    other routers that a given route can be FIB-suppressed.
 
 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.
+   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."
 
-   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 September 9, 2010.
+   This Internet-Draft will expire on March 4, 2011.
 
 Copyright Notice
-
    Copyright (c) 2010 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.  Code Components extracted from this document must
    include Simplified BSD License text as described in Section 4.e of
@@ -56,21 +49,21 @@
    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.  Code Components extracted from this document must
    include Simplified BSD License text as described in Section 4.e of
    the Trust Legal Provisions and are provided without warranty as
-   described in the BSD License.
+   described in the Simplified BSD License.
 
 Table of Contents
 
    1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
      1.1.  Requirements notation . . . . . . . . . . . . . . . . . . . 3
    2.  Specification . . . . . . . . . . . . . . . . . . . . . . . . . 3
    3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
    4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
    5.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
      5.1.  Normative References  . . . . . . . . . . . . . . . . . . . 4