RFC 2668: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3636.
Current document in this lineage: RFC 4836 — Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2668
- Published
- August 1999
- Authors
- A. Smith; J. Flick; K. de Graaf; D. Romascanu; D. McMaster; K. McCloghrie; S. Roberts
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 56
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
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 2666Definitions of Object Identifiers for Identifying Ethernet Chip SetsCurrent
August 1999
- RFC 2665Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
August 1999
- RFC 2674Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN ExtensionsObsoleted
August 1999
- RFC 2621RADIUS Accounting Server MIBObsoleted
June 1999
- RFC 2620RADIUS Accounting Client MIBObsoleted
June 1999
- RFC 2619RADIUS Authentication Server MIBObsoleted
June 1999
- RFC 2737Entity MIB (Version 2)Obsoleted
December 1999
- RFC 2493Textual Conventions for MIB Modules Using Performance History Based on 15 Minute IntervalsObsoleted
January 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?