RFC 7334: PCE-Based Computation Procedure to Compute Shortest Constrained Point-to-Multipoint (P2MP) Inter-Domain Traffic Engineering Label Switched Paths
In plain English — editorial summary, not part of the RFC
The ability to compute paths for constrained point-to-multipoint (P2MP) Traffic Engineering Label Switched Paths (TE LSPs) across multiple domains has been identified as a key requirement for the deployment of P2MP services in MPLS- and GMPLS-controlled networks. The Path Computation Element (PCE) has been recognized as an appropriate technology for the determination of inter-domain paths of P2MP TE LSPs. This document describes an experiment to provide procedures and extensions to the PCE Communication Protocol (PCEP) for the computation of inter-domain paths for P2MP TE LSPs.
Document record
- Document ID
- RFC7334
- Published
- August 2014
- Authors
- Q. Zhao; D. Dhody; D. King; Z. Ali; R. Casellas
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7331Bidirectional Forwarding Detection (BFD) Management Information BaseCurrent
August 2014
- RFC 7338Requirements and Framework for Point-to-Multipoint Pseudowires over MPLS Packet Switched NetworksCurrent
September 2014
- RFC 7330Definitions of Textual Conventions (TCs) for Bidirectional Forwarding Detection (BFD) ManagementCurrent
August 2014
- RFC 7325MPLS Forwarding Compliance and Performance RequirementsCurrent
August 2014
- RFC 7324Updates to MPLS Transport Profile Linear ProtectionCurrent
July 2014
- RFC 7349LDP Hello Cryptographic AuthenticationCurrent
August 2014
- RFC 7318Policy Qualifiers in Resource Public Key Infrastructure (RPKI) CertificatesCurrent
July 2014
- RFC 7353Security Requirements for BGP Path ValidationCurrent
August 2014
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?