The text/enriched MIME Content-type
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 21
- Abstract
- 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.
- Publication Date
- 1996-02-01
- Status Note
- Informational
- DOI
10.17487/RFC1896- Link
- https://doi.org/10.17487/RFC1896
- Author(s)
- Pete ResnickAmanda Walker
- Keyword(s)
- MIME
Latest version of IETF RFC 1896
Document Versions — IETF RFC 1896
-
▶ IETF RFC 1896 (1996-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 1341 [Superseded*]
- IETF RFC 1521 [Superseded*]
- IETF RFC 1523 [Superseded*]
- IETF RFC 1563 [Superseded*]
- IETF RFC 1642 [Superseded*]
- IETF RFC 1766 [Superseded*]
- IETF RFC 1866 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1896.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 1896, The text/enriched MIME Content-type. Available at https://doi.org/10.17487/RFC1896
Snippet:
IETF RFC 1896, The text/enriched MIME Content-type. Available at https://doi.org/10.17487/RFC1896
HTML (ISO 690 compliant)
Preview:
IETF RFC 1896, The text/enriched MIME Content-type. Available at https://doi.org/10.17487/RFC1896
Snippet:
<span class="citation"><cite>IETF RFC 1896</cite>, The text/enriched MIME Content-type. Available at <a href="https://doi.org/10.17487/RFC1896" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1896</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1896, The text/enriched MIME Content-type
doi: 10.17487/RFC1896
url: https://doi.org/10.17487/RFC1896
doi: 10.17487/RFC1896
url: https://doi.org/10.17487/RFC1896
Snippet:
<li> <cite id="bib-rfc1896">IETF RFC 1896</cite>, The text/enriched MIME Content-type <span class="doi">10.17487/RFC1896</span> </li>
Referenced By
- IETF RFC 2049 [Active*]
- IETF RFC 2646 [Superseded*]
- IETF RFC 3676 [Active*]