Re: [TLS] What's it called

Tim Bray <tbray@textuality.com> Thu, 24 June 2021 19:13 UTC

Return-Path: <tbray@textuality.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 D03163A2839 for <tls@ietfa.amsl.com>; Thu, 24 Jun 2021 12:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=textuality-com.20150623.gappssmtp.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 aPJTENBHGBMk for <tls@ietfa.amsl.com>; Thu, 24 Jun 2021 12:13:31 -0700 (PDT)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 497BD3A282D for <tls@ietf.org>; Thu, 24 Jun 2021 12:13:31 -0700 (PDT)
Received: by mail-lf1-x12d.google.com with SMTP id a11so12042669lfg.11 for <tls@ietf.org>; Thu, 24 Jun 2021 12:13:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fX/iRg9uFykAd6zL00pPr6DrDS2KdBa8llQGL1DiSSo=; b=Rn7A53JJiyiCKm0G2gStBFW/KyuD4HkzKiXMGKUe1OX++Fxw/VRHBDsqejwUI4xYzN K+4io2BeUBhoGGeGb9lXhsVsBHOsxntzhWkyI9F8Nkux2SAT50AUFgJ8oQDRf16lwUHB zVk57Tbl/pbFPI6kis9CQltlU5rEMsjj0hinihEflnkZiNheY7Ww4huc5WEx/Qaj67dE x7wyIgi2ra2fwNlh3EtPxek8fYDFtwSvfilT24P1KlHmaql+Zp8lrUNTnNQlmxzX8ciD pYtRspyqZ2Q0vQ21QHISrpyGTSH+bQB+/Kt19Q7x5xw8GzwkE7iPj68jlFpH8iuLHAc8 cxYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fX/iRg9uFykAd6zL00pPr6DrDS2KdBa8llQGL1DiSSo=; b=Xr+cDw9OoEAGQRC3yW67LbAghSLo3Ge4jrcRMurjxuhdaN34BEVYZC2gd3zDRr2Hfd sFwt3/y1poo07LSsMh25RBORh9W/H0Oxa8mEdUS8HUJoEWW4ip7J1XICUDo82mgijxSe KVUwq1/67nD+jOfmAjfYlI/gyiEW5M+WGDvhbchn+Ac4jBN/0371Ih+Coq/LHKnZGlaW 43fXJq2fBO3LlTxI4m04KQWiMtPr6ebHwMOYlKZaV5kZF5YV1sLoVwfWsTUu+BTrGill KnY/i4ZY+qRWdgmcPyBo+GOIaRkSWsl2TucU8zuVst/EFuD5X45Kal9ZKQfkIfqAFbz+ +xaQ==
X-Gm-Message-State: AOAM532bFOxkZ87N/E29cmMAENMcHwMpIRtei0uuaz3devP7SGyRMYUI fcr5N+14rNr2UKJxqo1+6o6gid3kgqfF2Oy28rTFkw==
X-Google-Smtp-Source: ABdhPJzmi6YV06azOnLsu3p/wNXeH3vmP0lxAh/TwRLE076jLM7RFXgxVdBmofyIfg//PkmSRuaVg2pOiSYN+mhz8Vo=
X-Received: by 2002:ac2:4579:: with SMTP id k25mr4924300lfm.451.1624562008094; Thu, 24 Jun 2021 12:13:28 -0700 (PDT)
MIME-Version: 1.0
References: <63CB8AEC-13F6-48DC-A400-2D6EBFA8AEE9@inf.ethz.ch>
In-Reply-To: <63CB8AEC-13F6-48DC-A400-2D6EBFA8AEE9@inf.ethz.ch>
From: Tim Bray <tbray@textuality.com>
Date: Thu, 24 Jun 2021 12:13:16 -0700
Message-ID: <CAHBU6itCysEves2H3+9-KR2ZUxWrfFqfq_xafEpqzkod__pYKA@mail.gmail.com>
To: Paterson Kenneth <kenny.paterson@inf.ethz.ch>
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "tls@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000688f2b05c587d1ad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/O0NbqEv9BvhQVlAJiQD4cicPplg>
Subject: Re: [TLS] What's it called
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Jun 2021 19:13:42 -0000

How much data is too much?

On Thu, Jun 24, 2021 at 12:02 PM Paterson Kenneth <
kenny.paterson@inf.ethz.ch> wrote:

> Hi Rich,
>
>
>
> We speak of reaching data limits, and the process of changing the key has
> many names, e.g. key rotation, key renewal, key refreshing, key updating.
>
>
>
> Any of those ring a bell?
>
>
>
> Cheers
>
>
>
> Kenny
>
>
>
>
>
> *From: *TLS <tls-bounces@ietf.org> on behalf of "Salz, Rich" <rsalz=
> 40akamai.com@dmarc.ietf.org>
> *Date: *Thursday, 24 June 2021 at 19:32
> *To: *"tls@ietf.org" <tls@ietf.org>
> *Subject: *[TLS] What's it called
>
>
>
> I’m blanking on a term and web searches turn up too much useless info.
>
>
>
> What is it called when we have to start using a new symmetric key because
> we’ve encrypted too much data with the old one?  Key exhaustion fits, but
> probably isn’t it.
>
>
>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>