RATS Attestation Stack: CoRIM, EAT, Attestation Results, CMW — draft-ietf-rats-corim, draft-ietf-rats-eat, draft-ietf-rats-ear, draft-ietf-rats-msg-wrap#
IETF 122 (Bangkok) digest Program Core pick Bangkok · 15–21 March 2025
- Tier: Core
- Why: Remote attestation is becoming the common substrate under both workload identity (device/hardware-backed proof feeding WIMSE and OAuth attestation-based auth above) and supply-chain trust (SCITT below) — this is the plumbing layer worth understanding once rather than per-consumer.
- What:
corim(Concise Reference Integrity Manifest) represents Endorsements and Reference Values a Verifier needs to appraise Evidence, in CBOR.eat(Entity Attestation Token) is an attested claims set describing an entity's state, as a CWT or JWT.ear(EAT Attestation Result) is the Verifier's output format, embedding a normalized "trustworthiness vector" for policy consumption.msg-wrap(CMW) is a common envelope for RATS' Evidence/Results/Endorsements messages, usable in CBOR protocols, JWTs/CWTs, and X.509 extensions alike. (from abstract only) - How: An Attester produces Evidence (EAT); a Verifier appraises it against CoRIM-encoded Endorsements/Reference Values and emits an EAR; CMW gives all of these a consistent wrapper so protocols don't each reinvent the envelope.
- Where applicable: General — TPM/TCG DICE-based device attestation, but architecture-neutral; increasingly the trust root that ACME device-attestation and cert-issuance workflows build on (see Adjacent, below).