Re: [lamps] WGLC for draft-ietf-lamps-cms-sha3-hash

[Russ Housley <[e-mail]>]

Daniel:
> 
> These will be useful for KEMRI with ML-KEM since it uses lots of variants of SHA3 and SHAKE under the covers so we will want a KDF using at least one of those.
>  
> While going over the draft I just found a few nits:
>  
> Section 3.1:
> Trailing braces on the following line:kmac
>                 The RSASSA PKCS#1 v1.5 is defined in [RFC8017]}}.
>  
> Section 5.1:
> “algorithm” is misspelled:
>                 [I-D.ietf-lamps-cms-kemri] is one place where algrithim identifiers
>  
> Section 6:
> Remove either “cryptographics” or “such” from the following line:
> number generators (PRNGs) to generate cryptographic such values can

These are all fixed.  Thanks for the careful read.
 
> The id-alg-hkdf-with-sha3-* object identifiers are currently TBD.  Since cms-kemri and cms-kyber implementation and interop is going on right now in the hackathon group, it would be nice to have those assigned.  Is it too late for early assignment?  Is it too early for normal assignment?  I don’t know if those OIDs will be the ones recommended by cms-kyber, but it would be nice to have some OIDs for specs that aren’t paywalled (kdf2, kdf3).

We can get early assignment if people need them for code, but normal practice is for early assignment to be temporary.  The temporary assignment becomes permanent when the RFC is published.

Russ