RFC 6161 on Elliptic Curve Algorithms for Cryptographic Message Syntax (CMS) Encrypted Key Package Content Type

rfc-editor@rfc-editor.org Mon, 11 April 2011 19:20 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F6393A6B34 for <ietf-announce@core3.amsl.com>; Mon, 11 Apr 2011 12:20:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.107
X-Spam-Level:
X-Spam-Status: No, score=-102.107 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 0XZ4d3l-oYTw for <ietf-announce@core3.amsl.com>; Mon, 11 Apr 2011 12:20:02 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 7B4253A6B33 for <ietf-announce@ietf.org>; Mon, 11 Apr 2011 12:20:02 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3F19CE076E; Mon, 11 Apr 2011 12:20:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6161 on Elliptic Curve Algorithms for Cryptographic Message Syntax (CMS) Encrypted Key Package Content Type
From: rfc-editor@rfc-editor.org
Message-Id: <20110411192003.3F19CE076E@rfc-editor.org>
Date: Mon, 11 Apr 2011 12:20:03 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2011 19:20:03 -0000

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

        
        RFC 6161

        Title:      Elliptic Curve Algorithms for Cryptographic 
                    Message Syntax (CMS) Encrypted Key Package 
                    Content Type 
        Author:     S. Turner
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2011
        Mailbox:    turners@ieca.com
        Pages:      3
        Characters: 5504
        Updates:    RFC6033

        I-D Tag:    draft-turner-ekpct-algs-update-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6161.txt

This document describes the conventions for using several Elliptic
Curve cryptographic algorithms with the Cryptographic Message Syntax
(CMS) encrypted key package content type.  Specifically, it includes
conventions necessary to implement Elliptic Curve Diffie-Hellman
(ECDH) with EnvelopedData and Elliptic Curve Digital Signature
Algorithm (ECDSA) with SignedData.  This document extends RFC 6033.
[STANDARDS-TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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-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