metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP)

Still current, but amended. Parts of this document are changed or extended by RFC 7896, RFC 8253, RFC 8356, RFC 9488, RFC 9756. Read both.

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

This document specifies the Path Computation Element (PCE) Communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a PCE, or between two PCEs. Such interactions include path computation requests and path computation replies as well as notifications of specific states related to the use of a PCE in the context of Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering. PCEP is designed to be flexible and extensible so as to easily allow for the addition of further messages and objects, should further requirements be expressed in the future. [STANDARDS-TRACK]

Document record

Document ID
RFC5440
Published
March 2009
Authors
JP. Vasseur; JL. Le Roux
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
87
Also known as
—
Updated by:
RFC 7896, RFC 8253, RFC 8356, RFC 9488, RFC 9756

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/5440-path-computation-element-pce-communication-protocol-pcep