Lightweight CMP Profile
draft-brockhaus-lamps-lightweight-cmp-profile-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Replaces draft-brockhaus-lamps-industrial-cmp-profile
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Internet Engineering Task Force                             H. Brockhaus
Internet-Draft                                                  S. Fries
Updates: 4210 (if approved)                                D. von Oheimb
Intended status: Standards Track                                 Siemens
Expires: January 8, 2020                                    July 7, 2019

                        Lightweight CMP Profile
            draft-brockhaus-lamps-lightweight-cmp-profile-00

Abstract

   The goal of this document is to facilitate interoperability and
   automation by profiling the Certificate Management Protocol (CMP)
   version 2 and the related Certificate Request Message Format (CRMF)
   version 2.  It specifies a subset of CMP and CRMF focusing on typical
   uses cases relevant for managing certificates of devices in many
   industrial and IoT scenarios.  To limit the overhead of certificate
   management for constrained devices only the most crucial types of
   transactions are specified as mandatory.  To foster interoperability
   also in more complex scenarios, other types of transactions are
   specified as recommended or optional.

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 8, 2020.

Copyright Notice

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

Brockhaus, et al.        Expires January 8, 2020                [Page 1]
Internet-Draft               Lightweight CMP                   July 2019

   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.  History of changes  . . . . . . . . . . . . . . . . . . . . .   3
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Motivation for profiling CMP  . . . . . . . . . . . . . .   4
     2.2.  Motivation for a lightweight profile for CMP  . . . . . .   5
     2.3.  Existing CMP profiles . . . . . . . . . . . . . . . . . .   6
     2.4.  Compatibility with existing CMP profiles  . . . . . . . .   6
     2.5.  Scope of this document  . . . . . . . . . . . . . . . . .   7
     2.6.  Structure of this document  . . . . . . . . . . . . . . .   8
     2.7.  Convention and Terminology  . . . . . . . . . . . . . . .   8
   3.  Architecture and use cases  . . . . . . . . . . . . . . . . .   9
     3.1.  Solution architecture . . . . . . . . . . . . . . . . . .   9
     3.2.  Basic generic CMP message content . . . . . . . . . . . .  10
     3.3.  Supported use cases . . . . . . . . . . . . . . . . . . .  10
       3.3.1.  Mandatory use cases . . . . . . . . . . . . . . . . .  11
       3.3.2.  Recommended Use Cases . . . . . . . . . . . . . . . .  11
       3.3.3.  Optional use cases  . . . . . . . . . . . . . . . . .  12
     3.4.  CMP message transport . . . . . . . . . . . . . . . . . .  12
   4.  Generic parts of the PKI message  . . . . . . . . . . . . . .  13
     4.1.  General description of the CMP message header . . . . . .  13
     4.2.  General description of the CMP message protection . . . .  15
     4.3.  General description of CMP message extraCerts . . . . . .  15
   5.  End Entity focused certificate management use cases . . . . .  16
     5.1.  Requesting a new certificate from a PKI . . . . . . . . .  16
       5.1.1.  A certificate from a new PKI with signature
               protection  . . . . . . . . . . . . . . . . . . . . .  18
       5.1.2.  Update an existing certificate with signature
               protection  . . . . . . . . . . . . . . . . . . . . .  23
       5.1.3.  A certificate from a PKI with MAC protection  . . . .  24
       5.1.4.  A certificate from a legacy PKI using PKCS#10 request  26
       5.1.5.  Generate the key pair centrally at the (L)RA/CA . . .  26
       5.1.6.  Delayed enrollment  . . . . . . . . . . . . . . . . .  27
       5.1.7.  Omitted confirmation  . . . . . . . . . . . . . . . .  28
Show full document text