The Use Cases for Path Computation Element (PCE) as a Central Controller (PCECC).
draft-ietf-teas-pcecc-use-cases-05
TEAS Working Group Q. Zhao
Internet-Draft Z. Li
Intended status: Informational B. Khasanov
Expires: September 9, 2020 D. Dhody
Huawei Technologies
K. Ke
Tencent Holdings Ltd.
L. Fang
Expedia, Inc.
C. Zhou
Cisco Systems
B. Zhang
Telus Communications
A. Rachitskiy
Mobile TeleSystems JLLC
A. Gulida
LLC "Lifetech"
March 8, 2020
The Use Cases for Path Computation Element (PCE) as a Central Controller
(PCECC).
draft-ietf-teas-pcecc-use-cases-05
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.
Zhao, et al. Expires September 9, 2020 [Page 1]
Internet-Draft PCECC March 2020
This is a living document to catalogue the use cases for PCECC.
There is currently no intention to publish this work as an RFC.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
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 September 9, 2020.
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
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.
Zhao, et al. Expires September 9, 2020 [Page 2]
Internet-Draft PCECC March 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
Show full document text