[105438] in Cypherpunks
FW: RFC 2440 on OpenPGP Message Format
daemon@ATHENA.MIT.EDU (Fisher Mark)
Wed Nov 11 18:37:08 1998
From: Fisher Mark <fisherm@tce.com>
To: cypherpunks@cyberpass.net
Date: Wed, 11 Nov 1998 18:10:58 -0500
Reply-To: Fisher Mark <fisherm@tce.com>
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_000_01BE0DC8.8FC55460
Content-Type: text/plain
> -----Original Message-----
> From: RFC Editor [SMTP:rfc-ed@ISI.EDU]
> Sent: Wednesday, November 11, 1998 5:06 PM
> Cc: rfc-ed@ISI.EDU
> Subject: RFC 2440 on OpenPGP Message Format
>
>
> A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 2440:
>
> Title: OpenPGP Message Format
> Author(s): J. Callas, L. Donnerhacke, H. Finney, R. Thayer
> Status: Proposed Standard
> Date: November 1998
> Mailbox: jon@pgp.com, lutz@iks-jena.de, hal@pgp.com,
> rodney@unitran.com
> Pages: 65
> Characters: 141371
> Updates/Obsoletes/See Also: None
> I-D Tag: draft-ietf-openpgp-formats-08.txt
>
> URL: ftp://ftp.isi.edu/in-notes/rfc2440.txt
>
> This document is maintained in order to publish all necessary
> information needed to develop interoperable applications based on the
> OpenPGP format. It is not a step-by-step cookbook for writing an
> application. It describes only the format and methods needed to read,
> check, generate, and write conforming packets crossing any network.
> It does not deal with storage and implementation questions. It does,
> however, discuss implementation issues necessary to avoid security
> flaws.
>
> This document is a product of the An Open Specification for Pretty
> Good Privacy 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@IETF.ORG. Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
> help: ways_to_get_rfcs. For example:
>
> To: rfc-info@RFC-EDITOR.ORG
> 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 RFC-Manager@RFC-EDITOR.ORG. Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.echo
> Submissions for Requests for Comments should be sent to
> RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
> Authors, for further information.
>
>
> Joyce K. Reynolds and Alegre Ramos
> 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. <<Untitled Attachment>>
------_=_NextPart_000_01BE0DC8.8FC55460
Content-Type: message/rfc822
Content-Description: Untitled Attachment
Content-Location: ATT-0-F23FE223AD79D21187B500805FCB3710-U
ntitled%20Attachment
To:
Subject:
Date: Wed, 11 Nov 1998 18:11:07 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: multipart/mixed;
boundary="----_=_NextPart_002_01BE0DC8.8FC55460"
------_=_NextPart_002_01BE0DC8.8FC55460
Content-Type: text/plain
------_=_NextPart_002_01BE0DC8.8FC55460
Content-Type: application/octet-stream;
name="ATT30256"
Content-Disposition: attachment;
filename="ATT30256"
Content-Location: ATT-0-0F2B251EA879D211BAE300A024621A82-A
TT30256.txt
Content-type: message/external-body;
access-type="mail-server";
server="RFC-INFO@RFC-EDITOR.ORG"
Content-Type: text/plain
Content-ID: <981111140400.RFC@RFC-EDITOR.ORG>
RETRIEVE: rfc
DOC-ID: rfc2440
------_=_NextPart_002_01BE0DC8.8FC55460
Content-Type: message/external-body;
site="in-notes";
dir="rfc2440.txt";
mode="ftp.isi.edu";
access-type="anon-ftp"
Content-Location: ATT-1-102B251EA879D211BAE300A024621A82-r
fc2440.url
------_=_NextPart_002_01BE0DC8.8FC55460--
------_=_NextPart_000_01BE0DC8.8FC55460--
