RFC 6933: Entity MIB (Version 4)
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 used for managing multiple logical and physical entities managed by a single Simple Network Management Protocol (SNMP) agent. This document specifies version 4 of the Entity MIB. This memo obsoletes version 3 of the Entity MIB module published as RFC 4133.
Document record
- Document ID
- RFC6933
- Published
- May 2013
- Authors
- A. Bierman; D. Romascanu; J. Quittek; M. Chandramouli
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 76
- Also known as
- —
- Obsoletes:
- RFC 4133
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 2037 (1996)
- RFC 2737 (1999)
- RFC 4133 (2005)
- RFC 6933 (2013)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6768ATM-Based xDSL Bonded Interfaces MIBCurrent
February 2013
- RFC 6767Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIBCurrent
February 2013
- RFC 6766xDSL Multi-Pair Bonding Using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIBCurrent
February 2013
- RFC 6765xDSL Multi-Pair Bonding (G.Bond) MIBCurrent
February 2013
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
- RFC 4011Policy Based Management MIBCurrent
March 2005
- RFC 3592Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface TypeCurrent
September 2003
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?