RFC 8623: Stateful Path Computation Element (PCE) Protocol Extensions for Usage with Point-to-Multipoint TE Label Switched Paths (LSPs)
In plain English — editorial summary, not part of the RFC
The Path Computation Element (PCE) has been identified as an appropriate technology for the determination of the paths of point- to-multipoint (P2MP) TE Label Switched Paths (LSPs). This document provides extensions required for the Path Computation Element Communication Protocol (PCEP) so as to enable the usage of a stateful PCE capability in supporting P2MP TE LSPs.
Document record
- Document ID
- RFC8623
- Published
- June 2019
- Authors
- U. Palle; D. Dhody; Y. Tanaka; V. Beeram
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 33
- Also known as
- —
- Updated by:
- RFC 9756
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.
- RFC 8625Ethernet Traffic Parameters with Availability InformationCurrent
August 2019
- RFC 8629Dynamic Link Exchange Protocol (DLEP) Multi-Hop Forwarding ExtensionCurrent
July 2019
- RFC 8614Updated Processing of Control Flags for BGP Virtual Private LAN Service (VPLS)Current
June 2019
- RFC 8632A YANG Data Model for Alarm ManagementCurrent
September 2019
- RFC 8611Label Switched Path (LSP) Ping and Traceroute Multipath Support for Link Aggregation Group (LAG) InterfacesUpdated
June 2019
- RFC 8637Applicability of the Path Computation Element (PCE) to the Abstraction and Control of TE Networks (ACTN)Current
July 2019
- RFC 8596MPLS Transport Encapsulation for the Service Function Chaining (SFC) Network Service Header (NSH)Current
June 2019
- RFC 8595An MPLS-Based Forwarding Plane for Service Function ChainingCurrent
June 2019
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?