[Tls-reg-review] [IANA #1260562] Request for Assignment (draft-irtf-cfrg-aegis-aead - tls-parameters)

Hi Rich and Yoav, 

Thanks for the quick review. We have a response from the applicant: 

Indeed, since this is for TLS, that would be numbers, and if N for "recommended" is the rule for IRTF rather than IETF submissions, let's put N.

To answer the second expert's question:

The L in TLS_AEGIS_128L_SHA256 is intentional and required. Both AEGIS-128L and AEGIS-128 exist, but these are different, and incompatible algorithms.

The 128 variant could be used in a TLS cipher suite as well but was not selected in the context of this work. The 128L variant has better security bounds and is substantially faster.

Using the "TLS_AEGIS_128_SHA256" name for AEGIS-128L would be confusing, and prevent an actual AEGIS-128 variant from being registered later if needed.

====

Please let us know if you have any further questions/comments. If we don't hear from you in the next couple of days, we will proceed with the assignments. 

Thanks,
Sabrina

On Wed Nov 09 10:59:48 2022, ynir.ietf@gmail.com wrote:
> So I guess we’re in agreement.  Except for that L part.
> 
> > On 9 Nov 2022, at 12:56, Salz, Rich
> > <rsalz=40akamai.com@dmarc.ietf.org> wrote:
> >
> > The request isn't for OIDs but rather assignment of numbers. :)
> >
> > Recommended is N.  AEGIS is not being standardized by the IETF, the
> > reference is to an IRTF draft.
> >
> > DTLS-OK value is fine. The requested names are fine.
> > I suppose 0x13,0x6 and 0x13,0x07 (the next free slots) are fine.
> >
> >
> > _______________________________________________
> > tls-reg-review mailing list
> > tls-reg-review@ietf.org
> > https://www.ietf.org/mailman/listinfo/tls-reg-review