RFC 7453: MPLS Transport Profile (MPLS-TP) Traffic Engineering (TE) 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 additional managed objects and textual conventions for tunnels, identifiers, and Label Switching Routers to support Multiprotocol Label Switching (MPLS) MIB modules for transport networks.
Document record
- Document ID
- RFC7453
- Published
- February 2015
- Authors
- V. Mahalingam; K. Sampath; S. Aldrin; T. Nadeau
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 62
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7455Transparent Interconnection of Lots of Links (TRILL): Fault ManagementCurrent
March 2015
- RFC 7456Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL)Current
March 2015
- RFC 7449Path Computation Element Communication Protocol (PCEP) Requirements for Wavelength Switched Optical Network (WSON) Routing and Wavelength AssignmentCurrent
February 2015
- RFC 7447Deprecation of BGP Entropy Label Capability AttributeCurrent
February 2015
- RFC 7446Routing and Wavelength Assignment Information Model for Wavelength Switched Optical NetworksCurrent
February 2015
- RFC 7442Carrying Protocol Independent Multicast - Sparse Mode (PIM-SM) in Any-Source Multicast (ASM) Mode Trees over Multipoint LDP (mLDP)Current
February 2015
- RFC 7441Encoding Multipoint LDP (mLDP) Forwarding Equivalence Classes (FECs) in the NLRI of BGP MCAST-VPN RoutesCurrent
January 2015
- RFC 7466An Optimization for the Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)Current
March 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?