RFC 1368: Definition of Managed Objects for IEEE 802.3 Repeater Devices
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1516.
Current document in this lineage: 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 TCP/IP-based internets. In particular, it defines objects for managing IEEE 802.3 10 Mb/second baseband repeaters, sometimes referred to as "hubs". [STANDARDS-TRACK]
Document record
- Document ID
- RFC1368
- Published
- October 1992
- Authors
- D. McMaster; K. McCloghrie
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 40
- Also known as
- —
- Obsoleted by:
- 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) ✓
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 1515Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)Obsoleted
September 1993
- RFC 1525Definitions of Managed Objects for Source Routing BridgesCurrent
September 1993
- RFC 1595Definitions of Managed Objects for the SONET/SDH Interface TypeObsoleted
March 1994
- RFC 1695Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2Obsoleted
August 1994
- RFC 2108Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2Current
February 1997
- RFC 2257Agent Extensibility (AgentX) Protocol Version 1Obsoleted
January 1998
- RFC 2358Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
June 1998
- RFC 2558Definitions of Managed Objects for the SONET/SDH Interface TypeObsoleted
March 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?