RFC 7571: GMPLS RSVP-TE Extensions for Lock Instruct and Loopback
In plain English — editorial summary, not part of the RFC
This document specifies extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) to support Lock Instruct (LI) and Loopback (LB) mechanisms for Label Switched Paths (LSPs). These mechanisms are applicable to technologies that use Generalized MPLS (GMPLS) for the control plane.
Document record
- Document ID
- RFC7571
- Published
- July 2015
- Authors
- J. Dong; M. Chen; Z. Li; D. Ceccarelli
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TECurrent
March 2015
- RFC 7455Transparent Interconnection of Lots of Links (TRILL): Fault ManagementCurrent
March 2015
- RFC 7759Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using Label Switched Path (LSP) PingCurrent
February 2016
- RFC 8256Requirements for Hitless MPLS Path Segment MonitoringCurrent
October 2017
- RFC 8372MPLS Flow Identification ConsiderationsCurrent
May 2018
- RFC 8403A Scalable and Topology-Aware MPLS Data-Plane Monitoring SystemCurrent
July 2018
- RFC 6435MPLS Transport Profile Lock Instruct and Loopback FunctionsCurrent
November 2011
- RFC 6428Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport ProfileUpdated
November 2011
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?