RFC 6435

MPLS Transport Profile Lock Instruct and Loopback Functions, November 2011

File formats:
icon for text file icon for PDF icon for HTML icon for inline errata
RFC 6371
S. Boutros, Ed.
S. Sivabalan, Ed.
R. Aggarwal, Ed.
M. Vigoureux, Ed.
X. Dai, Ed.
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 list mpls@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 6435


Two useful Operations, Administration, and Maintenance (OAM) functions in a transport network are "lock" and "loopback". The lock function enables an operator to lock a transport path such that it does not carry client traffic, but can continue to carry OAM messages and may carry test traffic. The loopback function allows an operator to set a specific node on the transport path into loopback mode such that it returns all received data.

This document specifies the lock function for MPLS networks and describes 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 of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search