RFC 2387: The MIME Multipart/Related Content-type

This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK]

Read RFC 2387 on the RFC Editor

Outgoing relationships (6 related RFCs)

Obsoletes, Informative reference — RFC 2112: The MIME Multipart/Related Content-type
Informative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Informative reference — RFC 1806: Communicating Presentation Information in Internet Messages: The Content-Disposition Header
Informative reference — RFC 1524: A User Agent Configuration Mechanism For Multimedia Mail Format Information
Informative reference — RFC 1873: Message/External-Body Content-ID Access Type
Informative reference — RFC 2111: Content-ID and Message-ID Uniform Resource Locators

Incoming relationships (9 related RFCs)

Normatively referenced by — RFC 4662: A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists
Normatively referenced by — RFC 8895: Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)
Normatively referenced by — RFC 3886: An Extensible Message Format for Message Tracking Responses
Normatively referenced by — RFC 5547: A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer
Normatively referenced by — RFC 5621: Message Body Handling in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 6362: Multiple Attachments for Electronic Data Interchange - Internet Integration (EDIINT)
Informatively referenced by — RFC 2392: Content-ID and Message-ID Uniform Resource Locators
Informatively referenced by — RFC 3458: Message Context for Internet Mail
Informatively referenced by — RFC 3391: The MIME Application/Vnd.pwg-multiplexed Content-Type