Secondary Certificate Authentication of HTTP Clients
draft-rosomakho-httpbis-secondary-client-certs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yaroslav Rosomakho , Jonathan Hoyland | ||
| Last updated | 2026-01-08 (Latest revision 2025-07-07) | ||
| 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
This document defines a mechanism for HTTP/2 and HTTP/3 clients to provide additional certificate-based credentials after the TLS handshake has completed, using TLS Exported Authenticators. Unlike traditional client authentication during the TLS handshake, this mechanism allows clients to present multiple certificates over the lifetime of a session.
Authors
Yaroslav Rosomakho
Jonathan Hoyland
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)