RFC 2984 on CAST-128 in CMS
RFC Editor <rfc-ed@ISI.EDU> Thu, 19 October 2000 16:19 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20091; Thu, 19 Oct 2000 12:19:07 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id MAA24847 for ietf-123-outbound.10@ietf.org; Thu, 19 Oct 2000 12:15:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id LAA24706 for <all-ietf@loki.ietf.org>; Thu, 19 Oct 2000 11:50:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA15235 for <all-ietf@ietf.org>; Thu, 19 Oct 2000 11:49:54 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id IAA11131; Thu, 19 Oct 2000 08:49:53 -0700 (PDT)
Message-Id: <200010191549.IAA11131@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2984 on CAST-128 in CMS
Cc: rfc-ed@ISI.EDU, ietf-smime@IMC.ORG
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 19 Oct 2000 08:49:53 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2984 Title: Use of the CAST-128 Encryption Algorithm in CMS Author(s): C. Adams Status: Standards Track Date: October 2000 Mailbox: cadams@entrust.com Pages: 6 Characters: 11591 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-smime-cast-128-02.txt URL: ftp://ftp.isi.edu/in-notes/rfc2984.txt This document specifies how to incorporate CAST-128 (RFC2144) into the S/MIME Cryptographic Message Syntax (CMS) as an additional algorithm for symmetric encryption. The relevant OIDs and processing steps are provided so that CAST-128 may be included in the CMS specification (RFC2630) for symmetric content and key encryption. This document is a product of the S/MIME Mail Security 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 Sandy Ginoza 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.
- RFC 2984 on CAST-128 in CMS RFC Editor