IETF Logo Mail Archive

Re: [quicwg/base-drafts] DATA frame encoding is inefficient for long dynamically generated bodies (#1885)

MikkelFJ <notifications@github.com> Mon, 22 October 2018 16:25 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 882801277D2 for <quic-issues@ietfa.amsl.com>; Mon, 22 Oct 2018 09:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.47
X-Spam-Level:
X-Spam-Status: No, score=-3.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 kHHgao1mSmuG for <quic-issues@ietfa.amsl.com>; Mon, 22 Oct 2018 09:25:04 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CD9F130EE5 for <quic-issues@ietf.org>; Mon, 22 Oct 2018 09:25:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=zIZVdR4lcaChgPtxQ9w6VUjQrms=; b=pQgA4OcalQynJqSr 6TF1epgumFASiWdOUwDir9PoUPLUz1ErLEucfFMO5InayEqOpXuEpPwWC9A1zjw/ eDfxZxdExKYP1KOEX2pLQDsBpA+c9GiQov+yc4ep7RlLRFIe2+jc16+S/ymsNTuY Eoh17ab1TItUyqUOU0uAKSjc9gk=
Received: by filter0696p1las1.sendgrid.net with SMTP id filter0696p1las1-9653-5BCDF9DE-B 2018-10-22 16:25:02.189525798 +0000 UTC m=+227445.550440700
Received: from github-lowworker-1ffe0ab.cp1-iad.github.net (unknown [192.30.252.38]) by ismtpd0013p1iad2.sendgrid.net (SG) with ESMTP id ne8GGc2vQh-QazIznvokbQ for <quic-issues@ietf.org>; Mon, 22 Oct 2018 16:25:02.086 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-1ffe0ab.cp1-iad.github.net (Postfix) with ESMTP id 14374381296 for <quic-issues@ietf.org>; Mon, 22 Oct 2018 09:25:02 -0700 (PDT)
Date: Mon, 22 Oct 2018 16:25:03 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe40cc3a9423f54c8290261a52e52f3b8c92039a292cf0000000117e5bbdd92a169ce16286866@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1885/431886267@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1885@github.com>
References: <quicwg/base-drafts/issues/1885@github.com>
Subject: Re: [quicwg/base-drafts] DATA frame encoding is inefficient for long dynamically generated bodies (#1885)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bcdf9deafd2_38fe3fad96ad45c077741d2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3DQLOz9s7yAtfaRIVtlK3fsKuRCTmcTZU91I /iS8aivDhR+5eZWNU19yTfkABxd2aRc5GfUUac2IwqBi0Z8u8qMTAowDfIdkUiDd5dRBCeRXmEJmTv mv2ODNvx71cou7Gq0gy8LZKft7WUrgx2Aj9j+Ih1qY6LpBax6bBFpXT+pw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/v701zOWXlZ92yg6gwRG473fzxos>
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, 22 Oct 2018 16:25:07 -0000

Are there any technical issues with placing DATA frames in its own stream, like ordering dependencie or undue receiver complexity? Otherwise it seems like a cleaner solution than hacking a 0 length for some frames. I agree with @kazuho that magic 0 for all frames just complicates frame handling in general.

-- 
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/1885#issuecomment-431886267

v2.23.0 | Report a Bug | By Email