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:23 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 95D03130E99 for <quic-issues@ietfa.amsl.com>; Mon, 22 Oct 2018 09:23:07 -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 1KAZIoBJgF3j for <quic-issues@ietfa.amsl.com>; Mon, 22 Oct 2018 09:23:05 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 D963D130E30 for <quic-issues@ietf.org>; Mon, 22 Oct 2018 09:20:32 -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=8TOw+Xul4xDIKrsinrRovWtjofI=; b=BGD+2YnOgMAHolwX OJdRBYwfoZCHtpKgNRQlPrq0H8/YYTpXHVwvwd1eSyiQNKGISc3UkynITGz89dIn cpKbFsN0z1m8JS1ZrHBJfQypYar5BEuJ8lgl0K7z/t71djJeKXfuJkJZQCYF9FbG n+bfEoLQxTymrNUFtEVFBnL1gbs=
Received: by filter0704p1las1.sendgrid.net with SMTP id filter0704p1las1-13325-5BCDF8CD-2B 2018-10-22 16:20:29.633710323 +0000 UTC m=+318147.060003613
Received: from github-lowworker-05ceafd.cp1-iad.github.net (unknown [192.30.252.40]) by ismtpd0013p1iad2.sendgrid.net (SG) with ESMTP id CcBK6WBES32VjkSASprKFg for <quic-issues@ietf.org>; Mon, 22 Oct 2018 16:20:29.545 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-05ceafd.cp1-iad.github.net (Postfix) with ESMTP id 85409460103 for <quic-issues@ietf.org>; Mon, 22 Oct 2018 09:20:29 -0700 (PDT)
Date: Mon, 22 Oct 2018 16:20:29 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abdc7e6808ae978de6bdc6d84b0013633bdfead70892cf0000000117e5bacd92a169ce16286866@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/431884806@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_5bcdf8cd751ad_4a533fa4718d45b41269316"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2XE6Fr+vtic7oNtZC/+DdPE9dItRqPFXZuHR 8ihmpoA9rSNJgXhs4IBM9gTtaLxxgibNdRpVvfPCxEsR/UGgnZWUucNRkLzd4mmixw5ZzPvlNgxFZX drZPO0c2k1oCljN4ClRQ+aDaAYh53d4viAhNQf2CjGYHoNBxAsVt3P1e3ygLF6ypy9OufgR+4Xbs6E Q=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/O65yTlyi9ay_pryWn6yLfGPHm2M>
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:23:14 -0000

Certainly taking the minimum of stream and frame seems like an invitation to problems.
Predeclaring trailers is inconvenient if you don't know that ahead of time. Separate stream, v2?

I (kind of) like what @kazuho wrote about blocks/boundaries within a stream in v2, but this is a large topic that digs into partial reliability. I'm not sure boundaries on their own are that useful because a flag in a stream header still require a stream frame while an application embedding its own framing can be more dense, depending on the frame size vs. packet size. I did make such a proposal a boundary proposal a long time ago (out of scope for v1).

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

v2.23.0 | Report a Bug | By Email