Path Computation Element (PCE) based Traffic Engineering (TE) in Native IP Networks
draft-ietf-teas-pce-native-ip-17
Document | Type | Active Internet-Draft (teas WG) | ||
---|---|---|---|---|
Authors | Aijun Wang , Boris Khasanov , Quintin Zhao , Huaimo Chen | |||
Last updated | 2021-03-03 (latest revision 2021-02-01) | |||
Replaces | draft-wang-teas-pce-native-ip | |||
Stream | Internent Engineering Task Force (IETF) | |||
Intended RFC status | Informational | |||
Formats | plain text xml pdf htmlized (tools) htmlized bibtex | |||
Reviews | ||||
Stream | WG state | Submitted to IESG for Publication | ||
Document shepherd | Lou Berger | |||
Shepherd write-up | Show (last changed 2020-12-18) | |||
IESG | IESG state | RFC Ed Queue | ||
Action Holders |
(None)
|
|||
Consensus Boilerplate | Yes | |||
Telechat date | ||||
Responsible AD | Deborah Brungard | |||
Send notices to | Lou Berger <lberger@labn.net> | |||
IANA | IANA review state | IANA OK - No Actions Needed | ||
IANA action state | No IANA Actions | |||
RFC Editor | RFC Editor state | RFC-EDITOR | ||
Details |
TEAS Working Group A. Wang Internet-Draft China Telecom Intended status: Informational B. Khasanov Expires: August 6, 2021 Yandex LLC Q. Zhao Etheric Networks H. Chen Futurewei February 2, 2021 Path Computation Element (PCE) based Traffic Engineering (TE) in Native IP Networks draft-ietf-teas-pce-native-ip-17 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). 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 August 6, 2021. Copyright Notice Copyright (c) 2021 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 Wang, et al. Expires August 6, 2021 [Page 1] Internet-Draft pce in native ip February 2021 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 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 Critical Parameters Delivery . . . . . . . 8 7. Deployment Consideration . . . . . . . . . . . . . . . . . . 9 7.1. Scalability . . . . . . . . . . . . . . . . . . . . . . . 9 7.2. High Availability . . . . . . . . . . . . . . . . . . . . 10 7.3. Incremental deployment . . . . . . . . . . . . . . . . . 10 7.4. Loop Avoidance . . . . . . . . . . . . . . . . . . . . . 10 7.5. E2E Path Performance Monitoring . . . . . . . . . . . . . 10 8. Security Considerations . . . . . . . . . . . . . . . . . . . 10 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 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 Path Computation Element (PCE) architecture described in [RFC4655] , introduced a broader use applicability for a PCE as a central controller. PCEP Protocol (PCEP) continues to be used as the protocol between PCE and Path Computation Client (PCC). Building on that 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 a native IP network based on use of a CCDRShow full document text