Re: [quicwg/base-drafts] Specify behavior for post-handshake CRYPTO messages (#2524)

ianswett <notifications@github.com> Tue, 19 March 2019 14:20 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 5C3021312B0 for <quic-issues@ietfa.amsl.com>; Tue, 19 Mar 2019 07:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level:
X-Spam-Status: No, score=-3 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 G0cv8j5OsYTU for <quic-issues@ietfa.amsl.com>; Tue, 19 Mar 2019 07:20:02 -0700 (PDT)
Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 8A4471312C0 for <quic-issues@ietf.org>; Tue, 19 Mar 2019 07:19:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=3lOWshErVzLRrlt4JE/Wi+csKdY=; b=lI3k5IKzUSK++8GJ IPKkdX6jmz6TAd9rIS/YGQ29dYxyQmskBuqs4Le0ILj4fRrTAF0i9CZ9F6f1ZOnB wae1KlAfN/9fEdG1WDchT/XTbuZ27wbRDXPAt6LI7980YynJFkyMOfaQvyDZ5a9e N8gKNBt2WgI/9Qz56QIcQURJG0g=
Received: by filter1778p1mdw1.sendgrid.net with SMTP id filter1778p1mdw1-28353-5C90FA89-C 2019-03-19 14:19:53.271182652 +0000 UTC m=+48413.346453971
Received: from github-lowworker-fc273f0.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0032p1iad2.sendgrid.net (SG) with ESMTP id YyNzlJESQJ-NDh3HsouuyQ for <quic-issues@ietf.org>; Tue, 19 Mar 2019 14:19:53.359 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-fc273f0.cp1-iad.github.net (Postfix) with ESMTP id 4796DC0EDC for <quic-issues@ietf.org>; Tue, 19 Mar 2019 07:19:53 -0700 (PDT)
Date: Tue, 19 Mar 2019 14:19:53 +0000 (UTC)
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab0cf917dd6cf005eab310707bc9c91e2f23bca82992cf0000000118a8bc8992a169ce192348df@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2524/c474391329@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2524@github.com>
References: <quicwg/base-drafts/pull/2524@github.com>
Subject: Re: [quicwg/base-drafts] Specify behavior for post-handshake CRYPTO messages (#2524)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c90fa89448e0_78cb3fc2946d45c05039bb"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak19xcbGSD4MTTT+mZph1sZEcrcKUIHMIvwhfK HtXqDvhpKVcR92ttcOwIfNh1JiIyDUMVBT/dJqzDgnH6Wh+SD7HQ60D5MGlVG2xezBYBOaY+HQELRs 4DUWRotdwuNbq11PvgFbrMPs45Li0TFJnbVbBcXMholgp+El2eaJRqeGdw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/a0kXoEq1c2Yb31XETzAEF4LRzbw>
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, 19 Mar 2019 14:20:05 -0000

As @martinthomson said, this was discussed in Tokyo and I believe included in the recent consensus call on the list, so I'd prefer to land this and gain some implementation experience, even if I might personally prefer a different solution.  As @nharper states, there are 3 options, and the WG has repeatedly said no to flow control and a number of people didn't like a fixed limit on the entire connection, so we ended up with the 3rd option.

-- 
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/pull/2524#issuecomment-474391329