--- 1/draft-ietf-teas-pce-native-ip-12.txt 2020-11-15 08:13:11.416669626 -0800 +++ 2/draft-ietf-teas-pce-native-ip-13.txt 2020-11-15 08:13:11.436669887 -0800 @@ -1,49 +1,49 @@ TEAS Working Group A. Wang Internet-Draft China Telecom Intended status: Experimental B. Khasanov -Expires: May 1, 2021 Huawei Technologies +Expires: May 19, 2021 Yandex LLC Q. Zhao Etheric Networks H. Chen Futurewei - October 28, 2020 + November 15, 2020 PCE in Native IP Network - draft-ietf-teas-pce-native-ip-12 + draft-ietf-teas-pce-native-ip-13 Abstract - This document defines the architecture for traffic engineering within - native IP network, using multiple BGP sessions strategy and PCE - -based central control mechanism. It uses the Central Control - Dynamic Routing (CCDR) procedures described in this document, and the - Path Computation Element Communication Protocol (PCEP) extension - specified in draft ietf-pce-pcep-extension-native-ip. + 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). Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. 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 1, 2021. + This Internet-Draft will expire on May 19, 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 @@ -58,84 +58,75 @@ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. CCDR Architecture in Simple Topology . . . . . . . . . . . . 4 4. CCDR Architecture in Large Scale Topology . . . . . . . . . . 5 5. CCDR Multiple BGP Sessions Strategy . . . . . . . . . . . . . 6 6. PCEP Extension for Key Parameters Delivery . . . . . . . . . 8 7. Deployment Consideration . . . . . . . . . . . . . . . . . . 9 7.1. Scalability . . . . . . . . . . . . . . . . . . . . . . . 9 7.2. High Availability . . . . . . . . . . . . . . . . . . . . 9 7.3. Incremental deployment . . . . . . . . . . . . . . . . . 10 + 7.4. Loop Avoidance . . . . . . . . . . . . . . . . . . . . . 10 8. Security Considerations . . . . . . . . . . . . . . . . . . . 10 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 11 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 11.1. Normative References . . . . . . . . . . . . . . . . . . 11 11.2. Informative References . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 1. Introduction + [RFC8283], based on an extension of the PCE architecture described in + [RFC4655] , introduced a broader use applicability for a PCE as a + central controller. PCEP is continued to be used as the protocol + between PCE and PCC. Building on this work, this document describes + a solution using a PCE for centralized control in a native IP network + to provide End-to-End(E2E) performance assurance and QoS for traffic. + The solution combines the use of distributed routing protocols and a + centralized controller, referred to as Centralized Control Dynamic + Routing(CCDR). + [RFC8735] describes the scenarios and simulation results for traffic - engineering in the native IP network to provide End-to-End (E2E) - performance assurance and QoS using PCE based centralized control, - referred to as Centralized Control Dynamic Routing (CCDR). Based on - the various scenarios and analysis as per [RFC8735], the solution for - traffic engineering in native IP network should meet the following + engineering in a native IP network based on use of a CCDR + architecture. Per [RFC8735], the architecture for traffic + engineering in a native IP network should meet the following criteria: o Same solution for native IPv4 and IPv6 traffic. o Support for intra-domain and inter-domain scenarios. o Achieve End to End traffic assurance, with determined QoS - behavior. - - o No changes in routers forwarding behavior. + behavior, for traffic requiring a service assurance(prioritized + traffic). - o Capability to use the power of centrally control and the - flexibility/robustness of distributed network control plane. + o No changes in a router's forwarding behavior. - o Different network requirements such as large traffic amount and - prefix scale. + o Capability to use the power of centralized control and the + flexibility/robustness of a distributed network control plane. - o Adjusting the optimal path dynamically upon the change of network - status. No need for physical links resources reservation in - advance. + o Support different network requirements such as large traffic + amount and prefix scale. - Stateful PCE [RFC8231] specifies a set of extensions to PCEP to - enable stateful control of paths such as MPLS-TE Label Switched - Paths(LSP)s between and across PCEP sessions in compliance with - [RFC4657]. It includes mechanisms to achieve state synchronization - between Path Computation Clients(PCCs) and PCEs, delegation of - control of LSPs to PCEs, and PCE control of timing and sequence of - path computations within and across PCEP sessions. Furthermore, - [RFC8281] specifies a mechanism to dynamically instantiate LSPs on a - PCC based on the requests from a stateful PCE or a controller using - stateful PCE. [RFC8283] introduces the architecture for PCE as a - central controller as an extension of the architecture described in - [RFC4655] and assumes the continued use of PCEP as the protocol used - between PCE and PCC.[RFC8283] further examines the motivations and - applicability for PCEP as a Southbound Interface (SBI), and - introduces the implications for the protocol. + o Ability to adjust the optimal path dynamically upon the changes of + network status. No need for physical links resources reservations + to be done in advance. - This document defines the architecture for traffic engineering within - native IP network, using multiple BGP session strategy, to meet the - above criteria in dynamical and centrally control mode. The - architecture is referred as CCDR architecture. It depends on the - central control (PCE) element to compute the optimal path for - selected traffic, and utilizes the dynamic routing behavior of - traditional IGP/BGP protocols to forward such traffic. + Building on the above documents, this document defines an + architecture meeting these requirements by using multiple a BGP + session strategy and a PCE as the centralized controller. The + architecture depends on the central control (PCE) element to compute + the optimal path, and utilizes the dynamic routing behavior of IGP/ + BGP protocols for forwarding the traffic. - The control messages between PCE and underlying network node are - transmitted via Path Computation Element Communications Protocol - (PCEP) protocol. The related PCEP extensions are provided in draft + The related PCEP extensions are provided in draft [I-D.ietf-pce-pcep-extension-native-ip]. 2. Terminology This document uses the following terms defined in [RFC5440]: o PCE o PCEP @@ -173,85 +163,85 @@ +-------------------------+ PF12 | | PF22 PF11 | | PF21 +---+ +-----+-----+ +-----+-----+ +---+ |SW1+---------+(lo11/lo12)+-------------+(lo21/lo22)+--------------+SW2| +---+ | R1 +-------------+ R2 | +---+ +-----------+ +-----------+ Figure 1: CCDR architecture in simple topology - In Intra-AS scenario, IGP and BGP are deployed between R1 and R2. In - inter-AS scenario, only native BGP protocol is deployed. The traffic - between each address pair may change in real time and the - corresponding source/destination addresses of the traffic may also - change dynamically. + In the Intra-AS scenario, IGP and BGP combined with a PCE are + deployed between R1 and R2. In the inter-AS scenario, only the + native BGP protocol is deployed. The traffic between each address + pair may change in real time and the corresponding source/destination + addresses of the traffic may also change dynamically. The key ideas of the CCDR architecture for this simple topology are - the followings: + the following: o Build two BGP sessions between R1 and R2, via the different loopback addresses on these routers. - o Set the explicit peer route on R1 and R2 respectively for BGP next - hop to different physical link addresses between R1 and R2. Such - explicit peer route can be set in the format of static route to - BGP peer address, which is different from the route learned from - the IGP protocol. + o Using the PCE, set the explicit peer route on R1 and R2 for BGP + next hop to different physical link addresses between R1 and R2. + The explicit peer route can be set in the format of a static + route, which is different from the route learned from the IGP + protocol. o Send different prefixes via the established BGP sessions. For example, PF11/PF21 via the BGP session 1 and PF12/PF22 via the BGP session 2. - After the above actions, the bi-direction traffic between the PF11 - and PF21, and the bi-direction traffic between PF12 and PF22 will go - through different physical links between R1 and R2. + After the above actions, the bi-directional traffic between the PF11 + and PF21, and the bi-directional traffic between PF12 and PF22 will + go through different physical links between R1 and R2. If there is more traffic between PF12 and PF22 that needs to be assured , one can add more physical links between R1 and R2 to reach - the the next hop for BGP session 2. In this cases the prefixes that + the next hop for BGP session 2. In this case, the prefixes that are advertised by the BGP peers need not be changed. - If, for example, there is bi-directional traffic from another address - pair that needs to be assured (for example prefix PF13/PF23), and the - total volume of assured traffic does not exceed the capacity of the + If, for example, there is bi-directional priority traffic from + another address pair (for example prefix PF13/PF23), and the total + volume of priority traffic does not exceed the capacity of the previously provisioned physical links, one need only to advertise the newly added source/destination prefixes via the BGP session 2. The - bi-direction traffic between PF13/PF23 will go through the assigned - dedicated physical links as the traffic between PF12/PF22. + bi-directional traffic between PF13/PF23 will go through the same + assigned dedicated physical links as the traffic between PF12/PF22. - Such decouple philosophy achieves the flexible control capability for - the network traffic, to achieve the determined QoS assurance effect - to meet the application's requirement. The router needs only support - native IP and multiple BGP sessions setup via different loopback - addresses. + Such a decoupling philosophy of the IGP/BGP traffic link and the + physical link achieves a flexible control capability for the network + traffic, achieving the needed QoS assurance to meet the application's + requirement. The router needs only support native IP and multiple + BGP sessions setup via different loopback addresses. 4. CCDR Architecture in Large Scale Topology - When the assured traffic spans across the large scale network, as - that illustrated in Figure 2, the multiple BGP sessions cannot be - established hop by hop, especially for the iBGP within one AS. + When the priority traffic spans across a large scale network, as that + illustrated in Figure 2, the multiple BGP sessions cannot be + established hop by hop, for example, the iBGP within one AS. - For such scenario, we should consider using the Route Reflector (RR) - [RFC4456] to achieve the similar effect. Every edge router will + For such a scenario, we propose using a Route Reflector (RR) + [RFC4456] to achieve a similar effect. Every edge router will establish two BGP sessions with the RR via different loopback addresses respectively. The other steps for traffic differentiation - are same as that described in the CCDR architecture for simple - topology. + are the same as that described in the CCDR architecture for the + simple topology. As shown in Figure 2, if we select R3 as the RR, every edge router(R1 and R7 in this example) will build two BGP session with the RR. If the PCE selects the dedicated path as R1-R2-R4-R7, then the operator should set the explicit peer routes via PCEP protocol on these routers respectively, pointing to the BGP next hop (loopback addresses of R1 and R7, which are used to send the prefix of the - assured traffic) to the selected forwarding address. + priority traffic) to the selected forwarding address. +-----+ +----------------+ PCE +------------------+ | +--+--+ | | | | | | | | ++-+ | +------------------+R3+-------------------+ PF12 | +--+ | PF22 PF11 | | PF21 @@ -260,22 +250,22 @@ +---+ ++-+ +--+ +--+ +-++ +---+ | | | | | +--+ +--+ | +------------+R2+----------+R4+-----------+ +--+ +--+ Figure 2: CCDR architecture in large scale network 5. CCDR Multiple BGP Sessions Strategy - In general situation, different applications may require different - QoS criteria, which may include: + Generally, different applications may require different QoS criteria, + which may include: o Traffic that requires low latency and is not sensitive to packet loss. o Traffic that requires low packet loss and can endure higher latency. o Traffic that requires low jitter. These different traffic requirements can be summarized in the @@ -287,68 +277,69 @@ | 1 | Low | Normal | Don't care | +----------------+-------------+---------------+-----------------+ | 2 | Normal | Low | Dont't care | +----------------+-------------+---------------+-----------------+ | 3 | Normal | Normal | Low | +----------------+-------------+---------------+-----------------+ Table 1. Traffic Requirement Criteria For Prefix Set No.1, we can select the shortest distance path to carry the traffic; for Prefix Set No.2, we can select the path that - has end to end under-loading links; For Prefix Set No.3, we can let - all assured traffic pass the determined single path, no Equal Cost + has end to end under-loading links; for Prefix Set No.3, we can let + traffic pass over a determined single path, as no Equal Cost Multipath (ECMP) distribution on the parallel links is desired. It is almost impossible to provide an End-to-End (E2E) path - efficiently with latency, jitter, packet loss constraints to meet the - above requirements in large scale IP-based network via the - distributed routing protocol, but these requirements can be solved - with the assistance of PCE, as that described in [RFC4655] and - [RFC8283] because the PCE has the overall network view, can collect - real network topology and network performance information about the - underlying network, select the appropriate path to meet various - network performance requirements of different traffics. + efficiently with latency, jitter, and packet loss constraints to meet + the above requirements in a large scale IP-based network only using a + distributed routing protocol, but these requirements can be met with + the assistance of PCE, as that described in [RFC4655] and [RFC8283]. + The PCE will have the overall network view, ability to collect the + real-time network topology, and the network performance information + about the underlying network. The PCE can select the appropriate + path to meet the various network performance requirements for + different traffic. The architecture to implement the CCDR Multiple BGP sessions strategy - is the followings: + is as the follows: - Here PCE is the main component of the Software Definition Network - (SDN) controller and is responsible for optimal path computation for - priority traffic. + The PCE will be responsible for the optimal path computation for the + different priority classes of traffic: - o SDN controller gets topology via BGP-LS [RFC7752] and link - utilization information via existing Network Monitor System (NMS) - from the underlying network. + o PCE collects topology information via BGP-LS [RFC7752] and link + utilization information via the existing Network Monitoring System + (NMS) from the underlying network. - o PCE calculates the appropriate path upon application's - requirements, sends the key parameters to edge/RR routers(R1, R7 - and R3 in Fig.3) to establish multiple BGP sessions. The loopback - addresses used for BGP sessions should be planned in advance and - distributed in the domain. + o PCE calculates the appropriate path based upon the application's + requirements, and sends the key parameters to edge/RR routers(R1, + R7 and R3 in Figure 3) to establish multiple BGP sessions. The + loopback addresses used for the BGP sessions should be planned in + advance and distributed in the domain. o PCE sends the route information to the routers (R1,R2,R4,R7 in - Fig.3) on forwarding path via PCEP + Figure 3) on the forwarding path via PCEP [I-D.ietf-pce-pcep-extension-native-ip] , to build the path to the BGP next-hop of the advertised prefixes. - o PCE send the prefixes information to the PCC to let them - advertises different prefixes via the specified BGP session. + o PCE send the prefixes information to the PCC for advertising + different prefixes via the specified BGP session. - o If the assured traffic prefixes were changed but the total volume - of assured traffic does not exceed the physical capacity of the - previous E2E path, PCE needs only change the prefixed advertised - via the edge routers (R1,R7 in Fig.3). + o If the priority traffic prefixes were changed but the total volume + of priority traffic does not exceed the physical capacity of the + previous E2E path, the PCE needs only change the prefixed + advertised via the edge routers (R1,R7 in Figure 3). - o If the volume of assured traffic exceeds the capacity of previous - calculated path, PCE can recalculate and add the appropriate paths - to accommodate the exceeding traffic. After that, PCE needs to - update on-path routers to build the forwarding path hop by hop. + o If the volume of priority traffic exceeds the capacity of the + previous calculated path, the PCE can recalculate and add the + appropriate paths to accommodate the exceeding traffic. After + that, the PCE needs to update the on-path routers to build the + forwarding path hop by hop. +------------+ | Application| +------+-----+ | +--------+---------+ +----------+SDN Controller/PCE+-----------+ | +--------^---------+ | | | | | | | @@ -359,122 +350,131 @@ PF12 | +--+ | PF22 PF11 | | PF21 +---+ +v-+ +--+ +--+ +-v+ +---+ |SW1+-------+R1+----------+R5+----------+R6+---------+R7+--------+SW2| +---+ ++-+ +--+ +--+ +-++ +---+ | | | | | +--+ +--+ | +------------+R2+----------+R4+-----------+ - Figure 3: CCDR architecture for Multi-BGP deployment + Figure 3: CCDR architecture for Multi-BGP sessions deployment 6. PCEP Extension for Key Parameters Delivery The PCEP protocol needs to be extended to transfer the following key parameters: o Peer information that is used to build the BGP session o Explicit route information to BGP next hop of advertised prefixes o Advertised prefixes and their associated BGP session. Once the router receives such information, it should establish the BGP session with the peer appointed in the PCEP message, build the - end to end dedicated path hop by hop and advertise the prefixes that + end to end dedicated path hop by hop, and advertise the prefixes that contained in the corresponding PCEP message. The dedicated path is preferred by making sure that the explicit route created by PCE has the higher priority (lower route preference) than the route information created by other dynamic protocols. All above dynamically created states (BGP sessions, Explicit route, Prefix advertised prefix, ) will be cleared on the expiration of state timeout interval which is based on the existing Stateful PCE [RFC8231] and PCECC [RFC8283] mechanism. - Details of communications between PCEP and BGP subsystems in router's - control plane are out of scope of this draft and will be described in - separate draft [I-D.ietf-pce-pcep-extension-native-ip] . + 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 + [I-D.ietf-pce-pcep-extension-native-ip] . 7. Deployment Consideration 7.1. Scalability - In CCDR architecture, PCE needs only influence the edge routers for - the prefixes advertisement via the multiple BGP sessions deployment. - The route information for these prefixes within the on-path routers - were distributed via the BGP protocol. + 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. - For multiple domains deployment, the PCE or the pool of PCEs that - responsible for these domains need only control the edge router to - build multiple EBGP sessions, all other procedures are the same that - in one domain. + For multiple domains deployment, the PCE, or the pool of PCEs + responsible for these domains, needs only to control the edge router + to build the multiple EBGP sessions; all other procedures are the + same as within one domain. - Unlike the solution from BGP Flowspec, the on-path router need only - keep the specific policy routes for the BGP next-hop of the + Unlike the solution from BGP Flowspec, the on-path router needs only + to keep the specific policy routes for the BGP next-hop of the differentiate prefixes, not the specific routes to the prefixes - themselves. This can lessen the burden from the table size of policy - based routes for the on-path routers, and has more expandability when - comparing with BGP flowspec or Openflow solution. For example, if we + themselves. This lessens the burden of the table size of policy + based routes for the on-path routers; and has more expandability + compared with BGP flowspec or Openflow solutions. For example, if we want to differentiate 1000 prefixes from the normal traffic, CCDR - needs only one explicit peer route in every on-path router, but the - BGP flowspec or Openflow needs 1000 policy routes on them. + needs only one explicit peer route in every on-path router, whereas + the BGP flowspec or Openflow solutions need 1000 policy routes on + them. 7.2. High Availability - The CCDR architecture is based on the distributed IP protocol. If - the PCE failed, the forwarding plane will not be impacted, as the BGP - session between all devices will not flap, and the forwarding table - will remain unchanged. + The CCDR architecture is based on the use of the native IP protocol. + If the PCE fails, the forwarding plane will not be impacted, as the + BGP sessions between all the devices will not flap and the forwarding + table remains unchanged. If one node on the optimal path is failed, the priority traffic will fall over to the best-effort forwarding path. One can even design - several assurance paths to load balance/hot-standby the priority - traffic to meet the path failure situation. + several paths to load balance/hot-standby the priority traffic to + meet the path failure situation. - For high availability of PCE/SDN-controller, operator should rely on - existing high availability solutions for SDN controller, such as - clustering technology and deployment. + For ensuring high availability of a PCE/SDN-controllers architecture, + an operator should rely on existing high availability solutions for + SDN controllers, such as clustering technology and deployment. 7.3. Incremental deployment Not every router within the network will support the PCEP extension - that defined in [I-D.ietf-pce-pcep-extension-native-ip] - simultaneously. + defined in [I-D.ietf-pce-pcep-extension-native-ip] simultaneously. - For such situations, router on the edge of domain can be upgraded - first, and then the traffic can be assured between different domains. - Within each domain, the traffic will be forwarded along the best- - effort path. Service provider can selectively upgrade the routers on - each domain in sequence. + For such situations, routers on the edge of a domain can be upgraded + first, and then the traffic can be prioritized between different + domains. Within each domain, the traffic will be forwarded along the + best-effort path. A Service provider can selectively upgrade the + routers on each domain in sequence. -8. Security Considerations +7.4. Loop Avoidance - A PCE needs to assure calculation of E2E path based on the status of - network and the service requirements in real-time. + A PCE needs to assure calculation of the E2E path based on the status + of network and the service requirements in real-time. - The PCE needs consider the explicit route deployment order (for - example, from tail router to head router) to eliminate the possible + The PCE needs to consider the explicit route deployment order (for + example, from tail rotuer to head rotuer) to eliminate any possible transient traffic loop. - The setup of BGP session, prefix advertisement and explicit peer - route establishment are all controlled by the PCE. To prevent the - bogus PCE to send harmful messages to the network nodes, the network - devices should authenticate the validity of PCE and keep secures - communication channel between them. Mechanism described in [RFC8253] - should be used to avoid such situation. +8. Security Considerations - CCDR architecture does not require the change of forward behavior on - the underlay devices, then there will no additional security impact - on the devices. + The setup of BGP sessions, prefix advertisement, and explicit peer + route establishment are all controlled by the PCE. To prevent a + bogus PCE sending harmful messages to the network nodes, the network + devices should authenticate the validity of the PCE and ensure a + secure communication channel between them. Mechanisms described in + [RFC8253] should be used. + + The CCDR architecture does not require the changes of forwarding + behavior on the underlay devices, there will no additional security + impacts on these devices. 9. IANA Considerations This document does not require any IANA actions. 10. Acknowledgement The author would like to thank Deborah Brungard, Adrian Farrel, Vishnu Beeram, Lou Berger, Dhruv Dhody, Raghavendra Mallya , Mike Koldychev, Haomian Zheng, Penghui Mi, Shaofu Peng and Jessica Chen @@ -487,25 +487,20 @@ [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)", RFC 4456, DOI 10.17487/RFC4456, April 2006, . [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation Element (PCE)-Based Architecture", RFC 4655, DOI 10.17487/RFC4655, August 2006, . - [RFC4657] Ash, J., Ed. and J. Le Roux, Ed., "Path Computation - Element (PCE) Communication Protocol Generic - Requirements", RFC 4657, DOI 10.17487/RFC4657, September - 2006, . - [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation Element (PCE) Communication Protocol (PCEP)", RFC 5440, DOI 10.17487/RFC5440, March 2009, . [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and S. Ray, "North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP", RFC 7752, DOI 10.17487/RFC7752, March 2016, . @@ -515,26 +510,20 @@ Extensions for Stateful PCE", RFC 8231, DOI 10.17487/RFC8231, September 2017, . [RFC8253] Lopez, D., Gonzalez de Dios, O., Wu, Q., and D. Dhody, "PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)", RFC 8253, DOI 10.17487/RFC8253, October 2017, . - [RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path - Computation Element Communication Protocol (PCEP) - Extensions for PCE-Initiated LSP Setup in a Stateful PCE - Model", RFC 8281, DOI 10.17487/RFC8281, December 2017, - . - [RFC8283] Farrel, A., Ed., Zhao, Q., Ed., Li, Z., and C. Zhou, "An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central Control", RFC 8283, DOI 10.17487/RFC8283, December 2017, . [RFC8735] Wang, A., Huang, X., Kou, C., Li, Z., and P. Mi, "Scenarios and Simulation Results of PCE in a Native IP Network", RFC 8735, DOI 10.17487/RFC8735, February 2020, . @@ -551,30 +540,30 @@ Aijun Wang China Telecom Beiqijia Town, Changping District Beijing 102209 China Email: wangaj3@chinatelecom.cn Boris Khasanov - Huawei Technologies - Moskovskiy Prospekt 97A - St.Petersburg 196084 + Yandex LLC + Ulitsa Lva Tolstogo 16 + Moscow Russia Email: bhassanov@yahoo.com + Quintin Zhao Etheric Networks 1009 S CLAREMONT ST SAN MATEO, CA 94402 USA Email: qzhao@ethericnetworks.com - Huaimo Chen Futurewei Boston, MA USA Email: huaimo.chen@futurewei.com