IETF Logo Mail Archive

[TLS] "Notes" column in draft-ietf-tls-rfc8447bis?

"Salz, Rich" <rsalz@akamai.com> Thu, 20 April 2023 19:16 UTC

Return-Path: <rsalz@akamai.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 1E3E9C151B0D for <tls@ietfa.amsl.com>; Thu, 20 Apr 2023 12:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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=akamai.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 dAf4mRVkGijd for <tls@ietfa.amsl.com>; Thu, 20 Apr 2023 12:16:47 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 720FEC152D83 for <tls@ietf.org>; Thu, 20 Apr 2023 12:16:47 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 33KJElQ5010045 for <tls@ietf.org>; Thu, 20 Apr 2023 20:16:46 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : content-type : mime-version; s=jan2016.eng; bh=OBlve7TeK0M0XF0TxdX0+GhATbxuNvrVSim/Pd+3MTQ=; b=Ybl1v5SrRJW6fL0zUTPMUaJUemOAEef4G3Ecr0tk7lZoDJm0acLw1UFN5oUGG4mU2h8Y IYcDvVp06r74x4yN/6Z7xORcbSUqtIEe41BkyLccjXkoqRzNetKkPKOILM20dyQTg/8E KjQ+yJZlttDsr67N/tdc+2LMKlnfniJEm3Cf6dxK2onZEG++NRw+TgpT3xhY2V6DxYm4 iV+VWFuxMCkuZK1OFbcehxR7Vrrh7HzyNiikf+Ry3DyufnR5VxjsU1cfuUP14k3qXoGa +djjVlOHPChXYAfRSjGaUJoWhFGDHLhdl486M2sr3hYJI/pjYV5LQwSXnN9yinguGWlv Kg==
Received: from prod-mail-ppoint7 (a72-247-45-33.deploy.static.akamaitechnologies.com [72.247.45.33] (may be forged)) by mx0a-00190b01.pphosted.com (PPS) with ESMTPS id 3q2sn0kwyt-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Thu, 20 Apr 2023 20:16:45 +0100
Received: from pps.filterd (prod-mail-ppoint7.akamai.com [127.0.0.1]) by prod-mail-ppoint7.akamai.com (8.17.1.19/8.17.1.19) with ESMTP id 33KIjR3v026206 for <tls@ietf.org>; Thu, 20 Apr 2023 15:16:44 -0400
Received: from email.msg.corp.akamai.com ([172.27.50.206]) by prod-mail-ppoint7.akamai.com (PPS) with ESMTPS id 3pyq90sdt5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Thu, 20 Apr 2023 15:16:44 -0400
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com (172.27.50.203) by ustx2ex-dag4mb7.msg.corp.akamai.com (172.27.50.206) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.26; Thu, 20 Apr 2023 12:16:44 -0700
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) by ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) with mapi id 15.02.1118.026; Thu, 20 Apr 2023 12:16:44 -0700
From: "Salz, Rich" <rsalz@akamai.com>
To: "tls@ietf.org" <tls@ietf.org>
Thread-Topic: "Notes" column in draft-ietf-tls-rfc8447bis?
Thread-Index: AQHZc7yk5dYhdyelckCbTfzFW/WfRw==
Date: Thu, 20 Apr 2023 19:16:44 +0000
Message-ID: <4E5AE0C0-E9FD-4BF8-8102-81F4A236C32B@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.71.23032500
x-originating-ip: [172.27.164.43]
Content-Type: multipart/alternative; boundary="_000_4E5AE0C0E9FD4BF8810281F4A236C32Bakamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-04-20_15,2023-04-20_01,2023-02-09_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=659 bulkscore=0 malwarescore=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2303200000 definitions=main-2304200159
X-Proofpoint-GUID: 3bq6xCeKO8ypyXD2MPNF4y00cUVi8VN-
X-Proofpoint-ORIG-GUID: 3bq6xCeKO8ypyXD2MPNF4y00cUVi8VN-
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-04-20_15,2023-04-20_01,2023-02-09_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 suspectscore=0 adultscore=0 mlxscore=0 malwarescore=0 impostorscore=0 clxscore=1011 lowpriorityscore=0 spamscore=0 bulkscore=0 mlxlogscore=585 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2303200000 definitions=main-2304200160
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/tKMd6nvFN4zve8XbjF7Bnzy1pvY>
Subject: [TLS] "Notes" column in draft-ietf-tls-rfc8447bis?
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, 20 Apr 2023 19:16:51 -0000

I’m starting to write the draft about TLS 1.2 being frozen.

It occurred to me that every TLS registry might need a “notes” column.  If someone defines a new crypto algorithm, sat AEGIS being considered in CFRG, we want to assign it a number but have a note saying “only for TLS 1.3 and later”
We could make it be a simple yes/no column, like “Pre-1.3?” but I think that’s needlessly terse.

Does that make sense?

v2.23.0 | Report a Bug | By Email