RFC 1563: The text/enriched MIME Content-type
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1896.
Current document in this lineage: RFC 1896 — The text/enriched MIME Content-type
In plain English — editorial summary, not part of the RFC
MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail. This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. The text/enriched MIME type is intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1563
- Published
- January 1994
- Authors
- N. Borenstein
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 16
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1523 (1993)
- RFC 1563 (1994)
- RFC 1896 (1996) ✓
Read the full history of The text/enriched MIME Content-type →
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 1685Writing X.400 O/R NamesCurrent
August 1994
- RFC 1711Classifications in E-mail RoutingCurrent
October 1994
- RFC 1725Post Office Protocol - Version 3Obsoleted
November 1994
- RFC 1806Communicating Presentation Information in Internet Messages: The Content-Disposition HeaderObsoleted
June 1995
- RFC 2183Communicating Presentation Information in Internet Messages: The Content-Disposition Header FieldUpdated
August 1997
- RFC 2184MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and ContinuationsObsoleted
August 1997
- RFC 1801MHS use of the X.500 Directory to support MHS RoutingCurrent
June 1995
- RFC 1802Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 RoutingCurrent
June 1995
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?