--- 1/draft-ietf-mpls-static-yang-11.txt	2020-11-01 20:13:33.707502755 -0800
+++ 2/draft-ietf-mpls-static-yang-12.txt	2020-11-01 20:13:33.743503668 -0800
@@ -1,25 +1,25 @@
 
 MPLS Working Group                                               T. Saad
 Internet-Draft                                          Juniper Networks
 Intended status: Standards Track                               R. Gandhi
-Expires: October 22, 2020                            Cisco Systems, Inc.
+Expires: May 5, 2021                                 Cisco Systems, Inc.
                                                                   X. Liu
                                                           Volta Networks
                                                                V. Beeram
                                                         Juniper Networks
                                                               I. Bryskin
                                                      Huawei Technologies
-                                                          April 20, 2020
+                                                       November 01, 2020
 
                  A YANG Data Model for MPLS Static LSPs
-                     draft-ietf-mpls-static-yang-11
+                     draft-ietf-mpls-static-yang-12
 
 Abstract
 
    This document contains the specification for the MPLS Static Label
    Switched Paths (LSPs) YANG model.  The model allows for the
    provisioning of static LSP(s) on Label Edge Router(s) LER(s) and
    Label Switched Router(s) LSR(s) devices along a LSP path without the
    dependency on any signaling protocol.  The MPLS Static LSP model
    augments the MPLS base YANG model with specific data to configure and
    manage MPLS Static LSP(s).
@@ -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 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 October 22, 2020.
+   This Internet-Draft will expire on May 5, 2021.
 
 Copyright Notice
 
    Copyright (c) 2020 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
@@ -715,27 +715,27 @@
       Cisco Systems, Inc.
       email: skraza@cisco.com
 
 6.  References
 
 6.1.  Normative References
 
    [I-D.ietf-mpls-base-yang]
               Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A
               YANG Data Model for MPLS Base", draft-ietf-mpls-base-
-              yang-14 (work in progress), March 2020.
+              yang-17 (work in progress), October 2020.
 
    [I-D.ietf-teas-yang-te]
               Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
-              "A YANG Data Model for Traffic Engineering Tunnels and
-              Interfaces", draft-ietf-teas-yang-te-23 (work in
-              progress), March 2020.
+              "A YANG Data Model for Traffic Engineering Tunnels, Label
+              Switched Paths and Interfaces", draft-ietf-teas-yang-te-25
+              (work in progress), July 2020.
 
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119,
               DOI 10.17487/RFC2119, March 1997,
               <https://www.rfc-editor.org/info/rfc2119>.
 
    [RFC3031]  Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
               Label Switching Architecture", RFC 3031,
               DOI 10.17487/RFC3031, January 2001,
               <https://www.rfc-editor.org/info/rfc3031>.