[TLS] Re: Adoption call for RFC 9147bis

hannes.tschofenig@gmx.net Sat, 07 December 2024 17:22 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 2C228C14F680; Sat, 7 Dec 2024 09:22:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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 (2048-bit key) header.d=gmx.net
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 3UpQadld2SNL; Sat, 7 Dec 2024 09:22:08 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C5A5C14F61E; Sat, 7 Dec 2024 09:22:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.net; s=s31663417; t=1733592119; x=1734196919; i=hannes.tschofenig@gmx.net; bh=EPp/eQWBOt/mFAmxGZTAPleotWhYShWNt2RSKy7etLU=; h=X-UI-Sender-Class:From:To:Cc:References:In-Reply-To:Subject:Date: Message-ID:MIME-Version:Content-Type:cc:content-transfer-encoding: content-type:date:from:message-id:mime-version:reply-to:subject: to; b=XndnG1YA87qRoQLSKtyg1dlcBQlvui4Qk0p2fIOq9zWfE/SopFgpAwP+LZo6/Kys fuK1XP844yTXW3xbaqnm47q+MmJEZ74S5WKi14hdZ2uyRPHYDyuCDimXmehhdWm1C Tw5sNm3q9pjvkFAmniA1MbiDO1mjN6SRkCqpXEqpZ4uoxn22SzsbTXoZpqeF0uFLN 01yz7pLoJc0N92EGPHE+a+/gmUgzsOjgmJurRmU6odeSVv7ll4VqlsIoXY1n30uH4 uM/0Dq+zJ4THVKVdt9eT8s1G3UJKBNTDlJbfSbFjWFuP+jeSMs4QKqKXMy7K8pSAv +bOmkL94oW/O99HnvQ==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from Surface ([88.130.144.215]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M8hZD-1tFrte0EWP-00EZfi; Sat, 07 Dec 2024 18:21:59 +0100
From: hannes.tschofenig@gmx.net
To: 'John Mattsson' <john.mattsson=40ericsson.com@dmarc.ietf.org>, 'Russ Housley' <housley@vigilsec.com>, 'Joe Salowey' <joe@salowey.net>
References: <CAOgPGoCZeE9hW5O+kwp_a32MttmV_7QyVkOjaDCM9ODPLPV8KQ@mail.gmail.com> <2FEDE71B-96B6-4831-8CA5-3C00EE8B197F@vigilsec.com> <GVXPR07MB9678AAF7159032F5250E132389352@GVXPR07MB9678.eurprd07.prod.outlook.com>
In-Reply-To: <GVXPR07MB9678AAF7159032F5250E132389352@GVXPR07MB9678.eurprd07.prod.outlook.com>
Date: Sat, 07 Dec 2024 18:21:56 +0100
Message-ID: <091501db48cc$8473a020$8d5ae060$@gmx.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0916_01DB48D4.E638F280"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQH9iWj0WthBwPbpPTNnwbDV5G7MjwFNpK3PAa8RPmayfp6OAA==
Content-Language: de-at
X-Provags-ID: V03:K1:P9A3VKb3GYqTy1kc1isR7/pUefehvqBa3yD3IHul1uwqh5BqR2R ZKU5LXH5cUwXCxlytdhgBAsGjZHKoro7mQO+S7v+BUU3R3prkuPy2GJyUDbKql5xV8mcYKw aFdxdGKdxhrVlatk3AZJr0decw4av5klSfdMXBm+6CRrct3+gmzbq9+ZDFjgZ3siBcWyPXK aV20a666GhZ7RuuOKcCaA==
UI-OutboundReport: notjunk:1;M01:P0:HKd2ItTcSls=;90DEp4ebknXm+SpEszYfOKroWo2 aZZrHskVOrrQYMJI5BQ8iuHA4HbWSPxzOSpbGgkFI9d/48PQiODU7LoEpYoX2bzyrHzXU+2o5 TqZ1qHLO7J606A7HS3gAi0lgFhsuCAu3u+j9KHK7s4/WL06fVFsDlCAb8tfNmwyVL2FUheZXj gl8a5wPdPXZqUoR1yZgrKR0g4QgTik3cnHHDR1CAIAWNgDMPNSvF8GyDFY5dMH6WN69fg7VGb xTn37CeNXmdhtorQO8GFxy6JRL0tdpmCXgP7RaElASu4JmFbYiqiYO2oNz4GkiXc4Tm+NOw10 eonqH5lKu9N7diOL5nagH6BmNuHul08awMoJcKrjdz0tBrhwENuMEhE33FQxcCScQtkwkKJcA Z4Zk1yrURZ7eRyej6CObIX9hwGjNqsp3mORdrvxJBGrlsbyrW6NOUjfLtNQZdVSLvSAwYJUzs SGWlrYj93Ualova/QNy1DqoRsKahiFAF2biAv0n5P5P9azDi1DMaHmR8jTrKlGVSfDlsVGfwB Pfio/svjXf4S+ORScQ60UCDLmN80bTpNjhZ8Ix0Xe4H6bPymDY4gHEcDh4Y/7B7lqTwKDA6+4 XzdwFzmV34omqzz8fJtm05OIlJwxOz0RC7iZ33DXlCfP8fK0y6ObU4a4A1KiuVxUmbBTMc5Gh HoipmBTP3Rw+r27lx3gEDKAR1dYsfdy1yNtZtB/uB2T2zsBfH2w/8QUQ9uCvpOfaZWLjcxVZ6 3wv27ZtW1yBJ35A+0hzNXSudMJSVfdoPdUmh2P+CPKQ7+ZGUf0sGRI+1Nq/PH0J6lu5hfNbbr 5iKjzuJ2NL4yINyLZSFNayfzDwl5liwyrJ/RxCdXp67ge4CnFPR+9Snab7tgHlPwi7/UIWU7Q 3IhkfW9nuLyw2XAyPrTZbKNaU2vp3iBmmUhAw+n7QkDRCv1youXQLDvZt0YIdWnd5H+sW/1pD FhBJl36CEEShK2pEWNyaYH98D1yt5ZhE+K6Io4QmS8S2nZeuYNjwxSPODH79WrMhYia/QW7h5 0514NHPzfQMMEiMxSyPS1f/7L9KQLhVJ8jaE/+ftH9Iei9Xzhwl3l5W+MiAM82CXrRf8UtWdh NrZlqpjW1HT+wy21obsk1+WZZXC/dr
Message-ID-Hash: BNPU66N7DZKD4KHLD7WW326INMFG2EQS
X-Message-ID-Hash: BNPU66N7DZKD4KHLD7WW326INMFG2EQS
X-MailFrom: hannes.tschofenig@gmx.net
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
CC: 'IETF TLS' <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Adoption call for RFC 9147bis
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/v3KuNVvtRPirDGNp8dL_2jzHXV0>
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>

Have to add a note to this statement:

 

“

Formal verification would likely have caught several of the issues identified by David Benjamin as well as the issues with post-handshake messages when replay protection is turned off identified by me. I hope everything going out the TLS WG in the future will be formally verified.

“

 

When everything goes smoothly, it’s the working group that gets the credit. But when something goes wrong, the blame falls squarely on the authors.

 

I am looking forward to your contributions to the formal analysis since you missed the opportunity last time.

 

Ciao
Hannes

 

From: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org> 
Sent: Montag, 2. Dezember 2024 19:43
To: Russ Housley <housley@vigilsec.com>; Joe Salowey <joe@salowey.net>
Cc: IETF TLS <tls@ietf.org>
Subject: [TLS] Re: Adoption call for RFC 9147bis

 

Hi,

I support adoption and just like Russ I look forward to formal verification. Formal verification would likely have caught several of the issues identified by David Benjamin as well as the issues with post-handshake messages when replay protection is turned off identified by me. I hope everything going out the TLS WG in the future will be formally verified.

 

Cheers,

John

 

From: Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com> >
Date: Monday, 2 December 2024 at 19:00
To: Joe Salowey <joe@salowey.net <mailto:joe@salowey.net> >
Cc: IETF TLS <tls@ietf.org <mailto:tls@ietf.org> >
Subject: [TLS] Re: Adoption call for RFC 9147bis

I do not object, but I look forward to the FATT review.

 

Russ

 

 

On Dec 2, 2024, at 12:38 PM, Joseph Salowey <joe@salowey.net <mailto:joe@salowey.net> > wrote:

 

This is a call for adoption of draft-rescorla-tls-rfc9147bis-00[1] as the basis for an RFC9147 bis document.  This document is seeded with the content of RFC 9147.  If you object to the adoption of this document please respond to this thread by December, 9 2024.

 

Cheers,

 

Joe, Deirdre, and Sean

 

[1] https://datatracker.ietf.org/doc/html/draft-rescorla-tls-rfc9147bis-00

 

_______________________________________________
TLS mailing list -- tls@ietf.org <mailto:tls@ietf.org> 
To unsubscribe send an email to tls-leave@ietf.org <mailto:tls-leave@ietf.org>