RFC 8306: Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
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
- —
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 8302Transparent Interconnection of Lots of Links (TRILL): ARP and Neighbor Discovery (ND) OptimizationCurrent
January 2018
- RFC 8300Network Service Header (NSH)Updated
January 2018
- RFC 8296Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS NetworksCurrent
January 2018
- RFC 8317Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)Current
January 2018
- RFC 8294Common YANG Data Types for the Routing AreaCurrent
December 2017
- RFC 8293A Framework for Multicast in Network Virtualization over Layer 3Current
January 2018
- RFC 8320LDP Extensions to Support Maximally Redundant TreesCurrent
February 2018
- RFC 8287Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data PlanesUpdated
December 2017
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?