UpdatedPROPOSED STANDARDIETF stream

RFC 8306: Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths

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

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

Point-to-point Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering Label Switched Paths (TE LSPs) may be established using signaling techniques, but their paths may first need to be determined. The Path Computation Element (PCE) has been identified as an appropriate technology for the determination of the paths of point-to-multipoint (P2MP) TE LSPs. This document describes extensions to the PCE Communication Protocol (PCEP) to handle requests and responses for the computation of paths for P2MP TE LSPs. This document obsoletes RFC 6006.

Document record

Document ID
RFC8306
Published
November 2017
Authors
Q. Zhao; D. Dhody; R. Palleti; D. King
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
43
Also known as
Obsoletes:
RFC 6006
Updated by:
RFC 9353

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/8306-extensions-to-the-path-computation-element-communication-protocol-pcep-for-point