Limited Use of Remote Keys, Protocol and Reference.
draft-hallambaker-lurk-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-03-18
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                                    P. Hallam-Baker
Internet-Draft                                         Comodo Group Inc.
Intended status: Informational                            March 18, 2016
Expires: September 19, 2016

          Limited Use of Remote Keys, Protocol and Reference.
                       draft-hallambaker-lurk-00

Abstract

   The Limited Use of Remote Keys (LURK) BOF has been scheduled with the
   objective of discussing approaches to mitigating security risks to
   TLS private keys.  In particular in situations where a Content
   Delivery Network (CDN) is used to deliver content and thus the party
   that is being authenticated is not the party that the user is
   attempting to authenticate.

   Three classes of solution are considered, short term credentials, a
   remote service offering to perform private key operations and a
   remote service that is further constrained through the use of some
   form of threshold approach.  A JSON/HTTP protocol implementing the
   second and third protocol is demonstrated and documented.

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 http://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 September 19, 2016.

Copyright Notice

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

Hallam-Baker           Expires September 19, 2016               [Page 1]
Internet-Draft         LURK Protocol and Reference            March 2016

   (http://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.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Related Specifications  . . . . . . . . . . . . . . . . .   4
     1.3.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Limited Life Credentials  . . . . . . . . . . . . . . . .   7
     2.2.  Private Key Service . . . . . . . . . . . . . . . . . . .   8
     2.3.  Partial Key Service . . . . . . . . . . . . . . . . . . .   9
   3.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   9
     3.1.  Establishing Trust Relationships  . . . . . . . . . . . .  10
       3.1.1.  Manual Administration . . . . . . . . . . . . . . . .  10
       3.1.2.  Using the Mathematical Mesh . . . . . . . . . . . . .  10
     3.2.  Service Connection  . . . . . . . . . . . . . . . . . . .  11
     3.3.  Creation of necessary key pairs . . . . . . . . . . . . .  12
     3.4.  Private key decryption  . . . . . . . . . . . . . . . . .  14
     3.5.  Private key Agreement . . . . . . . . . . . . . . . . . .  15
     3.6.  Private key signature . . . . . . . . . . . . . . . . . .  15
     3.7.  Key Disposal  . . . . . . . . . . . . . . . . . . . . . .  16
   4.  Lurk Key Service Reference  . . . . . . . . . . . . . . . . .  16
     4.1.  Request Messages  . . . . . . . . . . . . . . . . . . . .  17
       4.1.1.  Message: LurkRequest  . . . . . . . . . . . . . . . .  17
       4.1.2.  Message: LurkKeyRequest . . . . . . . . . . . . . . .  17
       4.1.3.  Message: LurkResponse . . . . . . . . . . . . . . . .  17
       4.1.4.  Successful Response Codes . . . . . . . . . . . . . .  18
       4.1.5.  Warning Response Codes  . . . . . . . . . . . . . . .  18
       4.1.6.  Error Response Codes  . . . . . . . . . . . . . . . .  19
       4.1.7.  Structure: Version  . . . . . . . . . . . . . . . . .  19
       4.1.8.  Structure: Encoding . . . . . . . . . . . . . . . . .  20
       4.1.9.  Structure: KeyParameters  . . . . . . . . . . . . . .  20
       4.1.10. Structure: ParametersRSA  . . . . . . . . . . . . . .  20
       4.1.11. Structure: ParametersECDH . . . . . . . . . . . . . .  21
     4.2.  Transaction: Hello  . . . . . . . . . . . . . . . . . . .  21
Show full document text