RFC 3864: Registration Procedures for Message Header Fields
In plain English — editorial summary, not part of the RFC
This specification defines registration procedures for the message header fields used by Internet mail, HTTP, Netnews and other applications. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3864
- Published
- September 2004
- Authors
- G. Klyne; M. Nottingham; J. Mogul
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 17
- Also known as
- BCP90
- Updated by:
- RFC 9110
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 3977Network News Transfer Protocol (NNTP)Updated
October 2006
- RFC 4024Voice Messaging Client BehaviourCurrent
July 2005
- RFC 4142Full-mode Fax Profile for Internet Mail (FFPIM)Current
November 2005
- RFC 4437Web Distributed Authoring and Versioning (WebDAV) Redirect Reference ResourcesCurrent
March 2006
- RFC 3253Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)Current
March 2002
- RFC 4590RADIUS Extension for Digest AuthenticationObsoleted
July 2006
- RFC 2965HTTP State Management MechanismObsoleted
October 2000
- RFC 4791Calendaring Extensions to WebDAV (CalDAV)Updated
March 2007
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?