[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[FYI] (Fwd) RFC 2440 on OpenPGP Message Format
- To: firstname.lastname@example.org
- Subject: [FYI] (Fwd) RFC 2440 on OpenPGP Message Format
- From: "Axel H. Horns" <email@example.com>
- Date: Thu, 12 Nov 1998 08:02:58 +0100
- Comment: This message comes from the debate mailing list.
- Organization: FITUG e.V.
- Priority: normal
- Reply-to: firstname.lastname@example.org
- Sender: email@example.com
------- Forwarded Message Follows -------
Subject: RFC 2440 on OpenPGP Message Format
Date: Wed, 11 Nov 1998 14:06:10 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries.
Title: OpenPGP Message Format
Author(s): J. Callas, L. Donnerhacke, H. Finney, R. Thayer
Status: Proposed Standard
Date: November 1998
Mailbox: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org,
Updates/Obsoletes/See Also: None
I-D Tag: draft-ietf-openpgp-formats-08.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
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
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:
Subject: getting 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