Re: [quicwg/base-drafts] It seems the minimal packet number length should be 14 bits (#2955)

Marten Seemann <> Wed, 07 August 2019 02:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2EFB5120096 for <>; Tue, 6 Aug 2019 19:37:35 -0700 (PDT)
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 TlVqHT_2uuF6 for <>; Tue, 6 Aug 2019 19:37:33 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A840812000E for <>; Tue, 6 Aug 2019 19:37:33 -0700 (PDT)
Date: Tue, 06 Aug 2019 19:37:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1565145453; bh=H0unWjQ7eCp6hsk6wP5nBMPQXpON50LzuGvboU+D3AA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oZ/Lk/bycCJw68hRw3msFbvWX5eCzG2VQzAUxdscm5eNCb3qalDKA40tPfeDpCPqJ KsatLAZ/Z5YgRVpetfwbt1fJ02sQcWnJPBcQqyLqiQVU0njR5XCGzUy36ElazMK5V8 K3p1lWAkLuto+k8rXN4rzAY/Q/3aKiusgxgdInqo=
From: Marten Seemann <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2955/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] It seems the minimal packet number length should be 14 bits (#2955)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d4a396cd92f8_2a813fcfcb0cd96c4689ce"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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: Wed, 07 Aug 2019 02:37:35 -0000

> This issue will cause the receiver ""ACK the wrong packet number"" and the related stream will hang for ever.

That's not correct. If you decode the packet number incorrectly, decryption of the packet will fail, since the packet number is used as the nonce for the AEAD. Really, the worst thing this will happen  in this case is that the packet is discarded as undecryptable and eventually detected as lost by the sender.

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