RFC 3638: Applicability Statement for Reclassification of RFC 1643 to Historic Status
In plain English — editorial summary, not part of the RFC
This memo recommends that RFC 1643 be reclassified as an Historic document and provides the supporting motivation for that recommendation.
Document record
- Document ID
- RFC3638
- Published
- October 2003
- Authors
- J. Flick; C. M. Heard
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 5
- Also known as
- —
- Obsoletes:
- RFC 1643
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
- RFC 1284 (1991)
- RFC 1398 (1993)
- RFC 1623 (1994)
- RFC 1643 (1994)
- RFC 3638 (2003)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2257Agent Extensibility (AgentX) Protocol Version 1Obsoleted
January 1998
- RFC 3216SMIng ObjectivesCurrent
December 2001
- RFC 2737Entity MIB (Version 2)Obsoleted
December 1999
- RFC 2674Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN ExtensionsObsoleted
August 1999
- RFC 2558Definitions of Managed Objects for the SONET/SDH Interface TypeObsoleted
March 1999
- RFC 1666Definitions of Managed Objects for SNA NAUs using SMIv2Current
August 1994
- RFC 1604Definitions of Managed Objects for Frame Relay ServiceObsoleted
March 1994
- RFC 1595Definitions of Managed Objects for the SONET/SDH Interface TypeObsoleted
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?