IETF Logo Mail Archive

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

Lucas Pardue <notifications@github.com> Mon, 22 October 2018 17:28 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 C669B128CB7 for <quic-issues@ietfa.amsl.com>; Mon, 22 Oct 2018 10:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.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_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 2xBGuhbKqbmu for <quic-issues@ietfa.amsl.com>; Mon, 22 Oct 2018 10:28:14 -0700 (PDT)
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 C66E71252B7 for <quic-issues@ietf.org>; Mon, 22 Oct 2018 10:28:13 -0700 (PDT)
Date: Mon, 22 Oct 2018 10:28:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1540229292; bh=YlMf+Hgj8LD5gv/JAq7eHE8SRGafZMgF3aziriNWVsc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xxpIqyGKDo+BBeSN4LOMtpDMpPwLgZ/b3zJoBTvRFwFTmCVS5mXjSZu7hxl9LgPKR DnMEjqRHx/pxi8+0JSLz45XJ2JZUw+mOD7ag7nVncpOfGax/7bdaJw+cdDX/YsOk11 bdLA34WcNv+tgPItad/jSYkSZt1kFRVdZIy/b0hs=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab9787049bd35742bb6dc04548c238b6c6ed36521492cf0000000117e5caac92a169ce16286866@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/431905899@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_5bce08ac5f94f_30733fadf86d45bc16016d"; 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/0_CIjk9DYwZR9rX3q4-IPcPqgAI>
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 17:28:16 -0000

@MikeBishop perhaps, the current specs about Transfer Encoding and use of the "Trailer" header have caught me out in the past - I'm not aware of people using TE in H2 or HQ since chunked is forbidden.

As you hint toward, my point was to expose some information about the framing flow on streams explicitly on the stream, if they deviate from the standard behaviour. Such a signal could be generated by an origin and used by other endpoints to determine their behaviour. If this was at the mapping layer, it could avoid the need to invoke QPACK. Although, there may be legitimate reasons to decode QPACk anyway.

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

v2.23.0 | Report a Bug | By Email