TLS Trust Anchor Identifiers
draft-beck-tls-trust-anchor-ids-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bob Beck , David Benjamin , Devon O'Brien , Kyle Nekritz | ||
| Last updated | 2024-12-18 | ||
| Replaced by | draft-ietf-tls-trust-anchor-ids | ||
| 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-tls-trust-anchor-ids | |
| 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
This document defines the TLS Trust Anchors extension, a mechanism for relying parties to convey trusted certification authorities. It describes individual certification authorities more succinctly than the TLS Certificate Authorities extension. Additionally, to support TLS clients with many trusted certification authorities, it supports a mode where servers describe their available certification paths and the client selects from them. Servers may describe this during connection setup, or in DNS for lower latency.
Authors
Bob Beck
David Benjamin
Devon O'Brien
Kyle Nekritz
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)