Skip to main content

Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)
draft-ietf-smime-ecc-06

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3278.
Authors Daniel R. L. Brown , Simon Blake-Wilson , Paul A. Lambert
Last updated 2021-04-15 (Latest revision 2001-05-15)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3278 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-ietf-smime-ecc-06
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.