Delivery-Date: Tue, 09 Feb 93 20:07:58 -0500 Return-Path: ietf-announce-request@IETF.CNRI.Reston.VA.US Return-Path: Received: from IETF.nri.reston.VA.US (IETF.CNRI.RESTON.VA.US) by TIS.COM (4.1/SUN-5.64) id AA05504; Tue, 9 Feb 93 20:07:57 EST Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11111; 9 Feb 93 18:00 EST Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10767; 9 Feb 93 17:58 EST Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa24060; 9 Feb 93 17:58 EST Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-10) id ; Tue, 9 Feb 1993 14:58:15 -0800 Message-Id: <199302092258.AA00165@zephyr.isi.edu> To: IETF-Announce:;@IETF.CNRI.Reston.VA.US Subject: RFC1424 on Key Certification and Related Services Cc: jkrey@isi.edu Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Date: Tue, 09 Feb 93 14:56:52 PST Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US From: "Joyce K. Reynolds" --NextPart A new Request for Comments is now available in online RFC libraries. RFC 1424: Title: Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services Author: B. Kaliski Mailbox: burt@rsa.com Pages: 9 Characters: 17,537 Updates/Obsoletes: none This document describes three types of service in support of Internet Privacy-Enhanced Mail (PEM): key certification, certificate- revocation list (CRL) storage, and CRL retrieval. This is one of a series of documents defining privacy enhancement mechanisms for electronic mail transferred using Internet mail protocols. This document is the product of many discussions at RSA Data Security, at Trusted Information Systems, and on the mailing list. This document is the product of the Privacy-Enhanced Electronic Mail Working Group. This is now a Proposed Standard Protocol. This RFC specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" 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-REQUEST@NIC.DDN.MIL. 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 NIC@NIC.DDN.MIL. 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 1111, "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="mail-server@nisc.sri.com" Content-Type: text/plain SEND rfc1424.txt --OtherAccess Content-Type: Message/External-body; name="rfc1424.txt"; site="nic.ddn.mil"; access-type="anon-ftp"; directory="rfc" Content-Type: text/plain --OtherAccess-- --NextPart--