Re: [quicwg/base-drafts] Forwarding upstream errors, and the implications (#3300)

Lucas Pardue <> Sat, 21 December 2019 10:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 49405120A3D for <>; Sat, 21 Dec 2019 02:23:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ce2G0XL6xG22 for <>; Sat, 21 Dec 2019 02:23:17 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 82142120A32 for <>; Sat, 21 Dec 2019 02:23:17 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id AA34A96025E for <>; Sat, 21 Dec 2019 02:23:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1576923796; bh=r4geJdEiZG60J3atXwyBm1qo5BgF8sBYFJ/5bBcMPnk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Vnv2A9POkXt99UkY15WxP+qs0VtVz+9Mrb7XH4cJCX5IZV535ZqI7WYw0+9mc5728 In+wXRay1lBeAro5nA+x2jOGorMBfjBhekDRgqEJY+EokKwIXTv6TjEQwv9hK7WQPC vIptzadfl/stRV/waIjLZuks7s946IoKmfo3K/Xk=
Date: Sat, 21 Dec 2019 02:23:16 -0800
From: Lucas Pardue <>
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 errors, and the implications (#3300)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dfdf2949aaa6_43753fc246ecd96413793bf"; 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, 21 Dec 2019 10:23:19 -0000

I am a yes for Q1. For Q2, if we wanted to pursue another frame type I don't (yet?) understand how it would work, won't the usefulness of the frame be subject to the size of DATA frames that people chose to use?

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