IETF Logo Mail Archive

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

Sabrina Tanamal via RT <iana-prot-param-comment@iana.org> Mon, 13 November 2023 18:30 UTC

Return-Path: <iana-shared@icann.org>
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 8DC0CC1522D3 for <tls-reg-review@ietfa.amsl.com>; Mon, 13 Nov 2023 10:30:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.634
X-Spam-Level:
X-Spam-Status: No, score=-0.634 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MISSING_HEADERS=1.021, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=no autolearn_force=no
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 I5k9cZWSCS3Q for <tls-reg-review@ietfa.amsl.com>; Mon, 13 Nov 2023 10:30:12 -0800 (PST)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE369C151707 for <tls-reg-review@ietf.org>; Mon, 13 Nov 2023 10:30:11 -0800 (PST)
Received: from request6.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id ABB75E13DE for <tls-reg-review@ietf.org>; Mon, 13 Nov 2023 18:30:11 +0000 (UTC)
Received: by request6.lax.icann.org (Postfix, from userid 48) id A9C03150EFB; Mon, 13 Nov 2023 18:30:11 +0000 (UTC)
RT-Owner: sabrina.tanamal
From: Sabrina Tanamal via RT <iana-prot-param-comment@iana.org>
Reply-To: iana-prot-param-comment@iana.org
In-Reply-To: <89C965AA-F13D-4C7F-8743-A7D23583BB31@fastly.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>
Message-ID: <rt-5.0.3-574994-1699900211-1337.1287496-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1287496
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: sabrina.tanamal@icann.org
CC: tls-reg-review@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Mon, 13 Nov 2023 18:30:11 +0000
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/afSqYzGFiQ43xcJVpUCjqXvT1F0>
Subject: [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
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:30:15 -0000

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://www.iana.org/assignments/tls-parameters
Document: https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-aegis-aead

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 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.

v2.23.0 | Report a Bug | By Email