RFC 2895: Remote Network Monitoring MIB Protocol Identifier Reference
In plain English — editorial summary, not part of the RFC
This memo defines a notation describing protocol layers in a protocol encapsulation, specifically for use in encoding ``INDEX`` values for the protocolDirTable, found in the RMON-2 MIB. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2895
- Published
- August 2000
- Authors
- A. Bierman; C. Bucci; R. Iddon
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 42
- Also known as
- —
Topics
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 2819Remote Network Monitoring Management Information BaseCurrent
May 2000
- RFC 3273Remote Network Monitoring Management Information Base for High Capacity NetworksUpdated
July 2002
- RFC 2925Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup OperationsObsoleted
September 2000
- RFC 2940Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol ClientsCurrent
October 2000
- RFC 2981Event MIBCurrent
October 2000
- RFC 2982Distributed Management Expression MIBCurrent
October 2000
- RFC 3014Notification Log MIBCurrent
November 2000
- RFC 2742Definitions of Managed Objects for Extensible SNMP AgentsCurrent
January 2000
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?