Re: [quicwg/base-drafts] Client MUST use 1-RTT packets if it reads 1-RTT packets (#2458)

Kazuho Oku <> Wed, 08 May 2019 23:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BE9E112014E for <>; Wed, 8 May 2019 16:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.464
X-Spam-Status: No, score=-1.464 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 AycPkBgY2JwJ for <>; Wed, 8 May 2019 16:42:28 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 01535120234 for <>; Wed, 8 May 2019 16:42:27 -0700 (PDT)
Date: Wed, 08 May 2019 16:42:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1557358947; bh=TVLb8PYTqvI1D4jBdc0jzj46G3kMBj4/wGgmrpL1UbE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gX4mZJq67aOYgGiRnSjyYv8UkOYLvEzKJdOCHn9ScoN97BIXb17L8s9cxjRj+jm/w xmEqFVbFYOZAl/wmvlHE/+Uz99F7LWQRDGxX1e2CmMwvmIFfOPlgmIUoSSS/gmcKDo 1LlIWfn4tNDUVxXAF+2Iy+Rfie/TMpRdW/RgvEkM=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2458/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Client MUST use 1-RTT packets if it reads 1-RTT packets (#2458)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd369632516e_8093f9afd0cd9601604f4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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: Wed, 08 May 2019 23:42:30 -0000

> detection with flow control would require special case code in stream processing, as in "check against the current window but if 0-RTT check against the initial window". Could be done, but that would be another wart.

It's actually something that can be implemented in a clear and concise way. The only thing you need to have are objects representing limits for each type of packets. When processing 0-RTT packets, the logic would refer to the limits declared by TP of the previous connection. When processing 1-RTT packets, the logic would refer to the limits declared by current TP and the max frames.

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