Application-Layer TLS
draft-friel-tls-atls-03

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Replaces draft-tschofenig-layered-tls, draft-friel-tls-over-http
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           O. Friel
Internet-Draft                                                 R. Barnes
Intended status: Standards Track                             M. Pritikin
Expires: January 9, 2020                                           Cisco
                                                           H. Tschofenig
                                                                Arm Ltd.
                                                              M. Baugher
                                                              Consultant
                                                           July 08, 2019

                         Application-Layer TLS
                        draft-friel-tls-atls-03

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 9, 2020.

Friel, et al.            Expires January 9, 2020                [Page 1]
Internet-Draft                    ATLS                         July 2019

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Application Layer End-to-End Security Use Cases . . . . . . .   4
     3.1.  Bootstrapping Devices . . . . . . . . . . . . . . . . . .   4
     3.2.  Constrained Devices . . . . . . . . . . . . . . . . . . .   5
   4.  ATLS Goals  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Architecture Overview . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Application Architecture  . . . . . . . . . . . . . . . .   7
     5.2.  Functional Design . . . . . . . . . . . . . . . . . . . .  13
     5.3.  Network Architecture  . . . . . . . . . . . . . . . . . .  15
   6.  ATLS Session Establishment  . . . . . . . . . . . . . . . . .  16
   7.  ATLS over HTTP Transport  . . . . . . . . . . . . . . . . . .  18
     7.1.  Protocol Summary  . . . . . . . . . . . . . . . . . . . .  18
     7.2.  Content-Type Header . . . . . . . . . . . . . . . . . . .  19
     7.3.  HTTP Status Codes . . . . . . . . . . . . . . . . . . . .  19
     7.4.  ATLS Session Tracking . . . . . . . . . . . . . . . . . .  19
     7.5.  Session Establishment and Key Exporting . . . . . . . . .  19
     7.6.  Illustrative ATLS over HTTP Session Establishment . . . .  19
     7.7.  ATLS and HTTP CONNECT . . . . . . . . . . . . . . . . . .  20
   8.  ATLS over CoAP Transport  . . . . . . . . . . . . . . . . . .  23
   9.  Key Exporting and Application Data Encryption . . . . . . . .  24
     9.1.  OSCORE  . . . . . . . . . . . . . . . . . . . . . . . . .  25
     9.2.  COSE  . . . . . . . . . . . . . . . . . . . . . . . . . .  26
   10. TLS Ciphersuite to COSE/OSCORE Algorithm Mapping  . . . . . .  26
   11. TLS Extensions  . . . . . . . . . . . . . . . . . . . . . . .  27
     11.1.  The "oscore_connection_id" Extension . . . . . . . . . .  27
     11.2.  The "cose_ext" Extension . . . . . . . . . . . . . . . .  27
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  28
Show full document text