Lightweight CMP Profile
draft-ietf-lamps-lightweight-cmp-profile-01
LAMPS Working Group H. Brockhaus
Internet-Draft S. Fries
Intended status: Standards Track D. von Oheimb
Expires: September 5, 2020 Siemens
March 4, 2020
Lightweight CMP Profile
draft-ietf-lamps-lightweight-cmp-profile-01
Abstract
The goal of this document is to facilitate interoperability and
automation by profiling the Certificate Management Protocol (CMP)
version 2, the related Certificate Request Message Format (CRMF)
version 2, and the HTTP Transfer for the Certificate Management
Protocol. 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 more constrained devices only the most crucial types
of operations are specified as mandatory. To foster interoperability
also in more complex scenarios, other types of operations 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 September 5, 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
Brockhaus, et al. Expires September 5, 2020 [Page 1]
Internet-Draft Lightweight CMP Profile March 2020
(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.
Table of Contents
1. History of changes . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Motivation for profiling CMP . . . . . . . . . . . . . . 6
2.2. Motivation for a lightweight profile for CMP . . . . . . 7
2.3. Existing CMP profiles . . . . . . . . . . . . . . . . . . 7
2.4. Compatibility with existing CMP profiles . . . . . . . . 9
2.5. Scope of this document . . . . . . . . . . . . . . . . . 11
2.6. Structure of this document . . . . . . . . . . . . . . . 11
2.7. Convention and Terminology . . . . . . . . . . . . . . . 12
3. Architecture and use cases . . . . . . . . . . . . . . . . . 13
3.1. Solution architecture . . . . . . . . . . . . . . . . . . 13
3.2. Basic generic CMP message content . . . . . . . . . . . . 14
3.3. Supported PKI management operations . . . . . . . . . . . 14
3.3.1. Mandatory PKI management operations . . . . . . . . . 15
3.3.2. Recommended PKI management operations . . . . . . . . 15
3.3.3. Optional PKI management operations . . . . . . . . . 16
3.4. CMP message transport . . . . . . . . . . . . . . . . . . 16
4. Generic parts of the PKI message . . . . . . . . . . . . . . 17
4.1. General description of the CMP message header . . . . . . 18
4.2. General description of the CMP message protection . . . . 19
4.3. General description of CMP message extraCerts . . . . . . 20
5. End Entity focused PKI management operations . . . . . . . . 20
5.1. Requesting a new certificate from a PKI . . . . . . . . . 21
5.1.1. Request a certificate from a new PKI with signature
protection . . . . . . . . . . . . . . . . . . . . . 22
5.1.2. Request a certificate from a trusted PKI with
signature protection . . . . . . . . . . . . . . . . 28
5.1.3. Update an existing certificate with signature
protection . . . . . . . . . . . . . . . . . . . . . 28
5.1.4. Request a certificate from a PKI with MAC protection 29
5.1.5. Request a certificate from a legacy PKI using PKCS#10
Show full document text