RFC 2978: IANA Charset Registration Procedures
In plain English — editorial summary, not part of the RFC
Multipurpose Internet Mail Extensions (MIME) and various other Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2978
- Published
- October 2000
- Authors
- N. Freed; J. Postel
- Status
- BEST CURRENT PRACTICE
- Stream
- Legacy
- Area
- —
- Pages
- 11
- Also known as
- BCP19
- Obsoletes:
- RFC 2278
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2958The application/whoispp-response Content-typeCurrent
October 2000
- RFC 2957The application/whoispp-query Content-TypeCurrent
October 2000
- RFC 3236The 'application/xhtml+xml' Media TypeCurrent
January 2002
- RFC 2442The Batch SMTP Media TypeCurrent
November 1998
- RFC 1911Voice Profile for Internet MailObsoleted
February 1996
- RFC 1896The text/enriched MIME Content-typeCurrent
February 1996
- RFC 1895The Application/CALS-1840 Content-typeCurrent
February 1996
- RFC 1641Using Unicode with MIMECurrent
July 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?