Re: [quicwg/base-drafts] Auth48 fixes for QPACK (PR #4986)
Mike Bishop <notifications@github.com> Tue, 26 April 2022 18:12 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 72835C1D24C5
for <quic-issues@ietfa.amsl.com>; Tue, 26 Apr 2022 11:12:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.26
X-Spam-Level:
X-Spam-Status: No, score=-2.26 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.575, DKIM_SIGNED=0.1,
DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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 ([50.223.129.194])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 3AVYRHakeJFm for <quic-issues@ietfa.amsl.com>;
Tue, 26 Apr 2022 11:12:10 -0700 (PDT)
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 4E3C7C1D2DB2
for <quic-issues@ietf.org>; Tue, 26 Apr 2022 11:11:47 -0700 (PDT)
Received: from github-lowworker-65e4a37.va3-iad.github.net
(github-lowworker-65e4a37.va3-iad.github.net [10.48.119.82])
by smtp.github.com (Postfix) with ESMTP id 9E5ED9034F8
for <quic-issues@ietf.org>; Tue, 26 Apr 2022 11:11:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1650996706;
bh=RDZDmMHHs24sbiPOsnFJFS4HXNC/kzXivYaTeSJhfvc=;
h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=lnxQvSmd5F3evPp9pD+5QqAVUEv1qDgqwD41j0LOPDgoSkUIEDnFltq9G5CeGXlSi
+SYa1V7Q9FTmk/w/K2+48oh3b7rUFv0dqJ0NhowJRgM5nc361F1wY7re1AIkuOB0zw
edEFp+VWn9kZD5HaNlXNWm4bZ4tddjS8hHsV8BCU=
Date: Tue, 26 Apr 2022 11:11:46 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts
<reply+AFTOJK4QKVUM56JEHMIWOFOAOVUGFEVBNHHEQ73GEU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/4986/review/953814265@github.com>
In-Reply-To: <quicwg/base-drafts/pull/4986@github.com>
References: <quicwg/base-drafts/pull/4986@github.com>
Subject: Re: [quicwg/base-drafts] Auth48 fixes for QPACK (PR #4986)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_626835e28f735_685dd41c1852c2";
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/TF16CFZHJUJL9nI0mmEK3RQ1NI4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.34
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 Apr 2022 18:12:11 -0000
@MikeBishop commented on this pull request. > +For clients not using 0-RTT data (whether 0-RTT is not attempted or is rejected) +and for all HTTP/3 servers, the maximum table capacity is 0 until the encoder +processes a SETTINGS frame with a non-zero value of +SETTINGS_QPACK_MAX_TABLE_CAPACITY. By parallel with the previous paragraph's first sentence. > +<aside><t> +Note: Padding schemes only provide limited protection against an attacker with +these capabilities, potentially only forcing an increased number of guesses to +learn the length associated with a given guess. Padding schemes also work +directly against compression by increasing the number of bits that are +transmitted. +</t></aside> I couldn't find a kramdown way to do this, so I just inlined the XML. -- Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/pull/4986#pullrequestreview-953814265 You are receiving this because you are subscribed to this thread. Message ID: <quicwg/base-drafts/pull/4986/review/953814265@github.com>