RFC 2387: The MIME Multipart/Related Content-type
In plain English — editorial summary, not part of the RFC
This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2387
- Published
- August 1998
- Authors
- E. Levinson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 10
- Also known as
- —
- Obsoletes:
- RFC 2112
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1872 (1995)
- RFC 2112 (1997)
- RFC 2387 (1998)
Read the full history of The MIME Multipart/Related Content-type →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3798Message Disposition NotificationObsoleted
May 2004
- RFC 2388Returning Values from Forms: multipart/form-dataObsoleted
August 1998
- RFC 2392Content-ID and Message-ID Uniform Resource LocatorsCurrent
August 1998
- RFC 2425A MIME Content-Type for Directory InformationObsoleted
September 1998
- RFC 2426vCard MIME Directory ProfileObsoleted
September 1998
- RFC 2445Internet Calendaring and Scheduling Core Object Specification (iCalendar)Obsoleted
November 1998
- RFC 2298An Extensible Message Format for Message Disposition NotificationsObsoleted
March 1998
- RFC 2557MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)Current
March 1999
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?