Re: [quicwg/base-drafts] Forwarding status of errors on streams (#3303)

Martin Thomson <notifications@github.com> Thu, 02 January 2020 03:18 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 32F92120046 for <quic-issues@ietfa.amsl.com>; Wed, 1 Jan 2020 19:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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_24=1.618, 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 FWliy6mGleO7 for <quic-issues@ietfa.amsl.com>; Wed, 1 Jan 2020 19:18:09 -0800 (PST)
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 DFFB812003E for <quic-issues@ietf.org>; Wed, 1 Jan 2020 19:18:08 -0800 (PST)
Received: from github-lowworker-9bcb4a1.ac4-iad.github.net (github-lowworker-9bcb4a1.ac4-iad.github.net [10.52.25.84]) by smtp.github.com (Postfix) with ESMTP id 359488C04F6 for <quic-issues@ietf.org>; Wed, 1 Jan 2020 19:18:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1577935088; bh=BNKyWTzZSxk4tLTZWhrwNIgwWqiIkd58X/y7Ckm7qxM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xMpb9gwLozMnlhykb9c5iZIRtuVHll6M41/UEiHT02DU1K0WNRxAmpaRn9IYwTTJv NtBl5rWnVHxgeqT1e+rG12KEoogP+q+GULvYHUuf1QcvqSSLLk8QPoSsqV5cUH1wlV pn86JKztD71ggyc65Q+6fMAf+0ERkpjbquDnNHGs=
Date: Wed, 01 Jan 2020 19:18:08 -0800
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6CBTFKWGPNFL4OWPF4DKJXBEVBNHHCAHIHBM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3303/c570109752@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3303@github.com>
References: <quicwg/base-drafts/pull/3303@github.com>
Subject: Re: [quicwg/base-drafts] Forwarding status of errors on streams (#3303)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e0d60f026134_1c473f9a74ccd960822ab"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/ChH8dKnKAuSXrOLOJxj_5g4XUSU>
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: Thu, 02 Jan 2020 03:18:10 -0000

I'm not suggesting that tunnels are forced to check what they forward, but that they assume responsibility for every byte they produce, forwarded or not.

An intermediary can forwards in the way you describe in that case.  But if the source produces junk, the intermediary can wear the consequences.  That doesn't mean that you have to check everything you get, but that's a call you would have to take on yourself.

The current text passes this cost on to clients in a way that will make it much harder to enforce protocol correctness at clients.  That's not healthy.

-- 
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/pull/3303#issuecomment-570109752