--- 1/draft-ietf-teas-pce-native-ip-13.txt	2020-11-24 18:13:09.649866651 -0800
+++ 2/draft-ietf-teas-pce-native-ip-14.txt	2020-11-24 18:13:09.669866932 -0800
@@ -1,23 +1,23 @@
 
 TEAS Working Group                                               A. Wang
 Internet-Draft                                             China Telecom
-Intended status: Experimental                                B. Khasanov
-Expires: May 19, 2021                                         Yandex LLC
+Intended status: Informational                               B. Khasanov
+Expires: May 29, 2021                                         Yandex LLC
                                                                  Q. Zhao
                                                         Etheric Networks
                                                                  H. Chen
                                                                Futurewei
-                                                       November 15, 2020
+                                                       November 25, 2020
 
                         PCE in Native IP Network
-                    draft-ietf-teas-pce-native-ip-13
+                    draft-ietf-teas-pce-native-ip-14
 
 Abstract
 
    This document defines an architecture for providing traffic
    engineering in a native IP network using multiple BGP sessions and a
    Path Computation Element (PCE)-based central control mechanism.  It
    defines the Central Control Dynamic Routing (CCDR) procedures and
    identifies needed extensions for the Path Computation Element
    Communication Protocol (PCEP).
 
@@ -29,21 +29,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 May 19, 2021.
+   This Internet-Draft will expire on May 29, 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
@@ -385,21 +385,21 @@
    [RFC8231] and PCECC [RFC8283] mechanism.
 
    Regarding the BGP session, it is not different from that configured
    via the manual or NETCONF/YANG.  Different BGP sessions are used
    mainly for the clarification of the network prefixes, which can be
    differentiated via the different BGP nexthop.  Based on this
    strategy, if we manipulate the path to the BGP nexthop, then the path
    to the prefixes that advertised with the BGP sessions will be changed
    accordingly.  Details of communications between PCEP and BGP
    subsystems in the router's control plane are out of scope of this
-   draft and will be described in a separate draft
+   draft and will be described in a separate
    [I-D.ietf-pce-pcep-extension-native-ip] .
 
 7.  Deployment Consideration
 
 7.1.  Scalability
 
    In the CCDR architecture, only the edge routers that connects with
    PCE are responsible for the prefixes advertisement via the multiple
    BGP sessions deployment.  The route information for these prefixes
    within the on-path routers is distributed via the BGP protocol.