---
# System prepended metadata

title: 'Attestation: Attestation Results for Secure Interactions'

---

# Attestation: Attestation Results for Secure Interactions
Moderator: Felix

# Thomas Hardjono & Henk Birkholz

Roll Call:
- Aeva Black
- Henk
- Thomas F.
- Felix
- Dave Thaler
- Shanwei
- Ned Smith
- Thomas H.
- Dan M.
- Muhammad Usama Sardar
- Yogesh
- Vinnie Scarlata

Discussion:

- IETF resources
    - [RATS WG](https://datatracker.ietf.org/doc/draft-ietf-rats-architecture/)
    - [draft-voit-rats-attestation-results](https://datatracker.ietf.org/doc/draft-voit-rats-attestation-results/)
        - That's the list of most common data artifacts needed by verifiers
    - [GitHub](https://github.com/ietf-rats/draft-voit-rats-attestation-results)
    - other claims (mainly from Evidence but may be copied into AR's):
        - [RATS EAT](https://tools.ietf.org/wg/rats/draft-ietf-rats-eat/)
        - [RATS SUIT](https://tools.ietf.org/id/draft-birkholz-rats-suit-claims-01.txt)

How does the relying party make sense of incoming attestation results from verifiers. (Different types of TEEs, HW, Manufacturers)

- 3 categories of features:
    - guest vm _in walled garden_ (SGX, SEV, ACCA = Arm Realms, TDX)
    - processes
    - application

- Evidence = Identity + Trustworthiness Claims + Freshness
- Normalization of claims

- Built upon [IETF's RATS architecture](https://datatracker.ietf.org/doc/draft-ietf-rats-architecture/)

- Evidence is fresh when it still reflects the state of the Attester
    - the discussion is still ongoing about how to guarantee freshness
    - Evidence freshness and/or Attestation Results freshness typically relies on the verifier to check (part of the Appraisal Policy)
    - It's very protocol and scenario-specific, so singular solution cannot be suggested to solve them all
- Veraison might be the first implementation? (First public?)
- Does EAT define nested claims?
    - It defines a _way_ to nest, but does not specify a name.
- [Aeva] If a dev wanted to start coding against the standards you're developing, where could they look?
  - [Henk] it's very early dayst hoping that the CCC-Attestation workstream will produce something by EOY'21.
  - [Thomas] EAT open-source implementations:
    * https://github.com/laurencelundblade/ctoken - C 
    * https://github.com/veraison/eat - golang 
- [Dan] How would you describe the difference in describing structure in EAT vs JSON (I understand EAT supports JSON or CBOR, but I mean json already provides structure)?
  - [Thomas] EAT uses JSON or CBOR to define either flat or structured "claims", i.e., name-value pairs with well-defined semantics



Follow ups:
- *what cool stuff did you learn?*
- *what should the community do next?*
