Re: [quicwg/base-drafts] QPACK: Encode Largest Reference modulo MaxEntries (#1763)

Bence Béky <notifications@github.com> Fri, 07 December 2018 16:26 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 C4510130E66 for <quic-issues@ietfa.amsl.com>; Fri, 7 Dec 2018 08:26:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.481
X-Spam-Level:
X-Spam-Status: No, score=-8.481 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.979, 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 yFgLTwjbfYcN for <quic-issues@ietfa.amsl.com>; Fri, 7 Dec 2018 08:26:26 -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 24999130E63 for <quic-issues@ietf.org>; Fri, 7 Dec 2018 08:26:26 -0800 (PST)
Date: Fri, 07 Dec 2018 08:26:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544199985; bh=mhRwvWdK31J+lF4bCbpfvgGQKZGJGFV9k89tPqJHaVk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tck0LycR+MDnf7kc9gPSb5/7uYHbYGJ85RmU655PkD19/sBp+wyqDRaYJckZQzL2q KCp1gg+QdnEvWQAWWKuumVzhCgq14EGGy+EEVXGM9HBD3HuTCLhx1MppMsSowMHZLh irgLR5QwW96w6K47eIbMo37lMCNdG7/busn9AOis=
From: Bence Béky <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8fc92db38c4e666240dfb3ef669dc6ea9f6bdeee92cf000000011822613192a169ce1586350b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1763/c445286014@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1763@github.com>
References: <quicwg/base-drafts/pull/1763@github.com>
Subject: Re: [quicwg/base-drafts] QPACK: Encode Largest Reference modulo MaxEntries (#1763)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c0a9f3122fa0_161a3fad5ccd45bc2833d0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: bencebeky
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/lJhMakvh5l5FitMd41b1eG4KPmc>
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, 07 Dec 2018 16:26:28 -0000

Sorry for asking the obvious but what happens if a Dynamic Table Size Update on the encoder stream is racing with a Header Data Prefix on a request stream?  How will the decoder know whether to use the maximum dynamic table size before or after the Dynamic Table Size Update for calculating MaxEntries to decode LargestReference?  Or is SETTINGS_HEADER_TABLE_SIZE used instead for calculating MaxEntries?

-- 
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/pull/1763#issuecomment-445286014