CoAP Transfer for the Certificate Management Protocol

The Certificate Management Protocol (CMP) is used by the PKI entities for the generation and management of certificates. One of the requirements of Certificate Management Protocol is to be independent of the transport protocol in use. CMP has mechanisms to take care of required transactions, error reporting and protection of messages. The Constrained Application Protocol (CoAP) defined in , and is a client-server protocol like HTTP. It is designed to be used by constrained devices over constrained networks. The recommended transport for CoAP is UDP, however specifies the support of CoAP over TCP, TLS and Websockets. This document specifies the use of CoAP over UDP as a transport medium for the CMP version 2 , CMP version 3 designated as CMP in this document and Lightweight CMP Profile . This document, in general, follows the HTTP transfer for CMP specifications defined in and specifies the requirements for using CoAP as a transfer mechanism for the CMP. This document also provides guidance on how to use a "CoAP-to-HTTP" proxy to ease adoption of CoAP transfer mechanism by enabling the interconnection with existing PKI entities already providing CMP over HTTP.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY",and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

A CMP transaction consists of exchanging PKIMessages between PKI End Entities (EEs), Registration Authorities (RAs), and Certification Authorities (CAs). If the EEs are constrained devices then they may prefer, as a CMP client, the use of CoAP instead of HTTP as the transfer mechanism. The RAs and CAs, in general, are not constrained and can support both CoAP and HTTP Client and Server implementations. This section specifies how to use CoAP as the transfer mechanism for the Certificate Management Protocol.

The CoAP URI format is described in section 6 of . The CoAP endpoints MUST support use of the path prefix "/.well-known/" as defined in and the registered name "cmp" to help with endpoint discovery and interoperability. Optional path segments MAY be added after the registered application name (i.e. after "/.well-known/cmp") to provide distinction. The path segment 'p' followed by an arbitraryLabel <name> could for example support the differentiation of specific CAs or certificate profiles. Further path segments, e.g., as specified in the Lightweight CMP Profile [I-D.ietf-lamps-lightweight-cmp-profile], could indicate PKI management operations using an operationLabel <operation>. A valid full CMP URI can look like this:

coap://www.example.com/.well-known/cmp/p/ coap://www.example.com/.well-known/cmp/p// ]]>

The EEs can be configured with enough information to form the CMP server URI. The minimum information that can be configured is the scheme i.e. "coap:" or "coaps:" and the authority portion of the URI, e.g. "example.com:5683". If the port number is not specified in the authority, then the default ports numbers MUST be assumed for the "coap:" and the "coaps:" scheme URIs. The default port for coap: scheme URIs is 5683 and the default port for coaps: scheme URIs is 5684 . Optionally, in the environments where a Local Registration Authority (LRA) or a Local CA is deployed, EEs can also use the CoAP service discovery mechanism to discover the URI of the Local RA or CA. The CoAP CMP endpoints supporting service discovery MUST also support resource discovery in the CoRE Link Format as described in . The Link MUST include the 'ct' attribute defined in section 7.2.1 of with the value of "application/pkixcmp" as defined in the CoAP Content-Formats IANA registry.

The CMP PKIMessages MUST be DER encoded and sent as the body of the CoAP POST request. A CMP client MUST send each CoAP requests marked as a Confirmable message . If the CoAP request is successful then the server MUST return a Success 2.xx response code otherwise server MUST return an appropriate Client Error 4.xx or Server Error 5.xx response code. A CMP RA or CA may choose to send a Piggybacked response to the client or it MAY send a Separate response in case it takes some time for CA or RA to process the CMP transaction. When transferring CMP PKIMesssage over CoAP the content-format "application/pkixcmp" MUST be used.

A CMP PKIMesssage consists of a header, body, protection, and extraCerts structures which may contain many optional and potentially large fields. Thus a CMP message can be much larger than the Maximum Transmission Unit (MTU) of the outgoing interface of the device. The EEs and RAs or CAs, MUST use the Block-Wise transfer mode to transfer such large messages instead of relying on IP fragmentation. If a CoAP-to-HTTP proxy is in the path between EEs and CA or EEs and RA then, if the server supports, it MUST use the chunked transfer encoding to send data over the HTTP transport. The proxy MUST try to reduce the number of packets sent by using an optimal chunk length for the HTTP transport.

CMP PKIMessages sent over CoAP MUST NOT use a Multicast destination address.

A CMP server may publish announcements, that can be event triggered or periodic, for the other PKI entities. Here is the list of CMP announcement messages prefixed by their respective ASN.1 identifier (section 5.1.2 )

An EE MAY use CoAP Observe option to register itself to get any announcement messages from the RA or CA. The EE can send a GET request to the server's URI suffixed by "/ann". For example a path to register for announcement messages may look like this:

/ann ]]> If the server supports CMP Announcements messages, then it MUST send appropriate Success 2.xx response code, otherwise it MUST send an appropriate Client Error 4.xx or Server Error 5.xx response code. If for some reason server cannot add the client to its list of observers for the announcements, it can omit the Observe option in the response to the client. A client on receiving a 2.xx success response without the Observe option MAY try after some time to register again for announcements from the CMP server. Since server can remove the EE from the list of observers for announcement messages, an EE SHOULD periodically re-register itself for announcement messages. Alternatively, an EE MAY periodically poll for the current status of the CA via the "PKI Information Request" message, see section 6.5 of . If supported, EEs may also use "Support Messages" defined in section 4.3 of Lightweight CMP Profile to get information about the CA status. These mechanisms will help constrained devices, that are acting as EEs, to conserve resources by eliminating the need to create an endpoint for receiving notifications from RA or CA. It will also simplify the implementation of a CoAP-to-HTTP proxy.

This section provides guidance on using a CoAP-to-HTTP proxy between EEs and RAs or CAs in order to avoid changes to the existing PKI implementation. Since the CMP payload is same over CoAP and HTTP transfer mechanisms, a CoAP-to-HTTP cross-protocol proxy can be implemented based on section 10 of . The CoAP-to-HTTP proxy can either be located closer to the EEs or closer to the RA or CA. The proxy MAY support service discovery and resource discovery as described in section 2.2. The CoAP-to-HTTP proxy MUST function as a reverse proxy, only permitting connections to a limited set of pre-configured servers. It is out of scope of this document on how a reverse proxy can route CoAP client requests to one of the configured servers. Some recommended mechanisms are as follows: Use the Uri-Path option to identify a server. Use separate hostnames for each of the configured servers and then use the Uri-Host option for routing the CoAP requests. Use separate hostnames for each of the configured servers and then use Server Name Indication in case of "coaps://" scheme for routing CoAP requests.

If PKIProtection is used, the PKIHeader and PKIBody of the CMP protocol are cryptographically protected against malicious modifications. As such, UDP can be used without compromising the security of the CMP protocol. Security Considerations for CoAP are defined in . The CMP protocol does not provide confidentiality of the CMP payloads. If confidentiality is desired, CoAP over DTLS MAY be used to provide confidentiality for the CMP payloads, although it cannot conceal that the CMP protocol is used within the DTLS layer. Section 9.1 of defines how to use DTLS for securing the CoAP. DTLS associations SHOULD be kept alive and re-used where possible to amortize on the additional overhead of DTLS on constrained devices. An EE might not witness all of the Announcement messages when using the CoAP Observe option , since the Observe option is a "best-effort" approach and the server might lose its state for subscribers to its announcement messages. The EEs may use an alternate method described in section 2.6 to obtain time critical changes such as CRL updates. Implementations SHOULD use the available datagram size and avoid small datagrams containing partial CMP PKIMessage data in order to reduce memory usage for packet buffering. A CoAP-to-HTTP proxy can also protect the PKI entities by handling UDP and CoAP messages. Proxy can mitigate attacks like denial of service attacks, replay attacks and resource-exhaustion attacks by enforcing basic checks like validating that the ASN.1 syntax is compliant to CMP messages and validating the PKIMessage protection before sending them to PKI entities. Since the Proxy may have access to the CMP-Level metadata and control over the flow of CMP messages therefore proper role based access control should be in place. Proxy can be deployed at the edge of the "End Entities" network or in front of an RA and CA to protect them. The proxy however may itself be vulnerable to resource-exhaustion attacks as it's required to buffer the CMP messages received over CoAP transport before sending it to the HTTP endpoint. This can be mitigated by using short timers for discarding the buffered messages and rate limiting clients based on the resource usage.

This document adds a new entry to the CoAP Content-Formats Registry code for the content-type "application/pkixcmp" for transferring CMP transactions over CoAP from the identifier range 256-9999 reserved for IETF specifications. Type name: application Subtype name: pkixcmp Encoding: Content may contain arbitrary octet values. The octet values are the ASN.1 DER encoding of a PKI message, as defined in the specifications. Reference: This document and This document also adds a new path segment "ann" to the CMP protocol registry for the EEs to register themselves for the announcement messages. Path Segment: ann Description: The path to send a GET request with CoAP Observer Option to register for CMP announcement messages. Reference: This document. This document references the cmp, in the Well-Known URIs IANA registry. Please add a reference of this document to the Well-Known URIs IANA registry for that entry. This document also refers the path segment "p" in the Certificate Management Protocol (CMP) IANA registry. Please add a reference of this document to the Certificate Management Protocol (CMP) for that path segment. [Note RFC Editor]: This document should be published together or after the CMP version 3 as it references IANA entries created by that Internet draft.

The authors would like to thank Hendrik Brockhaus, David von Oheimb, and Andreas Kretschmer for their guidance in writing the content of this document and providing valuable feedback.