CoAP Transport for CMPV2
draft-msahni-ace-cmpv2-coap-transport-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mohit Sahni , Saurabh Tripathi | ||
| Last updated | 2020-10-05 | ||
| Replaces | draft-msahni-tbd-cmpv2-coap-transport | ||
| Replaced by | RFC 9482 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Associated None milestones |
|
||
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ace-cmpv2-coap-transport | |
| 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
This document specifies the use of Constrained Application Protocol (CoAP) as a transport medium for the Certificate Management Protocol Version 2 (CMPv2) and Lightweight CMP Profile [Lightweight-CMP-Profile] CMPv2 defines the interaction between various PKI entities for the purpose of certificate creation and management. CoAP is an HTTP like client-server protocol used by various constrained devices in IoT space.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)