IETF Logo Mail Archive

Re: [quicwg/base-drafts] HTTP/3: behavior on unreasonable error cases (#4768)

Lucas Pardue <notifications@github.com> Wed, 20 January 2021 00:51 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 9A7A03A0ACB for <quic-issues@ietfa.amsl.com>; Tue, 19 Jan 2021 16:51:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 o2IJ3UIPnQIp for <quic-issues@ietfa.amsl.com>; Tue, 19 Jan 2021 16:51:14 -0800 (PST)
Received: from smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 333653A0AC5 for <quic-issues@ietf.org>; Tue, 19 Jan 2021 16:51:14 -0800 (PST)
Received: from github.com (hubbernetes-node-0ee181c.ac4-iad.github.net [10.52.114.19]) by smtp.github.com (Postfix) with ESMTPA id 45F35560626 for <quic-issues@ietf.org>; Tue, 19 Jan 2021 16:51:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1611103873; bh=ItPRGyoQRvgk/bQpj6FAe3ZerGEug9d4PjdIO5rHKpM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VaNFBfnop/+hswV7GODs/I1QI4ee07bl9B5H9Begsf/UAc9hHb9iPctlizKy9DlZr QOTmLELDkuxh3PG9JfKn/WhPExRFGwzcZhYEnUhilVTh2PKl9OiXnh8gq3QwDYdCUr xQ7cmlDwHgHhO6FCsoL1hTQ5H0gwxAZCCy7E1czU=
Date: Tue, 19 Jan 2021 16:51:13 -0800
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK65NZ5C4W7F6N6C7BN6CNPYDEVBNHHC6DX2VA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4768/763247742@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4768@github.com>
References: <quicwg/base-drafts/issues/4768@github.com>
Subject: Re: [quicwg/base-drafts] HTTP/3: behavior on unreasonable error cases (#4768)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_60077e8141c32_511a04416ac"; 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/jwB_TlSX42T3q-RzzCk349tQ3tg>
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:51:16 -0000

(As an individual) This is a fair observation. But as noted on #4766, trying to enforce accurate usage of error codes is a rocky Road. 

A sensible approach is to hope that the error codes your peer receives might include a specific and accurate error code that can be used for offline debugging or analysis. 

In reality, implementations should be expect generic or inaccurate error codes to be generated by a peer. And it it is in their interests not to build too many runtime application behaviours on top of expectations that might not be met.

-- 
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/4768#issuecomment-763247742

v2.23.0 | Report a Bug | By Email