RFC 2233: The Interfaces Group MIB using SMIv2
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2863.
Current document in this lineage: RFC 2863 — The Interfaces Group MIB
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 for managing Network Interfaces. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2233
- Published
- November 1997
- Authors
- K. McCloghrie; F. Kastenholz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 66
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 1229 (1991)
- RFC 1573 (1994)
- RFC 2233 (1997)
- RFC 2863 (2000) ✓
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 1694Definitions of Managed Objects for SMDS Interfaces using SMIv2Current
August 1994
- RFC 2248Network Services Monitoring MIBObsoleted
January 1998
- RFC 2257Agent Extensibility (AgentX) Protocol Version 1Obsoleted
January 1998
- RFC 2064Traffic Flow Measurement: Meter MIBObsoleted
January 1997
- RFC 2674Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN ExtensionsObsoleted
August 1999
- RFC 2737Entity MIB (Version 2)Obsoleted
December 1999
- RFC 1665Definitions of Managed Objects for SNA NAUs using SMIv2Obsoleted
July 1994
- 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?