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


        RFC 1847:

        Title:      Security Multiparts for MIME:
                    Multipart/Signed and Multipart/Encrypted
        Author:     J. Galvin, S. Murphy, S. Crocker & N. Freed
        Date:       October 1995
        Mailbox:    galvin@tis.com, sandy@tis.com,
                    crocker@cybercash.com, ned@innosoft.com 
        Pages:      11
        Characters: 23,679
        Updates/Obsoletes:  none

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


This document defines a framework within which security services may
be applied to MIME body parts.  MIME, an acronym for "Multipurpose
Internet Mail Extensions", defines the format of the contents of
Internet mail messages and provides for multi-part textual and
non-textual message bodies.  The new content types are subtypes of
multipart: signed and encrypted.  Each will contain two body parts:
one for the protected data and one for the control information
necessary to remove the protection.  The type and contents of the
control information body parts are determined by the value of the
protocol parameter of the enclosing multipart/signed or
multipart/encrypted content type, which is required to be present.
This RFC is the product of the Privacy-Enhanced Electronic Mail
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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.

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
USC/Information Sciences Institute