Re: [quicwg/base-drafts] H3 GOAWAY should be symmetric and cover bidi and uni streams (#2632)

afrind <> Tue, 17 September 2019 23:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8B8C312004F for <>; Tue, 17 Sep 2019 16:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_20=1.546, 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 frmyoxvPJeGU for <>; Tue, 17 Sep 2019 16:18:10 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BB7F012003E for <>; Tue, 17 Sep 2019 16:18:10 -0700 (PDT)
Date: Tue, 17 Sep 2019 16:18:09 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1568762289; bh=5FOhtXAfPpyujC2/nsK+L/l7KTb0KXUNuOSR9w5lBQc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pk4v0Oo6v4cHo6N/e/6cIMsiEBTMOEwAbG3A5xnNSkp51i0tdD1CHp9iD7k5iiK9e j6GXpDDh5+CIC1VNED7rSEaLjDF3RBpl6tne6D+oz1neUeS3rC+ggvdQgzg4H0sN6A T4+xwXdlfwmh2Bb3EhR5vnrpQYijtHjPniGHRWeo=
From: afrind <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2632/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] H3 GOAWAY should be symmetric and cover bidi and uni streams (#2632)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d8169b1da94d_2b853fc4520cd9641159e5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: afrind
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, 17 Sep 2019 23:18:13 -0000

A different use case came up:

Consider streaming a (potentially infinite) live video as a sequence of pushes.  How does a client signal its intent to close this connection, and stop the server from pushing more video segments?

The client can send a STOP_SENDING frame on the request stream which is receiving the PUSH_PROMISEs, but this may result in less than graceful termination of that stream.

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