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


        RFC 1848:

        Title:      MIME Object Security Services
        Author:     S. Crocker, N. Freed, J. Galvin & S. Murphy
        Date:       October 1995
        Mailbox:    crocker@cybercash.com, galvin@tis.com,
                    murphy@tis.com, ned@innosoft.com
        Pages:      48
        Characters: 95,010
        Updates/Obsoletes:  none

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


This document defines MIME Object Security Services (MOSS), a protocol
that uses the multipart/signed and multipart/encrypted framework to
apply digital signature and encryption services to MIME objects.  The
services are offered through the use of end-to-end cryptography
between an originator and a recipient at the application layer.
Asymmetric (public key) cryptography is used in support of the digital
signature service and encryption key management.  Symmetric (secret
key) cryptography is used in support of the encryption service.  The
procedures are intended to be compatible with a wide range of public
key management approaches, including both ad hoc and certificate-based
schemes.  Mechanisms are provided to support many public key
management approaches.  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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="mailserv@ds.internic.net"

Content-Type: text/plain
Content-ID: <951003091159.RFC@ISI.EDU>

SEND /rfc/rfc1848.txt

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc1848.txt";
        site="ds.internic.net";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain
Content-ID: <951003091159.RFC@ISI.EDU>

--OtherAccess--
--NextPart--