RFC 8131: RSVP-TE Signaling Procedure for End-to-End GMPLS Restoration and Resource Sharing
In plain English — editorial summary, not part of the RFC
In non-packet transport networks, there are requirements where the Generalized Multiprotocol Label Switching (GMPLS) end-to-end recovery scheme needs to employ a restoration Label Switched Path (LSP) while keeping resources for the working and/or protecting LSPs reserved in the network after the failure occurs. This document reviews how the LSP association is to be provided using Resource Reservation Protocol - Traffic Engineering (RSVP-TE) signaling in the context of a GMPLS end-to-end recovery scheme when using restoration LSP where failed LSP is not torn down. In addition, this document discusses resource sharing-based setup and teardown of LSPs as well as LSP reversion procedures. No new signaling extensions are defined by this document, and it is strictly informative in nature.
Document record
- Document ID
- RFC8131
- Published
- March 2017
- Authors
- X. Zhang; H. Zheng; R. Gandhi; Z. Ali; P. Brzozowski
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8138IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Routing HeaderUpdated
April 2017
- RFC 8139Transparent Interconnection of Lots of Links (TRILL): Appointed ForwardersCurrent
June 2017
- RFC 8116Security Threats to the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
May 2017
- RFC 8113Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type AllocationsObsoleted
March 2017
- RFC 8149RSVP Extensions for Reoptimization of Loosely Routed Point-to-Multipoint Traffic Engineering Label Switched Paths (LSPs)Current
April 2017
- RFC 8150MPLS Transport Profile Linear Protection MIBCurrent
April 2017
- RFC 8111Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)Current
May 2017
- RFC 8151Use Cases for Data Center Network Virtualization Overlay NetworksCurrent
May 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?