RFC 2108: Definitions of Managed Objects for IEEE 802.3 Repeater Devices 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 defines objects for managing IEEE 802.3 10 and 100 Mb/second baseband repeaters based on IEEE Std 802.3 Section 30, "10 & 100 Mb/s Management," October 26, 1995.
Document record
- Document ID
- RFC2108
- Published
- February 1997
- Authors
- K. de Graaf; D. Romascanu; D. McMaster; K. McCloghrie
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 82
- Also known as
- —
- Obsoletes:
- RFC 1516
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1368 (1992)
- RFC 1516 (1993)
- RFC 2108 (1997)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2257Agent Extensibility (AgentX) Protocol Version 1Obsoleted
January 1998
- RFC 2358Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
June 1998
- RFC 1695Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2Obsoleted
August 1994
- RFC 2665Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
August 1999
- RFC 2666Definitions of Object Identifiers for Identifying Ethernet Chip SetsCurrent
August 1999
- RFC 2674Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN ExtensionsObsoleted
August 1999
- RFC 2024Definitions of Managed Objects for Data Link Switching using SMIv2Current
October 1996
- RFC 2366Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM NetworksObsoleted
July 1998
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?