Search RFCs
RFC 6435
MPLS Transport Profile Lock Instruct and Loopback Functions,November 2011
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 6371
- Authors:
- S. Boutros, Ed.
S. Sivabalan, Ed.
R. Aggarwal, Ed.
M. Vigoureux, Ed.
X. Dai, Ed. - Stream:
- IETF
- Source:
- mpls (rtg)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6435
Discuss this RFC: Send questions or comments to the mailing listmpls@ietf.org
Other actions:View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6435
Abstract
Two useful Operations, Administration, and Maintenance (OAM)functions in a transport network are "lock" and "loopback". The lockfunction enables an operator to lock a transport path such that itdoes not carry client traffic, but can continue to carry OAM messagesand may carry test traffic. The loopback function allows an operatorto set a specific node on the transport path into loopback mode suchthat it returns all received data.
This document specifies the lock function for MPLS networks anddescribes how the loopback function operates in MPLS networks.
This document updates Sections 7.1.1 and 7.1.2 of RFC 6371. [STANDARDS-TRACK]
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.