Date: Tue, 09 Feb 93 20:46:59 -0500 From: James M Galvin Sender: pem-dev-relay@TIS.COM -----BEGIN PRIVACY-ENHANCED MESSAGE----- Proc-Type: 4,MIC-CLEAR Content-Domain: RFC822 Originator-ID-Asymmetric: MEYxCzAJBgNVBAYTAlVTMSQwIgYDVQQKExtUcnV zdGVkIEluZm9ybWF0aW9uIFN5c3RlbXMxETAPBgNVBAsTCEdsZW53b29k,02 MIC-Info: RSA-MD5,RSA,SdwD9j3bEJftgUxTr4Oxa2StKH4giFOjvS5ey4B578J pEMgQYtXDXhzX4eNKmV23FducCqWXBaOHL2zvK7jK5A== - ------------------------------------------------------------------------ This message digitally signed with Privacy Enhanced Mail. Get your copy of the Internet reference implementation from "pem-info@tis.com". - ------- Forwarded Message Message-ID: <199302092258.AA00113@zephyr.isi.edu> Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US From: "Joyce K. Reynolds" To: IETF-Announce:;@IETF.CNRI.Reston.VA.US cc: jkrey@isi.edu Date: Tue, 09 Feb 93 14:56:39 PST Subject: RFC1422 on Certificate-Based Key Management - - --NextPart A new Request for Comments is now available in online RFC libraries. RFC 1422: Title: Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management Author: S. Kent Mailbox: kent@BBN.COM Pages: 32 Characters: 86,085 Obsoletes: RFC 1114 This is one of a series of documents defining privacy enhancement mechanisms for electronic mail transferred using Internet mail protocols. This memo is the outgrowth of a series of meetings of the Privacy and Security Research Group of the Internet Research Task Force (IRTF) and the Privacy-Enhanced Electronic Mail Working Group of the Internet Engineering Task Force (IETF). The author would like to thank the members of the PSRG and the PEM WG for their comments and contributions at the meetings which led to the preparation of this document. The author also would like to thank contributors to the PEM-DEV mailing list ("pem-dev@tis.com") who have provided valuable input which is reflected in this memo. 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 rfc1422.txt - - --OtherAccess Content-Type: Message/External-body; name="rfc1422.txt"; site="nic.ddn.mil"; access-type="anon-ftp"; directory="rfc" Content-Type: text/plain - - --OtherAccess-- - - --NextPart-- - ------- End of Forwarded Message -----END PRIVACY-ENHANCED MESSAGE-----