Re: [quicwg/base-drafts] 0-RTT can't use transport parameters or 1-RTT frames (#2461)

David Schinazi <> Thu, 14 February 2019 20:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EDB1612EB11 for <>; Thu, 14 Feb 2019 12:49:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_HI=-5, 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 bABb8FwVCnLq for <>; Thu, 14 Feb 2019 12:49:09 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 39A3B129532 for <>; Thu, 14 Feb 2019 12:49:09 -0800 (PST)
Date: Thu, 14 Feb 2019 12:49:08 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1550177348; bh=sJ3ZGS10EFCsi1yqWZW6l25wgmpxaFFi+2hw2oe+VD4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZzqrdpFblxayigiL/1mqnfS8BCy+Rz6v0pFsfy6a9+gpINDjUPj/tJt+Wihk2O1vM AJSi8OmiDxthIDapo8f+02OsHUMFo/9aLwcYEAuP0GOS4QKVP5SO/LnS0A6tn5bmy8 ds/SihhseSZGKyUWfS3zbIpM4gYI3W1x+iFm1mvE=
From: David Schinazi <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2461/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] 0-RTT can't use transport parameters or 1-RTT frames (#2461)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c65d444241b6_13f53fc9cbed45c04413c1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
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: Thu, 14 Feb 2019 20:49:11 -0000

I know we agreed to this is Tokyo, but seeing the actual PR made me realize how complex and hard to enforce this is. Would it be possible to solve the issue in a simpler way by saying something along the lines of the following? `Once a server receives a valid 1-RTT packet with packet number n, any 0-RTT packet it receives with packet number greater than n MUST be ignored.` That way clients can't keep sending 0-RTT forever since they'll have to send a 1-RTT ACK to unblock the server-to-client flow control at some point.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: