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

Mike Bishop <> Wed, 24 April 2019 17:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7BA551203E3 for <>; Wed, 24 Apr 2019 10:45:29 -0700 (PDT)
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 IdC21WV_HTrv for <>; Wed, 24 Apr 2019 10:45:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C012D120406 for <>; Wed, 24 Apr 2019 10:45:26 -0700 (PDT)
Date: Wed, 24 Apr 2019 10:45:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1556127925; bh=EagbOE1nJu7FRL2wuRLskhoZREMBj5UWnZCisQbENdQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gqoiB5nRqDIlEBhiuHgb47Z+1zenHWMuDxOllI33lHugh9p4CBaKP0eIieUVSzVuE MMKFfEvAScPGtAAKEzRRTKm3qX7/ye9MG9UPHq2pcP2jQXmbowy49A5nQuR7oO+KlC W5ncfYCQZ/Atkq/bT6+NKonjpL9J/Vgyb2sPE0cw=
From: Mike Bishop <>
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_5cc0a0b58eeae_52183fb6a2ecd96430325"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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: Wed, 24 Apr 2019 17:45:36 -0000

@DaanDeMeyer, in keeping with HTTP/2, an endpoint can always decide to treat a stream error as a connection error.  However, you're correct that some (and after the associated PR, most) errors will always be connection errors, and your implementation could choose to always treat the others as stream errors.

Just make sure there's no issue if someone else decides to treat it as a connection error.

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