RFC 7905 on ChaCha20-Poly1305 Cipher Suites for Transport Layer Security (TLS)
rfc-editor@rfc-editor.org Wed, 22 June 2016 22:34 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F00512DD4B; Wed, 22 Jun 2016 15:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 h04vBC4BhU9z; Wed, 22 Jun 2016 15:34:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6953112DD4F; Wed, 22 Jun 2016 15:33:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 61465B80C0B; Wed, 22 Jun 2016 15:33:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7905 on ChaCha20-Poly1305 Cipher Suites for Transport Layer Security (TLS)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160622223329.61465B80C0B@rfc-editor.org>
Date: Wed, 22 Jun 2016 15:33:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/wfqnTOxQ80ulaEUXTkxypuGX_0I>
Cc: drafts-update-ref@iana.org, tls@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Wed, 22 Jun 2016 22:34:11 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7905
Title: ChaCha20-Poly1305 Cipher Suites for
Transport Layer Security (TLS)
Author: A. Langley,
W. Chang,
N. Mavrogiannopoulos,
J. Strombergson,
S. Josefsson
Status: Standards Track
Stream: IETF
Date: June 2016
Mailbox: agl@google.com,
wtc@google.com,
nmav@redhat.com,
joachim@secworks.se,
simon@josefsson.org
Pages: 8
Characters: 15575
Updates: RFC 5246, RFC 6347
I-D Tag: draft-ietf-tls-chacha20-poly1305-04.txt
URL: https://www.rfc-editor.org/info/rfc7905
DOI: http://dx.doi.org/10.17487/RFC7905
This document describes the use of the ChaCha stream cipher and
Poly1305 authenticator in the Transport Layer Security (TLS) and
Datagram Transport Layer Security (DTLS) protocols.
This document updates RFCs 5246 and 6347.
This document is a product of the Transport Layer Security 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