RFC 6639: Multiprotocol Label Switching Transport Profile (MPLS-TP) MIB-Based Management Overview
In plain English — editorial summary, not part of the RFC
A range of Management Information Base (MIB) modules has been developed to help model and manage the various aspects of Multiprotocol Label Switching (MPLS) networks. These MIB modules are defined in separate documents that focus on the specific areas of responsibility of the modules that they describe. The MPLS Transport Profile (MPLS-TP) is a profile of MPLS functionality specific to the construction of packet-switched transport networks. This document describes the MIB-based architecture for MPLS-TP, indicates the interrelationships between different existing MIB modules that can be leveraged for MPLS-TP network management, and identifies areas where additional MIB modules are required. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6639
- Published
- June 2012
- Authors
- D. King; M. Venkatesan
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 29
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6625Wildcards in Multicast VPN Auto-Discovery RoutesUpdated
May 2012
- RFC 6622Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)Obsoleted
May 2012
- RFC 6621Simplified Multicast ForwardingCurrent
May 2012
- RFC 6658Packet Pseudowire Encapsulation over an MPLS PSNCurrent
July 2012
- RFC 6667LDP 'Typed Wildcard' Forwarding Equivalence Class (FEC) for PWid and Generalized PWid FEC ElementsCurrent
July 2012
- RFC 6669An Overview of the Operations, Administration, and Maintenance (OAM) Toolset for MPLS-Based Transport NetworksCurrent
July 2012
- RFC 6608Subcodes for BGP Finite State Machine ErrorCurrent
May 2012
- RFC 6670The Reasons for Selecting a Single Solution for MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM)Current
July 2012
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?