IETF Logo Mail Archive

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

"Salz, Rich" <rsalz@akamai.com> Thu, 11 May 2023 18:54 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 CA506C151B2C for <tls@ietfa.amsl.com>; Thu, 11 May 2023 11:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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_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 Oi-IUi58E9H1 for <tls@ietfa.amsl.com>; Thu, 11 May 2023 11:54:34 -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 37DCFC13AE56 for <tls@ietf.org>; Thu, 11 May 2023 11:54:34 -0700 (PDT)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 34BIW9Wk017543 for <tls@ietf.org>; Thu, 11 May 2023 19:54:33 +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=GkzgErvBbvR6VKOa//0wqUT7rCtFzK23Sn/Rc9sGz3M=; b=Ct997a27XsTiGNDmbiDBYPWBEPNZWJ/vovXpiNNeE3nSxgaLGFi/yTfaqTYiDl1DaZoP g0Ka7GWhjLAlDMU6oDiE+cKBkPeXh5fx0s1cZNTlxOh5dgPs1ZJ1FtatTONkiAQ/DM8i Keoy8rx+qn24K1KMTT4wiwEosH02yC84TfLjLQZupo8CvFBWvQ6ZWWGtJxv9FzI+5SIv swxCgC05rN+Muh6ROULSZw6+CVIztB+YrJ2gqvFuUvJft0lHGChKRkjsVAyw2v/nnfFT Xxf5TdsKR5+kxgTkolQOAguIXZbQ+oqTGEzFkW0e7CqXjD8InoH32dVq/psruH8hJPwK sg==
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 3qf7ds0bb3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Thu, 11 May 2023 19:54:31 +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 34BGI6on030739 for <tls@ietf.org>; Thu, 11 May 2023 14:54:24 -0400
Received: from email.msg.corp.akamai.com ([172.27.50.203]) by prod-mail-ppoint7.akamai.com (PPS) with ESMTPS id 3qfm1tr47y-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tls@ietf.org>; Thu, 11 May 2023 14:54:23 -0400
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com (172.27.50.203) by ustx2ex-dag4mb4.msg.corp.akamai.com (172.27.50.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.26; Thu, 11 May 2023 11:54:23 -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, 11 May 2023 11:54:23 -0700
From: "Salz, Rich" <rsalz@akamai.com>
To: "tls@ietf.org" <tls@ietf.org>
Thread-Topic: [TLS] "Notes" column in draft-ietf-tls-rfc8447bis?
Thread-Index: AQHZhDoAuxeCX4w7sEmUBLmJ2VEisQ==
Date: Thu, 11 May 2023 18:54:23 +0000
Message-ID: <735D9094-3EA2-4B54-A841-DBBC10D6408C@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.72.23040900
x-originating-ip: [172.27.118.139]
Content-Type: multipart/alternative; boundary="_000_735D90943EA24B54A841DBBC10D6408Cakamaicom_"
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-05-11_15,2023-05-05_01,2023-02-09_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 phishscore=0 mlxlogscore=681 bulkscore=0 mlxscore=0 spamscore=0 malwarescore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2304280000 definitions=main-2305110162
X-Proofpoint-GUID: ko5CJ3WRq_LW0_nKykQRhKfHzPH3qAgz
X-Proofpoint-ORIG-GUID: ko5CJ3WRq_LW0_nKykQRhKfHzPH3qAgz
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-05-11_15,2023-05-05_01,2023-02-09_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 clxscore=1011 impostorscore=0 bulkscore=0 phishscore=0 priorityscore=1501 suspectscore=0 malwarescore=0 mlxlogscore=619 lowpriorityscore=0 adultscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2304280000 definitions=main-2305110163
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/AmNG-PxQuz8RQB4bpNhbsF213h8>
Subject: Re: [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, 11 May 2023 18:54:37 -0000

Ping.

From: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Date: Thursday, April 20, 2023 at 3:17 PM
To: "tls@ietf.org" <tls@ietf.org>
Subject: [TLS] "Notes" column in draft-ietf-tls-rfc8447bis?

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