RFC 1896: The text/enriched MIME Content-type
In plain English — editorial summary, not part of the RFC
This document defines one particular type of MIME data, the text/enriched MIME type. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1896
- Published
- February 1996
- Authors
- P. Resnick; A. Walker
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 21
- 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 →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1895The Application/CALS-1840 Content-typeCurrent
February 1996
- RFC 1911Voice Profile for Internet MailObsoleted
February 1996
- RFC 2278IANA Charset Registration ProceduresObsoleted
January 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 3236The 'application/xhtml+xml' Media TypeCurrent
January 2002
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?