[Curdle] RFC 8418 on Use of the Elliptic Curve Diffie-Hellman Key Agreement Algorithm with X25519 and X448 in the Cryptographic Message Syntax (CMS)
rfc-editor@rfc-editor.org Tue, 07 August 2018 05:38 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF501130F69; Mon, 6 Aug 2018 22:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tvCZYhWAHgPp; Mon, 6 Aug 2018 22:38:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB882130E87; Mon, 6 Aug 2018 22:38:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 836FCB817CF; Mon, 6 Aug 2018 22:38:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, curdle@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180807053847.836FCB817CF@rfc-editor.org>
Date: Mon, 06 Aug 2018 22:38:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/MIkRTgw1Qz7IBEBog7CIyf8MKQE>
Subject: [Curdle] RFC 8418 on Use of the Elliptic Curve Diffie-Hellman Key Agreement Algorithm with X25519 and X448 in the Cryptographic Message Syntax (CMS)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2018 05:39:00 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8418
Title: Use of the Elliptic Curve Diffie-Hellman
Key Agreement Algorithm with X25519 and X448
in the Cryptographic Message Syntax (CMS)
Author: R. Housley
Status: Standards Track
Stream: IETF
Date: August 2018
Mailbox: housley@vigilsec.com
Pages: 18
Characters: 36498
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-curdle-cms-ecdh-new-curves-10.txt
URL: https://www.rfc-editor.org/info/rfc8418
DOI: 10.17487/RFC8418
This document describes the conventions for using the Elliptic Curve
Diffie-Hellman (ECDH) key agreement algorithm with curve25519 and
curve448 in the Cryptographic Message Syntax (CMS).
This document is a product of the CURves, Deprecating and a Little more Encryption Working Group of the IETF.
This is now a Proposed Standard.
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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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