RFC 1873: Message/External-Body Content-ID Access Type
In plain English — editorial summary, not part of the RFC
The existing MIME Content-Type Message/External-Body access-types allow a MIME entity (body-part) to refer to an object that is not in the message by specifying how to access that object. The Content-ID access method described in this document provides the capability to refer to an object within the message. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC1873
- Published
- December 1995
- Authors
- E. Levinson; J. Clark
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 4
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1872The MIME Multipart/Related Content-typeObsoleted
December 1995
- RFC 1874SGML Media TypesCurrent
December 1995
- RFC 1867Form-based File Upload in HTMLObsoleted
November 1995
- RFC 1892The Multipart/Report Content Type for the Reporting of Mail System Administrative MessagesObsoleted
January 1996
- RFC 1894An Extensible Message Format for Delivery Status NotificationsObsoleted
January 1996
- RFC 1844Multimedia E-mail (MIME) User Agent ChecklistCurrent
August 1995
- RFC 1767MIME Encapsulation of EDI ObjectsCurrent
March 1995
- RFC 2110MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)Obsoleted
March 1997
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?