[quicwg/base-drafts] suggest easier way of initiating graceful shutdown from the server-side (#3341)

Kazuho Oku <notifications@github.com> Tue, 14 January 2020 14:14 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 126191200EC for <quic-issues@ietfa.amsl.com>; Tue, 14 Jan 2020 06:14:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id eBa5_GM8JAFN for <quic-issues@ietfa.amsl.com>; Tue, 14 Jan 2020 06:14:32 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E5BB1200D7 for <quic-issues@ietf.org>; Tue, 14 Jan 2020 06:14:32 -0800 (PST)
Date: Tue, 14 Jan 2020 06:14:31 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1579011271; bh=RYPzVTobeFGMvzlEnHg3er5TF2ZFWunFmp7TyGBafnk=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=02aAOMiSkP3hIJzqwbeMUY0W72RKa8S0xDgVb7w1r8wOj3kb2qVyc79K3X23w6EI+ c/Lwd+tPYR5onESyYDp8IzNWgpaczwsPOB47TNCGWkoxH8T67xbS624z8zxRnbYlVz r2P3Ukf4Dh2TwhYdtyVr5QSoK/Ji+TphhEXQkm88=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZO7WF53ZJ46XGNRRF4FL7UPEVBNHHCBQRINU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3341@github.com>
Subject: [quicwg/base-drafts] suggest easier way of initiating graceful shutdown from the server-side (#3341)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e1dccc74385c_45273ff6244cd95c22278"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/t7FJ5TXUaSS2EKGWCZOpRwkV9Cw>
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, 14 Jan 2020 14:14:37 -0000

At the moment, the recommended way of gracefully shutting down an H3 connection is, according to [section 5.2](https://quicwg.org/base-drafts/draft-ietf-quic-http.html#section-5.2-7):
> A server that is attempting to gracefully shut down a connection SHOULD send an initial GOAWAY frame with the last Stream ID set to the maximum value allowed by QUIC's MAX_STREAMS and SHOULD NOT increase the MAX_STREAMS limit thereafter. This signals to the client that a shutdown is imminent and that initiating further requests is prohibited._

It is my understanding that the reason we suggest sending "the maximum value allowed by QUIC's MAX_STREAMS" is because, unlike HTTP/2, we cannot send GOAWAY frame with an identifier value that is greater than any possible client-generated bidirectional stream ID.

However, the downside is that the current text assumes tight integration with the QUIC stack that might be unnecessary - let the QUIC stack provide current MAX_STREAMS value, and also stop giving the client new credits.

I am not against the status quo, but I think we might want to give practical advice. The minimum change can be to state "a server that is attempting to gracefully shutdown a connection SHOULD send an Initial GOAWAY frame with the last Stream ID set to the maximum value currently allowed by QUIC's MAX_STREAMS *or any value above that*."

Such change would imply that sending 2<sup>62</sup>-4 (the maximum stream ID for a request stream) assuming that the client would not send that much of requests on a single connection. Note that it is trivial for a server to make sure that the stream ID would not become that big - the server can always gracefully shutdown a connection well before the stream ID becomes that big.

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