IETF Logo Mail Archive

Re: [quicwg/base-drafts] Robert Wilton's QPACK Comment 3 (#4802)

Mike Bishop <notifications@github.com> Tue, 26 January 2021 23:30 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 406453A0D78 for <quic-issues@ietfa.amsl.com>; Tue, 26 Jan 2021 15:30:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.804
X-Spam-Level:
X-Spam-Status: No, score=-1.804 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 sDHtZ7fcU07m for <quic-issues@ietfa.amsl.com>; Tue, 26 Jan 2021 15:30:16 -0800 (PST)
Received: from out-27.smtp.github.com (out-27.smtp.github.com [192.30.252.210]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECC193A0D70 for <quic-issues@ietf.org>; Tue, 26 Jan 2021 15:30:15 -0800 (PST)
Received: from github.com (hubbernetes-node-cb8f454.ash1-iad.github.net [10.56.105.60]) by smtp.github.com (Postfix) with ESMTPA id 14C59900D96 for <quic-issues@ietf.org>; Tue, 26 Jan 2021 15:30:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1611703815; bh=Nt2RUvJ9tkzUQj/EXJhME1AQSRvLpOERkdCbyyUXa7Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=htkoGnqis8C3fCZxCvw8WVuP8cjt924Eik9lyPDPL8q4U6K0+xqLF5wLWzCNEzaaS SSOv/obhk0VZJVLTN1tNf90cPNKDcB5bWAOzoP801NYQQCpLWW7ZykK6HxkdNLJV2Q sMr3HYexf+2LghfjHkjL62VQBBqNT/gHsM6QYxhQ=
Date: Tue, 26 Jan 2021 15:30:15 -0800
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3OR2TTZ6RIGBSIVCF6DSDQPEVBNHHC6KACPU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4802/767898012@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4802@github.com>
References: <quicwg/base-drafts/issues/4802@github.com>
Subject: Re: [quicwg/base-drafts] Robert Wilton's QPACK Comment 3 (#4802)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_6010a60711e0f_5a1a042211e1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/Lm_JHYkAx0ZFO99hwp2RqwPJsZs>
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: Tue, 26 Jan 2021 23:30:17 -0000

The text is really attempting to say that an implementation MUST NOT continue to process to infinity; bounds must exist for basic sanity.  What those bounds will be is implementation-dependent.  Saying that they're limited to the table size is only true on the encoder stream; request streams can have string literals greater than the table size (consider the degenerate case of zero).

HTTP limits could be pushed down to QPACK such that the library will refuse to decode a larger string than the implementation would accept; I don't think that's necessarily required though.

-- 
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/4802#issuecomment-767898012

v2.23.0 | Report a Bug | By Email