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
- RFC2392
- Published
- August 1998
- Authors
- E. Levinson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 6
- Also known as
- —
- Obsoletes:
- RFC 2111
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2557MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)Current
March 1999
- RFC 2425A MIME Content-Type for Directory InformationObsoleted
September 1998
- RFC 2445Internet Calendaring and Scheduling Core Object Specification (iCalendar)Obsoleted
November 1998
- RFC 2244ACAP -- Application Configuration Access ProtocolUpdated
November 1997
- RFC 2652MIME Object Definitions for the Common Indexing Protocol (CIP)Current
August 1999
- RFC 2912Indicating Media Features for MIME ContentCurrent
September 2000
- RFC 2913MIME Content Types in Media Feature ExpressionsCurrent
September 2000
- RFC 3302Tag Image File Format (TIFF) - image/tiff MIME Sub-type RegistrationCurrent
September 2002
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?