--- 1/draft-ietf-bess-mvpn-msdp-sa-interoperation-02.txt	2019-09-02 20:13:03.681878238 -0700
+++ 2/draft-ietf-bess-mvpn-msdp-sa-interoperation-03.txt	2019-09-02 20:13:03.697878643 -0700
@@ -1,19 +1,19 @@
 
 BESS                                                            Z. Zhang
 Internet-Draft                                               L. Giuliano
 Updates: 6514 (if approved)                             Juniper Networks
-Intended status: Standards Track                        January 28, 2019
-Expires: August 1, 2019
+Intended status: Standards Track                       September 2, 2019
+Expires: March 5, 2020
 
                     MVPN and MSDP SA Interoperation
-             draft-ietf-bess-mvpn-msdp-sa-interoperation-02
+             draft-ietf-bess-mvpn-msdp-sa-interoperation-03
 
 Abstract
 
    This document specifies the procedures for interoperation between
    MVPN Source Active routes and customer MSDP Source Active routes,
    which is useful for MVPN provider networks offering services to
    customers with an existing MSDP infrastructure.  Without the
    procedures described in this document, VPN-specific MSDP sessions are
    required among the PEs that are customer MSDP peers.
 
@@ -31,21 +31,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 https://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 August 1, 2019.
+   This Internet-Draft will expire on March 5, 2020.
 
 Copyright Notice
 
    Copyright (c) 2019 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
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents