Re: [quicwg/base-drafts] Remembering transport parameters (#3434)

martinduke <> Mon, 10 February 2020 22:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DE3CD12087F for <>; Mon, 10 Feb 2020 14:52:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bg2wGf0x9yFf for <>; Mon, 10 Feb 2020 14:52:06 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8DF9F12082A for <>; Mon, 10 Feb 2020 14:52:06 -0800 (PST)
Date: Mon, 10 Feb 2020 14:52:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1581375125; bh=1Hh7yjq9P0HlB3de2eKtDQu1gH80S8UHapME00/LBRc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xoCoyjRQjl/cPrEAo7vbdu8xDONugp3oNvjUM7XBXD62GYCiz671gQDG+cNTlq3fH TKG7m5ndDMknyXQF5ZlnGP72QOiR3XHL6xlLisngxSwmv2VMyErc23OVucazbjWSUJ OfipxQbszeHOvh3Vcw695NDTYC8ryZbaEX4UqF2w=
From: martinduke <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3434/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Remembering transport parameters (#3434)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e41de9524310_55f13f901decd9609936f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 10 Feb 2020 22:52:08 -0000

There are three separate questions here:
1) Can a client exceed the previous max_packet_size in 0RTT? Clearly not.
2) Does the server have to do anything if it receives packets that exceed the old value? This isn't clear to me.
3) Is the server allowed to advertise a lower max_packet_size in its new TPs? I can imagine some use cases to motivate a "yes", and it has the advantage of being what the text already says.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: