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

Lucas Pardue <notifications@github.com> Thu, 18 October 2018 23:20 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 76E06130E22 for <quic-issues@ietfa.amsl.com>; Thu, 18 Oct 2018 16:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.064
X-Spam-Level:
X-Spam-Status: No, score=-3.064 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.064, 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 735r2aUz73kE for <quic-issues@ietfa.amsl.com>; Thu, 18 Oct 2018 16:20:07 -0700 (PDT)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 BE3DC130E00 for <quic-issues@ietf.org>; Thu, 18 Oct 2018 16:20:06 -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=AAoLhb/rfFZ/S2Ds+B6+Wqen29A=; b=kxXhLpMqEkXcgeX2 GeMTNVKUXHT13ojnYoa5Q3bAga+thSuFqvLOYMMcOvXPzx5Fd0t1oMHEATNr4rl4 NZlt/it2jQsDoqhnmpQzp7kh82mh13ityH59lKulhcL0j1XDUqXE+aHyuQ48i++i OsNd1TrMsPNJu5HBeSpKOWz5Zyw=
Received: by filter0879p1las1.sendgrid.net with SMTP id filter0879p1las1-7113-5BC91525-7 2018-10-18 23:20:05.268466561 +0000 UTC m=+828.225853350
Received: from github-lowworker-1ffe0ab.cp1-iad.github.net (unknown [192.30.252.38]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id yLoZA67KTCeZycTcfgPzEw for <quic-issues@ietf.org>; Thu, 18 Oct 2018 23:20:05.153 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-1ffe0ab.cp1-iad.github.net (Postfix) with ESMTP id 22C873812E6 for <quic-issues@ietf.org>; Thu, 18 Oct 2018 16:20:05 -0700 (PDT)
Date: Thu, 18 Oct 2018 23:20:05 +0000
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1a706df51b077afffde9c4d06fce75a199f2a0af92cf0000000117e0d72592a169ce16286866@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/431195623@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_5bc915251e79b_5efc3ff015ed45b4177675"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3yDWA56+PwW+H306SI2miwqcw7+d3O9yduLl kTFbw1Fa0bAxJEEs8i3DZEQZDW0+k4ROa0fy+poMrOHUJi0HSIaSycBtRhI3v20wbCCCkcahUuJoi8 rIs5dsCiqayo45Bv0jjElCnxwkqc8UE0nlK9j0GaMZ+0lvsha+QGHLVHpDCOvdCJnRm44BNN6qU8eW Q=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ogRKRq0HFNWUSIdmoMOj_ITVCrI>
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: Thu, 18 Oct 2018 23:20:09 -0000

I'm sympathetic to the issue but not sure it needs fixing in v1. What is worse case overhead?

The proposal seems similar to some aspect of Roberto and Jeff's ideas. A slightly different type of stream could carry just a response, and permit simple random access of bytes across the entire stream.

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