RFC 2922: Physical Topology 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 used for managing physical topology identification and discovery. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2922
- Published
- September 2000
- Authors
- A. Bierman; K. Jones
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2896Remote Network Monitoring MIB Protocol Identifier MacrosCurrent
August 2000
- RFC 2737Entity MIB (Version 2)Obsoleted
December 1999
- RFC 2674Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN ExtensionsObsoleted
August 1999
- RFC 2668Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)Obsoleted
August 1999
- RFC 2666Definitions of Object Identifiers for Identifying Ethernet Chip SetsCurrent
August 1999
- RFC 2665Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
August 1999
- RFC 2621RADIUS Accounting Server MIBObsoleted
June 1999
- RFC 2620RADIUS Accounting Client MIBObsoleted
June 1999
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?