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

Yoav or Nick, 

Do you also approve changing the description as requested below? 

Thanks,
Sabrina

On Mon Nov 13 18:49:57 2023, rsalz@akamai.com wrote:
> 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$>
> 
> 
> 