idnits 2.17.1 draft-turner-ekpct-algs-update-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC6033, but the abstract doesn't seem to directly say this. It does mention RFC6033 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 11, 2011) is 4820 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Informational RFC: RFC 5753 ** Downref: Normative reference to an Informational RFC: RFC 6090 Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Turner 3 Internet-Draft IECA 4 Updates: 6033 (once approved) February 11, 2011 5 Intended status: Standards Track 6 Expires: August 10, 2011 8 Elliptic Curve Algorithms for Cryptographic Message Syntax (CMS) 9 Encrypted Key Package Content Type 10 draft-turner-ekpct-algs-update-03.txt 12 Abstract 14 This document describes the conventions for using several Elliptic 15 Curve cryptographic algorithms with the Cryptographic Message Syntax 16 (CMS) encrypted key package content type. Specifically, it includes 17 conventions necessary to implement Elliptic Curve Diffie-Hellman 18 (ECDH) with EnvelopedData and Elliptic Curve Digital Signature 19 Algorithm (ECDSA) with SignedData. This document extends RFC 6033. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on August 10, 2011. 38 Copyright Notice 40 Copyright (c) 2011 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 Internet-DraftEC Algorithms for CMS Encrypted Key Packages 2011-02-11 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 1. Introduction 57 This document describes the conventions for using Elliptic Curve 58 cryptographic algorithms with the Cryptographic Message Syntax (CMS) 59 encrypted key package content type [RFC6032]. Specifically, it 60 includes conventions necessary to implement the following CMS content 61 types: EnvelopedData [RFC5652] and SignedData [RFC5652]. This 62 document amends [RFC6033]. Familiarity with [RFC6033] and [RFC5753] 63 is assumed. 65 This document does not define any new algorithms; instead, it refers 66 to previously defined algorithms. 68 1.1 Terminology 70 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 71 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 72 "OPTIONAL" in this document are to be interpreted as described in 73 [RFC2119]. 75 2. EnvelopedData 77 When key agreement is used, standard (as opposed to co-factor) ECDH 78 [RFC6090][RFC5753] MAY be supported. 80 3. SignedData 82 If an implementation encapsulates an EncryptedKeyPackage with a 83 SignedData [RFC5652], then it MAY support the signature scheme ECDSA 84 [RFC6090][RFC5753]. 86 4. Public Key Sizes 88 The easiest way to implement the SignedData and EnvelopedData is with 89 public key certificates [RFC5280][RFC5480]. If an implementation 90 supports ECDSA or ECDH, then it MUST support keys on the P-256 curve. 92 Internet-DraftEC Algorithms for CMS Encrypted Key Packages 2011-02-11 94 5. Security Considerations 96 The security considerations from [RFC5280], [RFC5480], [RFC5652], 97 [RFC5753], [RFC6033], and [RFC6090] apply. 99 6. IANA Considerations 101 None. Please remove this section prior to publication as an RFC. 103 7. References 105 7.1. Normative References 107 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 108 Requirement Levels", BCP 14, RFC 2119, March 1997. 110 [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., 111 Housley, R., and W. Polk, "Internet X.509 Public Key 112 Infrastructure Certificate and Certificate Revocation List 113 (CRL) Profile", RFC 5280, May 2008. 115 [RFC5480] Turner, S., Brown, D., Yiu, K., Housley, R., and T. Polk, 116 "Elliptic Curve Cryptography Subject Public Key 117 Information", RFC 5480, March 2009. 119 [RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 120 5652, September 2009. 122 [RFC5753] Turner, S., and D. Brown, "Use of Elliptic Curve 123 Cryptography (ECC) Algorithms in Cryptographic Message 124 Syntax (CMS)", RFC 5753, January 2010. 126 [RFC6032] Turner, S., and R. Housley, "Cryptographic Message Syntax 127 (CMS) Encrypted Key Package Content Type", RFC 6032, 128 December 2010. 130 [RFC6033] Turner, S., "Algorithms for Cryptographic Message Syntax 131 (CMS) Encrypted Key Package Content Type", RFC 6033, 132 December 2010. 134 [RFC6090] McGrew, D., Igoe, E., and M. Salter, "Fundamental Elliptic 135 Curve Cryptography Algorithms", RFC 6090, February 2011. 137 7.2. Informative References 139 None. 141 Internet-DraftEC Algorithms for CMS Encrypted Key Packages 2011-02-11 143 Authors' Addresses 145 Sean Turner 146 IECA, Inc. 147 3057 Nutley Street, Suite 106 148 Fairfax, VA 22031 149 USA 151 EMail: turners@ieca.com