RFC 7697: MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM) Identifiers Management Information Base (MIB)
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects to configure the Operations, Administration, and Maintenance (OAM) identifiers for Multiprotocol Label Switching (MPLS) and the MPLS-based Transport Profile (TP).
Document record
- Document ID
- RFC7697
- Published
- January 2016
- Authors
- P. Pan; S. Aldrin; M. Venkatesan; K. Sampath; T. Nadeau; S. Boutros
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 36
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7698Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) NetworksCurrent
November 2015
- RFC 7699Generalized Labels for the Flexi-Grid in Lambda Switch Capable (LSC) Label Switching RoutersCurrent
November 2015
- RFC 7705Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH AttributeCurrent
November 2015
- RFC 7689Signaling Extensions for Wavelength Switched Optical NetworksCurrent
November 2015
- RFC 7688GMPLS OSPF Enhancement for Signal and Network Element Compatibility for Wavelength Switched Optical NetworksCurrent
November 2015
- RFC 7708Using a Generic Associated Channel Label as a Virtual Circuit Connectivity Verification Channel IndicatorCurrent
November 2015
- RFC 7709Requirements for Very Fast Setup of GMPLS Label Switched Paths (LSPs)Current
November 2015
- RFC 7684OSPFv2 Prefix/Link Attribute AdvertisementCurrent
November 2015
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?