Re: [quicwg/base-drafts] Allow extra data after self-terminating h3 frames (#2291)

ianswett <notifications@github.com> Mon, 07 January 2019 16:02 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 A92E6130F1A for <quic-issues@ietfa.amsl.com>; Mon, 7 Jan 2019 08:02:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.447
X-Spam-Level:
X-Spam-Status: No, score=-6.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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_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 qh-N1cCm_ctd for <quic-issues@ietfa.amsl.com>; Mon, 7 Jan 2019 08:02:06 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28FC6130F29 for <quic-issues@ietf.org>; Mon, 7 Jan 2019 08:02:05 -0800 (PST)
Date: Mon, 07 Jan 2019 08:02:04 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546876924; bh=Pn+jv2Fd2/BPuFmHkv3maaR5zHsVkIIIV8SZS14idfQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hc3gGxnz6jTCPkhvtWX6qWzLFK7FtKc2PWxbqwqy9/fI/+rOvPmKldeZBKpLUt7dK Rump5pUR62JqwMIaNWlVp2kAgsnBeot1eIW4rT+Rh3O9wc8Wk2425CrQcNb28SA2e/ 7hxeEu+4t28YCltfysilOt6OO7gyYnHu1whKq2VM=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abab5f0fc3a3e4012dc786125fc62216b4a9b6d22f92cf00000001184b39fc92a169ce1797273c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2291/451983730@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2291@github.com>
References: <quicwg/base-drafts/issues/2291@github.com>
Subject: Re: [quicwg/base-drafts] Allow extra data after self-terminating h3 frames (#2291)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c3377fcfae7_32e03fcc3fad45bc495b0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/1wVfWQ4bMmkri2fiRK5NCkVLS60>
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: Mon, 07 Jan 2019 16:02:14 -0000

After thinking about this more, I'd prefer to change to TV for cases when forcing implementations to supply a length is adding complexity.  That fixes the same core issue: "What to do if the specified length doesn't match the actual length" in a different way.

-- 
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/issues/2291#issuecomment-451983730