Re: [quicwg/base-drafts] QUIC flow control is not quite like HTTP/2 (#3766)

Lucas Pardue <> Tue, 16 June 2020 22:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 56A273A086A for <>; Tue, 16 Jun 2020 15:22:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 3.303
X-Spam-Level: ***
X-Spam-Status: No, score=3.303 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, DKIM_VALID_EF=-0.1, GB_SUMOF=5, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id T8J3c8jnFk_R for <>; Tue, 16 Jun 2020 15:22:18 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0E2B23A0879 for <>; Tue, 16 Jun 2020 15:22:18 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 54CF78C0B55 for <>; Tue, 16 Jun 2020 15:22:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1592346137; bh=tIQvDWSH9e39+nkwL51wFFpSnQ3e00WzPiR7ObPzrpk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wRhTXcl9oey1ZUmCz97abgfa7W71MogLzjzMmcCFxO7wy9PKsELrO2hTcJ/Gr5HFs r8APdrx2mj04spZnAo7lrDwlEgqyLxM1IIX3rsieIgGokQ0b/lNBIYWV/zZyKGBgfw y3OuRgc5qkF0ofLg/EuezaGPClP3yoM7agTnlYxM=
Date: Tue, 16 Jun 2020 15:22:17 -0700
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3766/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] QUIC flow control is not quite like HTTP/2 (#3766)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ee9461945d8b_218b3f99840cd96c1501ec"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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: Tue, 16 Jun 2020 22:22:19 -0000

@LPardue commented on this pull request.

> +A receiver can advertise a larger limit for a stream by sending a MAX_STREAM_DATA
+frame with the Stream ID field set appropriately.  A MAX_STREAM_DATA frame
+indicates the maximum absolute byte offset of a stream.  A receiver could use the
+current offset of data consumed to determine the flow control offset to be
+advertised. A receiver MAY send MAX_STREAM_DATA frames in multiple packets in
+order to make sure that the sender receives an update before running out of
+flow control, even if one of the packets is lost.
+A receiver can advertise a larger limit for a connection by sending a MAX_DATA
+frame, which indicates the maximum of the sum of the absolute byte offsets of
+all streams.  A receiver maintains a cumulative sum of bytes received on all
+streams, which is used to check for flow control violations. A receiver might
+use a sum of bytes consumed on all streams to determine the maximum data limit
+to be advertised.
+Once a receiver advertises an offset for the connection or a stream, it MAY

Once a receiver advertises a limit for the connection or a stream, it MAY

limit seems more consistent now

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