A new Request for Comments is now available in online RFC libraries.
RFC 9689
Title: Use Cases for a PCE as a Central Controller (PCECC)
Author: Z. Li,
D. Dhody,
Q. Zhao,
Z. Ke,
B. Khasanov
Status: Informational
Stream: IETF
Date: December 2024
Mailbox: [email protected],
[email protected],
[email protected],
[email protected],
[email protected]
Pages: 37
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-teas-pcecc-use-cases-18.txt
URL: https://www.rfc-editor.org/info/rfc9689
DOI: 10.17487/RFC9689
The PCE is a core component of a Software-Defined Networking (SDN)
system. It can be used to compute optimal paths for network traffic
and update existing paths to reflect changes in the network or
traffic demands. The PCE was developed to derive Traffic Engineering
(TE) paths in MPLS networks, which are supplied to the headend of the
paths using the Path Computation Element Communication Protocol
(PCEP).
SDN has much broader applicability than signalled MPLS TE networks,
and the PCE may be used to determine paths in a range of use cases
including static Label-Switched Paths (LSPs), Segment Routing (SR),
Service Function Chaining (SFC), and most forms of a routed or
switched network. Therefore, it is 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.
A PCE as a Central Controller (PCECC) can simplify the processing of
a distributed control plane by blending it with elements of SDN
without necessarily completely replacing it. 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, which
are required for the PCECC use cases, are covered in separate
documents.
This document is a product of the Traffic Engineering Architecture and
Signaling Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
