6712
PROPOSED STANDARD
Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP) (Obsoleted)
Authors: T. Kause, M. Peylo
Date: September 2012
Area: sec
Working Group: pkix
Stream: IETF
Abstract
This document describes how to layer the Certificate Management Protocol (CMP) over HTTP. It is the "CMPtrans" document referenced in RFC 4210; therefore, this document updates the reference given therein. [STANDARDS-TRACK]
RFC 6712
Obsoleted by: 9811 PROPOSED STANDARD
Updated by: 9480
Internet Engineering Task Force (IETF) T. Kause
Request for Comments: 6712 SSH
Updates: <a href="./rfc4210">4210</a> M. Peylo
Category: Standards Track NSN
ISSN: 2070-1721 September 2012
<span class="h1">Internet X.509 Public Key Infrastructure -- HTTP Transfer</span>
<span class="h1">for the Certificate Management Protocol (CMP)</span>
Abstract
This document describes how to layer the Certificate Management
Protocol (CMP) over HTTP. It is the "CMPtrans" document referenced
in <a href="./rfc4210">RFC 4210</a>; therefore, this document updates the reference given
therein.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc6712">http://www.rfc-editor.org/info/rfc6712</a>.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Kause & Peylo Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6712">RFC 6712</a> CMPtrans September 2012</span>
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Conventions Used in This Document ...............................<a href="#page-3">3</a>
<a href="#section-3">3</a>. HTTP-Based Protocol .............................................<a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. HTTP Versions ..............................................<a href="#page-4">4</a>
<a href="#section-3.2">3.2</a>. Persistent Connections .....................................<a href="#page-4">4</a>
<a href="#section-3.3">3.3</a>. General Form ...............................................<a href="#page-4">4</a>
<a href="#section-3.4">3.4</a>. Media Type .................................................<a href="#page-4">4</a>
<a href="#section-3.5">3.5</a>. Communication Workflow .....................................<a href="#page-5">5</a>
<a href="#section-3.6">3.6</a>. HTTP Request-URI ...........................................<a href="#page-5">5</a>
<a href="#section-3.7">3.7</a>. Pushing of Announcements ...................................<a href="#page-5">5</a>
<a href="#section-3.8">3.8</a>. HTTP Considerations ........................................<a href="#page-6">6</a>
<a href="#section-4">4</a>. Implementation Considerations ...................................<a href="#page-7">7</a>
<a href="#section-5">5</a>. Security Considerations .........................................<a href="#page-7">7</a>
<a href="#section-6">6</a>. IANA Considerations .............................................<a href="#page-8">8</a>
<a href="#section-7">7</a>. Acknowledgments .................................................<a href="#page-8">8</a>
<a href="#section-8">8</a>. References ......................................................<a href="#page-9">9</a>
<a href="#section-8.1">8.1</a>. Normative References .......................................<a href="#page-9">9</a>
<a href="#section-8.2">8.2</a>. Informative References .....................................<a href="#page-9">9</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Certificate Management Protocol (CMP) [<a href="./rfc4210" title=""Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)"">RFC4210</a>] requires a well-
defined transfer mechanism to enable End Entities (EEs), Registration
Authorities (RAs), and Certification Authorities (CAs) to pass
PKIMessage sequences between them.
The first version of the CMP specification [<a href="./rfc2510" title=""Internet X.509 Public Key Infrastructure Certificate Management Protocols"">RFC2510</a>] included a brief
description of a simple transfer protocol layer on top of TCP. Its
features were simple transfer-level error handling and a mechanism to
poll for outstanding PKI messages. Additionally, it was mentioned
that PKI messages could also be conveyed using file-, E-mail-, and
HTTP-based transfer, but those were not specified in detail.
<span class="grey">Kause & Peylo Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6712">RFC 6712</a> CMPtrans September 2012</span>
The current version of the CMP specification [<a href="./rfc4210" title=""Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)"">RFC4210</a>] incorporated
its own polling mechanism, and thus the need for a transfer protocol
providing this functionality vanished. The remaining features CMP
requires from its transfer protocols are connection and error
handling.
Before this document was published as an RFC, the draft version
underwent drastic changes during the long-lasting work process. The
so-called "Direct TCP-Based Management Protocol" specified in
[<a href="./rfc2510" title=""Internet X.509 Public Key Infrastructure Certificate Management Protocols"">RFC2510</a>] was enhanced, and at some point a version existed where
this protocol was again transferred over HTTP. As both approaches
proved to be needless and cumbersome, implementers preferred to use
plain HTTP transfer following [<a href="./rfc1945" title=""Hypertext Transfer Protocol -- HTTP/1.0"">RFC1945</a>] or [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>]. This document
now reflects that by exclusively describing HTTP as the transfer
protocol for CMP.
The usage of HTTP for transferring CMP messages exclusively uses the
POST method for requests, effectively tunneling CMP over HTTP. While
this is generally considered bad practice and should not be emulated,
there are good reasons to do so for transferring CMP. HTTP is used
as it is generally easy to implement and it is able to traverse
network borders utilizing ubiquitous proxies. Most importantly, HTTP
is already commonly used in existing CMP implementations. Other HTTP
request methods, such as GET, are not used because PKI management
operations can only be triggered using CMP's PKI messages, which need
to be transferred using a POST request.
With its status codes, HTTP provides needed error reporting
capabilities. General problems on the server side, as well as those
directly caused by the respective request, can be reported to the
client.
As CMP implements a transaction ID, identifying transactions spanning
over more than just a single request/response pair, the statelessness
of HTTP is not blocking its usage as the transfer protocol for CMP
messages.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. HTTP-Based Protocol</span>
For direct interaction between two entities, where a reliable
transport protocol like TCP is available, HTTP SHOULD be utilized for
conveying CMP messages.
<span class="grey">Kause & Peylo Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6712">RFC 6712</a> CMPtrans September 2012</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. HTTP Versions</span>
Implementations MUST support HTTP/1.0 [<a href="./rfc1945" title=""Hypertext Transfer Protocol -- HTTP/1.0"">RFC1945</a>] and SHOULD support
HTTP/1.1 [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>].
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Persistent Connections</span>
HTTP persistent connections [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>] allow multiple interactions to
take place on the same HTTP connection. However, neither HTTP nor
the protocol specified in this document are designed to correlate
messages on the same connection in any meaningful way; persistent
connections are only a performance optimization. In particular,
intermediaries can do things like mix connections from different
clients into one "upstream" connection, terminate persistent
connections, and forward requests as non-persistent requests, etc.
As such, implementations MUST NOT infer that requests on the same
connection come from the same client (e.g., for correlating PKI
messages with ongoing transactions); every message is to be evaluated
in isolation.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. General Form</span>
A DER-encoded [<a href="#ref-ITU.X690.1994">ITU.X690.1994</a>] PKIMessage [<a href="./rfc4210" title=""Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)"">RFC4210</a>] is sent as the
entity-body of an HTTP POST request. If this HTTP request is
successful, the server returns the CMP response in the body of the
HTTP response. The HTTP response status code in this case MUST be
200; other "Successful 2xx" codes MUST NOT be used for this purpose.
HTTP responses to pushed CMP Announcement messages (i.e., CA
Certificate Announcement, Certificate Announcement, Revocation
Announcement, and Certificate Revocation List (CRL) Announcement)
utilize the status codes 201 and 202 to identify whether the received
information was processed.
While "Redirection 3xx" status codes MAY be supported by
implementations, clients should only be enabled to automatically
follow them after careful consideration of possible security
implications. As described in <a href="#section-5">Section 5</a>, "301 Moved Permanently"
could be misused for permanent denial of service.
All applicable "Client Error 4xx" or "Server Error 5xx" status codes
MAY be used to inform the client about errors.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Media Type</span>
The Internet Media Type "application/pkixcmp" MUST be set in the HTTP
Content-Type header field when conveying a PKIMessage.
<span class="grey">Kause & Peylo Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc6712">RFC 6712</a> CMPtrans September 2012</span>
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Communication Workflow</span>
In CMP, most communication is initiated by the EEs where every CMP
request triggers a CMP response message from the CA or RA.
The CMP Announcement messages described in <a href="#section-3.7">Section 3.7</a> are an
exception. Their creation may be triggered by certain events or done
on a regular basis by a CA. The recipient of the Announcement only
replies with an HTTP status code acknowledging the receipt or
indicating an error, but not with a CMP response.
If the receipt of an HTTP request is not confirmed by receiving an
HTTP response, it MUST be assumed that the transferred CMP message
was not successfully delivered to its destination.
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. HTTP Request-URI</span>
The Request-URI is formed as specified in [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>].
A server implementation MUST handle Request-URI paths, with or
without a trailing slash, as identical.
An example of a Request-Line and a Host header field in an HTTP/1.1
header, sending a CMP request to a server, located in the "/cmp" path
of the host "example.com", would be
POST /cmp HTTP/1.1
Host: example.com
or in the absoluteURI form
POST http://example.com/cmp/ HTTP/1.1
Host: example.com
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. Pushing of Announcements</span>
A CMP server may create event-triggered announcements or generate
them on a regular basis. It MAY utilize HTTP transfer to convey them
to a suitable recipient. In this use case, the CMP server acts as an
HTTP client, and the recipient needs to utilize an HTTP server. As
no request messages are specified for those announcements, they can
only be pushed to the recipient.
If an EE wants to poll for a potential CA Key Update Announcement or
the current CRL, a PKI Information Request using a General Message as
described in <a href="./rfc4210#appendix-E.5">Appendix E.5 of [RFC4210]</a> can be used.
<span class="grey">Kause & Peylo Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc6712">RFC 6712</a> CMPtrans September 2012</span>
When pushing Announcement messages, PKIMessage structures are sent as
the entity-body of an HTTP POST request.
Suitable recipients for CMP announcements might, for example, be
repositories storing the announced information, such as directory
services. Those services listen for incoming messages, utilizing the
same HTTP Request-URI scheme as defined in <a href="#section-3.6">Section 3.6</a>.
The following PKIMessages are announcements that may be pushed by a
CA. The prefixed numbers reflect ASN.1 numbering of the respective
element.
[<a id="ref-15">15</a>] CA Key Update Announcement
[16] Certificate Announcement
[17] Revocation Announcement
[18] CRL Announcement
CMP Announcement messages do not require any CMP response. However,
the recipient MUST acknowledge receipt with an HTTP response having
an appropriate status code and an empty body. When not receiving
such a response, it MUST be assumed that the delivery was not
successful. If applicable, the sending side MAY try sending the
Announcement again after waiting for an appropriate time span.
If the announced issue was successfully stored in a database or was
already present, the answer MUST be an HTTP response with a "201
Created" status code and an empty message body.
In case the announced information was only accepted for further
processing, the status code of the returned HTTP response MAY also be
"202 Accepted". After an appropriate delay, the sender may then try
to send the Announcement again and may repeat this until it receives
a confirmation that it has been successfully processed. The
appropriate duration of the delay and the option to increase it
between consecutive attempts should be carefully considered.
A receiver MUST answer with a suitable 4xx or 5xx HTTP error code
when a problem occurs.
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. HTTP Considerations</span>
While all defined features of the HTTP protocol are available to
implementations, they SHOULD keep the protocol utilization as simple
as possible. For example, there is no benefit in using chunked
Transfer-Encoding, as the length of an ASN.1 sequence is known when
starting to send it.
<span class="grey">Kause & Peylo Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc6712">RFC 6712</a> CMPtrans September 2012</span>
There is no need for the clients to send an "Expect" request-header
field with the "100-continue" expectation and wait for a "100
Continue" status as described in <a href="./rfc2616#section-8.2.3">Section 8.2.3 of [RFC2616]</a>. The CMP
payload sent by a client is relatively small, so having extra
messages exchanged is inefficient, as the server will only seldom
reject a message without evaluating the body.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Implementation Considerations</span>
Implementors should be aware that implementations might exist that
use a different approach for transferring CMP over HTTP, because this
document has been under development for more than a decade. Further,
implementations based on earlier drafts of this document might use an
unregistered "application/pkixcmp-poll" MIME type.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
The following aspects need to be considered by implementers and
users:
1. There is the risk for denial-of-service attacks through resource
consumption by opening many connections to an HTTP server.
Therefore, idle connections should be terminated after an
appropriate timeout; this may also depend on the available free
resources. After sending a CMP Error Message, the server should
close the connection, even if the CMP transaction is not yet
fully completed.
2. Without being encapsulated in effective security protocols, such
as Transport Layer Security (TLS) [<a href="./rfc5246" title=""The Transport Layer Security (TLS) Protocol Version 1.2"">RFC5246</a>], there is no
integrity protection at the HTTP protocol level. Therefore,
information from the HTTP protocol should not be used to change
state of the transaction.
3. Client users should be aware that storing the target location of
an HTTP response with the "301 Moved Permanently" status code
could be exploited by a man-in-the-middle attacker trying to
block them permanently from contacting the correct server.
4. If no measures to authenticate and protect the HTTP responses to
pushed Announcement messages are in place, their information
regarding the Announcement's processing state may not be trusted.
In that case, the overall design of the PKI system must not
depend on the Announcements being reliably received and processed
by their destination.
<span class="grey">Kause & Peylo Standards Track [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc6712">RFC 6712</a> CMPtrans September 2012</span>
5. CMP provides inbuilt integrity protection and authentication.
The information communicated unencrypted in CMP messages does not
contain sensitive information endangering the security of the PKI
when intercepted. However, it might be possible for an
eavesdropper to utilize the available information to gather
confidential technical or business critical information.
Therefore, users of the HTTP transfer for CMP might want to
consider using HTTP over TLS according to [<a href="./rfc2818" title=""HTTP Over TLS"">RFC2818</a>] or virtual
private networks created, for example, by utilizing Internet
Protocol Security according to [<a href="./rfc4301" title=""Security Architecture for the Internet Protocol"">RFC4301</a>]. Compliant
implementations MUST support TLS with the option to authenticate
both server and client.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
The IANA has already registered the MIME media type "application/
pkixcmp" for identifying CMP sequences due to an request made in
connection with [<a href="./rfc2510" title=""Internet X.509 Public Key Infrastructure Certificate Management Protocols"">RFC2510</a>].
No further action by the IANA is necessary for this document or any
anticipated updates.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span>
Amit Kapoor and Ronald Tschlaer were the original authors of this
document, and their version focused on the so-called "TCP-Based
Management Protocol", which has been removed from this document.
Their contact data, as originally stated by them, is as follows:
Amit Kapoor
Certicom
25801 Industrial Blvd
Hayward, CA
US
Email: [email protected]
Ronald Tschalaer
Certicom
25801 Industrial Blvd
Hayward, CA
US
Email: [email protected]
The authors gratefully acknowledge the contributions of various
members of the IETF PKIX working group and the ICSA CA-talk mailing
list (a list solely devoted to discussing CMP interoperability
efforts).
<span class="grey">Kause & Peylo Standards Track [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc6712">RFC 6712</a> CMPtrans September 2012</span>
By providing ideas, giving hints, and doing invaluable review work,
the following alphabetically listed individuals have significantly
contributed to this document:
Tomas Gustavsson, Primekey
Peter Gutmann, University of Auckland
Wolf-Dietrich Moeller, Nokia Siemens Networks
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-ITU.X690.1994">ITU.X690.1994</a>]
International Telecommunications Union, "Information
Technology - ASN.1 encoding rules: Specification of Basic
Encoding Rules (BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER)", ITU-T Recommendation
X.690, 1994.
[<a id="ref-RFC1945">RFC1945</a>] Berners-Lee, T., Fielding, R., and H. Frystyk, "Hypertext
Transfer Protocol -- HTTP/1.0", <a href="./rfc1945">RFC 1945</a>, May 1996.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2510">RFC2510</a>] Adams, C. and S. Farrell, "Internet X.509 Public Key
Infrastructure Certificate Management Protocols", <a href="./rfc2510">RFC</a>
<a href="./rfc2510">2510</a>, March 1999.
[<a id="ref-RFC2616">RFC2616</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, <a href="./rfc3986">RFC</a>
<a href="./rfc3986">3986</a>, January 2005.
[<a id="ref-RFC4210">RFC4210</a>] Adams, C., Farrell, S., Kause, T., and T. Mononen,
"Internet X.509 Public Key Infrastructure Certificate
Management Protocol (CMP)", <a href="./rfc4210">RFC 4210</a>, September 2005.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-RFC2818">RFC2818</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>, May 2000.
[<a id="ref-RFC4301">RFC4301</a>] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", <a href="./rfc4301">RFC 4301</a>, December 2005.
<span class="grey">Kause & Peylo Standards Track [Page 9]</span><span id="page-10" ></span>
<span class="grey"><a href="./rfc6712">RFC 6712</a> CMPtrans September 2012</span>
[<a id="ref-RFC5246">RFC5246</a>] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", <a href="./rfc5246">RFC 5246</a>, August 2008.
Authors' Addresses
Tomi Kause
SSH Communications Security
Takomotie 8
Helsinki 00380
Finland
EMail: [email protected]
Martin Peylo
Nokia Siemens Networks
Linnoitustie 6
Espoo 02600
Finland
EMail: [email protected]
Kause & Peylo Standards Track [Page 10]
Annotations
Select text to annotate