IETF Logo Mail Archive

Re: [quicwg/base-drafts] Ambiguous wording about error codes in HTTP/3 (#3276)

Lucas Pardue <notifications@github.com> Wed, 27 November 2019 14:27 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 8F631120948 for <quic-issues@ietfa.amsl.com>; Wed, 27 Nov 2019 06:27:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 5_MpMvMZJYPW for <quic-issues@ietfa.amsl.com>; Wed, 27 Nov 2019 06:27:10 -0800 (PST)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C037120915 for <quic-issues@ietf.org>; Wed, 27 Nov 2019 06:27:10 -0800 (PST)
Received: from github-lowworker-28f8021.ac4-iad.github.net (github-lowworker-28f8021.ac4-iad.github.net [10.52.25.98]) by smtp.github.com (Postfix) with ESMTP id B71C1A018B for <quic-issues@ietf.org>; Wed, 27 Nov 2019 06:27:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1574864829; bh=qMMFG8dqY0l8L0ce4PIm6BrXKZMNDbyj+6sb4B3gno4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HvLAIsnK+cZVb2OPz+mZ1JoadquhrQYQAj5q8L0fzFLmCHQ2kuCROiiJRdCYcBBf8 mS7pNa9xdkckwqgRT7bWXA0aGp/1qlaAvxEn21QAPhbTDa3eHcrtExQ3md57V/cVtO Nybi37emJdB30cXPNFN1WA8EZbSP8fv/zW62YV9g=
Date: Wed, 27 Nov 2019 06:27:09 -0800
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZGI7IPQLLKYTR56WV35O5D3EVBNHHB7DNHSM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3276/559109365@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3276@github.com>
References: <quicwg/base-drafts/issues/3276@github.com>
Subject: Re: [quicwg/base-drafts] Ambiguous wording about error codes in HTTP/3 (#3276)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dde87bda9825_6fc53fe3984cd9643958c2"; 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/-nVMEWxAIdIjKTLxAqJoIqPLtoQ>
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, 27 Nov 2019 14:27:12 -0000

I don't think the suggested change is aligned with the intent but there might be something we can do to improve the readability. 

"error codes" are used for normal operations when it comes to closing streams. So one interpretation of the current text is to say that if you get an unknown error code in a RESET_STREAM, don't treat it as any kind of error.  The suggested text "further error" confuses this interpretation.

-- 
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/3276#issuecomment-559109365

v2.23.0 | Report a Bug | By Email