Re: [quicwg/base-drafts] Why do we have final size? (#3739)

ianswett <> Mon, 08 June 2020 19:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 63C743A0F40 for <>; Mon, 8 Jun 2020 12:26:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Status: No, score=-1.483 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 zY32-4nqceg2 for <>; Mon, 8 Jun 2020 12:26:12 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6B3153A0F3F for <>; Mon, 8 Jun 2020 12:26:12 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id BCE4E6A0DB0 for <>; Mon, 8 Jun 2020 12:26:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1591644371; bh=5XUNGyM/5WvHOaYhVsIyHr1FworocNAk7WSJk7mLnnw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=eY+8p8urQJAh9aWH9w8xTHFqjTBErRqKcAAqZyM41GJ0y2o4KNXc0sMRcDTrQt4gR CvzUink2qfRWMk3o+e7AMdVQqTJRyliXngvUyi8b+hpmpari0f3C/KBKBnbtdjUTe4 3a97oNHgGhIFDSVndHTn1p4mya6xrfn5HKJsfShc=
Date: Mon, 08 Jun 2020 12:26:11 -0700
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3739/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Why do we have final size? (#3739)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ede90d3ad2d5_55f33ff59a8cd9604912f6"; 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, 08 Jun 2020 19:26:14 -0000

@ianswett commented on this pull request.

> +of a RESET_STREAM frame carries this value.  This ensures that all ways that a
+stream can be closed result in the number of bytes on the stream being reliably
+transmitted.  This guarantees that both endpoints agree on how much flow control

of a RESET_STREAM frame carries this value.  This ensures all closed streams have a known final size, guaranteeing both endpoints agree on how much flow control

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