CoAP Transport for CMPV2
draft-msahni-ace-cmpv2-coap-transport-01
ACE M. Sahni, Ed.
Internet-Draft S. Tripathi, Ed.
Intended status: Standards Track Palo Alto Networks
Expires: April 8, 2021 October 5, 2020
CoAP Transport for CMPV2
draft-msahni-ace-cmpv2-coap-transport-01
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.
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 April 8, 2021.
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
(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
Sahni & Tripathi Expires April 8, 2021 [Page 1]
Internet-Draft CoAP Transport for CMPV2 October 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. CoAP Transport For CMPv2 . . . . . . . . . . . . . . . . . . 3
2.1. Discovery of CMP Entities . . . . . . . . . . . . . . . . 3
2.2. CoAP URI Format . . . . . . . . . . . . . . . . . . . . . 3
2.3. CoAP Request Format . . . . . . . . . . . . . . . . . . . 4
2.4. CoAP Content-Format . . . . . . . . . . . . . . . . . . . 4
2.5. Announcement PKIMessage . . . . . . . . . . . . . . . . . 4
2.6. CoAP Block Wise Transfer Mode . . . . . . . . . . . . . . 4
2.7. Multicast CoAP . . . . . . . . . . . . . . . . . . . . . 4
3. Using CoAP over DTLS . . . . . . . . . . . . . . . . . . . . 4
4. Proxy support . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. CoAP to HTTP Proxy . . . . . . . . . . . . . . . . . . . 5
4.2. CoAPs to HTTPs Proxy . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 7
8.3. URL References . . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
The CMPv2 is used by PKI entities for the generation and management
of the certificates. One of the requirements of CMPv2 [RFC4210] is
to be independent of the transport protocol in use. CMP has
mechanisms to take care of required transactions, error reporting and
encryption of messages. The CoAP defined in [RFC7252], [RFC7959] and
[RFC8323] is a client-server protocol, like HTTP, that is designed to
be used by constrained devices over constrained networks. The
recommended transport for CoAP is UDP, however [RFC8323] specifies
the support of CoAP over TCP, TLS and Websockets. This document
specifies the use of CoAP as a transport medium for the CMPv2 and
Lightweight CMP Profile [Lightweight-CMP-Profile]. This document, in
general, follows the HTTP transport specifications for CMPv2 defined
in [RFC6712] and specifies the additional requirements for CoAP
transport. This document also provides guidance on how to use a
Show full document text