Dismiss
InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples (RFC2049)

IP.com Disclosure Number: IPCOM000004276D
Original Publication Date: 1996-Nov-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 20 page(s) / 48K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

N. Freed & N. Borenstein: AUTHOR

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

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 6% of the total text.

Network Working Group N. Freed

Request for Comments: 2049 Innosoft

Obsoletes: 1521, 1522, 1590 N. Borenstein

Category: Standards Track First Virtual

November 1996

Multipurpose Internet Mail Extensions

(MIME) Part Five:

Conformance Criteria and Examples

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

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

(1) textual message bodies in character sets other than

US-ASCII,

(2) an extensible set of different formats for non-textual

message bodies,

(3) multi-part message bodies, and

(4) textual header information in character sets other than

US-ASCII.

These documents are based on earlier work documented in RFC 934, STD

11, and RFC 1049, but extends and revises them. Because RFC 822 said

so little about message bodies, these documents are largely

orthogonal to (rather than a revision of) RFC 822.

The initial document in this set, RFC 2045, specifies the various

headers used to describe the structure of MIME messages. The second

document defines the general structure of the MIME media typing

system and defines an initial set of media types. The third

document, RFC 2047, describes extensions to RFC 822 to allow non-US-

ASCII text data in Internet mail header fields. The fourth document,

RFC 2048, specifies various IANA registration procedures for MIME-

related facilities. This fifth and final document describes MIME

conformance criteria as well as providing some illustrative examples

of MIME message formats, acknowledgements, and the bibliography.

These documents are revisions of RFCs 1521, 1522, and 1590, which

themselves were revisions of RFCs 1341 and 1342. Appendix B of this

document describes differences and changes from previous versions.

Table of Contents

1. Introduction .......................................... 2

2. MIME Conformance ...................................... 2

3. Guidelines for Sending Email Data ..................... 6

4. Canonical Encoding Model .............................. 9

5. Summary ........................................