IETF Logo Mail Archive

Re: [quicwg/base-drafts] Explicitly define H3_REQUEST_FOO as stream error (#4766)

Lucas Pardue <notifications@github.com> Wed, 20 January 2021 00:42 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 7DD693A0A65 for <quic-issues@ietfa.amsl.com>; Tue, 19 Jan 2021 16:42:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.804
X-Spam-Level:
X-Spam-Status: No, score=-1.804 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 WJ_R0-jgpqTW for <quic-issues@ietfa.amsl.com>; Tue, 19 Jan 2021 16:42:16 -0800 (PST)
Received: from smtp.github.com (out-25.smtp.github.com [192.30.252.208]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 427753A0A63 for <quic-issues@ietf.org>; Tue, 19 Jan 2021 16:42:16 -0800 (PST)
Received: from github.com (hubbernetes-node-8e6ce34.ash1-iad.github.net [10.56.102.69]) by smtp.github.com (Postfix) with ESMTPA id 73D0E840E1B for <quic-issues@ietf.org>; Tue, 19 Jan 2021 16:42:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1611103335; bh=igRcFvm3RzVwebQvsgJHwjsAQaq4uu8+8N+Td1seeo0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KV/gReQJ4EUra53WGgKuUSScjNjFrH4Gl54mqNqM19B0x6CDg1682k51j4gDTpDmO qEpHqM4tmA9W+lIfOmrqYFg5ZAU3d1C7OEfuH9IjfTt8CdDo84Z+hO7T3AesS5aa89 7f/hVHGXB0Nh8hmid8BEBeV817Uah9UbczCpYcEA=
Date: Tue, 19 Jan 2021 16:42:15 -0800
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6FTQZ6E444PV64NSV6CNOWPEVBNHHC6DXCQA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4766/763244518@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4766@github.com>
References: <quicwg/base-drafts/issues/4766@github.com>
Subject: Re: [quicwg/base-drafts] Explicitly define H3_REQUEST_FOO as stream error (#4766)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_60077c676fe83_4c01a0412459e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/XaS2LKjWUiPh8nbdAfe_A5QQm_Q>
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, 20 Jan 2021 00:42:18 -0000

Commenting as an individual.

The error code space is shared between connection and streams. The action associated with a stream error or connection error cause QUIC transport frames to be emitted, which can use a code.

H3 inherits H2's design philosophy that endpoints can generate a connection error at will. So while there are specific cases that describe "treat X as stream error foo", endpoints are also allowed to "treat X as connection error foo".

Constraining the error codes to different uses has a certain appeal. But then what do we say the the receiver of an error code of the wrong type should do? Generate its own error? I think this has come up a couple of times during H3 drafts but I'm satisfied that the flexibility we have today is about the best we can do. 

-- 
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/4766#issuecomment-763244518

v2.23.0 | Report a Bug | By Email