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

afrind <notifications@github.com> Mon, 29 April 2019 18:05 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 0B4FD1200D6 for <quic-issues@ietfa.amsl.com>; Mon, 29 Apr 2019 11:05:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level:
X-Spam-Status: No, score=-3.001 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_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 r7yjH8PC2t7y for <quic-issues@ietfa.amsl.com>; Mon, 29 Apr 2019 11:05:43 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 EC6E5120096 for <quic-issues@ietf.org>; Mon, 29 Apr 2019 11:05:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=U3OfuQ93xIBTY5UuAv25qfqHJkI=; b=vewmTOFVs4vmEOiY R9I8luFgPJerUVrOQqGpAgTiubQhyt+u8H81s6RyfXB3wUtQWju7LLxbis4CONdn cqeXWEUpiwYU2wtZ4w0K/resluTzjmMtmUNFGntwEi57BVYZALX8KZsCn3puXVUd 6pYL8XoOySbkF/hW+SgL7B5+w5U=
Received: by filter0521p1iad2.sendgrid.net with SMTP id filter0521p1iad2-11423-5CC73CE9-85 2019-04-29 18:05:29.842107102 +0000 UTC m=+334288.452600629
Received: from github-lowworker-63e61ec.cp1-iad.github.net (unknown [140.82.115.67]) by ismtpd0050p1iad1.sendgrid.net (SG) with ESMTP id 6xQbgvMaTZq-otL1wPL11A for <quic-issues@ietf.org>; Mon, 29 Apr 2019 18:05:29.774 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-63e61ec.cp1-iad.github.net (Postfix) with ESMTP id B1B362A030B for <quic-issues@ietf.org>; Mon, 29 Apr 2019 11:05:29 -0700 (PDT)
Date: Mon, 29 Apr 2019 18:05:29 +0000 (UTC)
From: afrind <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3ABBMKV2XTSZCS5BF22RXWTEVBNHHBTZTRJU@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/487683538@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_5cc73ce9acab7_53673fb5782cd964102539"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1J0Pck4J16T/u06oaIuy5nVH7QnowoEwoA1e f2SsbBQQ+OB4qirC7+oHCvQOkLomx+/CbR/r69Q9I3Yv80lQ42uqTNuPS+PeicpDWXBFLpaFzMro5m l22oVNAYIabi6kq6GrWdFC1Ndlrmn+1jgjGbnqweChITgZwkoQHi9tyQsg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/kOCDeOFNVnZ8aVuNsHppanljPnc>
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: Mon, 29 Apr 2019 18:05:45 -0000

The extension we are developing allows complete bidirectionality to HTTP, so a server can initiate a request/response to the client.  The H2 mapping of this extension uses a client-sent GOAWAY to clue the server in to stop doing this.  I don't know that missing this will break-badly; it probably depends on what application developers do with the bidirectionality.  It's asymmetric with H2, seemingly because we think we got it wrong in H2 and are trying to correct it?  I'm trying to say there is some value in keeping it symmetric.

I think Lucas correctly identified the semantics of what GOAWAY is - STOP_CREATING and PROCESSED.

As mentioned in the original issue, anyone writing an extension can also extend the GOAWAY frame under that extension that does what I proposed, so doing nothing is of course viable. 



-- 
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-487683538