1996-10-15 - RFC2015 on MIME Security with PGP (fwd)

Header Data

From: “P. J. Ponder” <ponder@freenet.tlh.FL.us>
To: cypherpunks@toad.com
Message Hash: db23394c70bedde1cf44330950cbf004df76fee5c41440b4f7b05e3f578baaf0
Message ID: <Pine.OSF.3.91.961014202320.27862A-100000@fn3.freenet.tlh.fl.us>
Reply To: N/A
UTC Datetime: 1996-10-15 00:21:22 UTC
Raw Date: Mon, 14 Oct 1996 17:21:22 -0700 (PDT)

Raw message

From: "P. J. Ponder" <ponder@freenet.tlh.FL.us>
Date: Mon, 14 Oct 1996 17:21:22 -0700 (PDT)
To: cypherpunks@toad.com
Subject: RFC2015 on MIME Security with PGP (fwd)
Message-ID: <Pine.OSF.3.91.961014202320.27862A-100000@fn3.freenet.tlh.fl.us>
MIME-Version: 1.0
Content-Type: text/plain


---------- Forwarded message ----------
Date: Mon, 14 Oct 96 14:18:26 PDT
From: RFC Editor <rfc-ed@ISI.EDU>
To: rfc-dist@ISI.EDU
Cc: rfc-ed@ISI.EDU
Subject: RFC2015 on MIME Security with PGP

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

        RFC 2015:
        Title:      MIME Security with Pretty Good Privacy (PGP)
        Author:     M. Elkins
        Date:       October 1996
        Mailbox:    P.O. Box 92957 - M1/102
                    Los Angeles, CA 90009-2957
        Pages:      8
        Characters: 14,223
        Updates/Obsoletes:  None

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

This document describes how Pretty Good Privacy (PGP) can be used to
provide privacy and authentication using the Multipurpose Internet
Mail Extensions (MIME) security content types described in RFC1847.

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 and Mary Kennedy
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.




Thread