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
One common attestation flow is where a device supplies claims/proof to an attestation server, which grants it a token (or cert chain, or quote, or whatever other synonym you want) that it can supply to various relying parties.
It might be desirable for OTrP to integrate with standard attestation mechanisms rather than define its own. The GetDeviceStateResponse message looks very similar to what one would want to supply to an attestation server. Should a TAM be able to return an attestation token/quote to the device? Or should attestation be done prior to sending the GetDeviceStateResponse and pass the token in the GetDeviceStateResponse?
It seems to me that it would be good if the TAM could return the attestation token/quote to the device, regardless of whether the TAM gets it from an attestation server, or the TAM is itself an attestation server.
One common attestation flow is where a device supplies claims/proof to an attestation server, which grants it a token (or cert chain, or quote, or whatever other synonym you want) that it can supply to various relying parties.
It might be desirable for OTrP to integrate with standard attestation mechanisms rather than define its own. The GetDeviceStateResponse message looks very similar to what one would want to supply to an attestation server. Should a TAM be able to return an attestation token/quote to the device? Or should attestation be done prior to sending the GetDeviceStateResponse and pass the token in the GetDeviceStateResponse?
It seems to me that it would be good if the TAM could return the attestation token/quote to the device, regardless of whether the TAM gets it from an attestation server, or the TAM is itself an attestation server.
This is related to architecture issue ietf-teep/architecture#17
The text was updated successfully, but these errors were encountered: