metasystema.org
ObsoletedINFORMATIONALLegacy stream

RFC 2278: IANA Charset Registration Procedures

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2978.

Current version: RFC 2978 — IANA Charset Registration Procedures

In plain English — editorial summary, not part of the RFC

MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other modern Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC2278
Published
January 1998
Authors
N. Freed; J. Postel
Status
INFORMATIONAL
Stream
Legacy
Area
—
Pages
10
Also known as
—
Obsoleted by:
RFC 2978

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.

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?

canonical URL: /rfc/2278-iana-charset-registration-procedures