RFC 3676: The Text/Plain Format and DelSp Parameters
In plain English — editorial summary, not part of the RFC
This specification establishes two parameters (Format and DelSP) to be used with the Text/Plain media type. In the presence of these parameters, trailing whitespace is used to indicate flowed lines and a canonical quote indicator is used to indicate quoted lines. This results in an encoding which appears as normal Text/Plain in older implementations, since it is in fact normal Text/Plain, yet provides for superior wrapping/flowing, and quoting. This document supersedes the one specified in RFC 2646, "The Text/Plain Format Parameter", and adds the DelSp parameter to accommodate languages/coded character sets in which ASCII spaces are not used or appear rarely. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3676
- Published
- February 2004
- Authors
- R. Gellens
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 20
- Also known as
- —
- Obsoletes:
- RFC 2646
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2318The text/css Media TypeCurrent
March 1998
- RFC 3949File Format for Internet FaxCurrent
February 2005
- RFC 3950Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type RegistrationCurrent
February 2005
- RFC 3250Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type RegistrationObsoleted
September 2002
- RFC 2778A Model for Presence and Instant MessagingCurrent
February 2000
- RFC 2301File Format for Internet FaxObsoleted
March 1998
- RFC 2298An Extensible Message Format for Message Disposition NotificationsObsoleted
March 1998
- RFC 2163Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM)Updated
January 1998
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?