--- 1/draft-ietf-idr-aigp-09.txt	2013-05-23 17:14:31.658270665 +0100
+++ 2/draft-ietf-idr-aigp-10.txt	2013-05-23 17:14:31.686271372 +0100
@@ -1,24 +1,26 @@
 
 Network Working Group                                  Pradosh Mohapatra
-Internet Draft                                              Rex Fernando
-Intended Status: Proposed Standard                         Eric C. Rosen
-Expires: May 27, 2013                                Cisco Systems, Inc.
+Internet Draft                                          Cumulus Networks
+Intended Status: Proposed Standard
+Expires: November 23, 2013                                  Rex Fernando
+                                                           Eric C. Rosen
+                                                     Cisco Systems, Inc.
 
                                                             James Uttaro
                                                                      ATT
 
-                                                       November 27, 2012
+                                                            May 23, 2013
 
               The Accumulated IGP Metric Attribute for BGP
 
-                       draft-ietf-idr-aigp-09.txt
+                       draft-ietf-idr-aigp-10.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
@@ -47,21 +49,21 @@
    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) 2012 IETF Trust and the persons identified as the
+   Copyright (c) 2013 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
    the Trust Legal Provisions and are provided without warranty as
@@ -80,21 +82,21 @@
  3.3.3      Modifications by a Non-Originator  .....................   8
  4          Decision Process  ......................................  10
  4.1        When a Route has an AIGP Attribute  ....................  10
  4.2        When the Route to the Next Hop has an AIGP attribute  ..  11
  5          Deployment Considerations  .............................  12
  6          IANA Considerations  ...................................  12
  7          Security Considerations  ...............................  12
  8          Acknowledgments  .......................................  12
  9          Authors' Addresses  ....................................  13
 10          Normative References  ..................................  13
-11          Informative References  ................................  14
+11          Informative References  ................................  13
 
 1. Specification of requirements
 
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
    document are to be interpreted as described in [RFC2119].
 
 2. Introduction
 
    There are many routing protocols that have been designed to run
@@ -509,24 +511,22 @@
 
 9. Authors' Addresses
 
    Rex Fernando
    Cisco Systems, Inc.
    170 Tasman Drive
    San Jose, CA  95134
    Email: rex@cisco.com
 
    Pradosh Mohapatra
-   Cisco Systems, Inc.
-   170 Tasman Drive
-   San Jose, CA  95134
-   Email: pmohapat@cisco.com
+   Cumulus Networks
+   Email: pmohapat@cumulusnetworks.com
 
    Eric C. Rosen
    Cisco Systems, Inc.
    1414 Massachusetts Avenue
    Boxborough, MA, 01719
    Email: erosen@cisco.com
 
    James Uttaro
    AT&T
    200 S. Laurel Avenue
@@ -535,18 +535,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-02.txt, October 2011.
+   fast-conn-restore-03.txt, January 2013.
 
    [BESTEXT], "Advertisement of the Best External Route in BGP", P.
    Marques, R. Fernando, E. Chen, P. Mohapatra, H. Gredler, draft-ietf-
    idr-best-external-05.txt, January 2012.
 
    [RFC2119] "Key words for use in RFCs to Indicate Requirement
    Levels.", S. Bradner, March 1997.