Handling Multiple Verifiers in the RATS Architecture
draft-zhang-rats-multiverifiers-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | zhang jun , Houda Labiod , Tieyan Li , Thanassis Giannetsos , Henk Birkholz | ||
| Last updated | 2025-04-24 (Latest revision 2024-10-21) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 the IETF Remote Attestation Procedures (RATS) architecture, a Verifier accepts Evidence and generates Attestation Results needed by Relying Parties. This document provides a solution to inconsistent behaviors of the Verifier in the RATS architecture by introducing a mechanism to aggregate Attestation Results collected from multiple Verifiers at the Relying Party while simplifying its policy and operation.
Authors
zhang jun
Houda Labiod
Tieyan Li
Thanassis Giannetsos
Henk Birkholz
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)