RFC 1907: Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3418.
Current document in this lineage: RFC 3418 — Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)
In plain English — editorial summary, not part of the RFC
It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1907
- Published
- January 1996
- Authors
- J. Case; K. McCloghrie; M. Rose; S. Waldbusser
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- mgt
- Pages
- 20
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1450 (1993)
- RFC 1907 (1996)
- RFC 3418 (2002) ✓
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 1908Coexistence between Version 1 and Version 2 of the Internet-standard Network Management FrameworkObsoleted
January 1996
- RFC 1906Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)Obsoleted
January 1996
- RFC 1905Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)Obsoleted
January 1996
- RFC 1904Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)Obsoleted
January 1996
- RFC 1903Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)Obsoleted
January 1996
- RFC 1902Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)Obsoleted
January 1996
- RFC 1901Introduction to Community-based SNMPv2Current
January 1996
- RFC 1909An Administrative Infrastructure for SNMPv2Current
February 1996
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?