Re: [quicwg/base-drafts] Talk about concurrency in H3 vs. H2 (#3114)

ianswett <> Mon, 21 October 2019 16:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1D9CF12010D for <>; Mon, 21 Oct 2019 09:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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_24=1.618, 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 ztXACxVaZozu for <>; Mon, 21 Oct 2019 09:41:59 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 75AB61200F8 for <>; Mon, 21 Oct 2019 09:41:59 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id C2EAF6A0DB6 for <>; Mon, 21 Oct 2019 09:41:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571676118; bh=qwZ4shDRrAgRzFDrdHL8tz4mAKiEPq0QyCYc1qJe+Tc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ki8hFEUTS3Yg0N0o5+IZqG7rOfg1+TECK+6IBfOPupxb6fmoUxhPgEHZDHUsUtJRZ Q3rwoj3i+phzQEHNTqn2ur/qjg+Yyafb2TZBRcb7849zpzVrkogae+QmIcVlEcDWvg tVqbQ2HSw5lcl83b9Qv6cxfSu+pTylqWcHqMZY1c=
Date: Mon, 21 Oct 2019 09:41:58 -0700
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3114/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Talk about concurrency in H3 vs. H2 (#3114)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5daddfd6b2077_78563fcae46cd95c298518"; 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
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, 21 Oct 2019 16:42:01 -0000

ianswett commented on this pull request.

> @@ -1814,6 +1814,15 @@ considerations about exhaustion of stream identifier space apply, though the
 space is significantly larger such that it is likely that other limits in QUIC
 are reached first, such as the limit on the connection flow control window.
+QUIC manages stream concurrency on behalf of HTTP/3.  QUIC considers a stream
+closed when all sent data and all acknowledgements for received data have been
+acknowledged by the peer.  HTTP/2 considers a stream closed when the frame

Or a reset has been sent and acknowledged.

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