Closed thomas-fossati closed 6 months ago
The TCG specification is publicly available here: https://trustedcomputinggroup.org/wp-content/uploads/DICE-Attestation-Architecture-Version-1.1-Revision-18_pub.pdf
Given cmw I-D more recently included cmw-collection, would it make sense for it to also define an ASN.1 form and register an OID?
The TCG specification is publicly available here: https://trustedcomputinggroup.org/wp-content/uploads/DICE-Attestation-Architecture-Version-1.1-Revision-18_pub.pdf
My bad! I missed this definition from DICE-AA:
tcg-dice-conceptual-message-wrapper OBJECT IDENTIFIER ::= {tcg-dice 9}
I guess it can be used as-is?
Given cmw I-D more recently included cmw-collection, would it make sense for it to also define an ASN.1 form and register an OID?
OK, what's left is registering one OID for the collection, i.e.:
cmw-collection OBJECT IDENTIFIER ::= { TBD }
CMWCollection ::= OCTET STRING
@hannestschofenig @nedmsmith?
LGTM
Current work in TCG DICE and IETF "attested CSR" requires embedding CMWs in X.509 artefacts (certs and CSRs).
We should register the relevant OIDs with IANA.