Application-Layer TLS

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Owen Friel  , Richard Barnes  , Max Pritikin  , Hannes Tschofenig  , Mark Baugher 
Last updated 2019-02-01 (latest revision 2018-07-31)
Replaces draft-tschofenig-layered-tls, draft-friel-tls-over-http
Stream (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document specifies how TLS sessions can be established at the application layer over untrusted transport between clients and services for the purposes of establishing secure end-to-end encrypted communications channels. Transport layer encodings for application layer TLS records are specified for HTTP and CoAP transport. Explicit identification of application layer TLS packets enables middleboxes to provide transport services and enforce suitable transport policies for these payloads, without requiring access to the unencrypted payload content. Multiple scenarios are presented identifying the need for end-to-end application layer encryption between clients and services, and the benefits of reusing the well- defined TLS protocol, and a standard TLS stack, to accomplish this are described. Application software architectures for building, and network architectures for deploying application layer TLS are outlined.


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.)