RFC 5298: Analysis of Inter-Domain Label Switched Path (LSP) Recovery
In plain English — editorial summary, not part of the RFC
Protection and recovery are important features of service offerings in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. Increasingly, MPLS and GMPLS networks are being extended from single domain scope to multi-domain environments. Various schemes and processes have been developed to establish Label Switched Paths (LSPs) in multi-domain environments. These are discussed in RFC 4726: "A Framework for Inter-Domain Multiprotocol Label Switching Traffic Engineering". This document analyzes the application of these techniques to protection and recovery in multi-domain networks. The main focus for this document is on establishing end-to-end diverse Traffic Engineering (TE) LSPs in multi-domain networks. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5298
- Published
- August 2008
- Authors
- T. Takeda; A. Farrel; Y. Ikejiri; JP. Vasseur
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5440Path Computation Element (PCE) Communication Protocol (PCEP)Updated
March 2009
- RFC 5152A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)Current
February 2008
- RFC 5521Extensions to the Path Computation Element Communication Protocol (PCEP) for Route ExclusionsCurrent
April 2009
- RFC 5623Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic EngineeringCurrent
September 2009
- RFC 5862Path Computation Clients (PCC) - Path Computation Element (PCE) Requirements for Point-to-Multipoint MPLS-TECurrent
June 2010
- RFC 4558Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification StatementCurrent
June 2006
- RFC 6457PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic EngineeringCurrent
December 2011
- RFC 7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TECurrent
March 2015
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?