RFC 6006: Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8306.
Current version: 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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6006
- Published
- September 2010
- Authors
- Q. Zhao; D. King; F. Verhaeghe; T. Takeda; Z. Ali; J. Meuric
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 33
- Also known as
- —
- Obsoleted by:
- RFC 8306
Topics
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 5722Handling of Overlapping IPv6 FragmentsUpdated
December 2009
- RFC 5584RTP Payload Format for the Adaptive TRansform Acoustic Coding (ATRAC) FamilyCurrent
July 2009
- RFC 5106The Extensible Authentication Protocol-Internet Key Exchange Protocol version 2 (EAP-IKEv2) MethodCurrent
February 2008
- RFC 6946Processing of IPv6 "Atomic" FragmentsCurrent
May 2013
- RFC 7499Support of Fragmentation of RADIUS PacketsCurrent
April 2015
- RFC 7588A Widely Deployed Solution to the Generic Routing Encapsulation (GRE) Fragmentation ProblemCurrent
July 2015
- RFC 8724SCHC: Generic Framework for Static Context Header Compression and FragmentationUpdated
April 2020
- RFC 8824Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)Current
June 2021
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?