[TLS] Re: Adoption call for TLS 1.2 Update for Long-term Support

Sean Turner <sean@sn3rd.com> Tue, 05 November 2024 16:26 UTC

Return-Path: <sean@sn3rd.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 74C58C222983 for <tls@ietfa.amsl.com>; Tue, 5 Nov 2024 08:26:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_BLOCKED=0.001, 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 (1024-bit key) header.d=sn3rd.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 TEY6Tpq9s4aW for <tls@ietfa.amsl.com>; Tue, 5 Nov 2024 08:26:43 -0800 (PST)
Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 837E1C22118D for <tls@ietf.org>; Tue, 5 Nov 2024 08:26:10 -0800 (PST)
Received: by mail-pf1-x42b.google.com with SMTP id d2e1a72fcca58-71e79f73aaeso4837969b3a.3 for <tls@ietf.org>; Tue, 05 Nov 2024 08:26:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; t=1730823970; x=1731428770; darn=ietf.org; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=TMdfqYUMayPW5gLVSZio9WWsOc8pi54FB/5uoHZRlcg=; b=I9uo1iXA7iSHDLVXg2vhK8vzgV89RapXEqSKTAZeKUz/x5uBb/AcZhAV8NU00sP04M Kukrd2Vu3ufL74omViP+bOKQ6991+NQMvqPXUgg9jJ1tjT6PwjUSGxI9gTZ3yYTR/GjD P6mvs0OabZPdcyr390PJhHEi4RkSgLjHiHesk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730823970; x=1731428770; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=TMdfqYUMayPW5gLVSZio9WWsOc8pi54FB/5uoHZRlcg=; b=WcE1lUuZsKkoz4UKycLGJoOdxiGj3XEHrLMGd7z6ytZOlfZEEHqN8jjJXwOBybvFlv vGDsFk8Q5WdR41A2qGB/iDaUerynmGpFAdYpAVn2v/+WUOTjvfdM/DyZsf4wwwWlqFX1 dUeRZgI429m5GF1KyMdZ28ox2rOjAZBS7hNXeGDecoZXAmOrzyeI/a82UyFVhAXZkfwS 0Uo6XRTCas2551ZwYtqbXU1qsAR41mapnBA2kJeZzfFnLmyrHI27ag10R2Egp3m62a+h bBQN8ldIPAXGrMUHIozyCmxEuk9+Bc+54hrr+SYoXXpmHa/3KkKUMeTIX8/CMfQqPXW0 uFhQ==
X-Gm-Message-State: AOJu0YzKb/uC+jWXzMqGgspWv8u+UVYggJhQlS/MnSs4UA8ZkCpUjgBr XsEqAiv9acTl9Ea8KLtrGBeMk1HY5D/lfz7d0rO6/swIqWEovVw736jaw30HJ0PLuW4ue2fd092 id+J9T1aC
X-Google-Smtp-Source: AGHT+IGP0KfuWEVaAz3duXSM0GSJ/HB3hF583ZTcdS8oBev57fpauaRoOKr8LNHctGQ7Gx4HhndzHw==
X-Received: by 2002:a05:6a00:988:b0:71e:6ef2:6c11 with SMTP id d2e1a72fcca58-72062f874bemr52401395b3a.9.1730823969659; Tue, 05 Nov 2024 08:26:09 -0800 (PST)
Received: from smtpclient.apple ([2001:67c:370:128:5ce0:907:16ac:720f]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-720bc205582sm9882056b3a.88.2024.11.05.08.26.08 for <tls@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Nov 2024 08:26:09 -0800 (PST)
From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.15\))
Date: Tue, 05 Nov 2024 16:26:08 +0000
References: <278163DF-0CB8-472F-84CB-0B8236FEC7C1@sn3rd.com>
To: TLS List <tls@ietf.org>
In-Reply-To: <278163DF-0CB8-472F-84CB-0B8236FEC7C1@sn3rd.com>
Message-Id: <E7B12531-3E98-46F7-B121-DFD4F2DEAD31@sn3rd.com>
X-Mailer: Apple Mail (2.3654.120.0.1.15)
Message-ID-Hash: PWRCI6J6MTGXSI74ZZUD7HUMXTWNSORR
X-Message-ID-Hash: PWRCI6J6MTGXSI74ZZUD7HUMXTWNSORR
X-MailFrom: sean@sn3rd.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Adoption call for TLS 1.2 Update for Long-term Support
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/ol6Jioe_GMURLpMYhdHSldnYn3w>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>


> On Nov 5, 2024, at 16:25, Sean Turner <sean@sn3rd.com> wrote:
> 
> REQUEST: Let’s not rehash all the context.  It is provided for those who might not remember or those that were not around for the duration.
> 
> CONTEXT: Way back in 2016 after the WG had embarked on developing TLS 1.3, Peter Gutmann suggested that another way to “fix” TLS was to specify a version of TLS that indicates a “known-good config drawn from the maybe 10 extension-RFCs”; see [0].  Peter submitted his “TLS 1.2 Update for Long-term Support”; see [1]. There was some list discussion; see [2]. Peter asked us about adopting the I-D; see [3]. He made changes based on that feedback; see [4]. At IETF 98, the WG discussed adopting this I-D and the sense of the room was to not adopt the I-D; see [5]. Progress on this document was paused while the WG worked on TLS 1.3. Once RFC 8447 was published, a code point was assigned for the “tls-lts” extensions; see [6] and [7]. Now that we are looking to publish Feature Freeze for TLS 1.2 [8][9] we want to make sure that the working group sentiment has not changed over time so we are running an adoption call for TLS-LTS. 
> 
> MESSAGE: This message is to judge consensus on whether there is support to adopt TLS 1.2 Update for Long-term Support; see [1].  If you support adoption and are willing to review and contribute text, please send a message to the list.  If you do not support adoption of this draft, please send a message to the list and indicate why.  This call will close on November X, 2024. 

Whoops November 26, 2024.

> Thanks,
> spt
> 
> [0] https://mailarchive.ietf.org/arch/msg/tls/Lr7VwcPCjzDJelUTRTIUJf_8-ww/ 
> [1] https://datatracker.ietf.org/doc/draft-gutmann-tls-lts/ 
> [2] https://mailarchive.ietf.org/arch/msg/tls/r4w75rooy-r8Ky-xXAUoslYTL_U/ 
> [3] https://mailarchive.ietf.org/arch/msg/tls/6tBftKBmxYz_wUcq79_zH8yDTQk/ 
> [4] https://mailarchive.ietf.org/arch/msg/tls/aw9BOS4HJ9uum0snEZqSuKA4BYw/
> [5] https://datatracker.ietf.org/meeting/98/materials/minutes-98-tls-00 
> [6] https://mailarchive.ietf.org/arch/msg/tls-reg-review/bP84S3tHSG9gAmc45CLTjpiA0z8/
> [7] https://mailarchive.ietf.org/arch/msg/tls/xmhnVQTckDmUkoxhx4wx1bfpYXM/ 
>   Thanks to Peter because he helped us iron out the
>   wrinkles in the tls-reg-review process.
> [8] https://datatracker.ietf.org/doc/draft-ietf-tls-tls12-frozen/ 
> [9] https://mailarchive.ietf.org/arch/msg/tls/f62yvLL_4mDEsRzAY46L4QLjakU/