--- 1/draft-ietf-bess-mvpn-pe-ce-00.txt	2015-10-05 06:15:09.085402288 -0700
+++ 2/draft-ietf-bess-mvpn-pe-ce-01.txt	2015-10-05 06:15:09.117403064 -0700
@@ -1,20 +1,20 @@
 
 Internet Engineering Task Force                                 K. Patel
 Internet-Draft                                             Cisco Systems
 Intended status: Standards Track                                E. Rosen
-Expires: October 8, 2015                                Juniper Networks
+Expires: April 7, 2016                                  Juniper Networks
                                                               Y. Rekhter
-                                                           April 6, 2015
+                                                         October 5, 2015
 
                      BGP as an MVPN PE-CE Protocol
-                     draft-ietf-bess-mvpn-pe-ce-00
+                     draft-ietf-bess-mvpn-pe-ce-01
 
 Abstract
 
    When a Service Provider offers BGP/MPLS IP VPN service to its
    customers, RFCs 6513 and 6514 describe protocols and procedures that
    the Service Provider can use in order to carry the customer's IP
    multicast traffic from one customer site to others.  BGP can be used
    to carry customer multicast routing information from one Provider
    Edge (PE) router to another, but it is assumed that PIM is running on
    the interface between a Customer Edge (CE) router and a PE router.
@@ -32,21 +32,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    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."
 
-   This Internet-Draft will expire on October 8, 2015.
+   This Internet-Draft will expire on April 7, 2016.
 
 Copyright Notice
 
    Copyright (c) 2015 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
@@ -498,54 +498,66 @@
 6.  Security Considerations
 
    This extension to BGP does not change the underlying security issues
    inherent in the existing [RFC4271] and [RFC6514].
 
 7.  References
 
 7.1.  Normative References
 
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
-              Requirement Levels", BCP 14, RFC 2119, March 1997.
+              Requirement Levels", BCP 14, RFC 2119,
+              DOI 10.17487/RFC2119, March 1997,
+              <http://www.rfc-editor.org/info/rfc2119>.
 
-   [RFC4271]  Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
-              Protocol 4 (BGP-4)", RFC 4271, January 2006.
+   [RFC4271]  Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
+              Border Gateway Protocol 4 (BGP-4)", RFC 4271,
+              DOI 10.17487/RFC4271, January 2006,
+              <http://www.rfc-editor.org/info/rfc4271>.
 
    [RFC4601]  Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
               "Protocol Independent Multicast - Sparse Mode (PIM-SM):
-              Protocol Specification (Revised)", RFC 4601, August 2006.
+              Protocol Specification (Revised)", RFC 4601,
+              DOI 10.17487/RFC4601, August 2006,
+              <http://www.rfc-editor.org/info/rfc4601>.
 
    [RFC4760]  Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
-              "Multiprotocol Extensions for BGP-4", RFC 4760, January
-              2007.
+              "Multiprotocol Extensions for BGP-4", RFC 4760,
+              DOI 10.17487/RFC4760, January 2007,
+              <http://www.rfc-editor.org/info/rfc4760>.
 
    [RFC5015]  Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
               "Bidirectional Protocol Independent Multicast (BIDIR-
-              PIM)", RFC 5015, October 2007.
+              PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007,
+              <http://www.rfc-editor.org/info/rfc5015>.
 
    [RFC5492]  Scudder, J. and R. Chandra, "Capabilities Advertisement
-              with BGP-4", RFC 5492, February 2009.
+              with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February
+              2009, <http://www.rfc-editor.org/info/rfc5492>.
 
-   [RFC6513]  Rosen, E. and R. Aggarwal, "Multicast in MPLS/BGP IP
-              VPNs", RFC 6513, February 2012.
+   [RFC6513]  Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
+              BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
+              2012, <http://www.rfc-editor.org/info/rfc6513>.
 
    [RFC6514]  Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
               Encodings and Procedures for Multicast in MPLS/BGP IP
-              VPNs", RFC 6514, February 2012.
+              VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,
+              <http://www.rfc-editor.org/info/rfc6514>.
 
 7.2.  Informative References
 
    [RFC4684]  Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk,
               R., Patel, K., and J. Guichard, "Constrained Route
               Distribution for Border Gateway Protocol/MultiProtocol
               Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual
-              Private Networks (VPNs)", RFC 4684, November 2006.
+              Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684,
+              November 2006, <http://www.rfc-editor.org/info/rfc4684>.
 
 Authors' Addresses
 
    Keyur Patel
    Cisco Systems
    170 W. Tasman Drive
    San Jose, CA  95134
    USA
 
    Email: keyupate@cisco.com