A Flags Extension for TLS 1.3
draft-ietf-tls-tlsflags-12
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Author | Yoav Nir | ||
Last updated | 2024-03-12 (Latest revision 2023-07-23) | ||
Replaces | draft-nir-tls-tlsflags | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Waiting for Implementation | |
Associated WG milestone |
|
||
Document shepherd | Sean Turner | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Yes | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | Christopher Wood <caw@heapingbits.net>, sean@sn3rd.com |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
A number of extensions are proposed in the TLS working group that carry no interesting information except the 1-bit indication that a certain optional feature is supported. Such extensions take 4 octets each. This document defines a flags extension that can provide such indications at an average marginal cost of 1 bit each. More precisely, it provides as many flag extensions as needed at 4 + the order of the last set bit divided by 8.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)