Re: [quicwg/base-drafts] Minimum size (#3848)
Martin Thomson <notifications@github.com> Wed, 08 July 2020 04:34 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 E1FCA3A07A9 for <quic-issues@ietfa.amsl.com>; Tue, 7 Jul 2020 21:34:23 -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, 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 SF_YyiCRyYgo for <quic-issues@ietfa.amsl.com>; Tue, 7 Jul 2020 21:34:22 -0700 (PDT)
Received: from out-13.smtp.github.com (out-13.smtp.github.com [192.30.254.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5ED93A07A5 for <quic-issues@ietf.org>; Tue, 7 Jul 2020 21:34:22 -0700 (PDT)
Received: from github-lowworker-275fa97.va3-iad.github.net (github-lowworker-275fa97.va3-iad.github.net [10.48.17.64]) by smtp.github.com (Postfix) with ESMTP id D1B222604A5 for <quic-issues@ietf.org>; Tue, 7 Jul 2020 21:34:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594182861; bh=jQKYZsa9g4vMcaELP5Opcra+/+5qm6HTHNQY0GNKIuA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Mqt8t4fJWNj2LAUZpkDD/eNRCrCAzWd5hN6LaC/qUfbS07aWJJN+5VoFAExO1niQ5 i+XBvMM2lFYaWnnG0zr9Q/E3y6iohaqdvqFWWcGABvI9Nf+PxbRqFDG7I9Qovqv5/b YSsehcOKIFZuXgdor8uVcaXRlAWRWb/5AhF1EVDs=
Date: Tue, 07 Jul 2020 21:34:21 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4U7BNTWLMEMRHBHB55CEW43EVBNHHCN2KTRY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3848/655277560@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3848@github.com>
References: <quicwg/base-drafts/issues/3848@github.com>
Subject: Re: [quicwg/base-drafts] Minimum size (#3848)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f054ccd8c058_658a3fcc360cd96445459"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/mh-ebi4JZ7wVoJlfIvr-qMWuILQ>
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: Wed, 08 Jul 2020 04:34:24 -0000
The logic is a little turgid and I think we were reluctant to show our working. The sender of a stateless reset can't know how big a connection ID the peer might have requested it use. This makes packets potentially distinguishable a peer wanted the largest connection ID size (20) and the packet size drops below 41 bytes. The sender of a stateless reset is required to reduce packet size for the stateless reset, unless it is counting somehow. So, if an endpoint wants to ensure that a peer can generate an indistinguishable stateless reset, assuming that its peer is following the size reduction rule, and assuming that the reduction is just one byte (because the stateless reset sender also wants it to be indistinguishable), then it needs to send packets of at least 42 bytes in the general case. But if it knows that it would never ever ask for a connection ID larger than N, then it can instead send packets of size N+22 and the goal is accomplished without sending larger packets all the time. -- 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/3848#issuecomment-655277560