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

Document Type Active Internet-Draft (individual)
Last updated 2020-06-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
TBD                                                        M. Sahni, Ed.
Internet-Draft                                        Palo Alto Networks
Intended status: Standards Track                            June 4, 2020
Expires: December 6, 2020

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

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.

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 December 6, 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
   (https://trustee.ietf.org/license-info) in effect on the date of

Sahni                   Expires December 6, 2020                [Page 1]
Internet-Draft          CoAP Transport for CMPV2               June 2020

   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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  CoAP Transport For CMPv2  . . . . . . . . . . . . . . . . . .   3
     2.1.  CoAP URI Format . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  CoAP Request Format . . . . . . . . . . . . . . . . . . .   3
     2.3.  CoAP Content-Format . . . . . . . . . . . . . . . . . . .   3
     2.4.  Announcement PKIMessage . . . . . . . . . . . . . . . . .   4
     2.5.  CoAP Block Wise Transfer Mode . . . . . . . . . . . . . .   4
     2.6.  Multicast CoAP  . . . . . . . . . . . . . . . . . . . . .   4
   3.  Using CoAP over DTLS  . . . . . . . . . . . . . . . . . . . .   4
   4.  Proxy support . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  CoAP to HTTP Proxy  . . . . . . . . . . . . . . . . . . .   5
     4.2.  CoAPs to HTTPs Proxy  . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
     8.3.  URL References  . . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The CMPv2 is used by the entities in PKI for the generation and
   management of the certificate.  One of the requirements of CMPv2
   [RFC4210] is to be usable over a variety of protocols.  The CoAP
   [RFC7252] and [RFC7959] is a client-server protocol like HTTP that is
   designed to be used by constrained devices over constrained networks
   (low power lossy networks).  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 "CoAP to HTTP" proxy
   for a better adaptation of CoAP transport without significant changes
Show full document text