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

Lucas Pardue <notifications@github.com> Mon, 07 January 2019 16:13 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 464F8130EF2 for <quic-issues@ietfa.amsl.com>; Mon, 7 Jan 2019 08:13:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
X-Spam-Level:
X-Spam-Status: No, score=-6.661 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_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: 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 sH7Z40ZO0njx for <quic-issues@ietfa.amsl.com>; Mon, 7 Jan 2019 08:13:09 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9732D130E9A for <quic-issues@ietf.org>; Mon, 7 Jan 2019 08:13:09 -0800 (PST)
Date: Mon, 07 Jan 2019 08:13:08 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546877588; bh=pbZMimvZo2qBMTdkhpX/SMkkgoFSg4mmUbs+43Dgd3k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NQejx7+wXvB+D6yU0r+e94ZMRje4Ogh6wgGd5Q6Xz8j+dCIzZ2CQuuYP/Hi0Ha2ok foar/ObaYrklGj7jcRbZfjjxi+4jWH/SvdhvGF7PJ2pQuCyjb/jK2fRB0A/8Zd000T eNG+8HcBUeCRKlxleSgnewsWYlwICfVnl7hckNsc=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6471fd8afc0c7396a04a1589b9ab140e2a24e32392cf00000001184b3c9492a169ce1797273c@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/451987473@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_5c337a9453f39_46923fbf43cd45b416468e"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/lZLHB2CSTRYwZApr6-ltjtJ304Q>
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:13:11 -0000

I don't understand how that works though, how does the receiver parse the frame if the length is unknown? 

For the DATA frame, in #2098 the exception was made for len=0 because we could use the EOS signal. 

-- 
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-451987473