idnits 2.17.00 (12 Aug 2021) /tmp/idnits63461/draft-ietf-pkix-cmc-trans-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == There is 1 instance of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 2 longer pages, the longest (page 4) being 67 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([CMC]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 16 == Unused Reference: 'CMS' is defined on line 165, but no explicit reference was found in the text == Unused Reference: 'CRMF' is defined on line 168, but no explicit reference was found in the text == Unused Reference: 'DH' is defined on line 173, but no explicit reference was found in the text == Unused Reference: 'DH-POP' is defined on line 175, but no explicit reference was found in the text == Unused Reference: 'HMAC' is defined on line 178, but no explicit reference was found in the text == Unused Reference: 'PKCS1' is defined on line 184, but no explicit reference was found in the text == Unused Reference: 'PKCS7' is defined on line 188, but no explicit reference was found in the text == Unused Reference: 'PKCS8' is defined on line 192, but no explicit reference was found in the text == Unused Reference: 'PKCS10' is defined on line 196, but no explicit reference was found in the text == Unused Reference: 'PKIXCERT' is defined on line 200, but no explicit reference was found in the text == Unused Reference: 'X942' is defined on line 219, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'CMC' ** Obsolete normative reference: RFC 2630 (ref. 'CMS') (Obsoleted by RFC 3369, RFC 3370) ** Obsolete normative reference: RFC 2511 (ref. 'CRMF') (Obsoleted by RFC 4211) -- Possible downref: Non-RFC (?) normative reference: ref. 'DH' -- Possible downref: Non-RFC (?) normative reference: ref. 'DH-POP' -- Possible downref: Non-RFC (?) normative reference: ref. 'HMAC' -- Possible downref: Non-RFC (?) normative reference: ref. 'PKCS1' ** Downref: Normative reference to an Informational RFC: RFC 2315 (ref. 'PKCS7') -- Possible downref: Non-RFC (?) normative reference: ref. 'PKCS8' -- Possible downref: Non-RFC (?) normative reference: ref. 'PKCS10' -- Possible downref: Non-RFC (?) normative reference: ref. 'PKIXCERT' ** Downref: Normative reference to an Historic RFC: RFC 2311 (ref. 'SMIMEV2') -- Possible downref: Non-RFC (?) normative reference: ref. 'SMIMEV3' -- Possible downref: Non-RFC (?) normative reference: ref. 'X942' Summary: 9 errors (**), 0 flaws (~~), 15 warnings (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PKIX Working Group J. Schaad 3 Internet Draft Soaring Hawk Consulting 4 Document: draft-ietf-pkix-cmc-trans-01.txt M.Myers 5 March 2002 TraceRoute Security 6 Expires: September 2002 X.Liu 7 Cisco 8 J. Weinstein 10 CMC Transport 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026 [1]. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. Internet-Drafts are draft documents valid for a maximum of 21 six months and may be updated, replaced, or obsoleted by other 22 documents at any time. It is inappropriate to use Internet- Drafts 23 as reference material or to cite them other than as "work in 24 progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Comments or suggestions for improvement may be made on the "ietf- 33 pkix" mailing list, or directly to the author. 35 Copyright Notice 37 Copyright (C) The Internet Society (2000). All Rights Reserved. 39 Abstract 41 This document defines a number of transport mechanisms that are used 42 to move [CMC] messages. The transport mechanisms described in this 43 document are: HTTP, file, mail and TCP. 45 1. Overview 47 This document defines a number of transport methods that are used to 48 move [CMC] messages. The transport mechanisms described in this 49 document are: HTTP, file, mail and TCP. 51 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 52 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 53 this document are to be interpreted as described in [RFC 2119]. 55 2. File based protocol 57 Enrollment messages and responses may be transferred between clients 58 and servers using file system-based mechanisms, such as when 59 enrollment is performed for an off-line client. When files are used 60 to transport binary, BER-encoded Full Enrollment Request and 61 Response messages. There MUST be only one instance of a request or 62 response message in a single file. The following file type 63 extensions SHOULD be used: 65 Message Type File Extension 67 Full PKI Request .crq 69 Full PKI Response .crp 71 3. Mail based protocol 73 MIME wrapping is defined for those environments that are MIME 74 native. 76 The basic mime wrapping in this section is taken from [SMIMEV2] and 77 [SMIMEV3]. Simple enrollment requests are encoded using the 78 "application/pkcs10" content type. A file name MUST be included 79 either in a content type or a content disposition statement. The 80 extension for the file MUST be ".p10". 82 Simple enrollment response messages MUST be encoded as content-type 83 "application/pkcs7-mime". An smime-type parameter MUST be on the 84 content-type statement with a value of "certs-only." A file name 85 with the ".p7c" extension MUST be specified as part of the content- 86 type or content-disposition statement. 88 Full enrollment request messages MUST be encoded as content-type 89 "application/pkcs7-mime". The smime-type parameter MUST be included 90 with a value of "CMC-enroll". A file name with the ".p7m" extension 91 MUST be specified as part of the content-type or content-disposition 92 statement. 94 Full enrollment response messages MUST be encoded as content-type 95 "application/pkcs7-mime". The smime-type parameter MUST be included 96 with a value of "CMC-response." A file name with the ".p7m" 97 extensions MUST be specified as part of the content-type or content- 98 disposition statement. 100 MIME TYPE File Extension SMIME-TYPE 102 application/pkcs10 .p10 N/A 103 (simple PKI request) 105 application/pkcs7-mime .p7m CMC-request 106 (full PKI request) 108 application/pkcs7-mime .p7c certs-only 109 (simple PKI response) 110 application/pkcs7-mime .p7m CMC-response 111 (full PKI response) 113 4. HTTP/HTTPS based protocol 115 HTTP messages are wrapped with by a mime object as specified above. 117 5. TCP based protocol 119 When CMC messages are sent over a TCP-Based connection, no wrapping 120 is required of the message. Messages are sent in their binary 121 encoded form. 123 The connection is closed by the server after generating a response 124 for the client. (All CMC request messages from client to server 125 generate a response message.) If a second set of messages from the 126 client to the server is required to complete the transaction, the 127 client generates a new TCP-Based connection for this purpose, it 128 cannot reuse an existing one. 130 Out of band setup can be used to keep a TCP-Based connection open 131 for more than one message pair. A situation where this can occur is 132 an RA talking to a CA over a specially setup TCP connection. 134 6 Socket-Based Transport 136 When enrollment messages and responses are sent over sockets, no 137 wrapping is required. Messages MUST be sent in their binary, BER- 138 encoded form. 140 7. Security Considerations 142 Mechanisms for thwarting replay attacks may be required in 143 particular implementations of this protocol depending on the 144 operational environment. In cases where the CA maintains significant 145 state information, replay attacks may be detectable without the 146 inclusion of the optional nonce mechanisms. Implementers of this 147 protocol need to carefully consider environmental conditions before 148 choosing whether or not to implement the senderNonce and 149 recipientNonce attributes described in section 5.6. Developers of 150 state-constrained PKI clients are strongly encouraged to incorporate 151 the use of these attributes. 153 8. Acknowledgments 155 The authors would like to thank Brian LaMacchia for his work in 156 developing and writing up many of the concepts presented in this 157 document. The authors would also like to thank Alex Deacon and Barb 158 Fox for their contributions. 160 9. References 162 [CMC] J. Schaad, M. Myers, X. Liu, J. Weinstein, ôBASEö, 163 . 165 [CMS] Housley, R., "Cryptographic Message Syntax", RFC 2630, 166 June 1999. 168 [CRMF] Myers, M., Adams, C., Solo, D. and D. Kemp, "Internet 169 X.509 Certificate Request Message Format", RFC 2511, 170 March 171 1999. 173 [DH] B. Kaliski, "PKCS 3: Diffie-Hellman Key Agreement v1.4" 175 [DH-POP] H. Prafullchandra, J. Schaad, "Diffie-Hellman Proof-of- 176 Possession Algorithms", Work in Progress. 178 [HMAC] Krawczyk, H., Bellare, M. and R. Canetti, "HMAC: Keyed- 180 Hashing for Message Authentication", RFC 2104, February 182 1997. 184 [PKCS1] Kaliski, B., "PKCS #1: RSA Encryption, Version 1.5", RFC 186 2313, March 1998. 188 [PKCS7] Kaliski, B., "PKCS #7: Cryptographic Message Syntax 189 v1.5", 190 RFC 2315, October 1997. 192 [PKCS8] RSA Laboratories, "PKCS#8: Private-Key Information Syntax 194 Standard, Version 1.2", November 1, 1993. 196 [PKCS10] Kaliski, B., "PKCS #10: Certification Request Syntax 198 v1.5", RFC 2314, October 1997. 200 [PKIXCERT] Housley, R., Ford, W., Polk, W. and D. Solo "Internet 202 X.509 Public Key Infrastructure Certificate and CRL 203 Profile", RFC 2459, January 1999. 205 [RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate 207 Requirement Levels", BCP 14, RFC 2119, March 1997. 209 [SMIMEV2] Dusse, S., Hoffman, P., Ramsdell, B., Lundblade, L. and 210 L. 211 Repka, "S/MIME Version 2 Message Specification", RFC 212 2311, 213 March 1998. 215 [SMIMEV3] Ramsdell, B., "S/MIME Version 3 Message Specification", 217 RFC 2633, June 1999. 219 [X942] Rescorla, E., "Diffie-Hellman Key Agreement Method", RFC 221 2631, June 1999. 223 10. Authors' Addresses 225 Jim Schaad 226 Soaring Hawk Consulting 228 EMail: jimsch@exmsft.com 229 Michael Myers 230 TraceRoute Security, Inc. 232 EMail: myers@coastside.net 234 Xiaoyi Liu 235 Cisco Systems 236 170 West Tasman Drive 237 San Jose, CA 95134 239 Phone: (480) 526-7430 240 EMail: xliu@cisco.com 242 Jeff Weinstein 244 EMail: jsw@meer.net 246 Full Copyright Statement 248 Copyright (C) The Internet Society (2000). All Rights Reserved. 250 This document and translations of it may be copied and furnished to 251 others, and derivative works that comment on or otherwise explain it 252 or assist in its implementation may be prepared, copied, published 253 and distributed, in whole or in part, without restriction of any 254 kind, provided that the above copyright notice and this paragraph 255 are included on all such copies and derivative works. However, this 256 document itself may not be modified in any way, such as by removing 257 the copyright notice or references to the Internet Society or other 258 Internet organizations, except as needed for the purpose of 259 developing Internet standards in which case the procedures for 260 copyrights defined in the Internet Standards process must be 261 followed, or as required to translate it into languages other than 262 English. 264 The limited permissions granted above are perpetual and will not be 265 revoked by the Internet Society or its successors or assigns. 267 This document and the information contained herein is provided on an 268 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 269 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 270 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 271 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 272 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 274 Acknowledgement 276 Funding for the RFC Editor function is currently provided by the 277 Internet Society.