RFC 1623: Definitions of Managed Objects for the Ethernet-like Interface Types
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1643.
Current document in this lineage: RFC 3638 — Applicability Statement for Reclassification of RFC 1643 to Historic Status
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 ethernet-like objects. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1623
- Published
- May 1994
- Authors
- F. Kastenholz
- Status
- HISTORIC
- Stream
- IETF
- Area
- int
- Pages
- 19
- 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 1650Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2Obsoleted
August 1994
- RFC 1694Definitions of Managed Objects for SMDS Interfaces using SMIv2Current
August 1994
- RFC 2366Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM NetworksObsoleted
July 1998
- RFC 2837Definitions of Managed Objects for the Fabric Element in Fibre Channel StandardObsoleted
May 2000
- RFC 1657Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2Obsoleted
July 1994
- RFC 1665Definitions of Managed Objects for SNA NAUs using SMIv2Obsoleted
July 1994
- RFC 1695Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2Obsoleted
August 1994
- RFC 2024Definitions of Managed Objects for Data Link Switching using SMIv2Current
October 1996
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?