RFC 1749: IEEE 802.5 Station Source Routing MIB using SMIv2
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 by IEEE 802.5 end-stations for managing source routes on a Token Ring network where IEEE source- routing is in use. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1749
- Published
- December 1994
- Authors
- K. McCloghrie; F. Baker; E. Decker
- Status
- HISTORIC
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
- Updates:
- RFC 1748
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1743IEEE 802.5 MIB using SMIv2Obsoleted
December 1994
- RFC 2037Entity MIB using SMIv2Obsoleted
October 1996
- RFC 2248Network Services Monitoring MIBObsoleted
January 1998
- RFC 2257Agent Extensibility (AgentX) Protocol Version 1Obsoleted
January 1998
- RFC 2737Entity MIB (Version 2)Obsoleted
December 1999
- RFC 1694Definitions of Managed Objects for SMDS Interfaces using SMIv2Current
August 1994
- RFC 1650Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2Obsoleted
August 1994
- RFC 1623Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
May 1994
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?