RFC 2111: Content-ID and Message-ID Uniform Resource Locators
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2392.
Current version: RFC 2392 — Content-ID and Message-ID Uniform Resource Locators
In plain English — editorial summary, not part of the RFC
The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2111
- Published
- March 1997
- Authors
- E. Levinson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 5
- Also known as
- —
- Obsoleted by:
- RFC 2392
Topics
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.
- RFC 2112The MIME Multipart/Related Content-typeObsoleted
March 1997
- RFC 2110MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)Obsoleted
March 1997
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
- RFC 1867Form-based File Upload in HTMLObsoleted
November 1995
- RFC 1942HTML TablesObsoleted
May 1996
- RFC 2310The Safe Response Header FieldCurrent
April 1998
- RFC 2802Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP)Current
April 2000
- RFC 2803Digest Values for DOM (DOMHASH)Current
April 2000
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?