The Entity Attestation Token (EAT)
draft-mandyam-rats-eat-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Giridhar Mandyam , Laurence Lundblade , Miguel Ballesteros , Jeremy O'Donoghue | ||
| Last updated | 2019-03-24 | ||
| Replaced by | draft-ietf-rats-eat | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-rats-eat | |
| 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 attestation format based on concise binary object representation (CBOR) is proposed that is suitable for inclusion in a CBOR Web Token (CWT), know as the Entity Attestation Token (EAT). The associated data can be used by a relying party to assess the security state of a remote device or module. 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.)