IETF Logo Mail Archive

Re: [quicwg/base-drafts] Some correctness issues in the HTTP/3 drafts are stream errors, not connection errors (#2511)

Daan De Meyer <notifications@github.com> Wed, 24 April 2019 11:40 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 307831202D2 for <quic-issues@ietfa.amsl.com>; Wed, 24 Apr 2019 04:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Level:
X-Spam-Status: No, score=-8.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_HI=-5, 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 tla7EnuWLRaq for <quic-issues@ietfa.amsl.com>; Wed, 24 Apr 2019 04:40:21 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B82C912006B for <quic-issues@ietf.org>; Wed, 24 Apr 2019 04:40:21 -0700 (PDT)
Date: Wed, 24 Apr 2019 04:40:20 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1556106020; bh=fWWc8/+DNsj/QPckmE+2CfC3CFNUTQym1KOrSrApyVw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TvLyHqlZpkYyONsyPsvTBjfq2R35sAjNJnkn/OxgW9KPSeR76cDEkB/Q2ed5BOV2V 9rGrcupt8zks/ugMW25iKq45HjrawGO/m5E8FwArHu9Wskipg95q+jiGJs6s53mhMs 26dk84rEUyLX/LsQmuNzRQZawZ31m6YzLFubwXVU=
From: Daan De Meyer <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5KPUREBS2P724E5UV2ZV62JEVBNHHBR6RTNQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2511/486187238@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2511@github.com>
References: <quicwg/base-drafts/issues/2511@github.com>
Subject: Re: [quicwg/base-drafts] Some correctness issues in the HTTP/3 drafts are stream errors, not connection errors (#2511)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cc04b248d444_2a7d3f95f1ccd9603872e2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DaanDeMeyer
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/RsLnA8hS58G-YXkDBDCuB8ypmpk>
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, 24 Apr 2019 11:40:23 -0000

>From an implementation point of view, being able to classify an error as either a connection error or a stream error would simplify error reporting since we'd be able to classify an error as either a connection error or a stream error without having to include extra information with the error.

As an example, at the moment, when returning a `HTTP_MALFORMED_FRAME` error from a function, I have to include whether the `HTTP_MALFORMED_FRAME` is a stream error or a connection error since it can be both. If every error could be classified as either a connection error or a stream error, I wouldn't have to include this extra information since a `HTTP_MALFORMED_FRAME` error would always be a connection error.

-- 
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/2511#issuecomment-486187238

v2.23.0 | Report a Bug | By Email