A Flags Extension for TLS 1.3
draft-nir-tls-tlsflags-02
| Document | Type | Replaced Internet-Draft (tls WG) | |
|---|---|---|---|
| Last updated | 2019-08-08 (latest revision 2019-07-23) | ||
| Replaced by | draft-ietf-tls-tlsflags | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-tls-tlsflags | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-nir-tls-tlsflags-02.txt
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
Yoav Nir (ynir.ietf@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)