The MIME Multipart/Related Content-type
Metadata
- Publisher
- IETF
- Doc Type
- Experimental
- Pages
- 8
- Abstract
- The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME body parts. This document defines the Multipart/Related content-type and provides examples of its use. This memo defines an Experimental Protocol for the Internet community.
- Publication Date
- 1995-12-01
- Status Note
- Experimental
- DOI
10.17487/RFC1872- Link
- https://doi.org/10.17487/RFC1872
- Author(s)
- Dr. Ed Levinson
- Keyword(s)
- MIME
Latest version of IETF RFC 1872
Document Versions — IETF RFC 1872
-
▶ IETF RFC 1872 (1995-12-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 822 [Superseded*]
- IETF RFC 1521 [Superseded*]
- IETF RFC 1524 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1872.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 1872, The MIME Multipart/Related Content-type. Available at https://doi.org/10.17487/RFC1872
Snippet:
IETF RFC 1872, The MIME Multipart/Related Content-type. Available at https://doi.org/10.17487/RFC1872
HTML (ISO 690 compliant)
Preview:
IETF RFC 1872, The MIME Multipart/Related Content-type. Available at https://doi.org/10.17487/RFC1872
Snippet:
<span class="citation"><cite>IETF RFC 1872</cite>, The MIME Multipart/Related Content-type. Available at <a href="https://doi.org/10.17487/RFC1872" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1872</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1872, The MIME Multipart/Related Content-type
doi: 10.17487/RFC1872
url: https://doi.org/10.17487/RFC1872
doi: 10.17487/RFC1872
url: https://doi.org/10.17487/RFC1872
Snippet:
<li> <cite id="bib-rfc1872">IETF RFC 1872</cite>, The MIME Multipart/Related Content-type <span class="doi">10.17487/RFC1872</span> </li>
Referenced By
- IETF RFC 2426 [Superseded*]