MeatballWiki |
RecentChanges |
Random Page |
Indices |
Categories
MultipurposeInternetMailExtensions, more commonly known as MIME, is a simple yet generic way of representing multiple data sources in one e-mail (
RFC 2822/
RFC 822) compatible stream.
- RFC 2045 - Format of Internet Message Bodies
- RFC 2046 - Media Types
- RFC 2047 - Message Header Extensions for Non-ASCII Text
- RFC 2048 - Registration Procedures
- RFC 2049 - Conformance Criteria and Examples
You may also be interested in:
- RFC 1524 - The formal description of mailcap files. Mailcap files describe how to handle media types
- RFC 2015 - MIME Security with Pretty Good Privacy (PGP)
- RFC 2110 - MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)
- RFC 2111 - Content-ID and Message-ID Uniform Resource Locators
- RFC 2112 - The MIME Multipart/Related Content-type
- RFC 2183 - Defines the syntax and sematics of the "Content-Disposition" header to convey presentational information
- RFC 2184 - MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
More recently, MIME has been XML-ized/HTTP-ized as BlockExtensibleExchangeProtocol? (BEEP/BXXP). This is not to say that BXXP is MIME, but it's clear that BXXP was influenced by HTTP which was influenced by MIME.