Re: [quicwg/base-drafts] Initial size of dynamic table (#1530)

Martin Thomson <notifications@github.com> Mon, 06 August 2018 10:54 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 310AA130E64 for <quic-issues@ietfa.amsl.com>; Mon, 6 Aug 2018 03:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 7Url4v6Kzxae for <quic-issues@ietfa.amsl.com>; Mon, 6 Aug 2018 03:54:19 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7818130DE2 for <quic-issues@ietf.org>; Mon, 6 Aug 2018 03:54:19 -0700 (PDT)
Date: Mon, 06 Aug 2018 03:54:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1533552858; bh=/2ujrbPoiNZzehkAZgVsY0qnoYh1q9D/K6RYcjJogqc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gbyNyZWMLDnbjjiOakVooPJKc95LqENGq8sdEjeprh8t+HdMJzeJJmK0zi4bx8yPF pKzFtEBPhtbaeHLZrksE6jjYNUEdPM/C/SJXC7GRyTusdfp1g2AEPTC7c99ZwnLqCd vbqDTjoDybT1d/hHoio+tXTCxUFohG8YwHtfyUqU=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab0e2be1e09e418e9a209cd3d3474ed16b7bbce11892cf00000001177feada92a169ce1431be2f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1530/410669757@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1530@github.com>
References: <quicwg/base-drafts/issues/1530@github.com>
Subject: Re: [quicwg/base-drafts] Initial size of dynamic table (#1530)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b6828daa5336_183f3ffb8dcd45c443164e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/QbTXI_MqVr2mwiuDh73xsdVxCaQ>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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, 06 Aug 2018 10:54:21 -0000

If the server has to remember what value was associated with 0-RTT, can't we agree on that?

That is, if the client attempts 0-RTT and the server accepts it, the value is set to the 0-RTT value.  We require that both peers remember the value from before, as we agreed in Montreal, so that's easy.

If 0-RTT is rejected, then it's a full handshake and they can all use the 1-RTT values.

In HPACK, we require the first header block that uses the dynamic table to include a table size update, because the table is assumed to start at 0 size (the default; also, settings might not be around when you send that header block).  In QPACK, you always know how much space there is - even if it might later increase - so why not use that?

-- 
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/1530#issuecomment-410669757