New Protocols Must Require TLS 1.3
draft-rsalz-uta-require-tls13-01
| Document | Type |
Replaced Internet-Draft
(uta WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Rich Salz , Nimrod Aviram | ||
| Last updated | 2024-04-19 (Latest revision 2024-04-03) | ||
| Replaced by | draft-ietf-uta-require-tls13 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-uta-require-tls13 | |
| 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
TLS 1.2 is in widespread use and can be configured such that it provides good security properties. TLS 1.3 is also in widespread use and fixes some known deficiencies with TLS 1.2, such as removing error-prone cryptographic primitives and encrypting more of the traffic so that it is not readable by outsiders. Since TLS 1.3 use is widespread, new protocols must require and assume its existence. This prescription does not pertain to DTLS (in any DTLS version); it pertains to TLS only.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)