LURK Extension version 1 for (D)TLS 1.3 Authentication
draft-mglt-lurk-tls13-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

LURK                                                          D. Migault
Internet-Draft                                                  Ericsson
Intended status: Standards Track                           July 02, 2018
Expires: January 3, 2019

         LURK Extension version 1 for (D)TLS 1.3 Authentication
                        draft-mglt-lurk-tls13-00

Abstract

   This document describes the LURK Extension 'tls13' which enables
   interactions between a LURK Client and a LURK Server in a context of
   authentication with (D)TLS 1.3.

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 3, 2019.

Copyright Notice

   Copyright (c) 2018 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.

Migault                  Expires January 3, 2019                [Page 1]
Internet-Draft                LURK/TLS 1.3                     July 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  LURK Header . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  handshake_server_key  . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Request Payload . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Response Payload  . . . . . . . . . . . . . . . . . . . .   6
     3.3.  LURK Client Behavior  . . . . . . . . . . . . . . . . . .   6
     3.4.  LURK Server Behavior  . . . . . . . . . . . . . . . . . .   7
   4.  auth  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  Request Payload . . . . . . . . . . . . . . . . . . . . .   9
     4.2.  Response Payload  . . . . . . . . . . . . . . . . . . . .  10
     4.3.  LURK Client Behavior (TLS Server) . . . . . . . . . . . .  10
     4.4.  LURK Client Behavior (TLS Client) . . . . . . . . . . . .  12
       4.4.1.  Local Ticket  . . . . . . . . . . . . . . . . . . . .  13
     4.5.  LURK Server Behavior  . . . . . . . . . . . . . . . . . .  14
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  16
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  16
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   This document defines a LURK extension for TLS 1.3.  This document
   assume s the reader is familiar with [I-D.mglt-lurk-lurk] that
   describes the LURK architecture as well as the LURK Protocol and the
   integration of the LURK extensions.  The motivations for the LURK
   Extension TLS 1.3 are similar to those for the LURK extension of TLS
   1.2 [I-D.mglt-lurk-tls12].

   LURK defines an interface to a Cryptographic Service that stores the
   security credentials - Typically the PSKs and private keys.
   Interactions with the Cryptographic Service can be performed by the
   TLS Client as well as by the TLS Server.

   The TLS Server expects from the Cryptographic Service:

   o  To retrieve the necessary keys to complete the handshake.  This
      typically includes the [sender]_handshake_traffic_secret to
      generate the keys necessary to encrypt the handshake extensions
      and messages, the [sender]_application_traffic_secret_N keys to
      protect the application data or the exporter_master_secret when
      needed.

   o  To generate of Handshake message or extensions that authenticate
      the TLS Server.  This typically includes the CertificateVerify and
      Finished message.

Migault                  Expires January 3, 2019                [Page 2]
Internet-Draft                LURK/TLS 1.3                     July 2018

   o  To retrieve NewSessionTicket to enable the TLS Client to perform
      session resumption.