Re: [lamps] Dilithium OIDs per security level?

["Kampanakis, Panos" <[e-mail]>]

Hi Mike,

Yes, the OIDs will be hardcoded per level. They will not be parametrized as this has caused problems in the past.

Note that NIST will assign these OIDs, they will not be allocated by IANA.


From: Spasm <[e-mail]> On Behalf Of Mike Ounsworth
Sent: Saturday, November 19, 2022 6:27 PM
To: 'LAMPS' <[e-mail]>
Subject: [EXTERNAL] [lamps] Dilithium OIDs per security level?


CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.


Hi Jake, Panos, Sean, Bas,

I could use some clarification on which OIDs you're planning to register cause I'm trying to cross-reference them when defining all the composite pairs.

The current version of draft-ietf-lamps-dilithium-certificates-00 has

id-dilithiumTBD which you seem to be using for the signature algorithm.




   id-dilithiumTBD OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)

            country(16) us(840) organization(1) gov(101) csor(3)

            nistAlgorithm(4) sigAlgs(3) TBD }


And also pk-dilithiumTBD which you seem to be using for the public key.

  PublicKeys PUBLIC-KEY ::= {
    -- This expands PublicKeys from RFC 5912
    pk-dilithiumTBD |
    pk-TBD-TBD,
    ...
  }


Next question: are you going to register those per level; ie id-dilithium2, id-dilithium3, id-dilithium5?

---
Mike Ounsworth
Software Security Architect, Entrust

Any email and files/attachments transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.