RFC 1231: IEEE 802.5 Token Ring MIB
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1743, RFC 1748.
Current document in this lineage: RFC 1748 — IEEE 802.5 MIB using SMIv2
In plain English — editorial summary, not part of the RFC
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.5 Token Ring technology described in 802.5 Token Ring Access Method and Physical Layer Specifications, IEEE Standard 802.5-1989. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1231
- Published
- May 1991
- Authors
- K. McCloghrie; R. Fox; E. Decker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- mgt
- Pages
- 23
- Also known as
- —
- Updated by:
- RFC 1239
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1231 (1991)
- RFC 1743 (1994)
- RFC 1748 (1994) ✓
Referenced by
3 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1230IEEE 802.4 Token Bus MIBUpdated
May 1991
- RFC 1232Definitions of managed objects for the DS1 Interface typeObsoleted
May 1991
- RFC 1229Extensions to the generic-interface MIBObsoleted
May 1991
- RFC 1233Definitions of managed objects for the DS3 Interface typeObsoleted
May 1991
- RFC 1224Techniques for managing asynchronously generated alertsCurrent
May 1991
- RFC 1215Convention for defining traps for use with the SNMPCurrent
March 1991
- RFC 1214OSI internet management: Management Information BaseCurrent
April 1991
- RFC 1213Management Information Base for Network Management of TCP/IP-based internets: MIB-IIUpdated
March 1991
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?