Lightweight Industrial CMP Profile
draft-brockhaus-lamps-industrial-cmp-profile-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Hendrik Brockhaus , Steffen Fries , David von Oheimb | ||
Last updated | 2019-03-11 | ||
Replaced by | draft-brockhaus-lamps-lightweight-cmp-profile | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-brockhaus-lamps-lightweight-cmp-profile | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The goal of this document is to facilitate interoperability and automation by profiling the Certificate Management Protocol (CMP) [RFC4210] and the related Certificate Request Message Format (CRMF) [RFC4211]. It specifies a subset of CMP and CRMF focusing on typical uses cases relevant for managing certificates of devices in 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.
Authors
Hendrik Brockhaus
Steffen Fries
David von Oheimb
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)