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


        RFC 1521:

        Title:      MIME (Multipurpose Internet Mail Extensions) Part
                    One: Mechanisms for Specifying and Describing
                    the Format of Internet Message Bodies
        Author:     N. Borenstein & N. Freed
        Mailbox:    nsb@bellcore.com, ned@innosoft.com
        Pages:      81
        Characters: 187,424
        Obsoletes:  1341


STD 11, RFC 822 defines a message representation protocol which
specifies considerable detail about message headers, but which leaves
the message content, or message body, as flat ASCII text.  This
document redefines the format of message bodies to allow multi-part
textual and non-textual message bodies to be represented and exchanged
without loss of information.  This is based on earlier work documented
in RFC 934 and STD 11, RFC 1049, but extends and revises that work.
Because RFC 822 said so little about message bodies, this document is
largely orthogonal to (rather than a revision of) RFC 822.

This is now a Draft Standard Protocol.

This RFC 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" for the standardization state and status
of this protocol.  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-REQUEST@NIC.DDN.MIL.

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 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute