MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 81
- Abstract
- This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. This is based on earlier work documented in RFC 934 and STD 11, RFC 1049, but extends and revises that work. [STANDARDS-TRACK]
- Publication Date
- 1993-09-01
- Status Note
- Draft Standard
- DOI
10.17487/RFC1521- ISSN
2070-1721- Link
- https://doi.org/10.17487/RFC1521
- Author(s)
- Dr. Nathaniel S. BorensteinNed Freed
- Keyword(s)
- Email, Multimedia
Latest version of IETF RFC 1521
Document Versions — IETF RFC 1521
-
▶ IETF RFC 1521 (1993-09-01)THIS DOC [SUPERSEDED] [AMENDED] [LATEST VERSION]
Superseded by:
- IETF RFC 2045 [Active*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2047 [Active*]
- IETF RFC 2048 [Superseded*]
- IETF RFC 2049 [Active*]
Bibliographic Reference(s)
- ADOBE.PostScript.2nd.1990 — POSTSCRIPT2 EXTERNAL
- ADOBE.PostScript.1985 — POSTSCRIPT EXTERNAL
- ANSI/INCITS X3.4:1986 (R1997) [Active]
- ISBN.0444873287 — X400 EXTERNAL
- ISBN.9780130366337 — ATK EXTERNAL
- ISO 646 [Active]
- ISO/IEC 2022 [Active, Amended]
- ISO/IEC 8859-1 [Active]
- ISO.11172 — MPEG EXTERNAL
- LOC.GIF.89a — GIF EXTERNAL
- IETF RFC 783 [Superseded*]
- IETF RFC 821 [Superseded*]
- IETF RFC 822 [Superseded*]
- IETF RFC 934 [Active*]
- IETF RFC 959 [Active*]
- IETF RFC 1049 [Active*]
- IETF RFC 1154 [Superseded*]
- IETF RFC 1340 [Superseded*]
- IETF RFC 1341 [Superseded*]
- IETF RFC 1342 [Superseded*]
- IETF RFC 1343 [Active*]
- IETF RFC 1344 [Active*]
- IETF RFC 1345 [Active*]
- IETF RFC 1421 [Active*]
- IETF RFC 1426 [Superseded*]
- IETF RFC 1522 [Superseded*]
- T-REC-G.711.1972 — PCM EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1521.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 1521, MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies. Available at https://doi.org/10.17487/RFC1521
Snippet:
IETF RFC 1521, MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies. Available at https://doi.org/10.17487/RFC1521
HTML (ISO 690 compliant)
Preview:
IETF RFC 1521, MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies. Available at https://doi.org/10.17487/RFC1521
Snippet:
<span class="citation"><cite>IETF RFC 1521</cite>, MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies. Available at <a href="https://doi.org/10.17487/RFC1521" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1521</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1521, MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies
doi: 10.17487/RFC1521
url: https://doi.org/10.17487/RFC1521
doi: 10.17487/RFC1521
url: https://doi.org/10.17487/RFC1521
Snippet:
<li> <cite id="bib-rfc1521">IETF RFC 1521</cite>, MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies <span class="doi">10.17487/RFC1521</span> </li>
Referenced By
- ISO 26430-2:2008 [Active, Reaffirmed]
- IETF RFC 1522 [Superseded*]
- IETF RFC 1523 [Superseded*]
- IETF RFC 1524 [Active*]
- IETF RFC 1528 [Superseded*]
- IETF RFC 1530 [Active*]
- IETF RFC 1554 [Active*]
- IETF RFC 1555 [Active*]
- IETF RFC 1556 [Active*]
- IETF RFC 1557 [Active*]
- IETF RFC 1563 [Superseded*]
- IETF RFC 1568 [Superseded*]
- IETF RFC 1590 [Superseded*]
- IETF RFC 1641 [Active*]
- IETF RFC 1642 [Superseded*]
- IETF RFC 1651 [Superseded*]
- IETF RFC 1652 [Superseded*]
- IETF RFC 1653 [Superseded*]
- IETF RFC 1700 [Superseded*]
- IETF RFC 1714 [Superseded*]
- IETF RFC 1730 [Superseded*]
- IETF RFC 1740 [Active*]
- IETF RFC 1741 [Active*]
- IETF RFC 1766 [Superseded*]
- IETF RFC 1767 [Active*]
- IETF RFC 1806 [Superseded*]
- IETF RFC 1808 [Superseded*]
- IETF RFC 1815 [Active*]
- IETF RFC 1830 [Superseded*]
- IETF RFC 1842 [Active*]
- IETF RFC 1845 [Active*]
- IETF RFC 1847 [Active*]
- IETF RFC 1848 [Active*]
- IETF RFC 1864 [Active*]
- IETF RFC 1866 [Superseded*]
- IETF RFC 1867 [Superseded*]
- IETF RFC 1869 [Superseded*]
- IETF RFC 1870 [Active*]
- IETF RFC 1872 [Superseded*]
- IETF RFC 1873 [Active*]
- IETF RFC 1874 [Active*]
- IETF RFC 1892 [Superseded*]
- IETF RFC 1894 [Superseded*]
- IETF RFC 1896 [Active*]
- IETF RFC 1911 [Superseded*]
- IETF RFC 1922 [Active*]
- IETF RFC 1945 [Active*]
- IETF RFC 2017 [Active*]
- IETF RFC 2049 [Active*]
- IETF RFC 2065 [Superseded*]
- IETF RFC 2076 [Active*]
- IETF RFC 2110 [Superseded*]
- IETF RFC 2111 [Superseded*]
- IETF RFC 2975 [Active*]
- IETF RFC 3066 [Superseded*]
- IETF RFC 3926 [Superseded*]
- IETF RFC 6709 [Active*]
- SMPTE ST 430-1:2017 [Superseded]
- SMPTE ST 430-1:2017 Am1:2019 [Superseded]
- SMPTE ST 430-2:2017 [Active]