The Use Cases for Path Computation Element (PCE) as a Central Controller (PCECC).
draft-ietf-teas-pcecc-use-cases-04

Document Type Expired Internet-Draft (teas WG)
Last updated 2020-01-05 (latest revision 2019-07-04)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-teas-pcecc-use-cases-04.txt

Abstract

The Path Computation Element (PCE) is a core component of a Software- Defined Networking (SDN) system. It can compute optimal paths for traffic across a network and can also update the paths to reflect changes in the network or traffic demands. PCE was developed to derive paths for MPLS Label Switched Paths (LSPs), which are supplied to the head end of the LSP using the Path Computation Element Communication Protocol (PCEP). SDN has a broader applicability than signaled MPLS traffic-engineered (TE) networks, and the PCE may be used to determine paths in a range of use cases including static LSPs, segment routing (SR), Service Function Chaining (SFC), and most forms of a routed or switched network. It is, therefore, reasonable to consider PCEP as a control protocol for use in these environments to allow the PCE to be fully enabled as a central controller. This document describes general considerations for PCECC deployment and examines its applicability and benefits, as well as its challenges and limitations, through a number of use cases. PCEP extensions required for stateful PCE usage are covered in separate documents. This is a living document to catalogue the use cases for PCECC. There is currently no intention to publish this work as an RFC.

Authors

Quintin Zhao (quintinzhao@gmail.com)
Zhenbin Li (lizhenbin@huawei.com)
Boris Khasanov (khasanov.boris@huawei.com)
Dhruv Dhody (dhruv.ietf@gmail.com)
Zekung Ke (kinghe@tencent.com)
Luyuan Fang (luyuanf@gmail.com)
Chao Zhou (chao.zhou@cisco.com)
Telus Communications (boris.zhang@telus.com)
Artem Rachitskiy (arachitskiy@mts.by)
Anton Gulida (anton.gulida@life.com.by)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)