RFC 2896: Remote Network Monitoring MIB Protocol Identifier Macros
In plain English — editorial summary, not part of the RFC
This memo contains various protocol identifier examples, which can be used to produce valid protocolDirTable ``INDEX`` encodings, as defined by the Remote Network Monitoring MIB and the RMON Protocol Identifier Reference. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2896
- Published
- August 2000
- Authors
- A. Bierman; C. Bucci; R. Iddon
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 84
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2074Remote Network Monitoring MIB Protocol IdentifiersObsoleted
January 1997
- RFC 2922Physical Topology MIBCurrent
September 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
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?