RFC 2223: Instructions to RFC Authors
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7322.
Current document in this lineage: RFC 7322 — RFC Style Guide
In plain English — editorial summary, not part of the RFC
This Request for Comments (RFC) provides information about the preparation of RFCs, and certain policies relating to the publication of RFCs. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2223
- Published
- October 1997
- Authors
- J. Postel; J. Reynolds
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 20
- Also known as
- —
- Obsoleted by:
- RFC 7322
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Referenced by
3 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 255530 Years of RFCsUpdated
April 1999
- RFC 2589Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory ServicesCurrent
May 1999
- RFC 3161Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)Updated
August 2001
- RFC 3507Internet Content Adaptation Protocol (ICAP)Current
April 2003
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?