The Entity Attestation Token (EAT)
draft-ietf-rats-eat-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Giridhar Mandyam , Laurence Lundblade , Miguel Ballesteros , Jeremy O'Donoghue | ||
| Last updated | 2020-08-23 (Latest revision 2020-02-20) | ||
| Replaces | draft-mandyam-rats-eat | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
INTDIR Telechat review
(of
-21)
by Haoyu Song
Ready w/issues
GENART Last Call review
(of
-21)
by Ines Robles
Ready w/nits
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Associated WG milestones |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
An Entity Attestation Token (EAT) provides a signed (attested) set of claims that describe state and characteristics of an entity, typically a device like a phone or an IoT device. These claims are used by a relying party to determine how much it wishes to trust the entity. An EAT is either a CWT or JWT with some attestation-oriented claims. To a large degree, all this document does is extend CWT and JWT. Contributing TBD
Authors
Giridhar Mandyam
Laurence Lundblade
Miguel Ballesteros
Jeremy O'Donoghue
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)