RFC 6107: Procedures for Dynamically Signaled Hierarchical Label Switched Paths
In plain English — editorial summary, not part of the RFC
Label Switched Paths (LSPs) set up in Multiprotocol Label Switching (MPLS) or Generalized MPLS (GMPLS) networks can be used to form links to carry traffic in those networks or in other (client) networks. Protocol mechanisms already exist to facilitate the establishment of such LSPs and to bundle traffic engineering (TE) links to reduce the load on routing protocols. This document defines extensions to those mechanisms to support identifying the use to which such LSPs are to be put and to enable the TE link endpoints to be assigned addresses or unnumbered identifiers during the signaling process. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6107
- Published
- February 2011
- Authors
- K. Shiomoto; A. Farrel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5862Path Computation Clients (PCC) - Path Computation Element (PCE) Requirements for Point-to-Multipoint MPLS-TECurrent
June 2010
- RFC 6457PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic EngineeringCurrent
December 2011
- RFC 5623Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic EngineeringCurrent
September 2009
- RFC 5521Extensions to the Path Computation Element Communication Protocol (PCEP) for Route ExclusionsCurrent
April 2009
- RFC 5495Description of the Resource Reservation Protocol - Traffic-Engineered (RSVP-TE) Graceful Restart ProceduresCurrent
March 2009
- RFC 5440Path Computation Element (PCE) Communication Protocol (PCEP)Updated
March 2009
- RFC 5298Analysis of Inter-Domain Label Switched Path (LSP) RecoveryCurrent
August 2008
- RFC 5253Applicability Statement for Layer 1 Virtual Private Network (L1VPN) Basic ModeCurrent
July 2008
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?