Application-Layer TLS
draft-friel-tls-atls-05
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Owen Friel , Richard Barnes , Max Pritikin , Hannes Tschofenig , Mark Baugher | ||
| Last updated | 2022-02-23 (Latest revision 2021-08-22) | ||
| Replaces | draft-tschofenig-layered-tls, draft-friel-tls-over-http | ||
| 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 specifies how TLS and DTLS can be used at the application layer for the purpose of establishing secure end-to-end encrypted communication security. Encodings for carrying TLS and DTLS payloads are specified for HTTP and CoAP to improve interoperability. While the use of TLS and DTLS is straight forward we present multiple deployment scenarios to illustrate the need for end-to-end application layer encryption and the benefits of reusing a widely deployed and readily available protocol. Application software architectures for building, and network architectures for deploying application layer TLS are outlined.
Authors
Owen Friel
Richard Barnes
Max Pritikin
Hannes Tschofenig
Mark Baugher
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)