RFC 4327: Link Management Protocol (LMP) Management Information Base (MIB)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4631.
Current version: RFC 4631 — Link Management Protocol (LMP) 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 for modeling the Link Management Protocol (LMP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC4327
- Published
- January 2006
- Authors
- M. Dubuc; T. Nadeau; J. Lang; E. McGinnis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 82
- Also known as
- —
- Obsoleted by:
- RFC 4631
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4328Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks ControlUpdated
January 2006
- RFC 4349High-Level Data Link Control (HDLC) Frames over Layer 2 Tunneling Protocol, Version 3 (L2TPv3)Updated
February 2006
- RFC 4360BGP Extended Communities AttributeUpdated
February 2006
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
- RFC 4365Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs)Current
February 2006
- RFC 4368Multiprotocol Label Switching (MPLS) Label-Controlled Asynchronous Transfer Mode (ATM) and Frame-Relay Management Interface DefinitionCurrent
January 2006
- RFC 4277Experience with the BGP-4 ProtocolCurrent
January 2006
- RFC 4377Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) NetworksCurrent
February 2006
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?