Exported Authenticators in TLS
draft-ietf-tls-exported-authenticator-07

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

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07

TLS                                                          N. Sullivan
Internet-Draft                                           Cloudflare Inc.
Intended status: Standards Track                           June 05, 2018
Expires: December 7, 2018

                     Exported Authenticators in TLS
                draft-ietf-tls-exported-authenticator-07

Abstract

   This document describes a mechanism in Transport Layer Security (TLS)
   to provide an exportable proof of ownership of a certificate that can
   be transmitted out of band and verified by the other party.

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 December 7, 2018.

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.

Sullivan                Expires December 7, 2018                [Page 1]
Internet-Draft         TLS Exported Authenticator              June 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   3
   3.  Authenticator Request . . . . . . . . . . . . . . . . . . . .   3
   4.  Authenticator . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Authenticator Keys  . . . . . . . . . . . . . . . . . . .   4
     4.2.  Authenticator Construction  . . . . . . . . . . . . . . .   5
       4.2.1.  Certificate . . . . . . . . . . . . . . . . . . . . .   5
       4.2.2.  CertificateVerify . . . . . . . . . . . . . . . . . .   6
       4.2.3.  Finished  . . . . . . . . . . . . . . . . . . . . . .   7
       4.2.4.  Authenticator Creation  . . . . . . . . . . . . . . .   7
   5.  Empty Authenticator . . . . . . . . . . . . . . . . . . . . .   8
   6.  API considerations  . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  The "request" API . . . . . . . . . . . . . . . . . . . .   8
     6.2.  The "get context" API . . . . . . . . . . . . . . . . . .   9
     6.3.  The "authenticate" API  . . . . . . . . . . . . . . . . .   9
     6.4.  The "validate" API  . . . . . . . . . . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   This document provides a way to authenticate one party of a Transport
   Layer Security (TLS) communication to another using a certificate
   after the session has been established.  This allows both the client
   and server to prove ownership of additional identities at any time
   after the handshake has completed.  This proof of authentication can
   be exported and transmitted out of band from one party to be
   validated by the other party.

   This mechanism provides two advantages over the authentication that
   TLS natively provides:

   multiple identities -  Endpoints that are authoritative for multiple
      identities - but do not have a single certificate that includes
      all of the identities - can authenticate with those identities
      over a single connection.

   spontaneous authentication -  Endpoints can authenticate after a
      connection is established, in response to events in a higher-layer
      protocol, as well as integrating more context.

Sullivan                Expires December 7, 2018                [Page 2]
Internet-Draft         TLS Exported Authenticator              June 2018