The Entity Attestation Token (EAT)
RFC 9711
Revision differences
Document history
Date | By | Action |
---|---|---|
2025-05-02
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
2025-05-01
|
(System) | IANA registries were updated to include RFC9711 |
2025-04-30
|
(System) | Received changes through RFC Editor sync (created document RFC 9711, created became rfc relationship between draft-ietf-rats-eat and RFC 9711, set abstract to 'An … Received changes through RFC Editor sync (created document RFC 9711, created became rfc relationship between draft-ietf-rats-eat and RFC 9711, set abstract to '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.', set pages to 85, set standardization level to Proposed Standard, added RFC published event at 2025-04-30) |
2025-04-30
|
(System) | RFC published |