database logo graphic

RFC 6435

"MPLS Transport Profile Lock Instruct and Loopback Functions", November 2011

Canonical URL:
http://www.rfc-editor.org/rfc/rfc6435.txt
This document is also available in this non-normative format: PDF.
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

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

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 4844.


Go to the RFC Editor Homepage.