CoAP Transport for CMPV2
draft-msahni-tbd-cmpv2-coap-transport-00

Document Type Replaced Internet-Draft (individual)
Author Mohit Sahni 
Last updated 2020-06-04
Replaced by draft-msahni-ace-cmpv2-coap-transport
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-msahni-ace-cmpv2-coap-transport
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-msahni-tbd-cmpv2-coap-transport-00.txt

Abstract

This document specifies how to use Constrained Application Protocol (CoAP) as a Transport Medium for the Certificate management protocol version 2 (CMPv2) and Lightweight CMP Profile [Lightweight-CMP-Profile] which is a subset of CMPv2 defined for Constrained devices. The CMPv2 defines the interaction between various PKI entities for the purpose of certificate creation and management. The CoAP is an HTTP like client-server protocol used by various constrained devices in the IoT and industrial scenarios. Constrained devices are devices that have low memory or CPU or power constraints and avoid the use of complex protocols like TCP to save resources.

Authors

Mohit Sahni (msahni@paloaltonetworks.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)