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

ianswett <> Tue, 19 March 2019 14:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5C3021312B0 for <>; Tue, 19 Mar 2019 07:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id G0cv8j5OsYTU for <>; Tue, 19 Mar 2019 07:20:02 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8A4471312C0 for <>; Tue, 19 Mar 2019 07:19:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; 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 with SMTP id filter1778p1mdw1-28353-5C90FA89-C 2019-03-19 14:19:53.271182652 +0000 UTC m=+48413.346453971
Received: from (unknown []) by (SG) with ESMTP id YyNzlJESQJ-NDh3HsouuyQ for <>; Tue, 19 Mar 2019 14:19:53.359 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 4796DC0EDC for <>; Tue, 19 Mar 2019 07:19:53 -0700 (PDT)
Date: Tue, 19 Mar 2019 14:19:53 +0000
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2524/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
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-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak19xcbGSD4MTTT+mZph1sZEcrcKUIHMIvwhfK HtXqDvhpKVcR92ttcOwIfNh1JiIyDUMVBT/dJqzDgnH6Wh+SD7HQ60D5MGlVG2xezBYBOaY+HQELRs 4DUWRotdwuNbq11PvgFbrMPs45Li0TFJnbVbBcXMholgp+El2eaJRqeGdw==
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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: