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

afrind <notifications@github.com> Wed, 17 April 2019 23:52 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 4097212025E for <quic-issues@ietfa.amsl.com>; Wed, 17 Apr 2019 16:52:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.597
X-Spam-Level:
X-Spam-Status: No, score=-1.597 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 CroV3a4S0RSa for <quic-issues@ietfa.amsl.com>; Wed, 17 Apr 2019 16:52:36 -0700 (PDT)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DB59120456 for <quic-issues@ietf.org>; Wed, 17 Apr 2019 16:52:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=KcDrfjtJBcYhRAicZTWbJpODU2Y=; b=eaIKNPVqiUBO4cUd VNB7hpbYrTui26E4JmIUVICChkPdVmbDHVqCAkPry1NeSoSvlTZdehXcBFUMmMda g6N40/8/YxJz4sIr3LS3+ktIeplyMs3SxPEr3yZ43NRtjvWL5eXO7lnRNFq4zAA5 u+wOTe5anc9GI7mFXshrQRPa1yI=
Received: by filter0383p1iad2.sendgrid.net with SMTP id filter0383p1iad2-31859-5CB7BC33-5E 2019-04-17 23:52:19.943759037 +0000 UTC m=+778113.021393978
Received: from github-lowworker-20a34ff.cp1-iad.github.net (unknown [192.30.252.43]) by ismtpd0003p1iad2.sendgrid.net (SG) with ESMTP id tyxWZXZTQQCi7G-wGav-iA for <quic-issues@ietf.org>; Wed, 17 Apr 2019 23:52:19.910 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-20a34ff.cp1-iad.github.net (Postfix) with ESMTP id E01CA3400FD for <quic-issues@ietf.org>; Wed, 17 Apr 2019 16:52:19 -0700 (PDT)
Date: Wed, 17 Apr 2019 23:52:20 +0000 (UTC)
From: afrind <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3JSRMG2O2BRORHBCN2YTXLHEVBNHHBTZTRJU@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@github.com>
Subject: [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_5cb7bc33de7b5_11313f9c648cd9684859f0"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1g7mv9OZurfIZMX4ZbswzIsnZzflOh7VuJyQ IqlMuSJEajzOH9/8t5g4jwgwQd4M/XqkHGNuWaDzL/AgffqbtxgfUMQeoX+Ip9npRHyhCXgs8qahtw 9rxkghakiw5V96BwZYFIGJjs03I2F5lRtGmG3sxhir6i13EECBzhtLJfzg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/3NzsfqLNdjXaxy6l1Va3g2ygK94>
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: Wed, 17 Apr 2019 23:52:52 -0000

The current spec only allows GOAWAY to be sent from the server to the client and contains only the last processed bidirectional stream ID.  This makes sense for the vanilla HTTP use case, but may not play well with extensions.  Unidirectional streams are a flexible extension point, and it may be useful for each endpoint to communicate to the peer the last processed unidirectional stream id.  An HTTP extension may also define a use for server initiated bidirectional streams, and may want the GOAWAY signal for these also.

True if it's an extension then the extension author can also extend GOAWAY to cover these cases or introduce another mechanism, but it would be a shame if many extensions had to cover the same ground.

I suggest we allow GOAWAY to be sent by either endpoint, and that it should contain both the last processed peer initiated bidirectional and unidirectional 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