[smime] RFC 5753 on Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)

rfc-editor@rfc-editor.org Mon, 25 January 2010 18:19 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: smime@core3.amsl.com
Delivered-To: smime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F62928C121; Mon, 25 Jan 2010 10:19:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.243
X-Spam-Level:
X-Spam-Status: No, score=-2.243 tagged_above=-999 required=5 tests=[AWL=0.357, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s3EkpFs1jDXJ; Mon, 25 Jan 2010 10:19:36 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 9664728C11C; Mon, 25 Jan 2010 10:19:36 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AB3D4E06BE; Mon, 25 Jan 2010 10:19:43 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100125181943.AB3D4E06BE@rfc-editor.org>
Date: Mon, 25 Jan 2010 10:19:43 -0800
Cc: smime@ietf.org, rfc-editor@rfc-editor.org
Subject: [smime] RFC 5753 on Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2010 18:19:37 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5753

        Title:      Use of Elliptic Curve Cryptography 
                    (ECC) Algorithms in Cryptographic Message Syntax 
                    (CMS) 
        Author:     S. Turner, D. Brown
        Status:     Informational
        Date:       January 2010
        Mailbox:    turners@ieca.com, 
                    dbrown@certicom.com
        Pages:      61
        Characters: 112095
        Obsoletes:  RFC3278

        I-D Tag:    draft-ietf-smime-3278bis-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5753.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 NIST FIPS 186-3 for
digital signature, NIST SP800-56A and SEC1 for key agreement, RFC
3370 and RFC 3565 for key wrap and content encryption, NIST FIPS
180-3 for message digest, SEC1 for key derivation, and RFC 2104 and RFC
4231 for message authentication code standards.  This document
obsoletes RFC 3278.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.

This document is a product of the S/MIME Mail Security Working Group of the IETF.


INFORMATIONAL: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC