Skip to main content

MPLS Transport Profile Lock Instruct and Loopback Functions
RFC 6435

Revision differences

Document history

Date By Action
2020-01-21
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'Two useful Operations, Administration, and Maintenance (OAM) functions in a transport network are "lock" and "loopback". …
Received changes through RFC Editor sync (changed abstract to '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]')
2015-10-14
(System) Notify list changed from mpls-chairs@ietf.org, draft-ietf-mpls-tp-li-lb@ietf.org to (None)
2011-11-17
Cindy Morgan State changed to RFC Published from RFC Ed Queue.
2011-11-16
(System) RFC published