%% You should probably cite draft-friel-tls-atls-05 instead of this revision.
@techreport{friel-tls-atls-02,
    number =    {draft-friel-tls-atls-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-friel-tls-atls/02/},
    author =    {Owen Friel and Richard Barnes and Max Pritikin and Hannes Tschofenig and Mark Baugher},
    title =     {{Application-Layer TLS}},
    pagetotal = 35,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {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.},
}