[Cfrg] XChaCha RFC Draft

Paragon Initiative Enterprises Security Team <security@paragonie.com> Thu, 09 January 2020 23:39 UTC

Return-Path: <scott@paragonie.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF7571200C7 for <cfrg@ietfa.amsl.com>; Thu, 9 Jan 2020 15:39:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=paragonie-com.20150623.gappssmtp.com
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 Rm_IEpvzECpf for <cfrg@ietfa.amsl.com>; Thu, 9 Jan 2020 15:39:19 -0800 (PST)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F57E12003E for <cfrg@irtf.org>; Thu, 9 Jan 2020 15:39:19 -0800 (PST)
Received: by mail-lf1-x136.google.com with SMTP id n25so92119lfl.0 for <cfrg@irtf.org>; Thu, 09 Jan 2020 15:39:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paragonie-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=BPOzP6VpzTD7wrXCbKJYcUq8ifK1LbfkvSlSsRDGWcg=; b=0IdDlgq07GQ8R3dUYr+QBkXZt5Fkj5/hrLcBiSDLHG1uYlrv6prkmzGHQgqOI3gf3u Krdo8xp7o4DTXIOizlqxYdnwPIjadkTUlTc9cjma4Y+x8u1yGQZ20ozA39FqKBGvubsx R1NWE0PIgPioff2hAO4v5X7BFNgr76O3pGaoDKGD/hpQxMbLQTvtGBOBXJOxGfI1Q9Vf OdKyDd62ZqPyW3VgF6CVme/qsF424YgTxKb8J3pbD4yzW50Ojp3UTtcQN3o+7+dIlRK4 sXIk8zV4rqPFuc6j1dmSQrtCqCTqEodHOnQtc6WJeGOxI5fg/0pURydI6EP+G13zquTl HIUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=BPOzP6VpzTD7wrXCbKJYcUq8ifK1LbfkvSlSsRDGWcg=; b=nmmf8abCsBL7HhCm0gF3h07J4DgdgAXeU9ucc0LDsNgW2QB6JU35kma/D+BdaVnVLk 5eA7RTSX3tqUDVtTVr79H3mEXzLxjYgIvdcEWPlKA9suHd0Z3taLXs4cWJ/XwjC2qwhb MY6Jh4fhQQi1a4YHYihf5dwmypF8k4X7wIJhg3OV2Sw4IBOXpX5qkgGI3WqayIm2qK28 LCEOz8Tucpv6Cpst3g3CNeXJoB86sAf0WuZVojaky0yjmizbbiwpuV80RanzkZQMJeXP YhM6g71xFsp+l7/flv7T46+Fv3VY4pquR1b7pVWuGhzmVU4HQMbTKaorpfw4fFSJ9AtE KCVw==
X-Gm-Message-State: APjAAAVFDlhqnvJ7gB1kTmrw1/3szgBbfML2Z1hSInr8xFwYjhkAP9Fk oBnAxiUvRNoHy7ubzDZOuipk0DFv01ixPNFPHhYqhI51EV4=
X-Google-Smtp-Source: APXvYqxsh+fvIZgiDLNOmxoKcUMHOLGdEi+KrCBqGxCzKVPiQEGpaDfGcPv61t+iq1ObapmCU1VaR7uE07zUnqUhhjM=
X-Received: by 2002:ac2:41c8:: with SMTP id d8mr179164lfi.65.1578613157129; Thu, 09 Jan 2020 15:39:17 -0800 (PST)
MIME-Version: 1.0
From: Paragon Initiative Enterprises Security Team <security@paragonie.com>
Date: Thu, 9 Jan 2020 18:39:04 -0500
Message-ID: <CAKws9z1cMkaWzYEjmP1cZ9Thp6bvo_Du=qGF36Xz=9JZQk2DDw@mail.gmail.com>
To: IRTF CFRG <cfrg@irtf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/coaC68uPo1nD_3rrjSh8UzHTevM>
Subject: [Cfrg] XChaCha RFC Draft
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2020 23:39:21 -0000

The XChaCha RFC draft has been updated, based on feedback from Kyle
Den Hartog about the ease of implementation for XChaCha decryption.

Additionally, the reference to ChaCha20-Poly1305 has been updated to
use RFC 8439.

Please let us know if you have any additional feedback so we can begin
the standardization process.