Additional Methods for Generating Subject Key Identifiers
draft-turner-additional-methods-4kis-09

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-08-27
Stream ISE
Intended RFC status (None)
Formats pdf htmlized bibtex
IETF conflict review conflict-review-turner-additional-methods-4kis
Stream ISE state Response to Review Needed
Consensus Boilerplate Unknown
Document shepherd None
IESG IESG state I-D Exists::AD Followup
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          S. Turner
Internet-Draft                                                      IECA
Intended Status: Informational                                   S. Kent
Expires: February 28, 2014                                           BBN
                                                               J. Manger
                                                                 Telstra
                                                         August 27, 2013

       Additional Methods for Generating Subject Key Identifiers
              draft-turner-additional-methods-4kis-09.txt
                                    
Abstract

   This document specifies additional example methods for generating Key
   Identifier values for use in the AKI (Authority Key Identifier) and
   SKI (Subject Key Identifier).

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."

Copyright Notice

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

 

Turner, Kent, & Manger   Exp. January 10, 2013                  [Page 1]
Internet-Draft        Additional Examples For KIs        August 27, 2013

1.  Introduction

   [RFC5280] defines the AKI (Authority Key Identifier) and SKI (Subject
   Key Identifier) certificate extensions.  [RFC5280] describes two
   example mechanisms for generating AKI/SKI values: a 160-bit SHA-1
   (Secure Hash Algorithm) hash of the public key and a four-bit type
   field with the value 0100 followed by the least significant 60 bits
   of the SHA-1 hash.  Both of these mechanisms were designed to be non-
   security critical.  This document defines three additional mechanisms
   for generating Key Identifier values, using SHA-256, SHA-384, and
   SHA-512 [SHS], that are similar to those examples defined in
   [RFC5280].

1.1.  Requirements Terminology

   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 [RFC2119].

2.  Additional Methods for Generating Key Identifiers

   As specified in [RFC5280], both authority and subject key identifiers
   SHOULD be derived from the public key.  Four additional mechanisms
   CAs can use to identify public keys are as follows:

     1) The keyIdentifier is composed of the leftmost 160-bits of the
        SHA-256 hash of the value of the BIT STRING subjectPublicKey
        (excluding the tag, length, and number of unused bits).

     2) The keyIdentifier is composed of the leftmost 160-bits of the
        SHA-384 hash of the value of the BIT STRING subjectPublicKey
        (excluding the tag, length, and number of unused bits).

     3) The keyIdentifier is composed of the leftmost 160-bits of the
        SHA-512 hash of the value of the BIT STRING subjectPublicKey
        (excluding the tag, length, and number of unused bits).

     4) The keyIdentifier is composed of the hash of the DER-encoding of
        the SubjectPublicKeyInfo value.

 

Turner, Kent, & Manger   Exp. January 10, 2013                  [Page 2]
Internet-Draft        Additional Examples For KIs        August 27, 2013

4.  Examples

        This section provides some examples.  The keys and SKIs are
        presented in hexadecimal (two hex digits per byte).

        Given the following DER-encoded SubjectPublicKeyInfo value
        holding an P-256 ECDSA key:

     30 59
        30 13
           06 07 2A8648CE3D0201    -- id-ecPublicKey
           06 08 2A8648CE3D030107  -- secp256r1
        03 42 00
              04 7F7F35A79794C950060B8029FC8F363A
                 28F11159692D9D34E6AC948190434735
Show full document text