Re: [quicwg/base-drafts] Disallow changes of table size after 0-RTT (#2276)

afrind <notifications@github.com> Fri, 11 January 2019 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 A81FD127133 for <quic-issues@ietfa.amsl.com>; Fri, 11 Jan 2019 09:28:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.552
X-Spam-Level:
X-Spam-Status: No, score=-12.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 JndBhDlVH2Pb for <quic-issues@ietfa.amsl.com>; Fri, 11 Jan 2019 09:28:28 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F590126CB6 for <quic-issues@ietf.org>; Fri, 11 Jan 2019 09:28:28 -0800 (PST)
Date: Fri, 11 Jan 2019 09:28:27 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547227707; bh=6begVWcJ/4bQv5dAlcubCVH0pTIiOnNHCvsT9HFGrSQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=p2OyHbUtyGz7/+ovejyWLMQVsoM7fkpLA5C/Bh4rljSnv7WGJpxYH0bvgTtwPoMyN d3qCb6XG2JkuM7Bd27aWp0DQ8ktqeatmuSNhnVgsQh7uCvhiSzGAp+IY++hkz/gkDY 7cgqj0lj6m/VMMTqU5c0WQrtPznRvOgu+4MNIetc=
From: afrind <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abfde50ae20f704222c2786a099f3b2b134c58b4b292cf000000011850943b92a169ce1789f586@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2276/453593927@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2276@github.com>
References: <quicwg/base-drafts/issues/2276@github.com>
Subject: Re: [quicwg/base-drafts] Disallow changes of table size after 0-RTT (#2276)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c38d23b7709d_16f83fd7b1ad45bc446756"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: afrind
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/Tzmzt_egjxkGkWgHZ4q2gjKoacg>
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, 11 Jan 2019 17:28:30 -0000

I agree we should not allow SETTINGS to carry a different value for the maximum dynamic table size than the remembered value of 0-RTT.  The one exception that seems workable is if the remembered value is 0 (no dynamic table), the server could send a non-zero value in SETTINGS - this is the same case as 1-RTT, since the default is 0.

True, it means the server must reject 0-RTT when it changes the size of the dynamic table it wants to support, but this is a very rare server side change.

I find the idea of putting a latch in the QPACK code that disallows eviction before SETTINGS kind of strange, though the code to do so doesn't seem complicated.

-- 
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/2276#issuecomment-453593927