Signed Public Key and Challenge
draft-leggett-spkac-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-05
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized 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)
Internet Engineering Task Force                          G. Leggett, Ed.
Internet-Draft                                           Pepperpot Media
Intended status: Informational                            D.W. van Gulik
Expires: 7 September 2020                WebWeaving Internet Engineering
                                                            6 March 2020

                    Signed Public Key and Challenge
                         draft-leggett-spkac-00

Abstract

   This memo describes the Signed Public Key and Challenge (SPKAC), a
   syntax to provide Proof-of-Possession of a Public Key to support
   federated (client) certificate enrolment.

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 7 September 2020.

Copyright Notice

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

Leggett & van Gulik     Expires 7 September 2020                [Page 1]
Internet-Draft                    SPKAC                       March 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
     1.2.  Historical  . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Signed Public Key and Challenge Profile . . . . . . . . . . .   3
     2.1.  spki  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  challenge . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  publicKeyAndChallenge . . . . . . . . . . . . . . . . . .   3
     2.4.  signatureAlgorithm  . . . . . . . . . . . . . . . . . . .   4
     2.5.  signature . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  ASN.1 Module SPKAC  . . . . . . . . . . . . . . . . . . . . .   4
   4.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
     6.1.  Use of the MD5 Message-Digest Algorithm . . . . . . . . .   7
     6.2.  Clear Text Challenge and Public Key . . . . . . . . . . .   8
     6.3.  UI/UX Denial of Service Design Issues . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   During a certificate enrollment process between a client (browser)
   and a certificate authority, the certificate authority requires that
   the client provide proof-of-possession of the public key of the
   certificate that will be signed by the certificate authority.

   The Signed Public Key and Challenge consists of a public key and an
   optional challenge, collectively signed by the private key of the end
   entity requesting certification.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

1.2.  Historical

   The SPKAC protocol was originally used by the Netscape web browser as
   part of their implementation of what eventually became the HTML5
   [W3C.REC-html5-20141028] keygen tag.  The keygen tag allowed a web
   browser to request a (client) certificate from a certificate
   authority over the world wide web, and the SPKAC protocol ensured the
   web browser possessed the key being signed by the certificate

Leggett & van Gulik     Expires 7 September 2020                [Page 2]
Internet-Draft                    SPKAC                       March 2020
Show full document text