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

Jana Iyengar <notifications@github.com> Tue, 21 January 2020 22:39 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 4FA9E1200A1 for <quic-issues@ietfa.amsl.com>; Tue, 21 Jan 2020 14:39:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.754
X-Spam-Level:
X-Spam-Status: No, score=-3.754 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_20=1.546, 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 NAF1UfJ8io8N for <quic-issues@ietfa.amsl.com>; Tue, 21 Jan 2020 14:39:49 -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 BE36912002E for <quic-issues@ietf.org>; Tue, 21 Jan 2020 14:39:49 -0800 (PST)
Received: from github-lowworker-c53a806.ac4-iad.github.net (github-lowworker-c53a806.ac4-iad.github.net [10.52.23.45]) by smtp.github.com (Postfix) with ESMTP id 904CF8C0FB5 for <quic-issues@ietf.org>; Tue, 21 Jan 2020 14:39:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1579646388; bh=BaJasY5st4GWoPvNNRC1ibqx3SPhiNowxGECaLJtRuY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iS6EVRKKnbKldjc1rnNFBF7VHXfLauvB/aM7W+U0GUiR53K5JPibGWn7p6y66u46x av0ZJTMPi1z2oT0P7lBGOQK5caojNVmuni8RBx7GuXAAtzkswAWKkYx57Cn9g7lTUk 7ojcrMTwSQC+E9zsG3OMpga9tx04Exg2yTUCkB4I=
Date: Tue, 21 Jan 2020 14:39:48 -0800
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK34BSAZ7SBYTXOBMD54GSYDJEVBNHHCBZFNCI@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/576919630@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_5e277db48141b_5ed93fdc42ecd96c1749db"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/bKDcvPZj6HsSS2rrV6uqq63_l8I>
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: Tue, 21 Jan 2020 22:39:51 -0000

This is useful, and we should merge this. I don't think this needs to be design.

-- 
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-576919630