TLS Client Authentication via DANE TLSA records
draft-ietf-dance-client-auth-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Shumon Huque , Viktor Dukhovni , Ash Wilson | ||
| Last updated | 2023-05-12 (Latest revision 2022-11-08) | ||
| Replaces | draft-huque-dane-client-cert | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | In WG Last Call | |
| 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
The DANE TLSA protocol [RFC6698] [RFC7671] describes how to publish Transport Layer Security (TLS) server certificates or public keys in the DNS. This document updates RFC 6698 and RFC 7671. It describes how to additionally use the TLSA record to publish client certificates or public keys, and also the rules and considerations for using them with TLS.
Authors
Shumon Huque
Viktor Dukhovni
Ash Wilson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)