MPLS Transport Profile Lock Instruct and Loopback Functions
RFC 6435, “MPLS Transport Profile Lock Instruct and Loopback Functions”, is a Proposed Standard document published in November 2011 by S. Boutros, S. Sivabalan, R. Aggarwal, M. Vigoureux, X. Dai. It updates RFC 6371. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6435 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6434 IPv6 Node Requirements
- RFC 6436 Rationale for Update to the IPv6 Flow Label Specification
- RFC 6433 Requirements for a Working Group Milestones Tool
- RFC 6437 IPv6 Flow Label Specification
- RFC 6432 Carrying Q.850 Codes in Reason Header Fields in SIP Responses
- RFC 6438 Using the IPv6 Flow Label for Equal Cost Multipath Routing and Link Aggregation in Tunnels
- RFC 6431 Huawei Port Range Configuration Options for PPP IP Control Protocol
- RFC 6439 Routing Bridges : Appointed Forwarders