Mhtml Workgroup RFCs
Browse Mhtml Workgroup RFCs by Number
- RFC2110 - MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)
- This document describes a set of guidelines that will allow conforming mail user agents to be able to send, deliver and display these objects, such as HTML objects, that can contain links represented by URIs. [STANDARDS-TRACK]
- RFC2111 - Content-ID and Message-ID Uniform Resource Locators
- 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]
- RFC2112 - The MIME Multipart/Related Content-type
- 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. [STANDARDS-TRACK]
- RFC2387 - The MIME Multipart/Related Content-type
- This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK]
- RFC2392 - Content-ID and Message-ID Uniform Resource Locators
- 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]
- RFC2557 - MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)
- This document a) defines the use of a MIME multipart/related structure to aggregate a text/html root resource and the subsidiary resources it references, and b) specifies a MIME content-header (Content-Location) that allow URIs in a multipart/related text/html root body part to reference subsidiary resources in other body parts of the same multipart/related structure. [STANDARDS-TRACK]
