Re: [quicwg/base-drafts] Retry integrity protection should not add new requirements to TLS API (#3366)

Martin Thomson <notifications@github.com> Mon, 20 January 2020 06:31 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83F20120043 for <quic-issues@ietfa.amsl.com>; Sun, 19 Jan 2020 22:31:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.682
X-Spam-Level:
X-Spam-Status: No, score=-3.682 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 i5RztYMxETd9 for <quic-issues@ietfa.amsl.com>; Sun, 19 Jan 2020 22:31:15 -0800 (PST)
Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABAA3120025 for <quic-issues@ietf.org>; Sun, 19 Jan 2020 22:31:15 -0800 (PST)
Received: from github-lowworker-2300405.va3-iad.github.net (github-lowworker-2300405.va3-iad.github.net [10.48.17.39]) by smtp.github.com (Postfix) with ESMTP id 157F48C0F25 for <quic-issues@ietf.org>; Sun, 19 Jan 2020 22:31:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1579501875; bh=dRaw1LaHVadNlTex/Lfy0cCA70APW8JvdJOFfJBTcXE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qJJXE9AVOsVhIhnbdlqhFvXGaq7e5JKDw1s8iutLrQtG4XW3liDBCcZ/UvQMswz6Y FzNV+GFSBRCFeycpR4MYXKRWHmIRrM8dspWjPXpIpeZSmAmvdlkfKJS30P7Z8t+5+B 5rJRIAb+7xt0bKpN1Fs9V9t/+Tx121x4QuXrre4U=
Date: Sun, 19 Jan 2020 22:31:15 -0800
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZXRSIOLF3WSDYUXGV4GJ53HEVBNHHCBZFNCI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3366/576126951@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3366@github.com>
References: <quicwg/base-drafts/issues/3366@github.com>
Subject: Re: [quicwg/base-drafts] Retry integrity protection should not add new requirements to TLS API (#3366)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e2549335992_16513fb0d38cd96c3194e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/N_sUaV8y0hv8FjYdhfq5VxjMCM8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2020 06:31:17 -0000

It would be easier for me to do as @kazuho suggested, but the overall effort is small.  I can live with either answer.  Note that the additional indirection can be hard-coded out if people find they want to prime their AES directly.  Of course, you don't need to run AES at all if you want to go that far.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3366#issuecomment-576126951