--- 1/draft-ietf-idr-aigp-06.txt	2011-12-12 18:13:57.254670853 +0100
+++ 2/draft-ietf-idr-aigp-07.txt	2011-12-12 18:13:57.286670722 +0100
@@ -1,24 +1,24 @@
 
 Network Working Group                                  Pradosh Mohapatra
 Internet Draft                                              Rex Fernando
 Intended Status: Proposed Standard                         Eric C. Rosen
-Expires: December 23, 2011                           Cisco Systems, Inc.
+Expires: June 12, 2012                               Cisco Systems, Inc.
 
                                                             James Uttaro
                                                                      ATT
 
-                                                           June 23, 2011
+                                                       December 12, 2011
 
               The Accumulated IGP Metric Attribute for BGP
 
-                       draft-ietf-idr-aigp-06.txt
+                       draft-ietf-idr-aigp-07.txt
 
 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
@@ -536,18 +536,18 @@
 
 10. Normative References
 
    [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-01.txt, March 2011.
+   fast-conn-restore-02.txt, October 2011.
 
    [BESTEXT], "Advertisement of the Best External Route in BGP", P.
    Marques, R. Fernando, E. Chen, P. Mohapatra, H. Gredler, draft-ietf-
    idr-best-external-04.txt, April 2011.
 
    [RFC2119] "Key words for use in RFCs to Indicate Requirement
    Levels.", S. Bradner, March 1997.