rfc9711v9.txt | rfc9711.txt | |||
---|---|---|---|---|
Internet Engineering Task Force (IETF) L. Lundblade | Internet Engineering Task Force (IETF) L. Lundblade | |||
Request for Comments: 9711 Security Theory LLC | Request for Comments: 9711 Security Theory LLC | |||
Category: Standards Track G. Mandyam | Category: Standards Track G. Mandyam | |||
ISSN: 2070-1721 | ISSN: 2070-1721 | |||
J. O'Donoghue | J. O'Donoghue | |||
Qualcomm Technologies Inc. | Qualcomm Technologies Inc. | |||
C. Wallace | C. Wallace | |||
Red Hound Software, Inc. | Red Hound Software, Inc. | |||
January 2025 | April 2025 | |||
The Entity Attestation Token (EAT) | The Entity Attestation Token (EAT) | |||
Abstract | Abstract | |||
An Entity Attestation Token (EAT) provides an attested claims set | An Entity Attestation Token (EAT) provides an attested claims set | |||
that describes the state and characteristics of an entity, a device | that describes the state and characteristics of an entity, a device | |||
such as a smartphone, an Internet of Things (IoT) device, network | such as a smartphone, an Internet of Things (IoT) device, network | |||
equipment, or such. This claims set is used by a relying party, | equipment, or such. This claims set is used by a relying party, | |||
server, or service to determine the type and degree of trust placed | server, or service to determine the type and degree of trust placed | |||
skipping to change at line 486 ¶ | skipping to change at line 486 ¶ | |||
uses the term "label" to refer to CBOR map keys to avoid confusion | uses the term "label" to refer to CBOR map keys to avoid confusion | |||
with cryptographic keys.) | with cryptographic keys.) | |||
Claim Value: The value portion of the claim. A claim value can be | Claim Value: The value portion of the claim. A claim value can be | |||
any CBOR data item or JSON value. | any CBOR data item or JSON value. | |||
Claims Set: The CBOR map or JSON object that contains the claims | Claims Set: The CBOR map or JSON object that contains the claims | |||
conveyed by the CWT or JWT. | conveyed by the CWT or JWT. | |||
This document reuses terminology from RATS Architecture [RFC9334]; | This document reuses terminology from RATS Architecture [RFC9334]; | |||
note that EAT does not capitalize RATS terms like “evidence” for | note that EAT does not capitalize RATS terms like "evidence" for | |||
easier readability: | easier readability: | |||
Attester: A role performed by an entity (typically a device) whose | Attester: A role performed by an entity (typically a device) whose | |||
evidence must be appraised in order to infer the extent to which | evidence must be appraised in order to infer the extent to which | |||
the attester is considered trustworthy, such as when deciding | the attester is considered trustworthy, such as when deciding | |||
whether it is authorized to perform some operation. | whether it is authorized to perform some operation. | |||
Verifier: A role that appraises the validity of evidence about an | Verifier: A role that appraises the validity of evidence about an | |||
attester and produces attestation results to be used by a relying | attester and produces attestation results to be used by a relying | |||
party. | party. | |||
End of changes. 2 change blocks. | ||||
2 lines changed or deleted | 2 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |