Differences between version 5 and predecessor to the previous major change of MIME.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Friday, April 11, 2003 6:52:45 pm | by StephenLewis | Revert |
| Older page: | version 3 | Last edited on Monday, July 29, 2002 7:50:19 pm | by CraigBox | Revert |
@@ -1,7 +1,18 @@
[Acronym] for __M__ultipurpose __I__nternet __M__ail __E__xtensions
-The format for modern email messages, this specifies how to encode attachments, and non-text bodies.
+The format for modern email messages, this specifies how to encode attachments, and non-text bodies. It also includes a type system, allowing type information to be included with message parts, and a means of specifying non-ASCII text in message headers
.
-MIME is
specified in RFC:1341
+The
MIME standards build on the message format
specified in RFC:822 (now updated to RFC:2822), so a MIME message is also an RFC:822 message, hence can be sent using standard internet protocols (such as [SMTP])
-[SMTP
] is used
to send email.
+
+MIME is currently a set of 5
[RFC
]s: [1]
+
+* RFC:2045 - Basic specification for MIME messages
+* RFC:2046 - MIME media typing system, and core type definitions
+* RFC:2047 - RFC:822 extensions
to allow non-ASCII data in message headers
+* RFC:2048 - [IANA] registration procedures for MIME related facilities
+* RFC:2049 - MIME conformance criteria
+
+These documents revise older versions of the MIME standard, such as RFC:1341 and RFC:1342
+
+[1] There are a bunch of additions, but these include most of the important basics
