RFC 4021: Registration of Mail and MIME Header Fields
In plain English — editorial summary, not part of the RFC
This document defines the initial IANA registration for permanent mail and MIME message header fields, per RFC 3864. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4021
- Published
- March 2005
- Authors
- G. Klyne; J. Palme
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 54
- Also known as
- —
- Updated by:
- RFC 5322
Topics
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 3737IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modulesCurrent
April 2004
- RFC 3692Assigning Experimental and Testing Numbers Considered UsefulCurrent
January 2004
- RFC 3575IANA Considerations for RADIUS (Remote Authentication Dial In User Service)Updated
July 2003
- RFC 4645Initial Language Subtag RegistryCurrent
September 2006
- RFC 2036Observations on the use of Components of the Class A Address Space within the InternetCurrent
October 1996
- RFC 6064SDP and RTSP Extensions Defined for 3GPP Packet-Switched Streaming Service and Multimedia Broadcast/Multicast ServiceCurrent
January 2011
- RFC 1917An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANACurrent
February 1996
- RFC 1881IPv6 Address Allocation ManagementCurrent
December 1995
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?