[quicwg/base-drafts] Auth48: Servers and non-0-RTT clients (Issue #4980)
Mike Bishop <notifications@github.com> Mon, 04 April 2022 18:43 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 7262C3A11D4
for <quic-issues@ietfa.amsl.com>; Mon, 4 Apr 2022 11:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.482
X-Spam-Level:
X-Spam-Status: No, score=-1.482 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1,
DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1,
RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01,
T_SCC_BODY_TEXT_LINE=-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 ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id l_T3z8kkYt6C for <quic-issues@ietfa.amsl.com>;
Mon, 4 Apr 2022 11:43:03 -0700 (PDT)
Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 25B313A11C9
for <quic-issues@ietf.org>; Mon, 4 Apr 2022 11:42:55 -0700 (PDT)
Received: from github-lowworker-d93c4b6.va3-iad.github.net
(github-lowworker-d93c4b6.va3-iad.github.net [10.48.17.47])
by smtp.github.com (Postfix) with ESMTP id 4B2EC90210E
for <quic-issues@ietf.org>; Mon, 4 Apr 2022 11:42:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1649097773;
bh=aUuQGtFgRh4Vr/OCyvl6XMiHnd66DaHmuY8y0qXl8Ko=;
h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post:
List-Unsubscribe:From;
b=WeuQNRxUMM4aOpGOC/r3TxNJw35V8Yd4U6lvqEY2OQJBaSaQgZKbU0xXbj7Tk5r5w
JmJZueQ6ZclgWfVDcRz2G/SY+wAhgEN5veatt35DQfMaWA6jcls12/civrMji7sEud
CE8bn/C0Wp2oGnZrjP7m6oM4GXgNpjA+cm62xFlE=
Date: Mon, 04 Apr 2022 11:42:53 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts
<reply+AFTOJKYDBCL4SUPIZ735I4WALBXK3EVBNHHEODY7YU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4980@github.com>
Subject: [quicwg/base-drafts] Auth48: Servers and non-0-RTT clients (Issue
#4980)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_624b3c2d3bcfb_4ce8c6fc3716d";
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/lut47aHDrLbcMHhvoX7RaFEevgk>
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: Mon, 04 Apr 2022 18:43:06 -0000
This is a change in the RFC Editor diff that I don't think works; pulling out for separate discussion. Original: > For HTTP/3 servers and HTTP/3 clients when 0-RTT is not attempted or is rejected, the maximum table capacity is 0 until the encoder processes a SETTINGS frame with a non-zero value of SETTINGS_QPACK_MAX_TABLE_CAPACITY. Proposed but incorrect: > When 0-RTT is not attempted or is rejected, for HTTP/3 servers and clients, the maximum table capacity is 0 until the encoder processes a SETTINGS frame with a non-zero value of SETTINGS_QPACK_MAX_TABLE_CAPACITY. The intended reading is: For... - HTTP/3 servers (always, regardless of 0-RTT) and - HTTP/3 clients when 0-RTT is not attempted or is rejected ...the maximum table capacity is 0. -- Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/4980 You are receiving this because you are subscribed to this thread. Message ID: <quicwg/base-drafts/issues/4980@github.com>
- [quicwg/base-drafts] Auth48: Servers and non-0-RT… Mike Bishop
- Re: [quicwg/base-drafts] Auth48: Servers and non-… Mike Bishop
- Re: [quicwg/base-drafts] Auth48: Servers and non-… Mike Bishop