Add CCA Token example #176
Conversation
| /arm-platform-implementation-id/ 2396: h’0000000000000000000000000000000000000000000000000000000000000001’ | ||
| } | ||
|
|
||
| / This is a full CWT-format token. The payload is a sample / |
There was a problem hiding this comment.
| / This is a full CWT-format token. The payload is a sample / | |
| / This is a full CWT-formatted token. The payload is a sample |
| The Confidential Compute Architecture (CCA) Platform Token is described in | ||
| {{I-D.ffm-rats-cca-token}} and is also based on the EAT format. Although the | ||
| full CCA attestation is composed of realm and platform evidence, for the purposes | ||
| of this example only the platform token is provided. |
There was a problem hiding this comment.
| of this example only the platform token is provided. | |
| of this example only the Platform token is provided. |
|
Thanks for the contribution, Giri. The text is good but I am wondering why you only included the Platform Evidence token instead of also the Realm token. Could you explain? |
Co-authored-by: Hannes Tschofenig <[email protected]>
Co-authored-by: Hannes Tschofenig <[email protected]>
Co-authored-by: Hannes Tschofenig <[email protected]>
Co-authored-by: Hannes Tschofenig <[email protected]>
I had not created a sample realm claim set yet, and this issue was pending for a while so I wanted to get something in for review. I can add a realm token example. One more question: will a single OID be allocated for CCA token? Or can different OID's be assigned for the different CCA attestation options? I think t least for CSR's there could potentially be three: (a) Platform token only, (b) DIrect model: Platform token + realm claims set, where a hash of the realm claims set is included in the platform token payload as challenge data, and (c) Delegated model: Platform token + Realm Attestation Token, where Platform token includes the Realm Attestation PubKey as challenge data. Another option is to just assign one OID for CCA, and have the variants be identified by CBOR tags. |
To address #172