Re: [TLS] Time to first byte vs time to last byte

Rob Sayre <sayrer@gmail.com> Thu, 07 March 2024 20:23 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA04CC14F6B0 for <tls@ietfa.amsl.com>; Thu, 7 Mar 2024 12:23:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 (2048-bit key) header.d=gmail.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 3kKagQooDE60 for <tls@ietfa.amsl.com>; Thu, 7 Mar 2024 12:23:54 -0800 (PST)
Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C5FDC14F696 for <tls@ietf.org>; Thu, 7 Mar 2024 12:23:54 -0800 (PST)
Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-a4499ef8b5aso20542566b.0 for <tls@ietf.org>; Thu, 07 Mar 2024 12:23:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709843032; x=1710447832; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7PimYs2nglVvzIqCTR7lcm60tC3Wt1zB+24OFhFk880=; b=NP+IgzgkD+3rYaPq2L0kovD4eMpCS44z2h3Vze8cB3eWwO3PY4MYh1Bn6M9OP17dCG S5Jm2TroTrXajQt5rtJvDOsZjbspSP5LjEHTRgfbSGGS8B6TKEXk9F7Wihu68Tyha4vL DxbFezVrV4jR3r/CC6KUbpa1IpEljfNmqm3AoVKHiNJblKe0K0+CQDMcZd3JhNJ/wlnF NN3Yxmio9iAa/3JT/P9B6bN2ArhA2tojmAa7u88OnRG9HdK+HKc+89ffsQb4v+ai0M7W d2rI04UDOy2sGxRIexCUuPT8EcVFzj0J5CRGhltubOdPUcF4uwsJNIMblbEGJcw3I8a9 113A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709843032; x=1710447832; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7PimYs2nglVvzIqCTR7lcm60tC3Wt1zB+24OFhFk880=; b=FTdsegLPTGByVVRJNIL5Hwi4d2WfedP2WUmJ/VZfoTNClVBa2tpq2aH5k0BHp50mL9 BOK6C7KrPmnKsbN/YjcvTYeHZ0Nxzx5VHvD+/SS2Fiq8WCZbu0JODUb6o15BKsOqjelH COODvD/MogirUnm7zOfYZy2HDiRDhfJMfV6gfx+QwC4NYQA2lTmAgIzNeDLs1AQlpU1L +iGc01UJJrvoBV5hFeSI5LztVTEFtPAE9EHLioltAbjooPgxdqxZGOGp4D5LtHWGt7zG te/eBZfGdXCFGd8wGTwU0zsmXC8a2NSivBGh3+FpZgxJT1pHsi2ZW597GyGp/I52+nLl Vv3A==
X-Gm-Message-State: AOJu0YxjKkRED+E5IPkT0MFoCs3/nQHECo81zsV5Q5CTjIoU0KmJQcXO LqFGo6I2Wvbk4yqHNaB4ixqMx27z3NPqCygivfxkQ6x7dZezB+N84dE1LZ4AsTfAAjX0+9tgv1S R4Ey/p7Bkv9Ckbgzjm7YWBPkGsUEurWS+
X-Google-Smtp-Source: AGHT+IHlKKz1IXpz1IJHoHTi9ahhMW641Y+qdMoEoCyIzOnbcKMpOuG0fqOvv0GQQjnuIcskzN6yeq6UKkfsMraUacg=
X-Received: by 2002:a17:906:27d1:b0:a3d:656a:4700 with SMTP id k17-20020a17090627d100b00a3d656a4700mr12974330ejc.71.1709843031726; Thu, 07 Mar 2024 12:23:51 -0800 (PST)
MIME-Version: 1.0
References: <CAFR824zRjvC=+EoXXpVVZYVevrZeuudgTCCSp42wbbBu1NPBXA@mail.gmail.com>
In-Reply-To: <CAFR824zRjvC=+EoXXpVVZYVevrZeuudgTCCSp42wbbBu1NPBXA@mail.gmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Thu, 07 Mar 2024 12:23:40 -0800
Message-ID: <CAChr6Syoy1PST0wQZWM+p7WSfM-FFMe1oWt=4_jEq6bbN_07dA@mail.gmail.com>
To: Deirdre Connolly <durumcrustulum@gmail.com>
Cc: "TLS@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000872669061317da11"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/yeGSz3K2B_AryHcXSw8EMdCpgl8>
Subject: Re: [TLS] Time to first byte vs time to last byte
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2024 20:23:57 -0000

I agree the efficiency concerns are generally overstated, but this study
should have measured QUIC etc, since the web pages will have all sorts of
awful performance problems. But the thing you have to watch out for is when
someone in the datacenter steps on the power cord or something (or DNS is
wrong, etc). Then, you get a stampede of clients reconnecting, and there
you really do care about how expensive the handshake is.

thanks,
Rob

On Thu, Mar 7, 2024 at 11:58 AM Deirdre Connolly <durumcrustulum@gmail.com>
wrote:

> "At the 2024 Workshop on Measurements, Attacks, and Defenses for the Web
> (MADweb), we presented a paper¹ advocating time to last byte (TTLB) as a
> metric for assessing the total impact of data-heavy, quantum-resistant
> algorithms such as ML-KEM and ML-DSA on real-world TLS 1.3 connections. Our
> paper shows that the new algorithms will have a much lower net effect on
> connections that transfer sizable amounts of data than they do on the TLS
> 1.3 handshake itself."
>
>
> https://www.amazon.science/blog/delays-from-post-quantum-cryptography-may-not-be-so-bad
>
> ¹
> https://www.amazon.science/publications/the-impact-of-data-heavy-post-quantum-tls-1-3-on-the-time-to-last-byte-of-real-world-connections/
>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>