Re: [quicwg/base-drafts] Don't specify RTT in HTTP (#3358)

Martin Thomson <> Mon, 20 January 2020 06:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 19CCC120025 for <>; Sun, 19 Jan 2020 22:23:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 62y_-qat757I for <>; Sun, 19 Jan 2020 22:23:40 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6ACDD120043 for <>; Sun, 19 Jan 2020 22:23:40 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id BF84CA10DF for <>; Sun, 19 Jan 2020 22:23:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1579501419; bh=bKkSiC7hOcAxKMI4vskfJ2KfFMDU843y+PHH6gFLKPQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GpqjLn+a09pE1RuJbprWVWcD1+zy5wC/dUqCwcwZuozEYUk8lE2ZTgWi9Fb/mAWdb dpAvyTEIvs3/B9fUa9lU0yucFd1u94SFsTI3jNCyAIm2eLKygfNYsPFZrfxzwjSokN TkMkAxT96FQNTmFWB4PBSMjrQjJ6unRjRvRttjOM=
Date: Sun, 19 Jan 2020 22:23:39 -0800
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3358/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Don't specify RTT in HTTP (#3358)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e25476bb052c_63c93fd48facd96c430cc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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: Mon, 20 Jan 2020 06:23:42 -0000

martinthomson commented on this pull request.

Seems alright.

> @@ -732,9 +732,10 @@ initial GOAWAY frame with the last Stream ID set to the maximum possible value
 for a client-initiated, bidirectional stream (i.e. 2^62-4 in case of QUIC
 version 1).  This GOAWAY frame signals to the client that shutdown is imminent
 and that initiating further requests is prohibited.  After allowing time for any
-in-flight requests (at least one round-trip time), the server would send another
-GOAWAY frame with an updated last Stream ID.  This ensures that a connection can
-be cleanly shut down without causing requests to fail.
+in-flight requests to reach the server, the server MAY send another GOAWAY frame
+indicating which requests it will accept before the end of the connection. This

Don't you mean "can send"?

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