--- 1/draft-ietf-idr-aigp-01.txt	2010-04-02 21:11:14.000000000 +0200
+++ 2/draft-ietf-idr-aigp-02.txt	2010-04-02 21:11:15.000000000 +0200
@@ -1,28 +1,24 @@
 
 Network Working Group                                  Pradosh Mohapatra
-Internet Draft                                       Cisco Systems, Inc.
-Intended Status: Proposed Standard
-Expires: April 7, 2010                                      Rex Fernando
-                                                  Juniper Networks, Inc.
-
-                                                           Eric C. Rosen
-                                                     Cisco Systems, Inc.
+Internet Draft                                              Rex Fernando
+Intended Status: Proposed Standard                         Eric C. Rosen
+Expires: October 2, 2010                             Cisco Systems, Inc.
 
                                                             James Uttaro
                                                                      ATT
 
-                                                         October 7, 2009
+                                                           April 2, 2010
 
               The Accumulated IGP Metric Attribute for BGP
 
-                       draft-ietf-idr-aigp-01.txt
+                       draft-ietf-idr-aigp-02.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.
@@ -33,28 +29,32 @@
    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.
 
 Copyright and License Notice
 
-   Copyright (c) 2009 IETF Trust and the persons identified as the
+   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 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.
+   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 Simplified BSD License.
 
 Abstract
 
    Routing protocols that have been designed to run within a single
    administrative domain ("IGPs") generally do so by assigning a metric
    to each link, and then choosing as the installed path between two
    nodes the path for which the total distance (sum of the metric of
    each link along the path) is minimized.  BGP, designed to provide
    routing over a large number of independent administrative domains
    ("autonomous systems"), does not make its path selection decisions
@@ -477,16 +477,16 @@
 
    [BGP], "A Border Gateway Protocol 4 (BGP-4)", Y. Rekhter, T. Li, S.
    Hares, RFC 4271, January 2006.
 
 11. Informative References
 
    [ADDPATH] "Fast Connectivity Restoration Using BGP Add-Path", P.
    Mohapatra, R. Fernando, C. Filsfils, R. Raszuk, draft-pmohapat-idr-
    fast-conn-restore-00.txt, September 2008.
 
-   [BESTEXT], " Advertisement of the Best-External Route to IBGP", P.
-   Marques, R. Fernando, E. Chen, P. Mohapatra, draft-marques-idr-best-
-   external-01.txt, March 2009.
+   [BESTEXT], " Advertisement of the Best External Route in BGP", P.
+   Marques, R. Fernando, E. Chen, P. Mohapatra, draft-ietf-idr-best-
+   external-01.txt, February 2010.
 
    [RFC2119] "Key words for use in RFCs to Indicate Requirement
    Levels.", S. Bradner, March 1997