MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- 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- Link
- https://doi.org/10.17487/RFC1521
- Author(s)
- Dr. Nathaniel S. Borenstein, Ned 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]
- RFC2047 NOT IN REGISTRY
- RFC2048 NOT IN REGISTRY
- RFC2049 NOT IN REGISTRY
Bibliographic Reference(s)
- ADOBE.PostScript.1985 NOT IN REGISTRY
- ADOBE.PostScript.2nd.1990 NOT IN REGISTRY
- ANSI/INCITS X3.4:1986 (R1997) [Active]
- ISBN.0444873287 NOT IN REGISTRY
- ISBN.9780130366337 NOT IN REGISTRY
- ISO.11172 NOT IN REGISTRY
- ISO/IEC 2022 [Active, Amended]
- ISO 646 [Active]
- ISO.8859 NOT IN REGISTRY
- LOC.GIF.89a NOT IN REGISTRY
- RFC1049 NOT IN REGISTRY
- RFC1154 NOT IN REGISTRY
- RFC1340 NOT IN REGISTRY
- RFC1341 NOT IN REGISTRY
- RFC1342 NOT IN REGISTRY
- RFC1343 NOT IN REGISTRY
- RFC1344 NOT IN REGISTRY
- RFC1345 NOT IN REGISTRY
- RFC1421 NOT IN REGISTRY
- RFC1426 NOT IN REGISTRY
- RFC1522 NOT IN REGISTRY
- RFC783 NOT IN REGISTRY
- RFC821 NOT IN REGISTRY
- RFC822 NOT IN REGISTRY
- RFC934 NOT IN REGISTRY
- RFC959 NOT IN REGISTRY
- T-REC-G.711.1972 NOT IN REGISTRY
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 1557 [Active*]
- SMPTE ST 430-1:2017 [Superseded]
- SMPTE ST 430-1:2017 Am1:2019 [Superseded]
- SMPTE ST 430-2:2017 [Active]