UpdatedPROPOSED STANDARDIETF stream

RFC 8231: Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE

Still current, but amended. Parts of this document are changed or extended by RFC 8786, RFC 9353, RFC 9753, RFC 9756, RFC 9862. Read both.

In plain English — editorial summary, not part of the RFC

The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests. Although PCEP explicitly makes no assumptions regarding the information available to the PCE, it also makes no provisions for PCE control of timing and sequence of path computations within and across PCEP sessions. This document describes a set of extensions to PCEP to enable stateful control of MPLS-TE and GMPLS Label Switched Paths (LSPs) via PCEP.

Document record

Document ID
RFC8231
Published
September 2017
Authors
E. Crabbe; I. Minei; J. Medved; R. Varga
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
57
Also known as

Topics

Referenced by

5 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8231-path-computation-element-communication-protocol-pcep-extensions-for-stateful-pce