About: MIME is a research topic. Over the lifetime, 26 publications have been published within this topic receiving 2383 citations. The topic is also known as: MIME.
TL;DR: This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for MIME to be applied to e-mail messages.
Abstract: STD 11, RFC 822 defines a message representation protocol specifying considerable detail about US-ASCII message headers, but which leaves the message content, or message body, as flat US-ASCII text. This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for
TL;DR: This memo describes an extension to the message format defined in RFC 1521, to allow the representation of character sets other than ASCII in RFC 822 (STD 11) message headers.
Abstract: This memo describes an extension to the message format defined in RFC 1521 [1], to allow the representation of character sets other than ASCII in RFC 822 (STD 11) message headers. The extensions described were designed to be highly compatible with existing Internet mail handling software, and to be easily implemented in mail readers that support RFC 1521.
TL;DR: This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for MIME-based mail delivery systems.
Abstract: STD 11, RFC 822, defines a message representation protocol specifying considerable detail about US-ASCII message headers, and leaves the message content, or message body, as flat US-ASCII text. This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for
TL;DR: This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for MIME to be used in e-mail.
Abstract: STD 11, RFC 822, defines a message representation protocol specifying considerable detail about US-ASCII message headers, and leaves the message content, or message body, as flat US-ASCII text. This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for
TL;DR: This document provides an applicability statement (RFC 2026, Section 3.2) that describes how to exchange structured business data securely using the HTTP transfer protocol, instead of SMTP; the applicability statements for SMTP is found in RFC 3335.
Abstract: This document provides an applicability statement (RFC 2026, Section
3.2) that describes how to exchange structured business data securely
using the HTTP transfer protocol, instead of SMTP; the applicability
statement for SMTP is found in RFC 3335. Structured business data may
be XML; Electronic Data Interchange (EDI) in either the American
National Standards Committee (ANSI) X12 format or the UN Electronic
Data Interchange for Administration, Commerce, and Transport
(UN/EDIFACT) format; or other structured data formats. The data is
packaged using standard MIME structures. Authentication and data
confidentiality are obtained by using Cryptographic Message Syntax
with S/MIME security body parts. Authenticated acknowledgements make
use of multipart/signed Message Disposition Notification (MDN)
responses to the original HTTP message. This applicability statement
is informally referred to as "AS2" because it is the second
applicability statement, produced after "AS1", RFC 3335. [STANDARDS-
TRACK]