ObsoletedEXPERIMENTALIETF stream

RFC 1872: The MIME Multipart/Related Content-type

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2112.

Current document in this lineage: RFC 2387The MIME Multipart/Related Content-type

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC1872
Published
December 1995
Authors
E. Levinson
Status
EXPERIMENTAL
Stream
IETF
Area
app
Pages
8
Also known as
Obsoleted by:
RFC 2112

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 1872 (1995)
  2. RFC 2112 (1997)
  3. RFC 2387 (1998)

Read the full history of The MIME Multipart/Related Content-type

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/1872-the-mime-multipart-related-content-type