You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Align to V2 profile of Arm CCA Platform and Realm Tokens #54
TBD. The first step of this is going through the diff (https://author-tools.ietf.org/iddiff?url1=draft-ffm-rats-cca-token-03&url2=draft-ffm-rats-cca-token-04&difftype=--html) and seeing what's missing. A quick scan suggest that there are a couple of new optional claims in the sw component, a new platform claim (tpm binding data), and the platform challenge needs to be replaced with workload binding; but I'm not sure if that's all. (And that is going on the assumption that QR brought us up to rev03 without anything missing from that).
(note: all of this really on veraison/ccatoken, rather than evcli, per se)
OK but we've already added somethings from rev04; including the MEC policy change, which is incompatible with rev03. So if rev03 corellates to V2, then this is already not it.
Activity
yogeshbdeshpande commentedon Oct 7, 2026
@setrofim what is left to be done for this issue..?
setrofim commentedon Oct 7, 2026
TBD. The first step of this is going through the diff (https://author-tools.ietf.org/iddiff?url1=draft-ffm-rats-cca-token-03&url2=draft-ffm-rats-cca-token-04&difftype=--html) and seeing what's missing. A quick scan suggest that there are a couple of new optional claims in the sw component, a new platform claim (tpm binding data), and the platform challenge needs to be replaced with workload binding; but I'm not sure if that's all. (And that is going on the assumption that QR brought us up to rev03 without anything missing from that).
(note: all of this really on veraison/ccatoken, rather than evcli, per se)
yogeshbdeshpande commentedon Oct 7, 2026
This issue was introduced to align the CCA Token and EVCLI to Draft 03 Version which is Profile_V2 in the CCA Token Code.
So we should certainly check, if what QR has done is complete with CCA Evidence Profile 03.
We have not moved to 04 version of the draft because that will be generated as a separate requirement.
setrofim commentedon Oct 7, 2026
OK but we've already added somethings from rev04; including the MEC policy change, which is incompatible with rev03. So if rev03 corellates to V2, then this is already not it.
yogeshbdeshpande commentedon Oct 7, 2026
Yes MECPolicy change was modified to u8 from string on requirement and needs to be fully backward compatible.
Realm Instance ID strictly not required but needed on request from Anton. So may be that is what is confusing..
I just checked the CCA Evidence Profile 03 Version and all claims seem to be now implemented..
Is the evcli now contains the values for each of the following now?
arm-platform-claim-map = {
arm-platform-profile, ==> Implemented
arm-platform-challenge, ==> Implemented
arm-platform-implementation-id, ==> Implemented
arm-platform-instance-id, ==> Implemented
arm-platform-config, ==> Implemented
arm-platform-lifecycle, ==> Implemented
arm-platform-sw-components, ==> Implemented
? arm-platform-verification-service, ==> Implemented
arm-platform-hash-algo-id, ==> Implemented
arm-platform-client-id, ==> Implemented
? arm-platform-manufacturing-config, ==> Implemented
? arm-platform-extension, ==> Implemented
? arm-platform-peer-signers, ==> Implemented
? arm-platform-tbb-rotpk, ==> Implemented
}
cca-realm-claim-map = {
cca-realm-challenge, ==> Implemented
? cca-realm-profile, ==> Implemented
cca-realm-personalization-value, ==> Implemented
cca-realm-initial-measurement, ==> Implemented
cca-realm-extensible-measurements, ==> Implemented
cca-realm-hash-algo-id, ==> Implemented
cca-realm-public-key, ==> Implemented
cca-realm-public-key-hash-algo-id, ==> Implemented
cca-realm-mec-policy, ==> Implemented
}
yogeshbdeshpande commentedon Oct 13, 2026
With PR #59 and PR #63 this issue is closed