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

[Russ Housley <[e-mail]>]

Roman:

There are four OIDs to be assigned by IANA in this Internet-Draft:

   id-alg OBJECT IDENTIFIER ::= { iso(1) member-body(2)
       us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) 3 }

   id-alg-hkdf-with-sha3-224 OBJECT IDENTIFIER ::= { id-alg TBD1 }

   id-alg-hkdf-with-sha3-256 OBJECT IDENTIFIER ::= { id-alg TBD2 }

   id-alg-hkdf-with-sha3-384 OBJECT IDENTIFIER ::= { id-alg TBD3 }

   id-alg-hkdf-with-sha3-512 OBJECT IDENTIFIER ::= { id-alg TBD4 }

Is it possible and practical to get these OIDs permanently assigned through the early assignment process?  As you can see blow, people want to start implementing.

Russ


> From: "Daniel Van Geest" <[e-mail]>
> Subject: RE: [lamps] WGLC for draft-ietf-lamps-cms-sha3-hash
> Date: January 31, 2024 at 12:51:16 PM EST
> To: "'Russ Housley'" <[e-mail]>
> Cc: "'SPASM'" <[e-mail]>
> 
>  
>  
> From: Russ Housley <[e-mail] <mailto:[e-mail]>> 
> Sent: Wednesday, January 31, 2024 5:33 PM
> To: Daniel Van Geest <[e-mail] <mailto:[e-mail]>>
> Cc: SPASM <[e-mail] <mailto:[e-mail]>>
> Subject: Re: [lamps] WGLC for draft-ietf-lamps-cms-sha3-hash
>  
> 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.
>  
> I’m not sure what this is supposed to mean.  Don’t release any software using the temporary assignments until the RFC is published and they become permanent?  We’d like these for interop testing of cms-kemri and cms-kyber, surely this will be an RFC before both of those are, so at least I have no intention of releasing before this is an RFC.
>  
> Russ