Re: [quicwg/base-drafts] Separate HTTP/3 stream errors from connection errors. (#2911)
Lucas Pardue <notifications@github.com> Sun, 21 July 2019 18:31 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 14A09120132 for <quic-issues@ietfa.amsl.com>; Sun, 21 Jul 2019 11:31:02 -0700 (PDT)
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 Os99j6CfVP7p for <quic-issues@ietfa.amsl.com>; Sun, 21 Jul 2019 11:31:00 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E7F8120161 for <quic-issues@ietf.org>; Sun, 21 Jul 2019 11:31:00 -0700 (PDT)
Date: Sun, 21 Jul 2019 11:30:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1563733859; bh=t2vApK8Ab44J8FISBZWTsuLVvhOoYxiVxRHsIRww6EA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1q997OovSxxMY+XZk7ivC19rMRqBV5hdspF9+NdRLOWA6YXGxDb2QR+O2wJUg1mcs yxhDEV2D4XHj53pgEg40WgRWE4tU4oxcA0+R13FKBSvTlNoZXUQ4FXSycAF5DQgV/J JFyOagESMuZZEVNh8KIeDY6DVdutw6Ou4oLmXJ0A=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5VCW33JUPJPLMOX3N3IHQ6HEVBNHHBYDQKAQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2911/513576904@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2911@github.com>
References: <quicwg/base-drafts/issues/2911@github.com>
Subject: Re: [quicwg/base-drafts] Separate HTTP/3 stream errors from connection errors. (#2911)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d34af639a9ec_17f73f8cfd0cd9646501f"; 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/zZWhzve-zORUPQrdy9pXNSfByCE>
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: Sun, 21 Jul 2019 18:31:02 -0000
I think what we're missing is that the distinction between connection error and stream "error" is explicitly present in the QUIC transport, by the use of different frames. It seems we are discarding that information and then trying to back-infer it from an error code. I'd argue that this is the wrong approach because in practice, there is a good chance the remote peer's approach to selecting error codes is different. -- 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/2911#issuecomment-513576904
- [quicwg/base-drafts] Separate HTTP/3 stream error… Daan De Meyer
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… Lucas Pardue
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… Lucas Pardue
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… Kazuho Oku
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… Lucas Pardue
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… Daan De Meyer
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… Lucas Pardue
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… Lucas Pardue
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… Daan De Meyer
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… ianswett
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… Lucas Pardue
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… Mike Bishop
- Re: [quicwg/base-drafts] Separate HTTP/3 stream e… Mike Bishop