RFC1984 on Cryptographic Technology (fwd)
An entity claiming to be RFC Editor wrote:
From majordom@ISI.EDU Thu Aug 22 13:27 EDT 1996 Message-Id: <199608201538.AA03394@zephyr.isi.edu> To: rfc-dist@ISI.EDU Subject: RFC1984 on Cryptographic Technology Cc: rfc-ed@ISI.EDU Mime-Version: 1.0 Date: Tue, 20 Aug 96 08:40:50 PDT From: RFC Editor
Sender: owner-rfc-dist@ISI.EDU Content-Type: Multipart/Mixed; Boundary=NextPart Content-Length: 3011
--NextPart A new Request for Comments is now available in online RFC libraries. RFC 1984: Title: IAB and IESG Statement on Cryptographic Technology and the Internet Author: IAB & IESG Date: August 1996 Mailbox: brian@dxcoms.cern.ch, fred@cisco.com Pages: 5 Characters: 10,738 Updates/Obsoletes: none URL: ftp://ds.internic.net/rfc/rfc1984.txt The Internet Architecture Board (IAB) and the Internet Engineering Steering Group (IESG), the bodies which oversee architecture and standards for the Internet, are concerned by the need for increased protection of international commercial transactions on the Internet, and by the need to offer all Internet users an adequate degree of privacy. Security mechanisms being developed in the Internet Engineering Task Force to meet these needs require and depend on the international use of adequate cryptographic technology. Ready access to such technology is therefore a key factor in the future growth of the Internet as a motor for international commerce and communication. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 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 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="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <960820082910.RFC@ISI.EDU> SEND /rfc/rfc1984.txt --OtherAccess Content-Type: Message/External-body; name="rfc1984.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="rfc" Content-Type: text/plain Content-ID: <960820082910.RFC@ISI.EDU> --OtherAccess-- --NextPart-- -- Mark Rogaski | Why read when you can just sit and | Member GTI System Admin | stare at things? | Programmers Local wendigo@gti.net | Any expressed opinions are my own | # 0xfffe wendigo@pobox.com | unless they can get me in trouble. | APL-CPIO
participants (1)
-
Mark Rogaski