Usage of OPAQUE with TLS 1.3
draft-sullivan-tls-opaque-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Nick Sullivan , Dr. Hugo Krawczyk , Owen Friel , Richard Barnes | ||
| Last updated | 2019-09-12 (Latest revision 2019-03-11) | ||
| RFC stream | (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 describes two mechanisms for enabling the use of the OPAQUE password-authenticated key exchange in TLS 1.3.
Authors
Nick Sullivan
Dr. Hugo Krawczyk
Owen Friel
Richard Barnes
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)