metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 8408: Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages

Still current, but amended. Parts of this document are changed or extended by RFC 8664. Read both.

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

A Path Computation Element (PCE) can compute Traffic Engineering (TE) paths through a network; these paths are subject to various constraints. Currently, TE paths are Label Switched Paths (LSPs) that are set up using the RSVP-TE signaling protocol. However, other TE path setup methods are possible within the PCE architecture. This document proposes an extension to the PCE Communication Protocol (PCEP) to allow support for different path setup methods over a given PCEP session.

Document record

Document ID
RFC8408
Published
July 2018
Authors
S. Sivabalan; J. Tantsura; I. Minei; R. Varga; J. Hardwick
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
12
Also known as
—
Updated by:
RFC 8664

Referenced by

One later RFC formally updates or obsoletes 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/8408-conveying-path-setup-type-in-pce-communication-protocol-pcep-messages