RFC 3278 on Use of ECC Algorithms in CMS
RFC Editor <rfc-ed@ISI.EDU> Sat, 11 May 2002 00:08 UTC
Received: from above.proper.com (mail.imc.org [208.184.76.43]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23954 for <smime-archive@odin.ietf.org>; Fri, 10 May 2002 20:08:44 -0400 (EDT)
Received: by above.proper.com (8.11.6/8.11.3) id g4ANw6Z01009 for ietf-smime-bks; Fri, 10 May 2002 16:58:06 -0700 (PDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g4ANw4L01005 for <ietf-smime@imc.org>; Fri, 10 May 2002 16:58:04 -0700 (PDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4ANw6m08402; Fri, 10 May 2002 16:58:06 -0700 (PDT)
Message-Id: <200205102358.g4ANw6m08402@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3278 on Use of ECC Algorithms in CMS
Cc: rfc-editor@rfc-editor.org, ietf-smime@imc.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 10 May 2002 16:58:06 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
Sender: owner-ietf-smime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-ID: <ietf-smime.imc.org>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>
A new Request for Comments is now available in online RFC libraries. RFC 3278 Title: Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS) Author(s): S. Blake-Wilson, D. Brown, P. Lambert Status: Informational Date: April 2002 Mailbox: sblakewi@certicom.com, dbrown@certicom.com, plambert@sprintmail.com Pages: 16 Characters: 33779 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-smime-ecc-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3278.txt This document describes how to use Elliptic Curve Cryptography (ECC) public-key algorithms in the Cryptographic Message Syntax (CMS). The ECC algorithms support the creation of digital signatures and the exchange of keys to encrypt or authenticate content. The definition of the algorithm processing is based on the ANSI X9.62 standard, developed by the ANSI X9F1 working group, the IEEE 1363 standard, and the SEC 1 standard. The readers attention is called to the Intellectual Property Rights section at the end of this document. This document is a product of the S/MIME Mail Security Working Group of the IETF. This memo provides information for the Internet community. It 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@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 3278 on Use of ECC Algorithms in CMS RFC Editor