Amplification window, initial congestion window, initial RTT and new post-quantum signature implications

"Kampanakis, Panos" <kpanos@amazon.com> Wed, 20 December 2023 04:10 UTC

Return-Path: <prvs=71131cec4=kpanos@amazon.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C894C14CE4A for <quic@ietfa.amsl.com>; Tue, 19 Dec 2023 20:10:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.402
X-Spam-Level:
X-Spam-Status: No, score=-4.402 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_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazon.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 8kW1oUPMZo3F for <quic@ietfa.amsl.com>; Tue, 19 Dec 2023 20:10:44 -0800 (PST)
Received: from smtp-fw-9106.amazon.com (smtp-fw-9106.amazon.com [207.171.188.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C93D0C151063 for <quic@ietf.org>; Tue, 19 Dec 2023 20:10:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1703045444; x=1734581444; h=from:to:subject:date:message-id:mime-version; bh=oK9KBnE0bXsWOgKCdTjA7f6gjfqd/HUN+11qao4Xf1M=; b=YSFktn4aDZuTsCXdrf5Glip770BMOSrDwtQJv7HFwIq+NPx/1E6leAL5 2ugEBUcNJ7+3gVVLqFXtzAfXbCaT+dbA2lnaK9vmFMe1zWQIXc/mDFiNg B+NtAZMYMAjtHiX2fyyHMKSl10qfGTdsPqVi1v/ht9q92/4nP0oRjH4iM o=;
X-IronPort-AV: E=Sophos;i="6.04,290,1695686400"; d="scan'208,217";a="691980335"
Received: from pdx4-co-svc-p1-lb2-vlan2.amazon.com (HELO email-inbound-relay-iad-1a-m6i4x-edda28d4.us-east-1.amazon.com) ([10.25.36.210]) by smtp-border-fw-9106.sea19.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Dec 2023 04:10:39 +0000
Received: from smtpout.prod.us-west-2.prod.farcaster.email.amazon.dev (iad7-ws-svc-p70-lb3-vlan3.iad.amazon.com [10.32.235.38]) by email-inbound-relay-iad-1a-m6i4x-edda28d4.us-east-1.amazon.com (Postfix) with ESMTPS id 20900804C8 for <quic@ietf.org>; Wed, 20 Dec 2023 04:10:37 +0000 (UTC)
Received: from EX19MTAUWC001.ant.amazon.com [10.0.7.35:3471] by smtpin.naws.us-west-2.prod.farcaster.email.amazon.dev [10.0.10.61:2525] with esmtp (Farcaster) id 169b51be-0b63-4efa-be3f-a944cf4f288c; Wed, 20 Dec 2023 04:10:37 +0000 (UTC)
X-Farcaster-Flow-ID: 169b51be-0b63-4efa-be3f-a944cf4f288c
Received: from EX19D001ANA004.ant.amazon.com (10.37.240.187) by EX19MTAUWC001.ant.amazon.com (10.250.64.174) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.40; Wed, 20 Dec 2023 04:10:36 +0000
Received: from EX19D001ANA001.ant.amazon.com (10.37.240.156) by EX19D001ANA004.ant.amazon.com (10.37.240.187) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1118.40; Wed, 20 Dec 2023 04:10:35 +0000
Received: from EX19D001ANA001.ant.amazon.com ([fe80::4f78:75cd:3117:8055]) by EX19D001ANA001.ant.amazon.com ([fe80::4f78:75cd:3117:8055%5]) with mapi id 15.02.1118.040; Wed, 20 Dec 2023 04:10:35 +0000
From: "Kampanakis, Panos" <kpanos@amazon.com>
To: "quic@ietf.org" <quic@ietf.org>
Subject: Amplification window, initial congestion window, initial RTT and new post-quantum signature implications
Thread-Topic: Amplification window, initial congestion window, initial RTT and new post-quantum signature implications
Thread-Index: Adoy+Sh38KvzpbxzT5OIdcsjhB7gIA==
Date: Wed, 20 Dec 2023 04:10:35 +0000
Message-ID: <f0360f9abbd6435b9dbf269e7f5bce65@amazon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.37.240.172]
Content-Type: multipart/alternative; boundary="_000_f0360f9abbd6435b9dbf269e7f5bce65amazoncom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fUPkfWS0Q7RSmXU4OS-7OCeAoTE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Dec 2023 04:10:49 -0000

Hi all,

I was wondering if there have been any discussion about new quantum-resistant algorithms and their impact on QUIC. Looking back in the list archive I could only find https://mailarchive.ietf.org/arch/msg/quic/cA_azemZvSQadc9FvWnMfN-malQ/  which brought up the initial congestion and the amplification window issues which could introduce an RTT each to the handshake due to the large "post-quantum auth data" from the server. I don't think that discussion converged to any actionable items.

Recently published https://www.nccoe.nist.gov/sites/default/files/2023-12/pqc-migration-nist-sp-1800-38c-preliminary-draft.pdf  (Section 7.3, Figure 5) also showed that packet pacing can introduce >RTT time to each handshake. kInitialRtt=333 is a "SHOULD" in RFC9002 so it could be adjusted, but I am not sure that should be left to the implementer.

Tweaking the amplification window to 10-15x as the new signature algos would require, increases the amplification risk. Validation tokens could alleviate the issue especially for clients that keep coming to the same servers, but it is not a general solution.

Increasing the initial congestion window is already done by CDNs, but I am not sure it is the norm for most QUIC uses.

So, has the WG generally considered options to address these issues?

Thank you,
Panos