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

Lucas Pardue <> Sat, 09 March 2019 09:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 19A0B12426E for <>; Sat, 9 Mar 2019 01:41:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Status: No, score=-6.597 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id m5noy9OF6dVX for <>; Sat, 9 Mar 2019 01:41:53 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9FE9B1200ED for <>; Sat, 9 Mar 2019 01:41:53 -0800 (PST)
Date: Sat, 09 Mar 2019 01:41:52 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1552124512; bh=NZ5WahUcLij0JOxMD+85bWr6EGhkKcc7fGPvvPepGrc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OgD0sVd+9PM1KGmzJwERHtFJLzUkkwOf/vGfrRg9c9F+al/tpy22SZjStYpt3Y6GK tlnkA6yjzUfr/6rATJwJGhmaQHY4D7ilTP964VPOt0l+l3/IiO6fOWs3SGWtJpiZoz V40/5c3VpH8yVCvjXSMofziOXTWvRV/86aMEZaJk=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2511/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
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_5c838a6099fe9_71643fe5ba8d45c01763783"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 09 Mar 2019 09:41:55 -0000

I'm ok with such changes but wonder if we should also add some further prose to the document that:

* highlights HTTP/3 difference to HTTP/2 i.e. "all errors are always connection errors"
* captures some of the guidance mentioned elsewhere like "identifying the stream on which a problem frame was delivered may be useful in error analysis, endpoints might want to include the stream ID in the reason phrase"

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: