RFC 8439 on ChaCha20 and Poly1305 for IETF Protocols
rfc-editor@rfc-editor.org Tue, 19 June 2018 06:12 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 778C3130ED0 for <ietf-announce@ietfa.amsl.com>; Mon, 18 Jun 2018 23:12:35 -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 ikD1oYL_nLUl for <ietf-announce@ietfa.amsl.com>; Mon, 18 Jun 2018 23:12:33 -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 40DFA124D68 for <ietf-announce@ietf.org>; Mon, 18 Jun 2018 23:12:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 28249B8125B; Mon, 18 Jun 2018 23:12:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
Subject: RFC 8439 on ChaCha20 and Poly1305 for IETF Protocols
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, cfrg@irtf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180619061233.28249B8125B@rfc-editor.org>
Date: Mon, 18 Jun 2018 23:12:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/zGXwbEIfsCT9zaU5HkAOsLPrtHQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
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: Tue, 19 Jun 2018 06:12:36 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8439
Title: ChaCha20 and Poly1305 for IETF Protocols
Author: Y. Nir,
A. Langley
Status: Informational
Stream: IRTF
Date: June 2018
Mailbox: ynir.ietf@gmail.com,
agl@google.com
Pages: 46
Characters: 88847
Obsoletes: RFC 7539
I-D Tag: draft-nir-cfrg-rfc7539bis-04.txt
URL: https://www.rfc-editor.org/info/rfc8439
DOI: 10.17487/RFC8439
This document defines the ChaCha20 stream cipher as well as the use
of the Poly1305 authenticator, both as stand-alone algorithms and as
a "combined mode", or Authenticated Encryption with Associated Data
(AEAD) algorithm.
RFC 7539, the predecessor of this document, was meant to serve as a
stable reference and an implementation guide. It was a product of
the Crypto Forum Research Group (CFRG). This document merges the
errata filed against RFC 7539 and adds a little text to the Security
Considerations section.
This document is a product of the Crypto Forum Research Group of the IRTF.
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, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
https://www.irtf.org/mailman/listinfo/irtf-announce
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