<?xml version='1.0'?>

<reference anchor='RFC2048'>

<front>
<title abbrev='MIME Registration Procedures'>Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures</title>
<author initials='N.' surname='Freed' fullname='Ned Freed'>
<organization>Innosoft International, Inc.</organization>
<address>
<postal>
<street>1050 East Garvey Avenue South</street>
<street>West Covina</street>
<street>CA 91790</street>
<country>USA</country></postal>
<phone>+1 818 919 3600</phone>
<facsimile>+1 818 919 3614</facsimile>
<email>ned@innosoft.com</email></address></author>
<author initials='J.' surname='Klensin' fullname='John Klensin'>
<organization>MCI</organization>
<address>
<postal>
<street>2100 Reston Parkway</street>
<street>Reston</street>
<street>VA 22091</street></postal>
<phone>+1 703 715-7361</phone>
<facsimile>+1 703 715-7436</facsimile>
<email>klensin@mci.net</email></address></author>
<author initials='J.' surname='Postel' fullname='Jon Postel'>
<organization>USC/Information Sciences Institute</organization>
<address>
<postal>
<street>4676 Admiralty Way</street>
<street>Marina del Rey</street>
<street>CA  90292</street>
<country>USA</country></postal>
<phone>+1 310 822 1511</phone>
<facsimile>+1 310 823 6714</facsimile>
<email>Postel@ISI.EDU</email></address></author>
<date month='November' year='1996' />
<area>Applications</area>
<keyword>mail</keyword>
<keyword>media type</keyword>
<keyword>multipurpose internet mail extensions</keyword>
<abstract>
<t>
   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

<list>
<t>
    (1)   textual message bodies in character sets other than
          US-ASCII,
</t>
<t>
    (2)   an extensible set of different formats for non-textual
          message bodies,
</t>
<t>
    (3)   multi-part message bodies, and
</t>
<t>
    (4)   textual header information in character sets other than
          US-ASCII.
</t></list></t>
<t>
   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.
   This fourth document, RFC 2048, specifies various IANA registration
   procedures for the following MIME facilities:

<list>
<t>
    (1)   media types,
</t>
<t>
    (2)   external body access types,
</t>
<t>
    (3)   content-transfer-encodings.
</t></list></t>
<t>
   Registration of character sets for use in MIME is covered elsewhere
   and is no longer addressed by this document.
</t>
<t>
   These documents are revisions of RFCs 1521 and 1522, which themselves
   were revisions of RFCs 1341 and 1342.  An appendix in RFC 2049
   describes differences and changes from previous versions.
</t></abstract></front>

<seriesInfo name='BCP' value='13' />
<seriesInfo name='RFC' value='2048' />
<format type='HTML' octets='54732' target='http://xml.resource.org/public/rfc/html/rfc2048.html' />
<format type='XML' octets='43342' target='http://xml.resource.org/public/rfc/xml/rfc2048.xml' />
</reference>
