metasystema.org
ObsoletedINFORMATIONALIETF stream

RFC 1523: 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 1563, 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. This memo provides information for the Internet community. It does not specify an Internet standard.

Document record

Document ID
RFC1523
Published
September 1993
Authors
N. Borenstein
Status
INFORMATIONAL
Stream
IETF
Area
app
Pages
15
Also known as
—
Obsoleted by:
RFC 1563, RFC 1896

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 1523 (1993)
  2. RFC 1563 (1994)
  3. RFC 1896 (1996) ✓

Read the full history of The text/enriched MIME Content-type →

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/1523-the-text-enriched-mime-content-type