metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 6435: MPLS Transport Profile Lock Instruct and Loopback Functions

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC6435
Published
November 2011
Authors
S. Boutros; S. Sivabalan; R. Aggarwal; M. Vigoureux; X. Dai
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
12
Also known as
—
Updates:
RFC 6371

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6435-mpls-transport-profile-lock-instruct-and-loopback-functions