IETF Logo Mail Archive

Re: [Tls-reg-review] [IANA #1287496] Re: Request for Assignment (draft-irtf-cfrg-aegis-aead - aead-parameters)

"Salz, Rich" <rsalz@akamai.com> Mon, 13 November 2023 18:49 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: tls-reg-review@ietfa.amsl.com
Delivered-To: tls-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EBE7C14F721 for <tls-reg-review@ietfa.amsl.com>; Mon, 13 Nov 2023 10:49:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.806
X-Spam-Level:
X-Spam-Status: No, score=-2.806 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 2vBjIpzAJ6NC for <tls-reg-review@ietfa.amsl.com>; Mon, 13 Nov 2023 10:49:50 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 5FA14C151707 for <tls-reg-review@ietf.org>; Mon, 13 Nov 2023 10:49:50 -0800 (PST)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.17.1.22/8.17.1.22) with ESMTP id 3ADFbRuo002558; Mon, 13 Nov 2023 18:49:27 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h= from:to:cc:subject:date:message-id:references:in-reply-to :content-type:content-id:content-transfer-encoding:mime-version; s=jan2016.eng; bh=/Vots6xTYoodzNiYaZei4maKYDpuHFq5adUSngLAPAA=; b= buM0HatWZqYEGHG9ZIxiEVWkOfZWLdGowwRRu6tr5n0zWol/txUEgklvidcmOww7 ++4phfVWJaZ0vb0DGYlSO5wEYz5PauQ6Alq4Zfbsf5/qonaYfQSptzS24PJD3/Ws RwskKWlMynEAIFQSZ3PnWTU0PmlVvNqUvdxvg9/wodvK0K4+Lv0vJfpph+gkM+9h udNYayDltG5pRGqBl4h9QowXhuNHLeLTv5hVlDYKqllJz8+85I0eDvVppWLIPqC7 VP9SxjpvFQHAMZPQfjqT8cKfZbDTdh8nKNYuJCI0cEApU3yUj3kOC7fFVAirWx+N 4inkq3OFW5zCqbX7wmt3ag==
Received: from prod-mail-ppoint3 (a72-247-45-31.deploy.static.akamaitechnologies.com [72.247.45.31] (may be forged)) by m0050102.ppops.net-00190b01. (PPS) with ESMTPS id 3u9yjrhyf8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 13 Nov 2023 18:49:27 +0000 (GMT)
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.17.1.19/8.17.1.19) with ESMTP id 3ADGlMGH026633; Mon, 13 Nov 2023 13:49:26 -0500
Received: from email.msg.corp.akamai.com ([172.27.50.203]) by prod-mail-ppoint3.akamai.com (PPS) with ESMTPS id 3uaqd2j42d-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 13 Nov 2023 13:49:26 -0500
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.1258.25; Mon, 13 Nov 2023 10:49:25 -0800
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.1258.025; Mon, 13 Nov 2023 10:49:25 -0800
From: "Salz, Rich" <rsalz@akamai.com>
To: "iana-prot-param-comment@iana.org" <iana-prot-param-comment@iana.org>
CC: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>
Thread-Topic: [Tls-reg-review] [IANA #1287496] Re: Request for Assignment (draft-irtf-cfrg-aegis-aead - aead-parameters)
Thread-Index: AQHaFl91gut3l29YIkq8MeVgwcSwjbB4ycqA
Date: Mon, 13 Nov 2023 18:49:25 +0000
Message-ID: <E910312D-BD62-4DF1-B808-A66C9D49A4AE@akamai.com>
References: <RT-Ticket-1287496@icann.org> <RT-Ticket-1261222@icann.org> <rt-4.4.3-436-1668808356-1016.1261222-37-0@icann.org> <rt-4.4.3-436-1668808638-666.1261222-37-0@icann.org> <rt-4.4.3-28527-1669845321-655.1261222-37-0@icann.org> <rt-4.4.3-14855-1670355385-1015.1261222-37-0@icann.org> <A674D9CF-25A5-41BE-A888-A34A0C29EB35@fastly.com> <89C965AA-F13D-4C7F-8743-A7D23583BB31@fastly.com> <rt-5.0.3-574994-1699900211-1337.1287496-9-0@icann.org>
In-Reply-To: <rt-5.0.3-574994-1699900211-1337.1287496-9-0@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.78.23102801
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A451C4CD23BA134DB72465C35F8B7941@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.987,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-11-13_09,2023-11-09_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 suspectscore=0 spamscore=0 mlxscore=0 bulkscore=0 adultscore=0 mlxlogscore=999 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2311060000 definitions=main-2311130153
X-Proofpoint-GUID: OeIvNSQ74r30Wd-Slv0XJF85yadXiUHT
X-Proofpoint-ORIG-GUID: OeIvNSQ74r30Wd-Slv0XJF85yadXiUHT
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.987,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-11-13_09,2023-11-09_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 malwarescore=0 mlxlogscore=999 suspectscore=0 clxscore=1015 impostorscore=0 phishscore=0 priorityscore=1501 bulkscore=0 adultscore=0 lowpriorityscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2311060001 definitions=main-2311130153
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/oGvPzuSKhnYwDV1mEY1g8DLEen8>
Subject: Re: [Tls-reg-review] [IANA #1287496] Re: Request for Assignment (draft-irtf-cfrg-aegis-aead - aead-parameters)
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: TLS REVIEW <tls-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls-reg-review/>
List-Post: <mailto:tls-reg-review@ietf.org>
List-Help: <mailto:tls-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2023 18:49:54 -0000

It's still a draft, so I'd be okay with just changing the description as requested.  (Which, yes, of course, changes the algorithm). But if the authors are in favor, that's another argument for making the change.

On 11/13/23, 1:30 PM, "tls-reg-review on behalf of Sabrina Tanamal via RT" <tls-reg-review-bounces@ietf.org <mailto:tls-reg-review-bounces@ietf.org> on behalf of iana-prot-param-comment@iana.org <mailto:iana-prot-param-comment@iana.org>> wrote:


TLS Experts, 


We received a request to update the following entry in the TLS Cipher Suites registry: 


Value: 0x13,0x07
Description: TLS_AEGIS_128L_SHA256 
DTLS-OK: Y
Recommended: N
Reference: [draft-irtf-cfrg-aegis-aead-00]


Would replacing the description as requested below be appropriate, or should we allocate a new entry? If it's the latter, which value should we assign? 


Registry: https://urldefense.com/v3/__https://www.iana.org/assignments/tls-parameters__;!!GjvTz_vk!SpksUVyfXam-og53Ca6zzd5kUmUjWNVwvNv5zYhLuKtNmhOy2If2QYoWwrOyja-Y40wWGe7WgDSX_rjat1ziXkQ$ <https://urldefense.com/v3/__https://www.iana.org/assignments/tls-parameters__;!!GjvTz_vk!SpksUVyfXam-og53Ca6zzd5kUmUjWNVwvNv5zYhLuKtNmhOy2If2QYoWwrOyja-Y40wWGe7WgDSX_rjat1ziXkQ$> 
Document: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-aegis-aead__;!!GjvTz_vk!SpksUVyfXam-og53Ca6zzd5kUmUjWNVwvNv5zYhLuKtNmhOy2If2QYoWwrOyja-Y40wWGe7WgDSX_rja_aLAsEc$ <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-aegis-aead__;!!GjvTz_vk!SpksUVyfXam-og53Ca6zzd5kUmUjWNVwvNv5zYhLuKtNmhOy2If2QYoWwrOyja-Y40wWGe7WgDSX_rja_aLAsEc$> 


The due date is December 4th, according to RFC 8447. 


Thank you,


Sabrina Tanamal
Lead IANA Services Specialist


On Fri Nov 10 13:25:01 2023, fdenis@fastly.com <mailto:fdenis@fastly.com> wrote:
> Hi Sabrina,
> 
> How this email finds you well.
> 
> The TLS Cipher Suite Registry includes the following entry:
> 
> TLS_AEGIS_256_SHA384 (0x13, 0x06)
> 
> A recently published research paper points out an issue with many of
> the currently assigned entries in that registry, and provides
> recommendations for future entries.
> 
> Following this, and before the final RFC review, we’d like to replace
> TLS_AEGIS_256_SHA384 with TLS_AEGIS_256_SHA512.
> 
> Can the name be updated, while keeping the previous value? Or does a
> new entry need to be added?
> 
> Kind regards,
> 
> -Frank.


_______________________________________________
tls-reg-review mailing list
tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org>
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/tls-reg-review__;!!GjvTz_vk!SpksUVyfXam-og53Ca6zzd5kUmUjWNVwvNv5zYhLuKtNmhOy2If2QYoWwrOyja-Y40wWGe7WgDSX_rjaMHFIGlY$ <https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/tls-reg-review__;!!GjvTz_vk!SpksUVyfXam-og53Ca6zzd5kUmUjWNVwvNv5zYhLuKtNmhOy2If2QYoWwrOyja-Y40wWGe7WgDSX_rjaMHFIGlY$>

v2.23.0 | Report a Bug | By Email