The RPC named 'basic-trust-establishment' uses the 'tpm20-signature scheme',
this may not be compatible with an implementation of this module on devices
only having a TPM 1.2. Additionally, the output for this RPC uses the
'tpm20-attestation-key-identifier' which may also have the same problem.
Therefore, two new RPCs such as 'tpm12-trust-establishment' and
'tpm20-trust-establishment' may need to be created to prevent ambiguity during
implementation.
The RPC named 'basic-trust-establishment' uses the 'tpm20-signature scheme', this may not be compatible with an implementation of this module on devices only having a TPM 1.2. Additionally, the output for this RPC uses the 'tpm20-attestation-key-identifier' which may also have the same problem. Therefore, two new RPCs such as 'tpm12-trust-establishment' and 'tpm20-trust-establishment' may need to be created to prevent ambiguity during implementation.
@Puru Kulkarni https://mailarchive.ietf.org/arch/msg/rats/bxEzxleXX69--KpDO8L_PBJZXtw