RFC 2646: The Text/Plain Format Parameter
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3676.
Current version: RFC 3676 — The Text/Plain Format and DelSp Parameters
In plain English — editorial summary, not part of the RFC
This memo proposes a new parameter to be used with Text/Plain, and, in the presence of this parameter, the use of trailing whitespace to indicate flowed lines. This results in an encoding which appears as normal Text/Plain in older implementations, since it is in fact normal Text/Plain. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2646
- Published
- August 1999
- Authors
- R. Gellens
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 14
- Also known as
- —
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 2318The text/css Media TypeCurrent
March 1998
- RFC 2442The Batch SMTP Media TypeCurrent
November 1998
- RFC 2957The application/whoispp-query Content-TypeCurrent
October 2000
- RFC 2958The application/whoispp-response Content-typeCurrent
October 2000
- RFC 2978IANA Charset Registration ProceduresCurrent
October 2000
- RFC 2278IANA Charset Registration ProceduresObsoleted
January 1998
- RFC 3236The 'application/xhtml+xml' Media TypeCurrent
January 2002
- RFC 1911Voice Profile for Internet MailObsoleted
February 1996
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?