RFC 4221: Multiprotocol Label Switching (MPLS) 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. This document describes the management architecture for MPLS and indicates the interrelationships between the different MIB modules used for MPLS network management. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4221
- Published
- November 2005
- Authors
- T. Nadeau; C. Srinivasan; A. Farrel
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6779Definition of Managed Objects for the Neighborhood Discovery ProtocolObsoleted
October 2012
- RFC 7184Definition of Managed Objects for the Optimized Link State Routing Protocol Version 2Current
April 2014
- RFC 7330Definitions of Textual Conventions (TCs) for Bidirectional Forwarding Detection (BFD) ManagementCurrent
August 2014
- RFC 7331Bidirectional Forwarding Detection (BFD) Management Information BaseCurrent
August 2014
- RFC 7367Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set ProcessCurrent
October 2014
- RFC 7420Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) ModuleCurrent
December 2014
- RFC 7939Definition of Managed Objects for the Neighborhood Discovery ProtocolCurrent
August 2016
- RFC 8150MPLS Transport Profile Linear Protection MIBCurrent
April 2017
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?