One document matched: draft-ietf-pkix-cmc-trans-07.txt
Differences from draft-ietf-pkix-cmc-trans-06.txt
PKIX Working Group J. Schaad
Internet-Draft Soaring Hawk Consulting
Expires: June 6, 2008 M. Myers
TraceRoute Security, Inc.
December 4, 2007
Certificate Management over CMS (CMC): Transport Protocols
draft-ietf-pkix-cmc-trans-07.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 6, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
This document defines a number of transport mechanisms that are used
to move CMC (Certificate Management over CMS (Cryptographic Message
Syntax)) messages. The transport mechanisms described in this
document are: HTTP, file, mail and TCP.
Schaad & Myers Expires June 6, 2008 [Page 1]
Internet-Draft CMC: Transport Protocols December 2007
1. Overview
This document defines a number of transport methods that are used to
move CMC messages (defined in [CMC-STRUCT]). The transport
mechanisms described in this document are: HTTP, file, mail and TCP.
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 [MUST].
2. File based protocol
Enrollment messages and responses may be transferred between clients
and servers using file system-based mechanisms, such as when
enrollment is performed for an off-line client. When files are used
to transport binary, Full PKI Request or Full PKI Response messages,
there MUST be only one instance of a request or response message in a
single file. The following file type extensions SHOULD be used:
+---------------------+----------------+
| Message Type | File Extension |
+---------------------+----------------+
| Simple PKI Request | .p10 |
| Full PKI Request | .crq |
| Simple PKI Response | .p7c |
| Full PKI Response | .crp |
+---------------------+----------------+
File PKI Request/Response Identification
3. Mail based protocol
MIME wrapping is defined for those environments that are MIME native.
The basic mime wrapping in this section is taken from [SMIMEV3].
When using a mail based protocol, MIME wrapping between the layers of
CMS wrapping is optional. Note that is different from the standard
S/MIME (Secure MIME) message.
Simple enrollment requests are encoded using the "application/pkcs10"
content type. A file name MUST be included either in a content type
or a content disposition statement. The extension for the file MUST
be ".p10".
Simple enrollment response messages MUST be encoded as content-type
"application/pkcs7-mime". An smime-type parameter MUST be on the
content-type statement with a value of "certs-only." A file name
Schaad & Myers Expires June 6, 2008 [Page 2]
Internet-Draft CMC: Transport Protocols December 2007
with the ".p7c" extension MUST be specified as part of the content-
type or content-disposition statement.
Full enrollment request messages MUST be encoded as content-type
"application/pkcs7-mime". The smime-type parameter MUST be included
with a value of "CMC-enroll". A file name with the ".p7m" extension
MUST be specified as part of the content-type or content-disposition
statement.
Full enrollment response messages MUST be encoded as content-type
"application/pkcs7-mime". The smime-type parameter MUST be included
with a value of "CMC-response." A file name with the ".p7m"
extensions MUST be specified as part of the content-type or content-
disposition statement.
+--------------+------------------------+------------+--------------+
| Item | MIME TYPE | File | SMIME-TYPE |
| | | Extension | |
+--------------+------------------------+------------+--------------+
| Simple PKI | application/pkcs10 | .p10 | N/A |
| Request | | | |
| Full PKI | application/pkcs7-mime | .p7m | CMC-request |
| Request | | | |
| Simple PKI | application/pkcs7-mime | .p7c | certs-only |
| Response | | | |
| Full PKI | application/pkcs7-mime | .p7m | CMC-response |
| Response | | | |
+--------------+------------------------+------------+--------------+
Table 2: MIME PKI Request/Response Identification
4. HTTP/HTTPS based protocol
This section describes the conventions for use of HTTP [HTTP] as a
transport layer. In most circumstances, the use of HTTP over TLS
[TLS] provides any necessary content protection from ease-droppers.
In order for CMC clients and servers using HTTP to interoperate, the
following rules apply.
Clients MUST use the POST method to submit their requests.
Servers MUST use the 200 response code for successful reponses.
Clients MAY attempt to send HTTP requests using TLS 1.0 [TLS] or
later, although servers are not required to support TLS.
Servers MUST NOT assume client support for any type of HTTP
authentication such as cookies, Basic authentication or Digest
authentication.
Schaad & Myers Expires June 6, 2008 [Page 3]
Internet-Draft CMC: Transport Protocols December 2007
Clients and servers are expected to follow the other rules and
restrictions in [HTTP]. Note that some of those rules are for
HTTP methods other than POST; clearly, only the rules that apply
to POST are relevant for this specification.
4.1. PKI Request
A PKI Request using the POST method is constructed as follows:
The Content-Type header MUST have the appropriate value from Table 2.
The body of the message is the binary value of the encoding of the
PKI Request.
4.2. PKI Response
An HTTP-based PKI Response is composed of the appropriate HTTP
headers, followed by the binary value of the BER (Basic Encoding
Rules) encoding of either a Simple or Full PKI Response.
The Content-Type header MUST have the appropriate value from Table 2.
5. TCP based protocol
When CMC messages are sent over a TCP-Based connection, no wrapping
is required of the message. Messages are sent in their binary
encoded form.
The connection is closed by the server after generating a response
for the client. (All CMC request messages from client to server
generate a response message.) If a second set of messages from the
client to the server is required to complete the transaction, the
client generates a new TCP-Based connection for this purpose; it
cannot reuse an existing one.
Out of band setup can be used to keep a TCP-Based connection open for
more than one message pair. A situation where this can occur is an
RA talking to a CA over a specially setup TCP connection.
There is no specific port that is to be used when doing TCP based
transport. This is to be configured out of band.
6. Socket-Based Transport
When enrollment messages and responses are sent over sockets, no
wrapping is required. Messages MUST be sent in their binary, BER-
Schaad & Myers Expires June 6, 2008 [Page 4]
Internet-Draft CMC: Transport Protocols December 2007
encoded form.
7. Security Considerations
Mechanisms for thwarting replay attacks may be required in particular
implementations of this protocol depending on the operational
environment. In cases where the CA maintains significant state
information, replay attacks may be detectable without the inclusion
of the optional nonce mechanisms. Implementers of this protocol need
to carefully consider environmental conditions before choosing
whether or not to implement the senderNonce and recipientNonce
attributes described in section 5.6 of [CMC-STRUCT]. Developers of
state-constrained PKI clients are strongly encouraged to incorporate
the use of these attributes.
8. IANA Considerations
There are no IANA considerations in this document.
9. Acknowledgments
The authors and the Working Group are grateful for the participation
of Xiaoui Lui and Jeff Weinstein in helping to author the original
versions of this document.
The authors would like to thank Brian LaMacchia for his work in
developing and writing up many of the concepts presented in this
document. The authors would also like to thank Alex Deacon and Barb
Fox for their contributions.
10. References
10.1. Normative References
[CMC-STRUCT]
Schaad, J. and M. Myers, "Certificate Management Messages
over CMS", draft-ietf-pkix-2797-bis-05.txt ,
September 2005.
[HTTP] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[MUST] Bradner, S., "Key words for use in RFCs to Indicate
Schaad & Myers Expires June 6, 2008 [Page 5]
Internet-Draft CMC: Transport Protocols December 2007
Requirement Levels", RFC 2119, BCP 14, March 1997.
[SMIMEV3] Ramsdell, B., "Secure/Multipurpose Internet Mail
Extensions (S/MIME) Version 3.1 Message Specification",
RFC 3851, July 2004.
10.2. Informative References
[TLS] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.1", RFC 4346, April 2006.
Authors' Addresses
Jim Schaad
Soaring Hawk Consulting
PO Box 675
Gold Bar, WA 98251
Phone: (425) 785-1031
Email: jimsch@nwlink.com
Michael Myers
TraceRoute Security, Inc.
Email: mmyers@fastq.com
Schaad & Myers Expires June 6, 2008 [Page 6]
Internet-Draft CMC: Transport Protocols December 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Schaad & Myers Expires June 6, 2008 [Page 7]
| PAFTECH AB 2003-2026 | 2026-04-23 11:28:37 |