RFC 6657: Update to MIME regarding "charset" Parameter Handling in Textual Media Types
In plain English — editorial summary, not part of the RFC
This document changes RFC 2046 rules regarding default "charset" parameter values for "text/*" media types to better align with common usage by existing clients and servers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6657
- Published
- July 2012
- Authors
- A. Melnikov; J. Reschke
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 2046
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2111Content-ID and Message-ID Uniform Resource LocatorsObsoleted
March 1997
- RFC 6522The Multipart/Report Media Type for the Reporting of Mail System Administrative MessagesUpdated
January 2012
- RFC 8081The "font" Top-Level Media TypeCurrent
February 2017
- RFC 8255Multiple Language Content TypeCurrent
October 2017
- RFC 3335MIME-based Secure Peer-to-Peer Business Data Interchange over the InternetCurrent
September 2002
- RFC 9996Media Types for Protocol BuffersCurrent
July 2026
- RFC 6409Message Submission for MailUpdated
November 2011
- RFC 6922The application/sql Media TypeCurrent
April 2013
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?