Remote Attestation Architecture
draft-thaler-rats-architecture-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dave Thaler | ||
| Last updated | 2020-05-07 (Latest revision 2019-11-04) | ||
| Replaced by | draft-ietf-rats-architecture | ||
| 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-architecture | |
| 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
In network protocol exchanges, it is often the case that one entity (a relying party) requires evidence about the remote peer (and system components [RFC4949] thereof), in order to assess the trustworthiness of the peer. This document describes an architecture for such remote attestation procedures (RATS), which enable relying parties to decide whether to consider a remote system component trustworthy or not.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)