Russ suggested Entrust could just assign the OIDs for composite sigs since we maintain an OID repository. Discuss this with the authors group and add to the next version -13?
From Russ: ": If you are going to use the Entrust OID arc for the module assignment, why not assign it now."
For example, the module assignment could be:
Composite-Signatures-2023
{ joint-iso-itu-t(2) country(16) us(840) organization(1) entrust(114027)
algorithm(80) composite(8) id-composite-signatures-2023 (1) }
Mike and I discussed, we think having IANA assignment would make it more official and not look like it is only for Entrust. The group decided that IANA assignment is the way to go, this will align with Composite KEM as well
From: https://github.com/EntrustCorporation/draft-ounsworth-composite-sigs/issues/126
Russ suggested Entrust could just assign the OIDs for composite sigs since we maintain an OID repository. Discuss this with the authors group and add to the next version -13?
From Russ: ": If you are going to use the Entrust OID arc for the module assignment, why not assign it now."
For example, the module assignment could be: Composite-Signatures-2023 { joint-iso-itu-t(2) country(16) us(840) organization(1) entrust(114027) algorithm(80) composite(8) id-composite-signatures-2023 (1) }
Today we have: Composite-Signatures-2023 { joint-iso-itu-t(2) country(16) us(840) organization(1) entrust(114027) algorithm(80) id-composite-signatures-2023 (TBDMOD) }
And in Composite KEM we are using (for comparison):
Composite-KEM-2023 {iso(1) identified-organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) id-mod-composite-kems(TBDMOD) }
Mike and I discussed, we think having IANA assignment would make it more official and not look like it is only for Entrust. The group decided that IANA assignment is the way to go, this will align with Composite KEM as well