[quicwg/base-drafts] 50a2b1: 0-RTT can't use transport parameters or 1-RTT frames
Martin Thomson <noreply@github.com> Wed, 13 February 2019 02:47 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 661CD130F4C for <quic-issues@ietfa.amsl.com>; Tue, 12 Feb 2019 18:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Level:
X-Spam-Status: No, score=-7.001 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 XRMLci433bFR for <quic-issues@ietfa.amsl.com>; Tue, 12 Feb 2019 18:47:50 -0800 (PST)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8D8C1277D2 for <quic-issues@ietf.org>; Tue, 12 Feb 2019 18:47:50 -0800 (PST)
Date: Tue, 12 Feb 2019 18:47:49 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1550026069; bh=xFhldIpYohORBN5UyMV9huwnnCR8yR+Oz7voXHV2EBI=; h=Date:From:To:Subject:From; b=0T9Rbb2h2heimW6tvcxp0OQkXCHwL/OdWP9/X6utfzpc3jI613/NjexZJJCyrfB6l CNwc0VbxlKQV2D6hkP+dn4lP2dxy44HqzVOXbsc2fgd5o/0VTl9Z2lTAKY5FdxCKVZ X8kDvkpTRo64ZBoPu5SctDbZUMlcQRACFsv8aZWk=
From: Martin Thomson <noreply@github.com>
To: quic-issues@ietf.org
Message-ID: <quicwg/base-drafts/push/refs/heads/0rtt-cant-respond-to-1rtt/000000-50a2b1@github.com>
Subject: [quicwg/base-drafts] 50a2b1: 0-RTT can't use transport parameters or 1-RTT frames
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-Auto-Response-Suppress: All
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/HKKx038DuDUdO0BEA2z3T1VYKfE>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Wed, 13 Feb 2019 02:47:52 -0000
Branch: refs/heads/0rtt-cant-respond-to-1rtt Home: https://github.com/quicwg/base-drafts Commit: 50a2b121866a8de0352b726645e74f87a20444cf https://github.com/quicwg/base-drafts/commit/50a2b121866a8de0352b726645e74f87a20444cf Author: Martin Thomson <mt@lowentropy.net> Date: 2019-02-13 (Wed, 13 Feb 2019) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- 0-RTT can't use transport parameters or 1-RTT frames While in theory a client could send 0-RTT after receiving 1-RTT, this is not a good idea. This PR ties down transport parameters and flow control and prevents a client from using anything it learns in the handshake or 1-RTT from affecting (or expanding) what it can do with 0-RTT. This prevents a client from using 0-RTT indefinitely and creates stronger bounds on what 0-RTT can be used for. Closes #2458, #2360.
- [quicwg/base-drafts] 50a2b1: 0-RTT can't use tran… Martin Thomson