[Teep] [Hackathon 1/3] Update: TEEP Agent / TAM / Verifier demo for IETF 125 Hackathon (TEEP, RATS, SUIT)

[Ken Takayama <[e-mail]>]

Dear TEEP, RATS, and SUIT WGs,

For IETF 124 we presented a demo implementation consisting of a
TEEP Agent, TAM, and Verifier using the Background Check Model.

We have now updated this demo for the IETF 125 Hackathon.

Repository:
https://github.com/s-miyazawa/teep-wasm-demo

This implementation integrates specifications from multiple WGs:

• TEEP – protocol between the TEEP Agent and TAM
• RATS – remote attestation using EAT
• SUIT – installation and reporting of Trusted Components

Some highlights of the update:

1. A database and management console for the TAM were added to make it
   easier to manage TEEP Agents and Trusted Components.

2. Inside an Intel SGX enclave (simulation mode), the TEEP Agent now
   receives a YOLOv8 object detection application as a WebAssembly
   module and executes it.

3. Remote attestation is implemented by binding the TEEP Agent public
   key to an EAT (Entity Attestation Token), allowing the TAM to trust
   the Agent key after successful verification.

4. Trusted Components are installed using a SUIT Manifest, and the
   installation results are reported from the TEEP Agent to the TAM
   using a SUIT Report.

While implementing the system according to the specifications, we
encountered several areas where implementation choices are required.
Some of these observations may be useful for other implementers.

I will share two follow-up emails describing these implementation
experiences in more detail.

Feedback from implementers across the TEEP, RATS, and SUIT communities
would be very welcome.

Best regards,
Ken