IETF Logo Mail Archive

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

Lucas Pardue <notifications@github.com> Fri, 19 October 2018 19:33 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 D4CA7130DD1 for <quic-issues@ietfa.amsl.com>; Fri, 19 Oct 2018 12:33:37 -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 e09PtQH_-9vE for <quic-issues@ietfa.amsl.com>; Fri, 19 Oct 2018 12:33:36 -0700 (PDT)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 0556E130F88 for <quic-issues@ietf.org>; Fri, 19 Oct 2018 12:33:35 -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=hTEHczK9azrqH/9GXgZDJq+j45o=; b=KdV2pH4f/76uYTNT e5bJ72VgS0AW7EhG5dGANICHlAq7Ss6fvdyguWUhHZn2xNQ9sekeKzBxHc+dIWSd lRk7iCqsROHBkbjsd0pXo0uU/I0gTyZ27Euq1YK2p7BYSuHhH0jFtXxWMMhjvTzp 9Kkffs/4ZgZyzDtiEQ9p8+OaYSk=
Received: by filter1624p1mdw1.sendgrid.net with SMTP id filter1624p1mdw1-18668-5BCA318F-5 2018-10-19 19:33:35.16085089 +0000 UTC m=+76459.147997672
Received: from github-lowworker-56a5eb2.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0023p1iad2.sendgrid.net (SG) with ESMTP id XBTzgEIZR0mUy2i6xLiQKQ for <quic-issues@ietf.org>; Fri, 19 Oct 2018 19:33:35.094 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-56a5eb2.cp1-iad.github.net (Postfix) with ESMTP id 1C9F5C0FAB for <quic-issues@ietf.org>; Fri, 19 Oct 2018 12:33:35 -0700 (PDT)
Date: Fri, 19 Oct 2018 19:33:35 +0000
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab36db087783ca2512b7709b261caf648f62e71f0592cf0000000117e1f38f92a169ce16286866@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/431474652@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_5bca318f169d5_b833f9b9d4d45b8194cb"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3DRSDAsTgj0XcSawi1amydaPogCglnn8zfnl QvlKLDZGqfWeV1Qo8x2BwM/TcPEW6M0gRoltbbZN+glcZFzXSmgNkySAB6is7Kkgs6OjYcpquLuhcv VkzVbXVAabfwjROYyUOc/Etkg/QS+VBrHfJZX1V43Mp+7TbnxfxkPvW6VXrnEvJh+GobRTaOsL0SXW 0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/MJ_gzY6hA7LDC5M_MRJr1oZIAk0>
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: Fri, 19 Oct 2018 19:33:38 -0000

gQUIC also has a different way of achieving HTTP header transfer, which means it had HoL blocking :)

Things are just different in HQ, it's a chance do you wind some of the compromises that QUIC made. As an implementor I'd like to have an environment that creates new opportunity, just as much as performance.

The direction of conversation is positive, and I agree performance isn't just shaving bandwidth. Mike's idea creates a general approach that I like.

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

v2.46.0 | Report a Bug | By Email | System Status