Using Early Data in DOTS
draft-boucadair-dots-earlydata-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mohamed Boucadair , Tirumaleswar Reddy.K | ||
| Last updated | 2019-08-02 (Latest revision 2019-01-29) | ||
| 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 discusses to what extent it is safe to send DOTS signal channel messages as Early Data in TLS 1.3. This document is not intended to be published as an RFC. It is edited to help understanding the conclusion about the safeness of using DOTS signal channel messages as early data.
Authors
Mohamed Boucadair
Tirumaleswar Reddy.K
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)