A new Request for Comments is now available in online RFC libraries.


        BCP 13:
        RFC 2048:

        Title:      Multipurpose Internet Mail Extensions
                    (MIME) Part Four:
                    Registration Procedures
        Author:     N. Freed, J. Klensin & J. Postel
        Date:       November 1996
        Mailbox:    ned@innosoft.com, klensin@mci.net, postel@isi.edu
        Pages:      21
        Characters: 45,033 
        Obsoletes:  1521, 1522, 1590

        URL:        ftp://ds.internic.net/rfc/rfc2048.txt


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
textual message bodies in character sets other than US-ASCII, an
extensible set of different formats for non-textual message bodies,
multi-part message bodies, and textual header information in character
sets other than US-ASCII.  This memo specifies various IANA
registration procedures for the following MIME facilities: media
types, external body access types, content-transfer-encodings.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute