CurrentPROPOSED STANDARDIETF stream

RFC 9711: The Entity Attestation Token (EAT)

In plain English — editorial summary, not part of the RFC

An Entity Attestation Token (EAT) provides an attested claims set that describes the state and characteristics of an entity, a device such as a smartphone, an Internet of Things (IoT) device, network equipment, or such. This claims set is used by a relying party, server, or service to determine the type and degree of trust placed in the entity. An EAT is either a CBOR Web Token (CWT) or a JSON Web Token (JWT) with attestation-oriented claims.

Document record

Document ID
RFC9711
Published
April 2025
Authors
L. Lundblade; G. Mandyam; J. O'Donoghue; C. Wallace
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
85
Also known as

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9711-the-entity-attestation-token-eat