IETF Logo Mail Archive

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

Robert Wilton <notifications@github.com> Tue, 02 February 2021 09:09 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 3A07B3A18A3 for <quic-issues@ietfa.amsl.com>; Tue, 2 Feb 2021 01:09:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.258
X-Spam-Level:
X-Spam-Status: No, score=-2.258 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_16=1.092, 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 2NcecgafYXYt for <quic-issues@ietfa.amsl.com>; Tue, 2 Feb 2021 01:09:27 -0800 (PST)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FC223A18A6 for <quic-issues@ietf.org>; Tue, 2 Feb 2021 01:09:27 -0800 (PST)
Received: from github.com (hubbernetes-node-bbd44e1.va3-iad.github.net [10.48.118.78]) by smtp.github.com (Postfix) with ESMTPA id DD0CFE0074 for <quic-issues@ietf.org>; Tue, 2 Feb 2021 01:09:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1612256966; bh=IuFb3OUDPfocV0HWs8rC1Xf0/2gDtFrc3E1JSC2yeIs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1/iD+EE/gueMIFoXWjxMGj1lJDMoLvNt/jQ81boAMzjoQhM7+sW0TTiVf7LBZgPke CAti96QK5ykruPiHPCbLU9n9zP2c/je9zZfWWYWqDb0H/6dRYXC1+vp//iy8P7b+Gk BA1q005AK7O32/dGQ0uFMy7RXmSI6WtLVVOJN52M=
Date: Tue, 02 Feb 2021 01:09:26 -0800
From: Robert Wilton <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4WRQV4JVOIPMYFTR56ET34NEVBNHHC6KACPU@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/771484898@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_601916c6da51c_591a049789"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: rgwilton
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/kNMwA3wfG7DDUDajudZt5mvCizg>
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, 02 Feb 2021 09:09:29 -0000

If HTTP/3 already sets practical limits on what the QPACK needs to accept then it is fine to say that.

Or to put this another way, the HTTP/3 implementations presumably are setting limits (or perhaps they are just relying on language/decoder limits).  How are they deciding what those limits should be?  How can they be sure that they will interoperate with all senders?

I'm not an HTTP expert, so perhaps I'm missing something obvious here.

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

v2.23.0 | Report a Bug | By Email