-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Composite Attester/Device Description #22
Comments
This sounds very interesting. Can you elaborate a bit more, e.g.,
|
I think it'd be good to clearly state here what the expected outcome of the discussion would be. A position paper? Some form of input for the RATS / TCG / ${RELEVANT_SDO}? Other? (CC: @TheBankster who put forward the need for a "composite attesters" track in the SIG.) |
Agree that a whitepaper or a guidance document on the CCC's position on composite attester modelling (token format) and also how the Verification should happen for the overall composite device, would benefit the community. |
@deeglaze on 27th Feb 2024 call: A few separate/separable dimensions to consider:
|
As per RATS Architecture, Composite Device comprises of multiple sub-attester and a lead attester.
A more deeper discussion is required in CCC as to how different member organisation would want to see the Composite Attester Modelling and how the Format of the Attestation Token would span out meeting all the necessary security objectives
The text was updated successfully, but these errors were encountered: