Re: [quicwg/base-drafts] Forwarding upstream error mid-body to downstream (#3300)

Kazuho Oku <> Tue, 17 December 2019 04:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1AD301200B6 for <>; Mon, 16 Dec 2019 20:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_HELO_NONE=0.001, 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 BzJpiae6WzeQ for <>; Mon, 16 Dec 2019 20:17:01 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5C0E81200A1 for <>; Mon, 16 Dec 2019 20:17:01 -0800 (PST)
Date: Mon, 16 Dec 2019 20:17:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1576556220; bh=FmrQuowKS3CPlU3MRFksVoT9DFBs1CSxSivh8xvF+sI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=P0EJ27H5syxTMiHTOcdJuSdvczbrJ75WVYSGkSW5mC+F+ouAKQQ/oHdMxzoLx3XIX bBm4lvlu2fi9gvevTsZgR4YMzSBVOh3x7BpVU68CIUvcTn5VgUCuvddEvza/tnGZat TFYTNA43y7bPUH8CSZ6kQr0S9mshE5hwxuvtf+nI=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3300/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Forwarding upstream error mid-body to downstream (#3300)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5df856bc701e2_38d73fcd91ecd96817468d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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: Tue, 17 Dec 2019 04:17:03 -0000

PS. Or, if we are to consider H3 tunnels that does not do reframing as something within the scope of the specification, I think we need to have something like #3303.

Consider the case of a H3-H3 intermediary that parses the request, and binds HTTP requests to different origins, transmitting the *response* as-is without dealing with frames. Such a tunnel would work as expected, assuming that QPACK dynamic table is not used.

In this type of design, a stream-level error (i.e. abrupt termination of a stream) does not indicate a connection-level error. Therefore, we need to state that.

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