RFC 2037: Entity MIB using SMIv2
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2737.
Current document in this lineage: 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 SNMP agent. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2037
- Published
- October 1996
- Authors
- K. McCloghrie; A. Bierman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 35
- Also known as
- —
- Obsoleted by:
- RFC 2737
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) ✓
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 2257Agent Extensibility (AgentX) Protocol Version 1Obsoleted
January 1998
- RFC 2248Network Services Monitoring MIBObsoleted
January 1998
- RFC 1749IEEE 802.5 Station Source Routing MIB using SMIv2Current
December 1994
- RFC 1743IEEE 802.5 MIB using SMIv2Obsoleted
December 1994
- RFC 2074Remote Network Monitoring MIB Protocol IdentifiersObsoleted
January 1997
- RFC 2108Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2Current
February 1997
- RFC 1748IEEE 802.5 MIB using SMIv2Updated
December 1994
- RFC 2358Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
June 1998
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?