[Curdle] RFC 8103 on Using ChaCha20-Poly1305 Authenticated Encryption in the Cryptographic Message Syntax (CMS)
rfc-editor@rfc-editor.org Tue, 28 February 2017 19:36 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 044FD12969D; Tue, 28 Feb 2017 11:36:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 JSYmfMQP8i76; Tue, 28 Feb 2017 11:36:18 -0800 (PST)
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 7945E1296AF; Tue, 28 Feb 2017 11:36:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 5DEF0B80347; Tue, 28 Feb 2017 11:36:09 -0800 (PST)
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
Message-Id: <20170228193609.5DEF0B80347@rfc-editor.org>
Date: Tue, 28 Feb 2017 11:36:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/RwUe_Et3rk4q8PzL4oVGTdcwrOQ>
Cc: drafts-update-ref@iana.org, curdle@ietf.org, rfc-editor@rfc-editor.org
Subject: [Curdle] RFC 8103 on Using ChaCha20-Poly1305 Authenticated Encryption in the Cryptographic Message Syntax (CMS)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Feb 2017 19:36:26 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8103 Title: Using ChaCha20-Poly1305 Authenticated Encryption in the Cryptographic Message Syntax (CMS) Author: R. Housley Status: Standards Track Stream: IETF Date: February 2017 Mailbox: housley@vigilsec.com Pages: 9 Characters: 18866 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-curdle-cms-chacha20-poly1305-06.txt URL: https://www.rfc-editor.org/info/rfc8103 DOI: 10.17487/RFC8103 This document describes the conventions for using ChaCha20-Poly1305 Authenticated Encryption in the Cryptographic Message Syntax (CMS). ChaCha20-Poly1305 is an authenticated encryption algorithm constructed of the ChaCha stream cipher and Poly1305 authenticator. 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