Skip to main content

The Entity Attestation Token (EAT)

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: The IESG <>,,,,,,
Subject: Protocol Action: 'The Entity Attestation Token (EAT)' to Proposed Standard (draft-ietf-rats-eat-24.txt)

The IESG has approved the following document:
- 'The Entity Attestation Token (EAT)'
  (draft-ietf-rats-eat-24.txt) as Proposed Standard

This document is the product of the Remote ATtestation ProcedureS Working

The IESG contact persons are Paul Wouters and Roman Danyliw.

A URL of this Internet-Draft is:

Ballot Text

Technical Summary

   An Entity Attestation Token (EAT) provides an attested claims set
   that describes state and characteristics of an entity, a device like
   a smartphone, IoT device, network equipment or such.  This claims set
   is used by a relying party, server or service to determine how much
   it wishes to trust the entity.

   An EAT is either a CBOR Web Token (CWT) or JSON Web Token (JWT) with
   attestation-oriented claims.

Working Group Summary

In additional to the history noted in the shepherd report, the WG held significant discussions on which claims should be sought for early allocation.

Document Quality

   EAT Libraries:
        - CBOR Formats - open source project
                o Rust:
        - EAT library - open source project
                o C:
        - A command line utility based on EAT library - open source project
                o C:
   EAT Profiles:
        - PSA
                o Golang:
                o C:
                o Python:
        - CCA
                o Golang:
                o C:
        - FIDO FDO - open source project
                o Java:
        - Global Platform - very early code of an EAT profile, may evolve into
        open source
        - Microsoft Azure Attestation - proprietary


   The Document Shepherd for this document is Ned Smith. The Responsible
   Area Director is Roman Danyliw.

RFC Editor Note