RFC 1643: 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 3638.
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
- RFC1643
- Published
- July 1994
- Authors
- F. Kastenholz
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- 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 1666Definitions of Managed Objects for SNA NAUs using SMIv2Current
August 1994
- RFC 1604Definitions of Managed Objects for Frame Relay ServiceObsoleted
March 1994
- RFC 2257Agent Extensibility (AgentX) Protocol Version 1Obsoleted
January 1998
- RFC 1658Definitions of Managed Objects for Character Stream Devices using SMIv2Current
July 1994
- RFC 1659Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2Current
July 1994
- RFC 1660Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2Current
July 1994
- RFC 1665Definitions of Managed Objects for SNA NAUs using SMIv2Obsoleted
July 1994
- RFC 1596Definitions of Managed Objects for Frame Relay ServiceObsoleted
March 1994
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?