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

afrind <notifications@github.com> Tue, 17 September 2019 23:18 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B8C312004F for <quic-issues@ietfa.amsl.com>; Tue, 17 Sep 2019 16:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id frmyoxvPJeGU for <quic-issues@ietfa.amsl.com>; Tue, 17 Sep 2019 16:18:10 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB7F012003E for <quic-issues@ietf.org>; 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; d=github.com; 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 <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK62L6NYNO4M57K5G6N3R2VEDEVBNHHBTZTRJU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2632/532438009@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2632@github.com>
References: <quicwg/base-drafts/issues/2632@github.com>
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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/DlmGK5SV-g_-gmBdeFT4228rfJc>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=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:
https://github.com/quicwg/base-drafts/issues/2632#issuecomment-532438009