idnits 2.17.1 draft-ietf-jose-json-web-algorithms-29.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 : ---------------------------------------------------------------------------- == There are 23 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 20, 2014) is 3588 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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 2894 -- Looks like a reference, but probably isn't: '0' on line 2894 -- Looks like a reference, but probably isn't: '7' on line 2866 -- Looks like a reference, but probably isn't: '65' on line 2874 -- Looks like a reference, but probably isn't: '49' on line 2868 -- Looks like a reference, but probably isn't: '50' on line 2868 -- Looks like a reference, but probably isn't: '56' on line 2868 -- Looks like a reference, but probably isn't: '71' on line 2868 -- Looks like a reference, but probably isn't: '67' on line 2868 -- Looks like a reference, but probably isn't: '77' on line 2868 -- Looks like a reference, but probably isn't: '5' on line 2872 -- Looks like a reference, but probably isn't: '108' on line 2874 -- Looks like a reference, but probably isn't: '105' on line 2874 -- Looks like a reference, but probably isn't: '99' on line 2874 -- Looks like a reference, but probably isn't: '101' on line 2874 -- Looks like a reference, but probably isn't: '3' on line 2878 -- Looks like a reference, but probably isn't: '66' on line 2880 -- Looks like a reference, but probably isn't: '111' on line 2880 -- Looks like a reference, but probably isn't: '98' on line 2880 -- Looks like a reference, but probably isn't: '128' on line 2884 -- Possible downref: Non-RFC (?) normative reference: ref. 'AES' -- Possible downref: Non-RFC (?) normative reference: ref. 'DSS' ** Downref: Normative reference to an Informational RFC: RFC 2104 ** Obsolete normative reference: RFC 2898 (Obsoleted by RFC 8018) ** Downref: Normative reference to an Informational RFC: RFC 3394 ** Downref: Normative reference to an Informational RFC: RFC 6090 ** Obsolete normative reference: RFC 7159 (Obsoleted by RFC 8259) -- Possible downref: Non-RFC (?) normative reference: ref. 'SEC1' -- Possible downref: Non-RFC (?) normative reference: ref. 'SHS' -- Possible downref: Non-RFC (?) normative reference: ref. 'USASCII' == Outdated reference: A later version (-18) exists of draft-ietf-precis-saslprepbis-07 == Outdated reference: A later version (-05) exists of draft-mcgrew-aead-aes-cbc-hmac-sha2-04 -- Obsolete informational reference (is this intentional?): RFC 3447 (Obsoleted by RFC 8017) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 5 errors (**), 0 flaws (~~), 4 warnings (==), 29 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 JOSE Working Group M. Jones 3 Internet-Draft Microsoft 4 Intended status: Standards Track June 20, 2014 5 Expires: December 22, 2014 7 JSON Web Algorithms (JWA) 8 draft-ietf-jose-json-web-algorithms-29 10 Abstract 12 The JSON Web Algorithms (JWA) specification registers cryptographic 13 algorithms and identifiers to be used with the JSON Web Signature 14 (JWS), JSON Web Encryption (JWE), and JSON Web Key (JWK) 15 specifications. It defines several IANA registries for these 16 identifiers. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on December 22, 2014. 35 Copyright Notice 37 Copyright (c) 2014 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 53 1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 5 54 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 55 3. Cryptographic Algorithms for Digital Signatures and MACs . . . 6 56 3.1. "alg" (Algorithm) Header Parameter Values for JWS . . . . 6 57 3.2. HMAC with SHA-2 Functions . . . . . . . . . . . . . . . . 7 58 3.3. Digital Signature with RSASSA-PKCS1-V1_5 . . . . . . . . . 8 59 3.4. Digital Signature with ECDSA . . . . . . . . . . . . . . . 9 60 3.5. Digital Signature with RSASSA-PSS . . . . . . . . . . . . 10 61 3.6. Using the Algorithm "none" . . . . . . . . . . . . . . . . 11 62 4. Cryptographic Algorithms for Key Management . . . . . . . . . 11 63 4.1. "alg" (Algorithm) Header Parameter Values for JWE . . . . 12 64 4.2. Key Encryption with RSAES-PKCS1-V1_5 . . . . . . . . . . . 14 65 4.3. Key Encryption with RSAES OAEP . . . . . . . . . . . . . . 14 66 4.4. Key Wrapping with AES Key Wrap . . . . . . . . . . . . . . 14 67 4.5. Direct Encryption with a Shared Symmetric Key . . . . . . 15 68 4.6. Key Agreement with Elliptic Curve Diffie-Hellman 69 Ephemeral Static (ECDH-ES) . . . . . . . . . . . . . . . . 15 70 4.6.1. Header Parameters Used for ECDH Key Agreement . . . . 16 71 4.6.1.1. "epk" (Ephemeral Public Key) Header Parameter . . 16 72 4.6.1.2. "apu" (Agreement PartyUInfo) Header Parameter . . 16 73 4.6.1.3. "apv" (Agreement PartyVInfo) Header Parameter . . 17 74 4.6.2. Key Derivation for ECDH Key Agreement . . . . . . . . 17 75 4.7. Key Encryption with AES GCM . . . . . . . . . . . . . . . 18 76 4.7.1. Header Parameters Used for AES GCM Key Encryption . . 19 77 4.7.1.1. "iv" (Initialization Vector) Header Parameter . . 19 78 4.7.1.2. "tag" (Authentication Tag) Header Parameter . . . 19 79 4.8. Key Encryption with PBES2 . . . . . . . . . . . . . . . . 19 80 4.8.1. Header Parameters Used for PBES2 Key Encryption . . . 20 81 4.8.1.1. "p2s" (PBES2 salt input) Parameter . . . . . . . . 20 82 4.8.1.2. "p2c" (PBES2 count) Parameter . . . . . . . . . . 21 83 5. Cryptographic Algorithms for Content Encryption . . . . . . . 21 84 5.1. "enc" (Encryption Algorithm) Header Parameter Values 85 for JWE . . . . . . . . . . . . . . . . . . . . . . . . . 21 86 5.2. AES_CBC_HMAC_SHA2 Algorithms . . . . . . . . . . . . . . . 22 87 5.2.1. Conventions Used in Defining AES_CBC_HMAC_SHA2 . . . . 22 88 5.2.2. Generic AES_CBC_HMAC_SHA2 Algorithm . . . . . . . . . 23 89 5.2.2.1. AES_CBC_HMAC_SHA2 Encryption . . . . . . . . . . . 23 90 5.2.2.2. AES_CBC_HMAC_SHA2 Decryption . . . . . . . . . . . 24 91 5.2.3. AES_128_CBC_HMAC_SHA_256 . . . . . . . . . . . . . . . 25 92 5.2.4. AES_192_CBC_HMAC_SHA_384 . . . . . . . . . . . . . . . 26 93 5.2.5. AES_256_CBC_HMAC_SHA_512 . . . . . . . . . . . . . . . 26 94 5.2.6. Content Encryption with AES_CBC_HMAC_SHA2 . . . . . . 26 95 5.3. Content Encryption with AES GCM . . . . . . . . . . . . . 27 96 6. Cryptographic Algorithms for Keys . . . . . . . . . . . . . . 27 97 6.1. "kty" (Key Type) Parameter Values . . . . . . . . . . . . 28 98 6.2. Parameters for Elliptic Curve Keys . . . . . . . . . . . . 28 99 6.2.1. Parameters for Elliptic Curve Public Keys . . . . . . 28 100 6.2.1.1. "crv" (Curve) Parameter . . . . . . . . . . . . . 28 101 6.2.1.2. "x" (X Coordinate) Parameter . . . . . . . . . . . 29 102 6.2.1.3. "y" (Y Coordinate) Parameter . . . . . . . . . . . 29 103 6.2.2. Parameters for Elliptic Curve Private Keys . . . . . . 29 104 6.2.2.1. "d" (ECC Private Key) Parameter . . . . . . . . . 29 105 6.3. Parameters for RSA Keys . . . . . . . . . . . . . . . . . 29 106 6.3.1. Parameters for RSA Public Keys . . . . . . . . . . . . 30 107 6.3.1.1. "n" (Modulus) Parameter . . . . . . . . . . . . . 30 108 6.3.1.2. "e" (Exponent) Parameter . . . . . . . . . . . . . 30 109 6.3.2. Parameters for RSA Private Keys . . . . . . . . . . . 30 110 6.3.2.1. "d" (Private Exponent) Parameter . . . . . . . . . 30 111 6.3.2.2. "p" (First Prime Factor) Parameter . . . . . . . . 30 112 6.3.2.3. "q" (Second Prime Factor) Parameter . . . . . . . 31 113 6.3.2.4. "dp" (First Factor CRT Exponent) Parameter . . . . 31 114 6.3.2.5. "dq" (Second Factor CRT Exponent) Parameter . . . 31 115 6.3.2.6. "qi" (First CRT Coefficient) Parameter . . . . . . 31 116 6.3.2.7. "oth" (Other Primes Info) Parameter . . . . . . . 31 117 6.4. Parameters for Symmetric Keys . . . . . . . . . . . . . . 32 118 6.4.1. "k" (Key Value) Parameter . . . . . . . . . . . . . . 32 119 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 120 7.1. JSON Web Signature and Encryption Algorithms Registry . . 33 121 7.1.1. Registration Template . . . . . . . . . . . . . . . . 34 122 7.1.2. Initial Registry Contents . . . . . . . . . . . . . . 35 123 7.2. Header Parameter Names Registration . . . . . . . . . . . 41 124 7.2.1. Registry Contents . . . . . . . . . . . . . . . . . . 41 125 7.3. JSON Web Encryption Compression Algorithms Registry . . . 42 126 7.3.1. Registration Template . . . . . . . . . . . . . . . . 42 127 7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 42 128 7.4. JSON Web Key Types Registry . . . . . . . . . . . . . . . 43 129 7.4.1. Registration Template . . . . . . . . . . . . . . . . 43 130 7.4.2. Initial Registry Contents . . . . . . . . . . . . . . 44 131 7.5. JSON Web Key Parameters Registration . . . . . . . . . . . 44 132 7.5.1. Registry Contents . . . . . . . . . . . . . . . . . . 44 133 7.6. JSON Web Key Elliptic Curve Registry . . . . . . . . . . . 46 134 7.6.1. Registration Template . . . . . . . . . . . . . . . . 47 135 7.6.2. Initial Registry Contents . . . . . . . . . . . . . . 47 136 8. Security Considerations . . . . . . . . . . . . . . . . . . . 48 137 8.1. Algorithms and Key Sizes will be Deprecated . . . . . . . 48 138 8.2. Key Lifetimes . . . . . . . . . . . . . . . . . . . . . . 48 139 8.3. RSAES-PKCS1-v1_5 Security Considerations . . . . . . . . . 49 140 8.4. AES GCM Security Considerations . . . . . . . . . . . . . 49 141 8.5. Plaintext JWS Security Considerations . . . . . . . . . . 49 142 8.6. Denial of Service Attacks . . . . . . . . . . . . . . . . 50 143 8.7. Reusing Key Material when Encrypting Keys . . . . . . . . 50 144 8.8. Password Considerations . . . . . . . . . . . . . . . . . 50 145 8.9. Key Entropy . . . . . . . . . . . . . . . . . . . . . . . 51 146 8.10. Differences between Digital Signatures and MACs . . . . . 51 147 8.11. Using Matching Algorithm Strengths . . . . . . . . . . . . 51 148 8.12. Adaptive Chosen-Ciphertext Attacks . . . . . . . . . . . . 51 149 8.13. Timing Attacks . . . . . . . . . . . . . . . . . . . . . . 51 150 8.14. RSA Private Key Representations and Blinding . . . . . . . 51 151 9. Internationalization Considerations . . . . . . . . . . . . . 51 152 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 52 153 10.1. Normative References . . . . . . . . . . . . . . . . . . . 52 154 10.2. Informative References . . . . . . . . . . . . . . . . . . 53 155 Appendix A. Algorithm Identifier Cross-Reference . . . . . . . . 55 156 A.1. Digital Signature/MAC Algorithm Identifier 157 Cross-Reference . . . . . . . . . . . . . . . . . . . . . 55 158 A.2. Key Management Algorithm Identifier Cross-Reference . . . 56 159 A.3. Content Encryption Algorithm Identifier Cross-Reference . 57 160 Appendix B. Test Cases for AES_CBC_HMAC_SHA2 Algorithms . . . . . 57 161 B.1. Test Cases for AES_128_CBC_HMAC_SHA_256 . . . . . . . . . 58 162 B.2. Test Cases for AES_192_CBC_HMAC_SHA_384 . . . . . . . . . 59 163 B.3. Test Cases for AES_256_CBC_HMAC_SHA_512 . . . . . . . . . 60 164 Appendix C. Example ECDH-ES Key Agreement Computation . . . . . . 61 165 Appendix D. Acknowledgements . . . . . . . . . . . . . . . . . . 63 166 Appendix E. Document History . . . . . . . . . . . . . . . . . . 64 167 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 73 169 1. Introduction 171 The JSON Web Algorithms (JWA) specification registers cryptographic 172 algorithms and identifiers to be used with the JSON Web Signature 173 (JWS) [JWS], JSON Web Encryption (JWE) [JWE], and JSON Web Key (JWK) 174 [JWK] specifications. It defines several IANA registries for these 175 identifiers. All these specifications utilize JavaScript Object 176 Notation (JSON) [RFC7159] based data structures. This specification 177 also describes the semantics and operations that are specific to 178 these algorithms and key types. 180 Registering the algorithms and identifiers here, rather than in the 181 JWS, JWE, and JWK specifications, is intended to allow them to remain 182 unchanged in the face of changes in the set of Required, Recommended, 183 Optional, and Deprecated algorithms over time. This also allows 184 changes to the JWS, JWE, and JWK specifications without changing this 185 document. 187 Names defined by this specification are short because a core goal is 188 for the resulting representations to be compact. 190 1.1. Notational Conventions 192 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 193 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 194 "OPTIONAL" in this document are to be interpreted as described in Key 195 words for use in RFCs to Indicate Requirement Levels [RFC2119]. If 196 these words are used without being spelled in uppercase then they are 197 to be interpreted with their normal natural language meanings. 199 BASE64URL(OCTETS) denotes the base64url encoding of OCTETS, per 200 Section 2. 202 UTF8(STRING) denotes the octets of the UTF-8 [RFC3629] representation 203 of STRING. 205 ASCII(STRING) denotes the octets of the ASCII [USASCII] 206 representation of STRING. 208 The concatenation of two values A and B is denoted as A || B. 210 2. Terminology 212 These terms defined by the JSON Web Signature (JWS) [JWS] 213 specification are incorporated into this specification: "JSON Web 214 Signature (JWS)", "Base64url Encoding", "Header Parameter", "JOSE 215 Header", "JWS Payload", "JWS Protected Header", "JWS Signature", "JWS 216 Signing Input", and "Plaintext JWS". 218 These terms defined by the JSON Web Encryption (JWE) [JWE] 219 specification are incorporated into this specification: "JSON Web 220 Encryption (JWE)", "Additional Authenticated Data (AAD)", 221 "Authentication Tag", "Ciphertext", "Content Encryption Key (CEK)", 222 "Direct Encryption", "Direct Key Agreement", "JWE Authentication 223 Tag", "JWE Ciphertext", "JWE Encrypted Key", "JWE Initialization 224 Vector", "JWE Protected Header", "Key Agreement with Key Wrapping", 225 "Key Encryption", "Key Management Mode", "Key Wrapping", and 226 "Plaintext". 228 These terms defined by the JSON Web Key (JWK) [JWK] specification are 229 incorporated into this specification: "JSON Web Key (JWK)" and "JSON 230 Web Key Set (JWK Set)". 232 3. Cryptographic Algorithms for Digital Signatures and MACs 234 JWS uses cryptographic algorithms to digitally sign or create a 235 Message Authentication Codes (MAC) of the contents of the JWS 236 Protected Header and the JWS Payload. 238 3.1. "alg" (Algorithm) Header Parameter Values for JWS 240 The table below is the set of "alg" (algorithm) header parameter 241 values defined by this specification for use with JWS, each of which 242 is explained in more detail in the following sections: 244 +---------------+------------------------------+--------------------+ 245 | alg Parameter | Digital Signature or MAC | Implementation | 246 | Value | Algorithm | Requirements | 247 +---------------+------------------------------+--------------------+ 248 | HS256 | HMAC using SHA-256 | Required | 249 | HS384 | HMAC using SHA-384 | Optional | 250 | HS512 | HMAC using SHA-512 | Optional | 251 | RS256 | RSASSA-PKCS-v1_5 using | Recommended | 252 | | SHA-256 | | 253 | RS384 | RSASSA-PKCS-v1_5 using | Optional | 254 | | SHA-384 | | 255 | RS512 | RSASSA-PKCS-v1_5 using | Optional | 256 | | SHA-512 | | 257 | ES256 | ECDSA using P-256 and | Recommended+ | 258 | | SHA-256 | | 259 | ES384 | ECDSA using P-384 and | Optional | 260 | | SHA-384 | | 261 | ES512 | ECDSA using P-521 and | Optional | 262 | | SHA-512 | | 263 | PS256 | RSASSA-PSS using SHA-256 and | Optional | 264 | | MGF1 with SHA-256 | | 265 | PS384 | RSASSA-PSS using SHA-384 and | Optional | 266 | | MGF1 with SHA-384 | | 267 | PS512 | RSASSA-PSS using SHA-512 and | Optional | 268 | | MGF1 with SHA-512 | | 269 | none | No digital signature or MAC | Optional | 270 | | performed | | 271 +---------------+------------------------------+--------------------+ 273 The use of "+" in the Implementation Requirements indicates that the 274 requirement strength is likely to be increased in a future version of 275 the specification. 277 See Appendix A.1 for a table cross-referencing the JWS digital 278 signature and MAC "alg" (algorithm) values defined in this 279 specification with the equivalent identifiers used by other standards 280 and software packages. 282 3.2. HMAC with SHA-2 Functions 284 Hash-based Message Authentication Codes (HMACs) enable one to use a 285 secret plus a cryptographic hash function to generate a Message 286 Authentication Code (MAC). This can be used to demonstrate that 287 whoever generated the MAC was in possession of the MAC key. The 288 algorithm for implementing and validating HMACs is provided in RFC 289 2104 [RFC2104]. 291 A key of the same size as the hash output (for instance, 256 bits for 292 "HS256") or larger MUST be used with this algorithm. 294 The HMAC SHA-256 MAC is generated per RFC 2104, using SHA-256 as the 295 hash algorithm "H", using the JWS Signing Input as the "text" value, 296 and using the shared key. The HMAC output value is the JWS 297 Signature. 299 The following "alg" (algorithm) Header Parameter values are used to 300 indicate that the JWS Signature is an HMAC value computed using the 301 corresponding algorithm: 303 +---------------------+--------------------+ 304 | alg Parameter Value | MAC Algorithm | 305 +---------------------+--------------------+ 306 | HS256 | HMAC using SHA-256 | 307 | HS384 | HMAC using SHA-384 | 308 | HS512 | HMAC using SHA-512 | 309 +---------------------+--------------------+ 311 The HMAC SHA-256 MAC for a JWS is validated by computing an HMAC 312 value per RFC 2104, using SHA-256 as the hash algorithm "H", using 313 the received JWS Signing Input as the "text" value, and using the 314 shared key. This computed HMAC value is then compared to the result 315 of base64url decoding the received encoded JWS Signature value. 316 Alternatively, the computed HMAC value can be base64url encoded and 317 compared to the received encoded JWS Signature value, as this 318 comparison produces the same result as comparing the unencoded 319 values. In either case, if the values match, the HMAC has been 320 validated. 322 Securing content and validation with the HMAC SHA-384 and HMAC SHA- 323 512 algorithms is performed identically to the procedure for HMAC 324 SHA-256 -- just using the corresponding hash algorithms with 325 correspondingly larger minimum key sizes and result values: 384 bits 326 each for HMAC SHA-384 and 512 bits each for HMAC SHA-512. 328 An example using this algorithm is shown in Appendix A.1 of [JWS]. 330 3.3. Digital Signature with RSASSA-PKCS1-V1_5 332 This section defines the use of the RSASSA-PKCS1-V1_5 digital 333 signature algorithm as defined in Section 8.2 of RFC 3447 [RFC3447] 334 (commonly known as PKCS #1), using SHA-2 [SHS] hash functions. 336 A key of size 2048 bits or larger MUST be used with these algorithms. 338 The RSASSA-PKCS1-V1_5 SHA-256 digital signature is generated as 339 follows: Generate a digital signature of the JWS Signing Input using 340 RSASSA-PKCS1-V1_5-SIGN and the SHA-256 hash function with the desired 341 private key. This is the JWS Signature value. 343 The following "alg" (algorithm) Header Parameter values are used to 344 indicate that the JWS Signature is a digital signature value computed 345 using the corresponding algorithm: 347 +---------------------+--------------------------------+ 348 | alg Parameter Value | Digital Signature Algorithm | 349 +---------------------+--------------------------------+ 350 | RS256 | RSASSA-PKCS-v1_5 using SHA-256 | 351 | RS384 | RSASSA-PKCS-v1_5 using SHA-384 | 352 | RS512 | RSASSA-PKCS-v1_5 using SHA-512 | 353 +---------------------+--------------------------------+ 355 The RSASSA-PKCS1-V1_5 SHA-256 digital signature for a JWS is 356 validated as follows: Submit the JWS Signing Input, the JWS 357 Signature, and the public key corresponding to the private key used 358 by the signer to the RSASSA-PKCS1-V1_5-VERIFY algorithm using SHA-256 359 as the hash function. 361 Signing and validation with the RSASSA-PKCS1-V1_5 SHA-384 and RSASSA- 362 PKCS1-V1_5 SHA-512 algorithms is performed identically to the 363 procedure for RSASSA-PKCS1-V1_5 SHA-256 -- just using the 364 corresponding hash algorithms instead of SHA-256. 366 An example using this algorithm is shown in Appendix A.2 of [JWS]. 368 3.4. Digital Signature with ECDSA 370 The Elliptic Curve Digital Signature Algorithm (ECDSA) [DSS] provides 371 for the use of Elliptic Curve cryptography, which is able to provide 372 equivalent security to RSA cryptography but using shorter key sizes 373 and with greater processing speed. This means that ECDSA digital 374 signatures will be substantially smaller in terms of length than 375 equivalently strong RSA digital signatures. 377 This specification defines the use of ECDSA with the P-256 curve and 378 the SHA-256 cryptographic hash function, ECDSA with the P-384 curve 379 and the SHA-384 hash function, and ECDSA with the P-521 curve and the 380 SHA-512 hash function. The P-256, P-384, and P-521 curves are 381 defined in [DSS]. 383 The ECDSA P-256 SHA-256 digital signature is generated as follows: 385 1. Generate a digital signature of the JWS Signing Input using ECDSA 386 P-256 SHA-256 with the desired private key. The output will be 387 the pair (R, S), where R and S are 256 bit unsigned integers. 389 2. Turn R and S into octet sequences in big endian order, with each 390 array being be 32 octets long. The octet sequence 391 representations MUST NOT be shortened to omit any leading zero 392 octets contained in the values. 394 3. Concatenate the two octet sequences in the order R and then S. 395 (Note that many ECDSA implementations will directly produce this 396 concatenation as their output.) 398 4. The resulting 64 octet sequence is the JWS Signature value. 400 The following "alg" (algorithm) Header Parameter values are used to 401 indicate that the JWS Signature is a digital signature value computed 402 using the corresponding algorithm: 404 +---------------------+-------------------------------+ 405 | alg Parameter Value | Digital Signature Algorithm | 406 +---------------------+-------------------------------+ 407 | ES256 | ECDSA using P-256 and SHA-256 | 408 | ES384 | ECDSA using P-384 and SHA-384 | 409 | ES512 | ECDSA using P-521 and SHA-512 | 410 +---------------------+-------------------------------+ 412 The ECDSA P-256 SHA-256 digital signature for a JWS is validated as 413 follows: 415 1. The JWS Signature value MUST be a 64 octet sequence. If it is 416 not a 64 octet sequence, the validation has failed. 418 2. Split the 64 octet sequence into two 32 octet sequences. The 419 first octet sequence represents R and the second S. The values R 420 and S are represented as octet sequences using the Integer-to- 421 OctetString Conversion defined in Section 2.3.7 of SEC1 [SEC1] 422 (in big endian octet order). 424 3. Submit the JWS Signing Input R, S and the public key (x, y) to 425 the ECDSA P-256 SHA-256 validator. 427 Signing and validation with the ECDSA P-384 SHA-384 and ECDSA P-521 428 SHA-512 algorithms is performed identically to the procedure for 429 ECDSA P-256 SHA-256 -- just using the corresponding hash algorithms 430 with correspondingly larger result values. For ECDSA P-384 SHA-384, 431 R and S will be 384 bits each, resulting in a 96 octet sequence. For 432 ECDSA P-521 SHA-512, R and S will be 521 bits each, resulting in a 433 132 octet sequence. 435 Examples using these algorithms are shown in Appendices A.3 and A.4 436 of [JWS]. 438 3.5. Digital Signature with RSASSA-PSS 440 This section defines the use of the RSASSA-PSS digital signature 441 algorithm as defined in Section 8.1 of RFC 3447 [RFC3447] with the 442 MGF1 mask generation function and SHA-2 hash functions, always using 443 the same hash function for both the RSASSA-PSS hash function and the 444 MGF1 hash function. The size of the salt value is the same size as 445 the hash function output. All other algorithm parameters use the 446 defaults specified in Section A.2.3 of RFC 3447. 448 A key of size 2048 bits or larger MUST be used with this algorithm. 450 The RSASSA-PSS SHA-256 digital signature is generated as follows: 451 Generate a digital signature of the JWS Signing Input using RSASSA- 452 PSS-SIGN, the SHA-256 hash function, and the MGF1 mask generation 453 function with SHA-256 with the desired private key. This is the JWS 454 signature value. 456 The following "alg" (algorithm) Header Parameter values are used to 457 indicate that the JWS Signature is a digital signature value computed 458 using the corresponding algorithm: 460 +---------------------+---------------------------------------------+ 461 | alg Parameter Value | Digital Signature Algorithm | 462 +---------------------+---------------------------------------------+ 463 | PS256 | RSASSA-PSS using SHA-256 and MGF1 with | 464 | | SHA-256 | 465 | PS384 | RSASSA-PSS using SHA-384 and MGF1 with | 466 | | SHA-384 | 467 | PS512 | RSASSA-PSS using SHA-512 and MGF1 with | 468 | | SHA-512 | 469 +---------------------+---------------------------------------------+ 471 The RSASSA-PSS SHA-256 digital signature for a JWS is validated as 472 follows: Submit the JWS Signing Input, the JWS Signature, and the 473 public key corresponding to the private key used by the signer to the 474 RSASSA-PSS-VERIFY algorithm using SHA-256 as the hash function and 475 using MGF1 as the mask generation function with SHA-256. 477 Signing and validation with the RSASSA-PSS SHA-384 and RSASSA-PSS 478 SHA-512 algorithms is performed identically to the procedure for 479 RSASSA-PSS SHA-256 -- just using the alternative hash algorithm in 480 both roles. 482 3.6. Using the Algorithm "none" 484 JWSs MAY also be created that do not provide integrity protection. 485 Such a JWS is called a "Plaintext JWS". A Plaintext JWS MUST use the 486 "alg" value "none", and is formatted identically to other JWSs, but 487 MUST use the empty octet sequence as its JWS Signature value. 488 Receivers MUST verify that the JWS Signature value is the empty octet 489 sequence. See Section 8.5 for security considerations associated 490 with using this algorithm. 492 4. Cryptographic Algorithms for Key Management 494 JWE uses cryptographic algorithms to encrypt or determine the Content 495 Encryption Key (CEK). 497 4.1. "alg" (Algorithm) Header Parameter Values for JWE 499 The table below is the set of "alg" (algorithm) Header Parameter 500 values that are defined by this specification for use with JWE. 501 These algorithms are used to encrypt the CEK, producing the JWE 502 Encrypted Key, or to use key agreement to agree upon the CEK. 504 +-------------------+-----------------+------------+----------------+ 505 | alg Parameter | Key Management | Additional | Implementation | 506 | Value | Algorithm | Header | Requirements | 507 | | | Parameters | | 508 +-------------------+-----------------+------------+----------------+ 509 | RSA1_5 | RSAES-PKCS1-V1_ | (none) | Required | 510 | | 5 | | | 511 | RSA-OAEP | RSAES OAEP | (none) | Optional | 512 | | using default | | | 513 | | parameters | | | 514 | RSA-OAEP-256 | RSAES OAEP | (none) | Optional | 515 | | using SHA-256 | | | 516 | | and MGF1 with | | | 517 | | SHA-256 | | | 518 | A128KW | AES Key Wrap | (none) | Recommended | 519 | | with default | | | 520 | | initial value | | | 521 | | using 128 bit | | | 522 | | key | | | 523 | A192KW | AES Key Wrap | (none) | Optional | 524 | | with default | | | 525 | | initial value | | | 526 | | using 192 bit | | | 527 | | key | | | 528 | A256KW | AES Key Wrap | (none) | Recommended | 529 | | with default | | | 530 | | initial value | | | 531 | | using 256 bit | | | 532 | | key | | | 533 | dir | Direct use of a | (none) | Recommended | 534 | | shared | | | 535 | | symmetric key | | | 536 | | as the CEK | | | 537 | ECDH-ES | Elliptic Curve | "epk", | Recommended+ | 538 | | Diffie-Hellman | "apu", | | 539 | | Ephemeral | "apv" | | 540 | | Static key | | | 541 | | agreement using | | | 542 | | Concat KDF | | | 543 | ECDH-ES+A128KW | ECDH-ES using | "epk", | Recommended | 544 | | Concat KDF and | "apu", | | 545 | | CEK wrapped | "apv" | | 546 | | with "A128KW" | | | 547 | ECDH-ES+A192KW | ECDH-ES using | "epk", | Optional | 548 | | Concat KDF and | "apu", | | 549 | | CEK wrapped | "apv" | | 550 | | with "A192KW" | | | 551 | ECDH-ES+A256KW | ECDH-ES using | "epk", | Recommended | 552 | | Concat KDF and | "apu", | | 553 | | CEK wrapped | "apv" | | 554 | | with "A256KW" | | | 555 | A128GCMKW | Key wrapping | "iv", | Optional | 556 | | with AES GCM | "tag" | | 557 | | using 128 bit | | | 558 | | key | | | 559 | A192GCMKW | Key wrapping | "iv", | Optional | 560 | | with AES GCM | "tag" | | 561 | | using 192 bit | | | 562 | | key | | | 563 | A256GCMKW | Key wrapping | "iv", | Optional | 564 | | with AES GCM | "tag" | | 565 | | using 256 bit | | | 566 | | key | | | 567 | PBES2-HS256+A128K | PBES2 with HMAC | "p2s", | Optional | 568 | W | SHA-256 and | "p2c" | | 569 | | "A128KW" | | | 570 | | wrapping | | | 571 | PBES2-HS384+A192K | PBES2 with HMAC | "p2s", | Optional | 572 | W | SHA-384 and | "p2c" | | 573 | | "A192KW" | | | 574 | | wrapping | | | 575 | PBES2-HS512+A256K | PBES2 with HMAC | "p2s", | Optional | 576 | W | SHA-512 and | "p2c" | | 577 | | "A256KW" | | | 578 | | wrapping | | | 579 +-------------------+-----------------+------------+----------------+ 581 The Additional Header Parameters column indicates what additional 582 Header Parameters are used by the algorithm, beyond "alg", which all 583 use. All but "dir" and "ECDH-ES" also produce a JWE Encrypted Key 584 value. 586 The use of "+" in the Implementation Requirements indicates that the 587 requirement strength is likely to be increased in a future version of 588 the specification. 590 See Appendix A.2 for a table cross-referencing the JWE "alg" 591 (algorithm) values defined in this specification with the equivalent 592 identifiers used by other standards and software packages. 594 4.2. Key Encryption with RSAES-PKCS1-V1_5 596 This section defines the specifics of encrypting a JWE CEK with 597 RSAES-PKCS1-V1_5 [RFC3447]. The "alg" Header Parameter value 598 "RSA1_5" is used for this algorithm. 600 A key of size 2048 bits or larger MUST be used with this algorithm. 602 An example using this algorithm is shown in Appendix A.2 of [JWE]. 604 4.3. Key Encryption with RSAES OAEP 606 This section defines the specifics of encrypting a JWE CEK with RSAES 607 using Optimal Asymmetric Encryption Padding (OAEP) [RFC3447]. Two 608 sets of parameters for using OAEP are defined, which use different 609 hash functions. In the first case, the default parameters specified 610 by RFC 3447 in Section A.2.1 are used. (Those default parameters are 611 the SHA-1 hash function and the MGF1 with SHA-1 mask generation 612 function.) In the second case, the SHA-256 hash function and the 613 MGF1 with SHA-256 mask generation function are used. 615 The following "alg" (algorithm) Header Parameter values are used to 616 indicate that the JWE Encrypted Key is the result of encrypting the 617 CEK using the corresponding algorithm: 619 +---------------------+---------------------------------------------+ 620 | alg Parameter Value | Key Management Algorithm | 621 +---------------------+---------------------------------------------+ 622 | RSA-OAEP | RSAES OAEP using default parameters | 623 | RSA-OAEP-256 | RSAES OAEP using SHA-256 and MGF1 with | 624 | | SHA-256 | 625 +---------------------+---------------------------------------------+ 627 A key of size 2048 bits or larger MUST be used with these algorithms. 629 An example using RSAES OAEP with the default parameters is shown in 630 Appendix A.1 of [JWE]. 632 4.4. Key Wrapping with AES Key Wrap 634 This section defines the specifics of encrypting a JWE CEK with the 635 Advanced Encryption Standard (AES) Key Wrap Algorithm [RFC3394] using 636 the default initial value specified in Section 2.2.3.1. 638 The following "alg" (algorithm) Header Parameter values are used to 639 indicate that the JWE Encrypted Key is the result of encrypting the 640 CEK using the corresponding algorithm and key size: 642 +------------------+------------------------------------------------+ 643 | alg Parameter | Key Management Algorithm | 644 | Value | | 645 +------------------+------------------------------------------------+ 646 | A128KW | AES Key Wrap with default initial value using | 647 | | 128 bit key | 648 | A192KW | AES Key Wrap with default initial value using | 649 | | 192 bit key | 650 | A256KW | AES Key Wrap with default initial value using | 651 | | 256 bit key | 652 +------------------+------------------------------------------------+ 654 An example using this algorithm is shown in Appendix A.3 of [JWE]. 656 4.5. Direct Encryption with a Shared Symmetric Key 658 This section defines the specifics of directly performing symmetric 659 key encryption without performing a key wrapping step. In this case, 660 the shared symmetric key is used directly as the Content Encryption 661 Key (CEK) value for the "enc" algorithm. An empty octet sequence is 662 used as the JWE Encrypted Key value. The "alg" Header Parameter 663 value "dir" is used in this case. 665 Refer to the security considerations on key lifetimes in Section 8.2 666 and AES GCM in Section 8.4 when considering utilizing direct 667 encryption. 669 4.6. Key Agreement with Elliptic Curve Diffie-Hellman Ephemeral Static 670 (ECDH-ES) 672 This section defines the specifics of key agreement with Elliptic 673 Curve Diffie-Hellman Ephemeral Static [RFC6090], in combination with 674 the Concat KDF, as defined in Section 5.8.1 of [NIST.800-56A]. The 675 key agreement result can be used in one of two ways: 677 1. directly as the Content Encryption Key (CEK) for the "enc" 678 algorithm, in the Direct Key Agreement mode, or 680 2. as a symmetric key used to wrap the CEK with the "A128KW", 681 "A192KW", or "A256KW" algorithms, in the Key Agreement with Key 682 Wrapping mode. 684 A new ephemeral public key value MUST be generated for each key 685 agreement operation. 687 In Direct Key Agreement mode, the output of the Concat KDF MUST be a 688 key of the same length as that used by the "enc" algorithm. In this 689 case, the empty octet sequence is used as the JWE Encrypted Key 690 value. The "alg" Header Parameter value "ECDH-ES" is used in the 691 Direct Key Agreement mode. 693 In Key Agreement with Key Wrapping mode, the output of the Concat KDF 694 MUST be a key of the length needed for the specified key wrapping 695 algorithm. In this case, the JWE Encrypted Key is the CEK wrapped 696 with the agreed upon key. 698 The following "alg" (algorithm) Header Parameter values are used to 699 indicate that the JWE Encrypted Key is the result of encrypting the 700 CEK using the result of the key agreement algorithm as the key 701 encryption key for the corresponding key wrapping algorithm: 703 +-------------------+-----------------------------------------------+ 704 | alg Parameter | Key Management Algorithm | 705 | Value | | 706 +-------------------+-----------------------------------------------+ 707 | ECDH-ES+A128KW | ECDH-ES using Concat KDF and CEK wrapped with | 708 | | "A128KW" | 709 | ECDH-ES+A192KW | ECDH-ES using Concat KDF and CEK wrapped with | 710 | | "A192KW" | 711 | ECDH-ES+A256KW | ECDH-ES using Concat KDF and CEK wrapped with | 712 | | "A256KW" | 713 +-------------------+-----------------------------------------------+ 715 4.6.1. Header Parameters Used for ECDH Key Agreement 717 The following Header Parameter names are used for key agreement as 718 defined below. 720 4.6.1.1. "epk" (Ephemeral Public Key) Header Parameter 722 The "epk" (ephemeral public key) value created by the originator for 723 the use in key agreement algorithms. This key is represented as a 724 JSON Web Key [JWK] public key value. It MUST contain only public key 725 parameters and SHOULD contain only the minimum JWK parameters 726 necessary to represent the key; other JWK parameters included can be 727 checked for consistency and honored or can be ignored. This Header 728 Parameter MUST be present and MUST be understood and processed by 729 implementations when these algorithms are used. 731 4.6.1.2. "apu" (Agreement PartyUInfo) Header Parameter 733 The "apu" (agreement PartyUInfo) value for key agreement algorithms 734 using it (such as "ECDH-ES"), represented as a base64url encoded 735 string. When used, the PartyUInfo value contains information about 736 the sender. Use of this Header Parameter is OPTIONAL. This Header 737 Parameter MUST be understood and processed by implementations when 738 these algorithms are used. 740 4.6.1.3. "apv" (Agreement PartyVInfo) Header Parameter 742 The "apv" (agreement PartyVInfo) value for key agreement algorithms 743 using it (such as "ECDH-ES"), represented as a base64url encoded 744 string. When used, the PartyVInfo value contains information about 745 the receiver. Use of this Header Parameter is OPTIONAL. This Header 746 Parameter MUST be understood and processed by implementations when 747 these algorithms are used. 749 4.6.2. Key Derivation for ECDH Key Agreement 751 The key derivation process derives the agreed upon key from the 752 shared secret Z established through the ECDH algorithm, per Section 753 6.2.2.2 of [NIST.800-56A]. 755 Key derivation is performed using the Concat KDF, as defined in 756 Section 5.8.1 of [NIST.800-56A], where the Digest Method is SHA-256. 757 The Concat KDF parameters are set as follows: 759 Z 760 This is set to the representation of the shared secret Z as an 761 octet sequence. 763 keydatalen 764 This is set to the number of bits in the desired output key. For 765 "ECDH-ES", this is length of the key used by the "enc" algorithm. 766 For "ECDH-ES+A128KW", "ECDH-ES+A192KW", and "ECDH-ES+A256KW", this 767 is 128, 192, and 256, respectively. 769 AlgorithmID 770 The AlgorithmID value is of the form Datalen || Data, where Data 771 is a variable-length string of zero or more octets, and Datalen is 772 a fixed-length, big endian 32 bit counter that indicates the 773 length (in octets) of Data. In the Direct Key Agreement case, 774 Data is set to the octets of the UTF-8 representation of the "enc" 775 Header Parameter value. In the Key Agreement with Key Wrapping 776 case, Data is set to the octets of the UTF-8 representation of the 777 "alg" Header Parameter value. 779 PartyUInfo 780 The PartyUInfo value is of the form Datalen || Data, where Data is 781 a variable-length string of zero or more octets, and Datalen is a 782 fixed-length, big endian 32 bit counter that indicates the length 783 (in octets) of Data. If an "apu" (agreement PartyUInfo) Header 784 Parameter is present, Data is set to the result of base64url 785 decoding the "apu" value and Datalen is set to the number of 786 octets in Data. Otherwise, Datalen is set to 0 and Data is set to 787 the empty octet sequence. 789 PartyVInfo 790 The PartyVInfo value is of the form Datalen || Data, where Data is 791 a variable-length string of zero or more octets, and Datalen is a 792 fixed-length, big endian 32 bit counter that indicates the length 793 (in octets) of Data. If an "apv" (agreement PartyVInfo) Header 794 Parameter is present, Data is set to the result of base64url 795 decoding the "apv" value and Datalen is set to the number of 796 octets in Data. Otherwise, Datalen is set to 0 and Data is set to 797 the empty octet sequence. 799 SuppPubInfo 800 This is set to the keydatalen represented as a 32 bit big endian 801 integer. 803 SuppPrivInfo 804 This is set to the empty octet sequence. 806 Applications need to specify how the "apu" and "apv" parameters are 807 used for that application. The "apu" and "apv" values MUST be 808 distinct, when used. Applications wishing to conform to 809 [NIST.800-56A] need to provide values that meet the requirements of 810 that document, e.g., by using values that identify the sender and 811 recipient. Alternatively, applications MAY conduct key derivation in 812 a manner similar to The Diffie-Hellman Key Agreement Method 813 [RFC2631]: In that case, the "apu" field MAY either be omitted or 814 represent a random 512-bit value (analogous to PartyAInfo in 815 Ephemeral-Static mode in RFC 2631) and the "apv" field SHOULD NOT be 816 present. 818 See Appendix C for an example key agreement computation using this 819 method. 821 4.7. Key Encryption with AES GCM 823 This section defines the specifics of encrypting a JWE Content 824 Encryption Key (CEK) with Advanced Encryption Standard (AES) in 825 Galois/Counter Mode (GCM) [AES] [NIST.800-38D]. 827 Use of an Initialization Vector of size 96 bits is REQUIRED with this 828 algorithm. The Initialization Vector is represented in base64url 829 encoded form as the "iv" (initialization vector) Header Parameter 830 value. 832 The Additional Authenticated Data value used is the empty octet 833 string. 835 The requested size of the Authentication Tag output MUST be 128 bits, 836 regardless of the key size. 838 The JWE Encrypted Key value is the Ciphertext output. 840 The Authentication Tag output is represented in base64url encoded 841 form as the "tag" (authentication tag) Header Parameter value. 843 The following "alg" (algorithm) Header Parameter values are used to 844 indicate that the JWE Encrypted Key is the result of encrypting the 845 CEK using the corresponding algorithm and key size: 847 +---------------------+---------------------------------------------+ 848 | alg Parameter Value | Key Management Algorithm | 849 +---------------------+---------------------------------------------+ 850 | A128GCMKW | Key wrapping with AES GCM using 128 bit key | 851 | A192GCMKW | Key wrapping with AES GCM using 192 bit key | 852 | A256GCMKW | Key wrapping with AES GCM using 256 bit key | 853 +---------------------+---------------------------------------------+ 855 4.7.1. Header Parameters Used for AES GCM Key Encryption 857 The following Header Parameters are used for AES GCM key encryption. 859 4.7.1.1. "iv" (Initialization Vector) Header Parameter 861 The "iv" (initialization vector) Header Parameter value is the 862 base64url encoded representation of the Initialization Vector value 863 used for the key encryption operation. This Header Parameter MUST be 864 present and MUST be understood and processed by implementations when 865 these algorithms are used. 867 4.7.1.2. "tag" (Authentication Tag) Header Parameter 869 The "tag" (authentication tag) Header Parameter value is the 870 base64url encoded representation of the Authentication Tag value 871 resulting from the key encryption operation. This Header Parameter 872 MUST be present and MUST be understood and processed by 873 implementations when these algorithms are used. 875 4.8. Key Encryption with PBES2 877 This section defines the specifies of performing password-based 878 encryption of a JWE CEK, by first deriving a key encryption key from 879 a user-supplied password using PBES2 schemes as specified in Section 880 6.2 of [RFC2898], then by encrypting the JWE CEK using the derived 881 key. 883 These algorithms use HMAC SHA-2 algorithms as the Pseudo-Random 884 Function (PRF) for the PBKDF2 key derivation and AES Key Wrap 885 [RFC3394] for the encryption scheme. The PBES2 password input is an 886 octet sequence; if the password to be used is represented as a text 887 string rather than an octet sequence, the UTF-8 encoding of the text 888 string MUST be used as the octet sequence. The salt parameter MUST 889 be computed from the "p2s" (PBES2 salt input) Header Parameter value 890 and the "alg" (algorithm) Header Parameter value as specified in the 891 "p2s" definition below. The iteration count parameter MUST be 892 provided as the "p2c" Header Parameter value. The algorithms 893 respectively use HMAC SHA-256, HMAC SHA-384, and HMAC SHA-512 as the 894 PRF and use 128, 192, and 256 bit AES Key Wrap keys. Their derived- 895 key lengths respectively are 16, 24, and 32 octets. 897 The following "alg" (algorithm) Header Parameter values are used to 898 indicate that the JWE Encrypted Key is the result of encrypting the 899 CEK using the result of the corresponding password-based encryption 900 algorithm as the key encryption key for the corresponding key 901 wrapping algorithm: 903 +---------------------+---------------------------------------------+ 904 | alg Parameter Value | Key Management Algorithm | 905 +---------------------+---------------------------------------------+ 906 | PBES2-HS256+A128KW | PBES2 with HMAC SHA-256 and "A128KW" | 907 | | wrapping | 908 | PBES2-HS384+A192KW | PBES2 with HMAC SHA-384 and "A192KW" | 909 | | wrapping | 910 | PBES2-HS512+A256KW | PBES2 with HMAC SHA-512 and "A256KW" | 911 | | wrapping | 912 +---------------------+---------------------------------------------+ 914 See Appendix C of JSON Web Key (JWK) [JWK] for an example key 915 encryption computation using "PBES2-HS256+A128KW". 917 4.8.1. Header Parameters Used for PBES2 Key Encryption 919 The following Header Parameters are used for Key Encryption with 920 PBES2. 922 4.8.1.1. "p2s" (PBES2 salt input) Parameter 924 The "p2s" (PBES2 salt input) Header Parameter encodes a Salt Input 925 value, which is used as part of the PBKDF2 salt value. The "p2s" 926 value is BASE64URL(Salt Input). This Header Parameter MUST be 927 present and MUST be understood and processed by implementations when 928 these algorithms are used. 930 The salt expands the possible keys that can be derived from a given 931 password. A Salt Input value containing 8 or more octets MUST be 932 used. A new Salt Input value MUST be generated randomly for every 933 encryption operation; see [RFC4086] for considerations on generating 934 random values. The salt value used is (UTF8(Alg) || 0x00 || Salt 935 Input), where Alg is the "alg" Header Parameter value. 937 4.8.1.2. "p2c" (PBES2 count) Parameter 939 The "p2c" (PBES2 count) Header Parameter contains the PBKDF2 940 iteration count, represented as a positive integer. This Header 941 Parameter MUST be present and MUST be understood and processed by 942 implementations when these algorithms are used. 944 The iteration count adds computational expense, ideally compounded by 945 the possible range of keys introduced by the salt. A minimum 946 iteration count of 1000 is RECOMMENDED. 948 5. Cryptographic Algorithms for Content Encryption 950 JWE uses cryptographic algorithms to encrypt and integrity protect 951 the Plaintext and to also integrity protect additional authenticated 952 data. 954 5.1. "enc" (Encryption Algorithm) Header Parameter Values for JWE 956 The table below is the set of "enc" (encryption algorithm) Header 957 Parameter values that are defined by this specification for use with 958 JWE. 960 +-------------+------------------------+------------+---------------+ 961 | enc | Content Encryption | Additional | Implementatio | 962 | Parameter | Algorithm | Header | nRequirements | 963 | Value | | Parameters | | 964 +-------------+------------------------+------------+---------------+ 965 | A128CBC-HS2 | AES_128_CBC_HMAC_SHA_2 | (none) | Required | 966 | 56 | 56 authenticated | | | 967 | | encryption algorithm, | | | 968 | | as defined in | | | 969 | | Section 5.2.3 | | | 970 | A192CBC-HS3 | AES_192_CBC_HMAC_SHA_3 | (none) | Optional | 971 | 84 | 84 authenticated | | | 972 | | encryption algorithm, | | | 973 | | as defined in | | | 974 | | Section 5.2.4 | | | 975 | A256CBC-HS5 | AES_256_CBC_HMAC_SHA_5 | (none) | Required | 976 | 12 | 12 authenticated | | | 977 | | encryption algorithm, | | | 978 | | as defined in | | | 979 | | Section 5.2.5 | | | 980 | A128GCM | AES GCM using 128 bit | (none) | Recommended | 981 | | key | | | 982 | A192GCM | AES GCM using 192 bit | (none) | Optional | 983 | | key | | | 984 | A256GCM | AES GCM using 256 bit | (none) | Recommended | 985 | | key | | | 986 +-------------+------------------------+------------+---------------+ 988 The Additional Header Parameters column indicates what additional 989 Header Parameters are used by the algorithm, beyond "enc", which all 990 use. All also use a JWE Initialization Vector value and produce JWE 991 Ciphertext and JWE Authentication Tag values. 993 See Appendix A.3 for a table cross-referencing the JWE "enc" 994 (encryption algorithm) values defined in this specification with the 995 equivalent identifiers used by other standards and software packages. 997 5.2. AES_CBC_HMAC_SHA2 Algorithms 999 This section defines a family of authenticated encryption algorithms 1000 built using a composition of Advanced Encryption Standard (AES) in 1001 Cipher Block Chaining (CBC) mode with PKCS #7 padding [AES] 1002 [NIST.800-38A] operations and HMAC [RFC2104] [SHS] operations. This 1003 algorithm family is called AES_CBC_HMAC_SHA2. It also defines three 1004 instances of this family, the first using 128 bit CBC keys and HMAC 1005 SHA-256, the second using 192 bit CBC keys and HMAC SHA-384, and the 1006 third using 256 bit CBC keys and HMAC SHA-512. Test cases for these 1007 algorithms can be found in Appendix B. 1009 These algorithms are based upon Authenticated Encryption with AES-CBC 1010 and HMAC-SHA [I-D.mcgrew-aead-aes-cbc-hmac-sha2], performing the same 1011 cryptographic computations, but with the Initialization Vector and 1012 Authentication Tag values remaining separate, rather than being 1013 concatenated with the Ciphertext value in the output representation. 1014 This option is discussed in Appendix B of that specification. This 1015 algorithm family is a generalization of the algorithm family in 1016 [I-D.mcgrew-aead-aes-cbc-hmac-sha2], and can be used to implement 1017 those algorithms. 1019 5.2.1. Conventions Used in Defining AES_CBC_HMAC_SHA2 1021 We use the following notational conventions. 1023 CBC-PKCS5-ENC(X, P) denotes the AES CBC encryption of P using PKCS 1024 #7 padding using the cipher with the key X. 1026 MAC(Y, M) denotes the application of the Message Authentication 1027 Code (MAC) to the message M, using the key Y. 1029 5.2.2. Generic AES_CBC_HMAC_SHA2 Algorithm 1031 This section defines AES_CBC_HMAC_SHA2 in a manner that is 1032 independent of the AES CBC key size or hash function to be used. 1033 Section 5.2.2.1 and Section 5.2.2.2 define the generic encryption and 1034 decryption algorithms. Section 5.2.3 and Section 5.2.5 define 1035 instances of AES_CBC_HMAC_SHA2 that specify those details. 1037 5.2.2.1. AES_CBC_HMAC_SHA2 Encryption 1039 The authenticated encryption algorithm takes as input four octet 1040 strings: a secret key K, a plaintext P, additional authenticated data 1041 A, and an initialization vector IV. The authenticated ciphertext 1042 value E and the authentication tag value T are provided as outputs. 1043 The data in the plaintext are encrypted and authenticated, and the 1044 additional authenticated data are authenticated, but not encrypted. 1046 The encryption process is as follows, or uses an equivalent set of 1047 steps: 1049 1. The secondary keys MAC_KEY and ENC_KEY are generated from the 1050 input key K as follows. Each of these two keys is an octet 1051 string. 1053 MAC_KEY consists of the initial MAC_KEY_LEN octets of K, in 1054 order. 1056 ENC_KEY consists of the final ENC_KEY_LEN octets of K, in 1057 order. 1059 Here we denote the number of octets in the MAC_KEY as 1060 MAC_KEY_LEN, and the number of octets in ENC_KEY as ENC_KEY_LEN; 1061 the values of these parameters are specified by the AEAD 1062 algorithms (in Section 5.2.3 and Section 5.2.5). The number of 1063 octets in the input key K is the sum of MAC_KEY_LEN and 1064 ENC_KEY_LEN. When generating the secondary keys from K, MAC_KEY 1065 and ENC_KEY MUST NOT overlap. Note that the MAC key comes before 1066 the encryption key in the input key K; this is in the opposite 1067 order of the algorithm names in the identifier 1068 "AES_CBC_HMAC_SHA2". 1070 2. The Initialization Vector (IV) used is a 128 bit value generated 1071 randomly or pseudorandomly for use in the cipher. 1073 3. The plaintext is CBC encrypted using PKCS #7 padding using 1074 ENC_KEY as the key, and the IV. We denote the ciphertext output 1075 from this step as E. 1077 4. The octet string AL is equal to the number of bits in A expressed 1078 as a 64-bit unsigned integer in network byte order. 1080 5. A message authentication tag T is computed by applying HMAC 1081 [RFC2104] to the following data, in order: 1083 the additional authenticated data A, 1085 the initialization vector IV, 1087 the ciphertext E computed in the previous step, and 1089 the octet string AL defined above. 1091 The string MAC_KEY is used as the MAC key. We denote the output 1092 of the MAC computed in this step as M. The first T_LEN bits of M 1093 are used as T. 1095 6. The Ciphertext E and the Authentication Tag T are returned as the 1096 outputs of the authenticated encryption. 1098 The encryption process can be illustrated as follows. Here K, P, A, 1099 IV, and E denote the key, plaintext, additional authenticated data, 1100 initialization vector, and ciphertext, respectively. 1102 MAC_KEY = initial MAC_KEY_LEN bytes of K, 1104 ENC_KEY = final ENC_KEY_LEN bytes of K, 1106 E = CBC-PKCS5-ENC(ENC_KEY, P), 1108 M = MAC(MAC_KEY, A || IV || E || AL), 1110 T = initial T_LEN bytes of M. 1112 5.2.2.2. AES_CBC_HMAC_SHA2 Decryption 1114 The authenticated decryption operation has four inputs: K, A, E, and 1115 T as defined above. It has only a single output, either a plaintext 1116 value P or a special symbol FAIL that indicates that the inputs are 1117 not authentic. The authenticated decryption algorithm is as follows, 1118 or uses an equivalent set of steps: 1120 1. The secondary keys MAC_KEY and ENC_KEY are generated from the 1121 input key K as in Step 1 of Section 5.2.2.1. 1123 2. The integrity and authenticity of A and E are checked by 1124 computing an HMAC with the inputs as in Step 5 of 1125 Section 5.2.2.1. The value T, from the previous step, is 1126 compared to the first MAC_KEY length bits of the HMAC output. If 1127 those values are identical, then A and E are considered valid, 1128 and processing is continued. Otherwise, all of the data used in 1129 the MAC validation are discarded, and the AEAD decryption 1130 operation returns an indication that it failed, and the operation 1131 halts. (But see Section 11.2 of [JWE] for security 1132 considerations on thwarting timing attacks.) 1134 3. The value E is decrypted and the PKCS #7 padding is removed. The 1135 value IV is used as the initialization vector. The value ENC_KEY 1136 is used as the decryption key. 1138 4. The plaintext value is returned. 1140 5.2.3. AES_128_CBC_HMAC_SHA_256 1142 This algorithm is a concrete instantiation of the generic 1143 AES_CBC_HMAC_SHA2 algorithm above. It uses the HMAC message 1144 authentication code [RFC2104] with the SHA-256 hash function [SHS] to 1145 provide message authentication, with the HMAC output truncated to 128 1146 bits, corresponding to the HMAC-SHA-256-128 algorithm defined in 1147 [RFC4868]. For encryption, it uses AES in the Cipher Block Chaining 1148 (CBC) mode of operation as defined in Section 6.2 of [NIST.800-38A], 1149 with PKCS #7 padding and a 128 bit initialization vector (IV) value. 1151 The AES_CBC_HMAC_SHA2 parameters specific to AES_128_CBC_HMAC_SHA_256 1152 are: 1154 The input key K is 32 octets long. 1156 ENC_KEY_LEN is 16 octets. 1158 MAC_KEY_LEN is 16 octets. 1160 The SHA-256 hash algorithm is used for the HMAC. 1162 The HMAC-SHA-256 output is truncated to T_LEN=16 octets, by 1163 stripping off the final 16 octets. 1165 5.2.4. AES_192_CBC_HMAC_SHA_384 1167 AES_192_CBC_HMAC_SHA_384 is based on AES_128_CBC_HMAC_SHA_256, but 1168 with the following differences: 1170 The input key K is 48 octets long instead of 32. 1172 ENC_KEY_LEN is 24 octets instead of 16. 1174 MAC_KEY_LEN is 24 octets instead of 16. 1176 SHA-384 is used for the HMAC instead of SHA-256. 1178 The HMAC SHA-384 value is truncated to T_LEN=24 octets instead of 1179 16. 1181 5.2.5. AES_256_CBC_HMAC_SHA_512 1183 AES_256_CBC_HMAC_SHA_512 is based on AES_128_CBC_HMAC_SHA_256, but 1184 with the following differences: 1186 The input key K is 64 octets long instead of 32. 1188 ENC_KEY_LEN is 32 octets instead of 16. 1190 MAC_KEY_LEN is 32 octets instead of 16. 1192 SHA-512 is used for the HMAC instead of SHA-256. 1194 The HMAC SHA-512 value is truncated to T_LEN=32 octets instead of 1195 16. 1197 5.2.6. Content Encryption with AES_CBC_HMAC_SHA2 1199 This section defines the specifics of performing authenticated 1200 encryption with the AES_CBC_HMAC_SHA2 algorithms. 1202 The CEK is used as the secret key K. 1204 The following "enc" (encryption algorithm) Header Parameter values 1205 are used to indicate that the JWE Ciphertext and JWE Authentication 1206 Tag values have been computed using the corresponding algorithm: 1208 +---------------+---------------------------------------------------+ 1209 | enc Parameter | Content Encryption Algorithm | 1210 | Value | | 1211 +---------------+---------------------------------------------------+ 1212 | A128CBC-HS256 | AES_128_CBC_HMAC_SHA_256 authenticated encryption | 1213 | | algorithm, as defined in Section 5.2.3 | 1214 | A192CBC-HS384 | AES_192_CBC_HMAC_SHA_384 authenticated encryption | 1215 | | algorithm, as defined in Section 5.2.4 | 1216 | A256CBC-HS512 | AES_256_CBC_HMAC_SHA_512 authenticated encryption | 1217 | | algorithm, as defined in Section 5.2.5 | 1218 +---------------+---------------------------------------------------+ 1220 5.3. Content Encryption with AES GCM 1222 This section defines the specifics of performing authenticated 1223 encryption with Advanced Encryption Standard (AES) in Galois/Counter 1224 Mode (GCM) [AES] [NIST.800-38D]. 1226 The CEK is used as the encryption key. 1228 Use of an initialization vector of size 96 bits is REQUIRED with this 1229 algorithm. 1231 The requested size of the Authentication Tag output MUST be 128 bits, 1232 regardless of the key size. 1234 The following "enc" (encryption algorithm) Header Parameter values 1235 are used to indicate that the JWE Ciphertext and JWE Authentication 1236 Tag values have been computed using the corresponding algorithm and 1237 key size: 1239 +---------------------+------------------------------+ 1240 | enc Parameter Value | Content Encryption Algorithm | 1241 +---------------------+------------------------------+ 1242 | A128GCM | AES GCM using 128 bit key | 1243 | A192GCM | AES GCM using 192 bit key | 1244 | A256GCM | AES GCM using 256 bit key | 1245 +---------------------+------------------------------+ 1247 An example using this algorithm is shown in Appendix A.1 of [JWE]. 1249 6. Cryptographic Algorithms for Keys 1251 A JSON Web Key (JWK) [JWK] is a JSON data structure that represents a 1252 cryptographic key. These keys can be either asymmetric or symmetric. 1253 They can hold both public and private information about the key. 1254 This section defines the parameters for keys using the algorithms 1255 specified by this document. 1257 6.1. "kty" (Key Type) Parameter Values 1259 The table below is the set of "kty" (key type) parameter values that 1260 are defined by this specification for use in JWKs. 1262 +--------------+--------------------------------+-------------------+ 1263 | kty | Key Type | Implementation | 1264 | Parameter | | Requirements | 1265 | Value | | | 1266 +--------------+--------------------------------+-------------------+ 1267 | EC | Elliptic Curve [DSS] | Recommended+ | 1268 | RSA | RSA [RFC3447] | Required | 1269 | oct | Octet sequence (used to | Required | 1270 | | represent symmetric keys) | | 1271 +--------------+--------------------------------+-------------------+ 1273 The use of "+" in the Implementation Requirements indicates that the 1274 requirement strength is likely to be increased in a future version of 1275 the specification. 1277 6.2. Parameters for Elliptic Curve Keys 1279 JWKs can represent Elliptic Curve [DSS] keys. In this case, the 1280 "kty" member value MUST be "EC". 1282 6.2.1. Parameters for Elliptic Curve Public Keys 1284 An elliptic curve public key is represented by a pair of coordinates 1285 drawn from a finite field, which together define a point on an 1286 elliptic curve. The following members MUST be present for elliptic 1287 curve public keys: 1289 o "crv" 1290 o "x" 1291 o "y" 1293 SEC1 [SEC1] point compression is not supported for any values. 1295 6.2.1.1. "crv" (Curve) Parameter 1297 The "crv" (curve) member identifies the cryptographic curve used with 1298 the key. Curve values from [DSS] used by this specification are: 1300 o "P-256" 1301 o "P-384" 1302 o "P-521" 1304 These values are registered in the IANA JSON Web Key Elliptic Curve 1305 registry defined in Section 7.6. Additional "crv" values MAY be 1306 used, provided they are understood by implementations using that 1307 Elliptic Curve key. The "crv" value is a case-sensitive string. 1309 6.2.1.2. "x" (X Coordinate) Parameter 1311 The "x" (x coordinate) member contains the x coordinate for the 1312 elliptic curve point. It is represented as the base64url encoding of 1313 the octet string representation of the coordinate, as defined in 1314 Section 2.3.5 of SEC1 [SEC1]. The length of this octet string MUST 1315 be the full size of a coordinate for the curve specified in the "crv" 1316 parameter. For example, if the value of "crv" is "P-521", the octet 1317 string must be 66 octets long. 1319 6.2.1.3. "y" (Y Coordinate) Parameter 1321 The "y" (y coordinate) member contains the y coordinate for the 1322 elliptic curve point. It is represented as the base64url encoding of 1323 the octet string representation of the coordinate, as defined in 1324 Section 2.3.5 of SEC1 [SEC1]. The length of this octet string MUST 1325 be the full size of a coordinate for the curve specified in the "crv" 1326 parameter. For example, if the value of "crv" is "P-521", the octet 1327 string must be 66 octets long. 1329 6.2.2. Parameters for Elliptic Curve Private Keys 1331 In addition to the members used to represent Elliptic Curve public 1332 keys, the following member MUST be present to represent Elliptic 1333 Curve private keys. 1335 6.2.2.1. "d" (ECC Private Key) Parameter 1337 The "d" (ECC private key) member contains the Elliptic Curve private 1338 key value. It is represented as the base64url encoding of the octet 1339 string representation of the private key value, as defined in 1340 Sections C.4 and 2.3.7 of SEC1 [SEC1]. The length of this octet 1341 string MUST be ceiling(log-base-2(n)/8) octets (where n is the order 1342 of the curve). 1344 6.3. Parameters for RSA Keys 1346 JWKs can represent RSA [RFC3447] keys. In this case, the "kty" 1347 member value MUST be "RSA". 1349 6.3.1. Parameters for RSA Public Keys 1351 The following members MUST be present for RSA public keys. 1353 6.3.1.1. "n" (Modulus) Parameter 1355 The "n" (modulus) member contains the modulus value for the RSA 1356 public key. It is represented as the base64url encoding of the 1357 value's unsigned big endian representation as an octet sequence. The 1358 octet sequence MUST utilize the minimum number of octets to represent 1359 the value. 1361 6.3.1.2. "e" (Exponent) Parameter 1363 The "e" (exponent) member contains the exponent value for the RSA 1364 public key. It is represented as the base64url encoding of the 1365 value's unsigned big endian representation as an octet sequence. The 1366 octet sequence MUST utilize the minimum number of octets to represent 1367 the value. For instance, when representing the value 65537, the 1368 octet sequence to be base64url encoded MUST consist of the three 1369 octets [1, 0, 1]. 1371 6.3.2. Parameters for RSA Private Keys 1373 In addition to the members used to represent RSA public keys, the 1374 following members are used to represent RSA private keys. The 1375 parameter "d" is REQUIRED for RSA private keys. The others enable 1376 optimizations and SHOULD be included by producers of JWKs 1377 representing RSA private keys. If the producer includes any of the 1378 other private key parameters, then all of the others MUST be present, 1379 with the exception of "oth", which MUST only be present when more 1380 than two prime factors were used. The consumer of a JWK MAY choose 1381 to accept an RSA private key that does not contain a complete set of 1382 the private key parameters other than "d", including JWKs in which 1383 "d" is the only RSA private key parameter included. 1385 6.3.2.1. "d" (Private Exponent) Parameter 1387 The "d" (private exponent) member contains the private exponent value 1388 for the RSA private key. It is represented as the base64url encoding 1389 of the value's unsigned big endian representation as an octet 1390 sequence. The octet sequence MUST utilize the minimum number of 1391 octets to represent the value. 1393 6.3.2.2. "p" (First Prime Factor) Parameter 1395 The "p" (first prime factor) member contains the first prime factor, 1396 a positive integer. It is represented as the base64url encoding of 1397 the value's unsigned big endian representation as an octet sequence. 1398 The octet sequence MUST utilize the minimum number of octets to 1399 represent the value. 1401 6.3.2.3. "q" (Second Prime Factor) Parameter 1403 The "q" (second prime factor) member contains the second prime 1404 factor, a positive integer. It is represented as the base64url 1405 encoding of the value's unsigned big endian representation as an 1406 octet sequence. The octet sequence MUST utilize the minimum number 1407 of octets to represent the value. 1409 6.3.2.4. "dp" (First Factor CRT Exponent) Parameter 1411 The "dp" (first factor CRT exponent) member contains the Chinese 1412 Remainder Theorem (CRT) exponent of the first factor, a positive 1413 integer. It is represented as the base64url encoding of the value's 1414 unsigned big endian representation as an octet sequence. The octet 1415 sequence MUST utilize the minimum number of octets to represent the 1416 value. 1418 6.3.2.5. "dq" (Second Factor CRT Exponent) Parameter 1420 The "dq" (second factor CRT exponent) member contains the Chinese 1421 Remainder Theorem (CRT) exponent of the second factor, a positive 1422 integer. It is represented as the base64url encoding of the value's 1423 unsigned big endian representation as an octet sequence. The octet 1424 sequence MUST utilize the minimum number of octets to represent the 1425 value. 1427 6.3.2.6. "qi" (First CRT Coefficient) Parameter 1429 The "dp" (first CRT coefficient) member contains the Chinese 1430 Remainder Theorem (CRT) coefficient of the second factor, a positive 1431 integer. It is represented as the base64url encoding of the value's 1432 unsigned big endian representation as an octet sequence. The octet 1433 sequence MUST utilize the minimum number of octets to represent the 1434 value. 1436 6.3.2.7. "oth" (Other Primes Info) Parameter 1438 The "oth" (other primes info) member contains an array of information 1439 about any third and subsequent primes, should they exist. When only 1440 two primes have been used (the normal case), this parameter MUST be 1441 omitted. When three or more primes have been used, the number of 1442 array elements MUST be the number of primes used minus two. Each 1443 array element MUST be an object with the following members: 1445 6.3.2.7.1. "r" (Prime Factor) 1447 The "r" (prime factor) parameter within an "oth" array member 1448 represents the value of a subsequent prime factor, a positive 1449 integer. It is represented as the base64url encoding of the value's 1450 unsigned big endian representation as an octet sequence. The octet 1451 sequence MUST utilize the minimum number of octets to represent the 1452 value. 1454 6.3.2.7.2. "d" (Factor CRT Exponent) 1456 The "d" (Factor CRT Exponent) parameter within an "oth" array member 1457 represents the CRT exponent of the corresponding prime factor, a 1458 positive integer. It is represented as the base64url encoding of the 1459 value's unsigned big endian representation as an octet sequence. The 1460 octet sequence MUST utilize the minimum number of octets to represent 1461 the value. 1463 6.3.2.7.3. "t" (Factor CRT Coefficient) 1465 The "t" (factor CRT coefficient) parameter within an "oth" array 1466 member represents the CRT coefficient of the corresponding prime 1467 factor, a positive integer. It is represented as the base64url 1468 encoding of the value's unsigned big endian representation as an 1469 octet sequence. The octet sequence MUST utilize the minimum number 1470 of octets to represent the value. 1472 6.4. Parameters for Symmetric Keys 1474 When the JWK "kty" member value is "oct" (octet sequence), the member 1475 "k" is used to represent a symmetric key (or another key whose value 1476 is a single octet sequence). An "alg" member SHOULD also be present 1477 to identify the algorithm intended to be used with the key, unless 1478 the application uses another means or convention to determine the 1479 algorithm used. 1481 6.4.1. "k" (Key Value) Parameter 1483 The "k" (key value) member contains the value of the symmetric (or 1484 other single-valued) key. It is represented as the base64url 1485 encoding of the octet sequence containing the key value. 1487 7. IANA Considerations 1489 The following registration procedure is used for all the registries 1490 established by this specification. 1492 Values are registered with a Specification Required [RFC5226] after a 1493 two-week review period on the [TBD]@ietf.org mailing list, on the 1494 advice of one or more Designated Experts. However, to allow for the 1495 allocation of values prior to publication, the Designated Expert(s) 1496 may approve registration once they are satisfied that such a 1497 specification will be published. 1499 Registration requests must be sent to the [TBD]@ietf.org mailing list 1500 for review and comment, with an appropriate subject (e.g., "Request 1501 for access token type: example"). [[ Note to the RFC Editor: The name 1502 of the mailing list should be determined in consultation with the 1503 IESG and IANA. Suggested name: jose-reg-review. ]] 1505 Within the review period, the Designated Expert(s) will either 1506 approve or deny the registration request, communicating this decision 1507 to the review list and IANA. Denials should include an explanation 1508 and, if applicable, suggestions as to how to make the request 1509 successful. Registration requests that are undetermined for a period 1510 longer than 21 days can be brought to the IESG's attention (using the 1511 iesg@iesg.org mailing list) for resolution. 1513 Criteria that should be applied by the Designated Expert(s) includes 1514 determining whether the proposed registration duplicates existing 1515 functionality, determining whether it is likely to be of general 1516 applicability or whether it is useful only for a single application, 1517 and whether the registration makes sense. 1519 IANA must only accept registry updates from the Designated Expert(s) 1520 and should direct all requests for registration to the review mailing 1521 list. 1523 It is suggested that multiple Designated Experts be appointed who are 1524 able to represent the perspectives of different applications using 1525 this specification, in order to enable broadly-informed review of 1526 registration decisions. In cases where a registration decision could 1527 be perceived as creating a conflict of interest for a particular 1528 Expert, that Expert should defer to the judgment of the other 1529 Expert(s). 1531 7.1. JSON Web Signature and Encryption Algorithms Registry 1533 This specification establishes the IANA JSON Web Signature and 1534 Encryption Algorithms registry for values of the JWS and JWE "alg" 1535 (algorithm) and "enc" (encryption algorithm) Header Parameters. The 1536 registry records the algorithm name, the algorithm usage locations, 1537 implementation requirements, and a reference to the specification 1538 that defines it. The same algorithm name can be registered multiple 1539 times, provided that the sets of usage locations are disjoint. 1541 It is suggested that when algorithms can use keys of different 1542 lengths, that the length of the key be included in the algorithm 1543 name. This allows readers of the JSON text to easily make security 1544 consideration decisions. 1546 The implementation requirements of an algorithm MAY be changed over 1547 time by the Designated Experts(s) as the cryptographic landscape 1548 evolves, for instance, to change the status of an algorithm to 1549 Deprecated, or to change the status of an algorithm from Optional to 1550 Recommended+ or Required. Changes of implementation requirements are 1551 only permitted on a Specification Required basis, with the new 1552 specification defining the revised implementation requirements level. 1554 7.1.1. Registration Template 1556 Algorithm Name: 1557 The name requested (e.g., "example"). This name is case- 1558 sensitive. Names may not match other registered names in a case- 1559 insensitive manner unless the Designated Expert(s) state that 1560 there is a compelling reason to allow an exception in this 1561 particular case. 1563 Algorithm Description: 1564 Brief description of the Algorithm (e.g., "Example description"). 1566 Algorithm Usage Location(s): 1567 The algorithm usage location. This must be one or more of the 1568 values "alg" or "enc" if the algorithm is to be used with JWS or 1569 JWE. The value "JWK" is used if the algorithm identifier will be 1570 used as a JWK "alg" member value, but will not be used with JWS or 1571 JWE; this could be the case, for instance, for non-authenticated 1572 encryption algorithms. Other values may be used with the approval 1573 of a Designated Expert. 1575 JOSE Implementation Requirements: 1576 The algorithm implementation requirements for JWS and JWE, which 1577 must be one the words Required, Recommended, Optional, Deprecated, 1578 or Prohibited. Optionally, the word can be followed by a "+" or 1579 "-". The use of "+" indicates that the requirement strength is 1580 likely to be increased in a future version of the specification. 1581 The use of "-" indicates that the requirement strength is likely 1582 to be decreased in a future version of the specification. Any 1583 identifiers registered for non-authenticated encryption algorithms 1584 or other algorithms that are otherwise unsuitable for direct use 1585 as JWS or JWE algorithms must be registered as "Prohibited". 1587 Change Controller: 1588 For Standards Track RFCs, state "IESG". For others, give the name 1589 of the responsible party. Other details (e.g., postal address, 1590 email address, home page URI) may also be included. 1592 Specification Document(s): 1593 Reference to the document(s) that specify the parameter, 1594 preferably including URI(s) that can be used to retrieve copies of 1595 the document(s). An indication of the relevant sections may also 1596 be included but is not required. 1598 7.1.2. Initial Registry Contents 1600 o Algorithm Name: "HS256" 1601 o Algorithm Description: HMAC using SHA-256 1602 o Algorithm Usage Location(s): "alg" 1603 o JOSE Implementation Requirements: Required 1604 o Change Controller: IESG 1605 o Specification Document(s): Section 3.1 of [[ this document ]] 1607 o Algorithm Name: "HS384" 1608 o Algorithm Description: HMAC using SHA-384 1609 o Algorithm Usage Location(s): "alg" 1610 o JOSE Implementation Requirements: Optional 1611 o Change Controller: IESG 1612 o Specification Document(s): Section 3.1 of [[ this document ]] 1614 o Algorithm Name: "HS512" 1615 o Algorithm Description: HMAC using SHA-512 1616 o Algorithm Usage Location(s): "alg" 1617 o JOSE Implementation Requirements: Optional 1618 o Change Controller: IESG 1619 o Specification Document(s): Section 3.1 of [[ this document ]] 1621 o Algorithm Name: "RS256" 1622 o Algorithm Description: RSASSA-PKCS-v1_5 using SHA-256 1623 o Algorithm Usage Location(s): "alg" 1624 o JOSE Implementation Requirements: Recommended 1625 o Change Controller: IESG 1626 o Specification Document(s): Section 3.1 of [[ this document ]] 1628 o Algorithm Name: "RS384" 1629 o Algorithm Description: RSASSA-PKCS-v1_5 using SHA-384 1630 o Algorithm Usage Location(s): "alg" 1631 o JOSE Implementation Requirements: Optional 1632 o Change Controller: IESG 1633 o Specification Document(s): Section 3.1 of [[ this document ]] 1635 o Algorithm Name: "RS512" 1636 o Algorithm Description: RSASSA-PKCS-v1_5 using SHA-512 1637 o Algorithm Usage Location(s): "alg" 1638 o JOSE Implementation Requirements: Optional 1639 o Change Controller: IESG 1640 o Specification Document(s): Section 3.1 of [[ this document ]] 1642 o Algorithm Name: "ES256" 1643 o Algorithm Description: ECDSA using P-256 and SHA-256 1644 o Algorithm Usage Location(s): "alg" 1645 o JOSE Implementation Requirements: Recommended+ 1646 o Change Controller: IESG 1647 o Specification Document(s): Section 3.1 of [[ this document ]] 1649 o Algorithm Name: "ES384" 1650 o Algorithm Description: ECDSA using P-384 and SHA-384 1651 o Algorithm Usage Location(s): "alg" 1652 o JOSE Implementation Requirements: Optional 1653 o Change Controller: IESG 1654 o Specification Document(s): Section 3.1 of [[ this document ]] 1656 o Algorithm Name: "ES512" 1657 o Algorithm Description: ECDSA using P-521 and SHA-512 1658 o Algorithm Usage Location(s): "alg" 1659 o JOSE Implementation Requirements: Optional 1660 o Change Controller: IESG 1661 o Specification Document(s): Section 3.1 of [[ this document ]] 1663 o Algorithm Name: "PS256" 1664 o Algorithm Description: RSASSA-PSS using SHA-256 and MGF1 with SHA- 1665 256 1666 o Algorithm Usage Location(s): "alg" 1667 o JOSE Implementation Requirements: Optional 1668 o Change Controller: IESG 1669 o Specification Document(s): Section 3.1 of [[ this document ]] 1671 o Algorithm Name: "PS384" 1672 o Algorithm Description: RSASSA-PSS using SHA-384 and MGF1 with SHA- 1673 384 1674 o Algorithm Usage Location(s): "alg" 1675 o JOSE Implementation Requirements: Optional 1676 o Change Controller: IESG 1677 o Specification Document(s): Section 3.1 of [[ this document ]] 1678 o Algorithm Name: "PS512" 1679 o Algorithm Description: RSASSA-PSS using SHA-512 and MGF1 with SHA- 1680 512 1681 o Algorithm Usage Location(s): "alg" 1682 o JOSE Implementation Requirements: Optional 1683 o Change Controller: IESG 1684 o Specification Document(s): Section 3.1 of [[ this document ]] 1686 o Algorithm Name: "none" 1687 o Algorithm Description: No digital signature or MAC performed 1688 o Algorithm Usage Location(s): "alg" 1689 o JOSE Implementation Requirements: Optional 1690 o Change Controller: IESG 1691 o Specification Document(s): Section 3.1 of [[ this document ]] 1693 o Algorithm Name: "RSA1_5" 1694 o Algorithm Description: RSAES-PKCS1-V1_5 1695 o Algorithm Usage Location(s): "alg" 1696 o JOSE Implementation Requirements: Required 1697 o Change Controller: IESG 1698 o Specification Document(s): Section 4.1 of [[ this document ]] 1700 o Algorithm Name: "RSA-OAEP" 1701 o Algorithm Description: RSAES OAEP using default parameters 1702 o Algorithm Usage Location(s): "alg" 1703 o JOSE Implementation Requirements: Optional 1704 o Change Controller: IESG 1705 o Specification Document(s): Section 4.1 of [[ this document ]] 1707 o Algorithm Name: "RSA-OAEP-256" 1708 o Algorithm Description: RSAES OAEP using SHA-256 and MGF1 with SHA- 1709 256 1710 o Algorithm Usage Location(s): "alg" 1711 o JOSE Implementation Requirements: Optional 1712 o Change Controller: IESG 1713 o Specification Document(s): Section 4.1 of [[ this document ]] 1715 o Algorithm Name: "A128KW" 1716 o Algorithm Description: AES Key Wrap using 128 bit key 1717 o Algorithm Usage Location(s): "alg" 1718 o JOSE Implementation Requirements: Recommended 1719 o Change Controller: IESG 1720 o Specification Document(s): Section 4.1 of [[ this document ]] 1722 o Algorithm Name: "A192KW" 1723 o Algorithm Description: AES Key Wrap using 192 bit key 1724 o Algorithm Usage Location(s): "alg" 1725 o JOSE Implementation Requirements: Optional 1726 o Change Controller: IESG 1727 o Specification Document(s): Section 4.1 of [[ this document ]] 1729 o Algorithm Name: "A256KW" 1730 o Algorithm Description: AES Key Wrap using 256 bit key 1731 o Algorithm Usage Location(s): "alg" 1732 o JOSE Implementation Requirements: Recommended 1733 o Change Controller: IESG 1734 o Specification Document(s): Section 4.1 of [[ this document ]] 1736 o Algorithm Name: "dir" 1737 o Algorithm Description: Direct use of a shared symmetric key 1738 o Algorithm Usage Location(s): "alg" 1739 o JOSE Implementation Requirements: Recommended 1740 o Change Controller: IESG 1741 o Specification Document(s): Section 4.1 of [[ this document ]] 1743 o Algorithm Name: "ECDH-ES" 1744 o Algorithm Description: ECDH-ES using Concat KDF 1745 o Algorithm Usage Location(s): "alg" 1746 o JOSE Implementation Requirements: Recommended+ 1747 o Change Controller: IESG 1748 o Specification Document(s): Section 4.1 of [[ this document ]] 1750 o Algorithm Name: "ECDH-ES+A128KW" 1751 o Algorithm Description: ECDH-ES using Concat KDF and "A128KW" 1752 wrapping 1753 o Algorithm Usage Location(s): "alg" 1754 o JOSE Implementation Requirements: Recommended 1755 o Change Controller: IESG 1756 o Specification Document(s): Section 4.1 of [[ this document ]] 1758 o Algorithm Name: "ECDH-ES+A192KW" 1759 o Algorithm Description: ECDH-ES using Concat KDF and "A192KW" 1760 wrapping 1761 o Algorithm Usage Location(s): "alg" 1762 o JOSE Implementation Requirements: Optional 1763 o Change Controller: IESG 1764 o Specification Document(s): Section 4.1 of [[ this document ]] 1766 o Algorithm Name: "ECDH-ES+A256KW" 1767 o Algorithm Description: ECDH-ES using Concat KDF and "A256KW" 1768 wrapping 1769 o Algorithm Usage Location(s): "alg" 1770 o JOSE Implementation Requirements: Recommended 1771 o Change Controller: IESG 1772 o Specification Document(s): Section 4.1 of [[ this document ]] 1774 o Algorithm Name: "A128GCMKW" 1775 o Algorithm Description: Key wrapping with AES GCM using 128 bit key 1776 o Algorithm Usage Location(s): "alg" 1777 o JOSE Implementation Requirements: Optional 1778 o Change Controller: IESG 1779 o Specification Document(s): Section 4.7 of [[ this document ]] 1781 o Algorithm Name: "A192GCMKW" 1782 o Algorithm Description: Key wrapping with AES GCM using 192 bit key 1783 o Algorithm Usage Location(s): "alg" 1784 o JOSE Implementation Requirements: Optional 1785 o Change Controller: IESG 1786 o Specification Document(s): Section 4.7 of [[ this document ]] 1788 o Algorithm Name: "A256GCMKW" 1789 o Algorithm Description: Key wrapping with AES GCM using 256 bit key 1790 o Algorithm Usage Location(s): "alg" 1791 o JOSE Implementation Requirements: Optional 1792 o Change Controller: IESG 1793 o Specification Document(s): Section 4.7 of [[ this document ]] 1795 o Algorithm Name: "PBES2-HS256+A128KW" 1796 o Algorithm Description: PBES2 with HMAC SHA-256 and "A128KW" 1797 wrapping 1798 o Algorithm Usage Location(s): "alg" 1799 o JOSE Implementation Requirements: Optional 1800 o Change Controller: IESG 1801 o Specification Document(s): Section 4.8 of [[ this document ]] 1803 o Algorithm Name: "PBES2-HS384+A192KW" 1804 o Algorithm Description: PBES2 with HMAC SHA-384 and "A192KW" 1805 wrapping 1806 o Algorithm Usage Location(s): "alg" 1807 o JOSE Implementation Requirements: Optional 1808 o Change Controller: IESG 1809 o Specification Document(s): Section 4.8 of [[ this document ]] 1811 o Algorithm Name: "PBES2-HS512+A256KW" 1812 o Algorithm Description: PBES2 with HMAC SHA-512 and "A256KW" 1813 wrapping 1814 o Algorithm Usage Location(s): "alg" 1815 o JOSE Implementation Requirements: Optional 1816 o Change Controller: IESG 1817 o Specification Document(s): Section 4.8 of [[ this document ]] 1819 o Algorithm Name: "A128CBC-HS256" 1820 o Algorithm Description: AES_128_CBC_HMAC_SHA_256 authenticated 1821 encryption algorithm 1822 o Algorithm Usage Location(s): "enc" 1823 o JOSE Implementation Requirements: Required 1824 o Change Controller: IESG 1825 o Specification Document(s): Section 5.1 of [[ this document ]] 1827 o Algorithm Name: "A192CBC-HS384" 1828 o Algorithm Description: AES_192_CBC_HMAC_SHA_384 authenticated 1829 encryption algorithm 1830 o Algorithm Usage Location(s): "enc" 1831 o JOSE Implementation Requirements: Optional 1832 o Change Controller: IESG 1833 o Specification Document(s): Section 5.1 of [[ this document ]] 1835 o Algorithm Name: "A256CBC-HS512" 1836 o Algorithm Description: AES_256_CBC_HMAC_SHA_512 authenticated 1837 encryption algorithm 1838 o Algorithm Usage Location(s): "enc" 1839 o JOSE Implementation Requirements: Required 1840 o Change Controller: IESG 1841 o Specification Document(s): Section 5.1 of [[ this document ]] 1843 o Algorithm Name: "A128GCM" 1844 o Algorithm Description: AES GCM using 128 bit key 1845 o Algorithm Usage Location(s): "enc" 1846 o JOSE Implementation Requirements: Recommended 1847 o Change Controller: IESG 1848 o Specification Document(s): Section 5.1 of [[ this document ]] 1850 o Algorithm Name: "A192GCM" 1851 o Algorithm Description: AES GCM using 192 bit key 1852 o Algorithm Usage Location(s): "enc" 1853 o JOSE Implementation Requirements: Optional 1854 o Change Controller: IESG 1855 o Specification Document(s): Section 5.1 of [[ this document ]] 1857 o Algorithm Name: "A256GCM" 1858 o Algorithm Description: AES GCM using 256 bit key 1859 o Algorithm Usage Location(s): "enc" 1860 o JOSE Implementation Requirements: Recommended 1861 o Change Controller: IESG 1862 o Specification Document(s): Section 5.1 of [[ this document ]] 1864 7.2. Header Parameter Names Registration 1866 This specification registers the Header Parameter names defined in 1867 Section 4.6.1, Section 4.7.1, and Section 4.8.1 in the IANA JSON Web 1868 Signature and Encryption Header Parameters registry defined in [JWS]. 1870 7.2.1. Registry Contents 1872 o Header Parameter Name: "epk" 1873 o Header Parameter Description: Ephemeral Public Key 1874 o Header Parameter Usage Location(s): JWE 1875 o Change Controller: IESG 1876 o Specification Document(s): Section 4.6.1.1 of [[ this document ]] 1878 o Header Parameter Name: "apu" 1879 o Header Parameter Description: Agreement PartyUInfo 1880 o Header Parameter Usage Location(s): JWE 1881 o Change Controller: IESG 1882 o Specification Document(s): Section 4.6.1.2 of [[ this document ]] 1884 o Header Parameter Name: "apv" 1885 o Header Parameter Description: Agreement PartyVInfo 1886 o Header Parameter Usage Location(s): JWE 1887 o Change Controller: IESG 1888 o Specification Document(s): Section 4.6.1.3 of [[ this document ]] 1890 o Header Parameter Name: "iv" 1891 o Header Parameter Description: Initialization Vector 1892 o Header Parameter Usage Location(s): JWE 1893 o Change Controller: IESG 1894 o Specification Document(s): Section 4.7.1.1 of [[ this document ]] 1896 o Header Parameter Name: "tag" 1897 o Header Parameter Description: Authentication Tag 1898 o Header Parameter Usage Location(s): JWE 1899 o Change Controller: IESG 1900 o Specification Document(s): Section 4.7.1.2 of [[ this document ]] 1902 o Header Parameter Name: "p2s" 1903 o Header Parameter Description: PBES2 salt 1904 o Header Parameter Usage Location(s): JWE 1905 o Change Controller: IESG 1906 o Specification Document(s): Section 4.8.1.1 of [[ this document ]] 1907 o Header Parameter Name: "p2c" 1908 o Header Parameter Description: PBES2 count 1909 o Header Parameter Usage Location(s): JWE 1910 o Change Controller: IESG 1911 o Specification Document(s): Section 4.8.1.2 of [[ this document ]] 1913 7.3. JSON Web Encryption Compression Algorithms Registry 1915 This specification establishes the IANA JSON Web Encryption 1916 Compression Algorithms registry for JWE "zip" member values. The 1917 registry records the compression algorithm value and a reference to 1918 the specification that defines it. 1920 7.3.1. Registration Template 1922 Compression Algorithm Value: 1923 The name requested (e.g., "example"). Because a core goal of this 1924 specification is for the resulting representations to be compact, 1925 it is RECOMMENDED that the name be short -- not to exceed 8 1926 characters without a compelling reason to do so. This name is 1927 case-sensitive. Names may not match other registered names in a 1928 case-insensitive manner unless the Designated Expert(s) state that 1929 there is a compelling reason to allow an exception in this 1930 particular case. 1932 Compression Algorithm Description: 1933 Brief description of the compression algorithm (e.g., "Example 1934 description"). 1936 Change Controller: 1937 For Standards Track RFCs, state "IESG". For others, give the name 1938 of the responsible party. Other details (e.g., postal address, 1939 email address, home page URI) may also be included. 1941 Specification Document(s): 1942 Reference to the document(s) that specify the parameter, 1943 preferably including URI(s) that can be used to retrieve copies of 1944 the document(s). An indication of the relevant sections may also 1945 be included but is not required. 1947 7.3.2. Initial Registry Contents 1949 o Compression Algorithm Value: "DEF" 1950 o Compression Algorithm Description: DEFLATE 1951 o Change Controller: IESG 1952 o Specification Document(s): JSON Web Encryption (JWE) [JWE] 1954 7.4. JSON Web Key Types Registry 1956 This specification establishes the IANA JSON Web Key Types registry 1957 for values of the JWK "kty" (key type) parameter. The registry 1958 records the "kty" value, implementation requirements, and a reference 1959 to the specification that defines it. 1961 The implementation requirements of a key type MAY be changed over 1962 time by the Designated Experts(s) as the cryptographic landscape 1963 evolves, for instance, to change the status of a key type to 1964 Deprecated, or to change the status of a key type from Optional to 1965 Recommended+ or Required. Changes of implementation requirements are 1966 only permitted on a Specification Required basis, with the new 1967 specification defining the revised implementation requirements level. 1969 7.4.1. Registration Template 1971 "kty" Parameter Value: 1972 The name requested (e.g., "example"). Because a core goal of this 1973 specification is for the resulting representations to be compact, 1974 it is RECOMMENDED that the name be short -- not to exceed 8 1975 characters without a compelling reason to do so. This name is 1976 case-sensitive. Names may not match other registered names in a 1977 case-insensitive manner unless the Designated Expert(s) state that 1978 there is a compelling reason to allow an exception in this 1979 particular case. 1981 Key Type Description: 1982 Brief description of the Key Type (e.g., "Example description"). 1984 Change Controller: 1985 For Standards Track RFCs, state "IESG". For others, give the name 1986 of the responsible party. Other details (e.g., postal address, 1987 email address, home page URI) may also be included. 1989 JOSE Implementation Requirements: 1990 The key type implementation requirements for JWS and JWE, which 1991 must be one the words Required, Recommended, Optional, Deprecated, 1992 or Prohibited. Optionally, the word can be followed by a "+" or 1993 "-". The use of "+" indicates that the requirement strength is 1994 likely to be increased in a future version of the specification. 1995 The use of "-" indicates that the requirement strength is likely 1996 to be decreased in a future version of the specification. 1998 Specification Document(s): 1999 Reference to the document(s) that specify the parameter, 2000 preferably including URI(s) that can be used to retrieve copies of 2001 the document(s). An indication of the relevant sections may also 2002 be included but is not required. 2004 7.4.2. Initial Registry Contents 2006 This specification registers the values defined in Section 6.1. 2008 o "kty" Parameter Value: "EC" 2009 o Key Type Description: Elliptic Curve 2010 o JOSE Implementation Requirements: Recommended+ 2011 o Change Controller: IESG 2012 o Specification Document(s): Section 6.2 of [[ this document ]] 2014 o "kty" Parameter Value: "RSA" 2015 o Key Type Description: RSA 2016 o JOSE Implementation Requirements: Required 2017 o Change Controller: IESG 2018 o Specification Document(s): Section 6.3 of [[ this document ]] 2020 o "kty" Parameter Value: "oct" 2021 o Key Type Description: Octet sequence 2022 o JOSE Implementation Requirements: Required 2023 o Change Controller: IESG 2024 o Specification Document(s): Section 6.4 of [[ this document ]] 2026 7.5. JSON Web Key Parameters Registration 2028 This specification registers the parameter names defined in Sections 2029 6.2, 6.3, and 6.4 in the IANA JSON Web Key Parameters registry 2030 defined in [JWK]. 2032 7.5.1. Registry Contents 2034 o Parameter Name: "crv" 2035 o Parameter Description: Curve 2036 o Used with "kty" Value(s): "EC" 2037 o Parameter Information Class: Public 2038 o Change Controller: IESG 2039 o Specification Document(s): Section 6.2.1.1 of [[ this document ]] 2041 o Parameter Name: "x" 2042 o Parameter Description: X Coordinate 2043 o Used with "kty" Value(s): "EC" 2044 o Parameter Information Class: Public 2045 o Change Controller: IESG 2046 o Specification Document(s): Section 6.2.1.2 of [[ this document ]] 2047 o Parameter Name: "y" 2048 o Parameter Description: Y Coordinate 2049 o Used with "kty" Value(s): "EC" 2050 o Parameter Information Class: Public 2051 o Change Controller: IESG 2052 o Specification Document(s): Section 6.2.1.3 of [[ this document ]] 2054 o Parameter Name: "d" 2055 o Parameter Description: ECC Private Key 2056 o Used with "kty" Value(s): "EC" 2057 o Parameter Information Class: Private 2058 o Change Controller: IESG 2059 o Specification Document(s): Section 6.2.2.1 of [[ this document ]] 2061 o Parameter Name: "n" 2062 o Parameter Description: Modulus 2063 o Used with "kty" Value(s): "RSA" 2064 o Parameter Information Class: Public 2065 o Change Controller: IESG 2066 o Specification Document(s): Section 6.3.1.1 of [[ this document ]] 2068 o Parameter Name: "e" 2069 o Parameter Description: Exponent 2070 o Used with "kty" Value(s): "RSA" 2071 o Parameter Information Class: Public 2072 o Change Controller: IESG 2073 o Specification Document(s): Section 6.3.1.2 of [[ this document ]] 2075 o Parameter Name: "d" 2076 o Parameter Description: Private Exponent 2077 o Used with "kty" Value(s): "RSA" 2078 o Parameter Information Class: Private 2079 o Change Controller: IESG 2080 o Specification Document(s): Section 6.3.2.1 of [[ this document ]] 2082 o Parameter Name: "p" 2083 o Parameter Description: First Prime Factor 2084 o Used with "kty" Value(s): "RSA" 2085 o Parameter Information Class: Private 2086 o Change Controller: IESG 2087 o Specification Document(s): Section 6.3.2.2 of [[ this document ]] 2089 o Parameter Name: "q" 2090 o Parameter Description: Second Prime Factor 2091 o Used with "kty" Value(s): "RSA" 2092 o Parameter Information Class: Private 2093 o Change Controller: IESG 2094 o Specification Document(s): Section 6.3.2.3 of [[ this document ]] 2096 o Parameter Name: "dp" 2097 o Parameter Description: First Factor CRT Exponent 2098 o Used with "kty" Value(s): "RSA" 2099 o Parameter Information Class: Private 2100 o Change Controller: IESG 2101 o Specification Document(s): Section 6.3.2.4 of [[ this document ]] 2103 o Parameter Name: "dq" 2104 o Parameter Description: Second Factor CRT Exponent 2105 o Used with "kty" Value(s): "RSA" 2106 o Parameter Information Class: Private 2107 o Change Controller: IESG 2108 o Specification Document(s): Section 6.3.2.5 of [[ this document ]] 2110 o Parameter Name: "qi" 2111 o Parameter Description: First CRT Coefficient 2112 o Used with "kty" Value(s): "RSA" 2113 o Parameter Information Class: Private 2114 o Change Controller: IESG 2115 o Specification Document(s): Section 6.3.2.6 of [[ this document ]] 2117 o Parameter Name: "oth" 2118 o Parameter Description: Other Primes Info 2119 o Used with "kty" Value(s): "RSA" 2120 o Parameter Information Class: Private 2121 o Change Controller: IESG 2122 o Specification Document(s): Section 6.3.2.7 of [[ this document ]] 2124 o Parameter Name: "k" 2125 o Parameter Description: Key Value 2126 o Used with "kty" Value(s): "oct" 2127 o Parameter Information Class: Private 2128 o Change Controller: IESG 2129 o Specification Document(s): Section 6.4.1 of [[ this document ]] 2131 7.6. JSON Web Key Elliptic Curve Registry 2133 This specification establishes the IANA JSON Web Key Elliptic Curve 2134 registry for JWK "crv" member values. The registry records the curve 2135 name, implementation requirements, and a reference to the 2136 specification that defines it. This specification registers the 2137 parameter names defined in Section 6.2.1.1. 2139 The implementation requirements of a curve MAY be changed over time 2140 by the Designated Experts(s) as the cryptographic landscape evolves, 2141 for instance, to change the status of a curve to Deprecated, or to 2142 change the status of a curve from Optional to Recommended+ or 2143 Required. Changes of implementation requirements are only permitted 2144 on a Specification Required basis, with the new specification 2145 defining the revised implementation requirements level. 2147 7.6.1. Registration Template 2149 Curve Name: 2150 The name requested (e.g., "example"). Because a core goal of this 2151 specification is for the resulting representations to be compact, 2152 it is RECOMMENDED that the name be short -- not to exceed 8 2153 characters without a compelling reason to do so. This name is 2154 case-sensitive. Names may not match other registered names in a 2155 case-insensitive manner unless the Designated Expert(s) state that 2156 there is a compelling reason to allow an exception in this 2157 particular case. 2159 Curve Description: 2160 Brief description of the curve (e.g., "Example description"). 2162 JOSE Implementation Requirements: 2163 The curve implementation requirements for JWS and JWE, which must 2164 be one the words Required, Recommended, Optional, Deprecated, or 2165 Prohibited. Optionally, the word can be followed by a "+" or "-". 2166 The use of "+" indicates that the requirement strength is likely 2167 to be increased in a future version of the specification. The use 2168 of "-" indicates that the requirement strength is likely to be 2169 decreased in a future version of the specification. 2171 Change Controller: 2172 For Standards Track RFCs, state "IESG". For others, give the name 2173 of the responsible party. Other details (e.g., postal address, 2174 email address, home page URI) may also be included. 2176 Specification Document(s): 2177 Reference to the document(s) that specify the parameter, 2178 preferably including URI(s) that can be used to retrieve copies of 2179 the document(s). An indication of the relevant sections may also 2180 be included but is not required. 2182 7.6.2. Initial Registry Contents 2184 o Curve Name: "P-256" 2185 o Curve Description: P-256 curve 2186 o JOSE Implementation Requirements: Recommended+ 2187 o Change Controller: IESG 2188 o Specification Document(s): Section 6.2.1.1 of [[ this document ]] 2190 o Curve Name: "P-384" 2191 o Curve Description: P-384 curve 2192 o JOSE Implementation Requirements: Optional 2193 o Change Controller: IESG 2194 o Specification Document(s): Section 6.2.1.1 of [[ this document ]] 2196 o Curve Name: "P-521" 2197 o Curve Description: P-521 curve 2198 o JOSE Implementation Requirements: Optional 2199 o Change Controller: IESG 2200 o Specification Document(s): Section 6.2.1.1 of [[ this document ]] 2202 8. Security Considerations 2204 All of the security issues faced by any cryptographic application 2205 must be faced by a JWS/JWE/JWK agent. Among these issues are 2206 protecting the user's asymmetric private and symmetric secret keys, 2207 preventing various attacks, and helping avoid mistakes such as 2208 inadvertently encrypting a message to the wrong recipient. The 2209 entire list of security considerations is beyond the scope of this 2210 document, but some significant considerations are listed here. 2212 The security considerations in [AES], [DSS], [JWE], [JWK], [JWS], 2213 [NIST.800-38A], [NIST.800-38D], [NIST.800-56A], [RFC2104], [RFC3394], 2214 [RFC3447], [RFC5116], [RFC6090], and [SHS] apply to this 2215 specification. 2217 8.1. Algorithms and Key Sizes will be Deprecated 2219 Eventually the algorithms and/or key sizes currently described in 2220 this specification will no longer be considered sufficiently secure 2221 and will be deprecated. Therefore, implementers and deployments must 2222 be prepared for this eventuality. 2224 8.2. Key Lifetimes 2226 Many algorithms have associated security considerations related to 2227 key lifetimes and/or the number of times that a key may be used. 2228 Those security considerations continue to apply when using those 2229 algorithms with JOSE data structures. 2231 8.3. RSAES-PKCS1-v1_5 Security Considerations 2233 While Section 8 of RFC 3447 [RFC3447] explicitly calls for people not 2234 to adopt RSASSA-PKCS-v1_5 for new applications and instead requests 2235 that people transition to RSASSA-PSS, this specification does include 2236 RSASSA-PKCS-v1_5, for interoperability reasons, because it commonly 2237 implemented. 2239 Keys used with RSAES-PKCS1-v1_5 must follow the constraints in 2240 Section 7.2 of RFC 3447 [RFC3447]. In particular, keys with a low 2241 public key exponent value must not be used. 2243 8.4. AES GCM Security Considerations 2245 Keys used with AES GCM must follow the constraints in Section 8.3 of 2246 [NIST.800-38D], which states: "The total number of invocations of the 2247 authenticated encryption function shall not exceed 2^32, including 2248 all IV lengths and all instances of the authenticated encryption 2249 function with the given key". In accordance with this rule, AES GCM 2250 MUST NOT be used with the same key value more than 2^32 times. 2252 An Initialization Vector value MUST never be used multiple times with 2253 the same AES GCM key. One way to prevent this is to store a counter 2254 with the key and increment it with every use. The counter can also 2255 be used to prevent exceeding the 2^32 limit above. 2257 This security consideration does not apply to the composite AES-CBC 2258 HMAC SHA-2 or AES Key Wrap algorithms. 2260 8.5. Plaintext JWS Security Considerations 2262 Plaintext JWSs (JWSs that use the "alg" value "none") provide no 2263 integrity protection. Thus, they must only be used in contexts where 2264 the payload is secured by means other than a digital signature or MAC 2265 value, or need not be secured. 2267 Implementations that support Plaintext JWS objects MUST NOT accept 2268 such objects as valid unless the application specifies that it is 2269 acceptable for a specific object to not be integrity-protected. 2270 Implementations MUST NOT accept Plaintext JWS objects by default. 2271 For example, the "verify" method of a hypothetical JWS software 2272 library might have a Boolean "acceptUnsigned" parameter that 2273 indicates "none" is an acceptable "alg" value. As another example, 2274 the "verify" method might take a list of algorithms that are 2275 acceptable to the application as a parameter and would reject 2276 Plaintext JWS values if "none" is not in that list. 2278 In order to mitigate downgrade attacks, applications MUST NOT signal 2279 acceptance of Plaintext JWS objects at a global level, and SHOULD 2280 signal acceptance on a per-object basis. For example, suppose an 2281 application accepts JWS objects over two channels, (1) HTTP and (2) 2282 HTTPS with client authentication. It requires a JWS signature on 2283 objects received over HTTP, but accepts Plaintext JWS objects over 2284 HTTPS. If the application were to globally indicate that "none" is 2285 acceptable, then an attacker could provide it with an unsigned object 2286 over HTTP and still have that object successfully validate. Instead, 2287 the application needs to indicate acceptance of "none" for each 2288 object received over HTTPS (e.g., by setting "acceptUnsigned" to 2289 "true" for the first hypothetical JWS software library above), but 2290 not for each object received over HTTP. 2292 8.6. Denial of Service Attacks 2294 Receiving agents that validate signatures and sending agents that 2295 encrypt messages need to be cautious of cryptographic processing 2296 usage when validating signatures and encrypting messages using keys 2297 larger than those mandated in this specification. An attacker could 2298 send certificates with keys that would result in excessive 2299 cryptographic processing, for example, keys larger than those 2300 mandated in this specification, which could swamp the processing 2301 element. Agents that use such keys without first validating the 2302 certificate to a trust anchor are advised to have some sort of 2303 cryptographic resource management system to prevent such attacks. 2305 8.7. Reusing Key Material when Encrypting Keys 2307 It is NOT RECOMMENDED to reuse the same key material (Key Encryption 2308 Key, Content Encryption Key, Initialization Vector, etc.) to encrypt 2309 multiple JWK or JWK Set objects, or to encrypt the same JWK or JWK 2310 Set object multiple times. One suggestion for preventing re-use is 2311 to always generate a new set key material for each encryption 2312 operation, based on the considerations noted in this document as well 2313 as from [RFC4086]. 2315 8.8. Password Considerations 2317 Passwords are vulnerable to a number of attacks. To help mitigate 2318 some of these limitations, this document applies principles from 2319 [RFC2898] to derive cryptographic keys from user-supplied passwords. 2321 However, the strength of the password still has a significant impact. 2322 A high-entropy password has greater resistance to dictionary attacks. 2323 [NIST-800-63-1] contains guidelines for estimating password entropy, 2324 which can help applications and users generate stronger passwords. 2326 An ideal password is one that is as large as (or larger than) the 2327 derived key length. However, passwords larger than a certain 2328 algorithm-specific size are first hashed, which reduces an attacker's 2329 effective search space to the length of the hash algorithm. It is 2330 RECOMMENDED that a password used for "PBES2-HS256+A128KW" be no 2331 shorter than 16 octets and no longer than 128 octets and a password 2332 used for "PBES2-HS512+A256KW" be no shorter than 32 octets and no 2333 longer than 128 octets long. 2335 Still, care needs to be taken in where and how password-based 2336 encryption is used. These algorithms can still be susceptible to 2337 dictionary-based attacks if the iteration count is too small; this is 2338 of particular concern if these algorithms are used to protect data 2339 that an attacker can have indefinite number of attempts to circumvent 2340 the protection, such as protected data stored on a file system. 2342 8.9. Key Entropy 2344 See Section 10.1 of [JWS] for security considerations on key entropy. 2346 8.10. Differences between Digital Signatures and MACs 2348 See Section 10.4 of [JWS] for security considerations on differences 2349 between digital signatures and MACs. 2351 8.11. Using Matching Algorithm Strengths 2353 See Section 11.1 of [JWE] for security considerations on using 2354 matching algorithm strengths. 2356 8.12. Adaptive Chosen-Ciphertext Attacks 2358 See Section 11.2 of [JWE] for security considerations on adaptive 2359 chosen-ciphertext attacks. 2361 8.13. Timing Attacks 2363 See Section 10.3 of [JWS] and Section 11.3 of [JWE] for security 2364 considerations on timing attacks. 2366 8.14. RSA Private Key Representations and Blinding 2368 See Section 9.3 of [JWK] for security considerations on RSA private 2369 key representations and blinding. 2371 9. Internationalization Considerations 2373 Passwords obtained from users are likely to require preparation and 2374 normalization to account for differences of octet sequences generated 2375 by different input devices, locales, etc. It is RECOMMENDED that 2376 applications to perform the steps outlined in 2377 [I-D.ietf-precis-saslprepbis] to prepare a password supplied directly 2378 by a user before performing key derivation and encryption. 2380 10. References 2382 10.1. Normative References 2384 [AES] National Institute of Standards and Technology (NIST), 2385 "Advanced Encryption Standard (AES)", FIPS PUB 197, 2386 November 2001. 2388 [DSS] National Institute of Standards and Technology, "Digital 2389 Signature Standard (DSS)", FIPS PUB 186-4, July 2013. 2391 [JWE] Jones, M. and J. Hildebrand, "JSON Web Encryption (JWE)", 2392 draft-ietf-jose-json-web-encryption (work in progress), 2393 June 2014. 2395 [JWK] Jones, M., "JSON Web Key (JWK)", 2396 draft-ietf-jose-json-web-key (work in progress), 2397 June 2014. 2399 [JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web 2400 Signature (JWS)", draft-ietf-jose-json-web-signature (work 2401 in progress), June 2014. 2403 [NIST.800-38A] 2404 National Institute of Standards and Technology (NIST), 2405 "Recommendation for Block Cipher Modes of Operation", 2406 NIST PUB 800-38A, December 2001. 2408 [NIST.800-38D] 2409 National Institute of Standards and Technology (NIST), 2410 "Recommendation for Block Cipher Modes of Operation: 2411 Galois/Counter Mode (GCM) and GMAC", NIST PUB 800-38D, 2412 December 2001. 2414 [NIST.800-56A] 2415 National Institute of Standards and Technology (NIST), 2416 "Recommendation for Pair-Wise Key Establishment Schemes 2417 Using Discrete Logarithm Cryptography", NIST Special 2418 Publication 800-56A, Revision 2, May 2013. 2420 [RFC2104] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed- 2421 Hashing for Message Authentication", RFC 2104, 2422 February 1997. 2424 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2425 Requirement Levels", BCP 14, RFC 2119, March 1997. 2427 [RFC2898] Kaliski, B., "PKCS #5: Password-Based Cryptography 2428 Specification Version 2.0", RFC 2898, September 2000. 2430 [RFC3394] Schaad, J. and R. Housley, "Advanced Encryption Standard 2431 (AES) Key Wrap Algorithm", RFC 3394, September 2002. 2433 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 2434 10646", STD 63, RFC 3629, November 2003. 2436 [RFC4868] Kelly, S. and S. Frankel, "Using HMAC-SHA-256, HMAC-SHA- 2437 384, and HMAC-SHA-512 with IPsec", RFC 4868, May 2007. 2439 [RFC6090] McGrew, D., Igoe, K., and M. Salter, "Fundamental Elliptic 2440 Curve Cryptography Algorithms", RFC 6090, February 2011. 2442 [RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data 2443 Interchange Format", RFC 7159, March 2014. 2445 [SEC1] Standards for Efficient Cryptography Group, "SEC 1: 2446 Elliptic Curve Cryptography", May 2009. 2448 [SHS] National Institute of Standards and Technology, "Secure 2449 Hash Standard (SHS)", FIPS PUB 180-3, October 2008. 2451 [USASCII] American National Standards Institute, "Coded Character 2452 Set -- 7-bit American Standard Code for Information 2453 Interchange", ANSI X3.4, 1986. 2455 10.2. Informative References 2457 [CanvasApp] 2458 Facebook, "Canvas Applications", 2010. 2460 [I-D.ietf-precis-saslprepbis] 2461 Saint-Andre, P. and A. Melnikov, "Preparation and 2462 Comparison of Internationalized Strings Representing 2463 Usernames and Passwords", draft-ietf-precis-saslprepbis-07 2464 (work in progress), March 2014. 2466 [I-D.mcgrew-aead-aes-cbc-hmac-sha2] 2467 McGrew, D., Foley, J., and K. Paterson, "Authenticated 2468 Encryption with AES-CBC and HMAC-SHA", 2469 draft-mcgrew-aead-aes-cbc-hmac-sha2-04 (work in progress), 2470 February 2014. 2472 [I-D.miller-jose-jwe-protected-jwk] 2473 Miller, M., "Using JavaScript Object Notation (JSON) Web 2474 Encryption (JWE) for Protecting JSON Web Key (JWK) 2475 Objects", draft-miller-jose-jwe-protected-jwk-02 (work in 2476 progress), June 2013. 2478 [I-D.rescorla-jsms] 2479 Rescorla, E. and J. Hildebrand, "JavaScript Message 2480 Security Format", draft-rescorla-jsms-00 (work in 2481 progress), March 2011. 2483 [JCA] Oracle, "Java Cryptography Architecture (JCA) Reference 2484 Guide", 2014. 2486 [JSE] Bradley, J. and N. Sakimura (editor), "JSON Simple 2487 Encryption", September 2010. 2489 [JSS] Bradley, J. and N. Sakimura (editor), "JSON Simple Sign", 2490 September 2010. 2492 [MagicSignatures] 2493 Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic 2494 Signatures", January 2011. 2496 [NIST-800-63-1] 2497 National Institute of Standards and Technology (NIST), 2498 "Electronic Authentication Guideline", NIST 800-63-1, 2499 December 2011. 2501 [RFC2631] Rescorla, E., "Diffie-Hellman Key Agreement Method", 2502 RFC 2631, June 1999. 2504 [RFC3275] Eastlake, D., Reagle, J., and D. Solo, "(Extensible Markup 2505 Language) XML-Signature Syntax and Processing", RFC 3275, 2506 March 2002. 2508 [RFC3447] Jonsson, J. and B. Kaliski, "Public-Key Cryptography 2509 Standards (PKCS) #1: RSA Cryptography Specifications 2510 Version 2.1", RFC 3447, February 2003. 2512 [RFC4086] Eastlake, D., Schiller, J., and S. Crocker, "Randomness 2513 Requirements for Security", BCP 106, RFC 4086, June 2005. 2515 [RFC5116] McGrew, D., "An Interface and Algorithms for Authenticated 2516 Encryption", RFC 5116, January 2008. 2518 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 2519 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 2520 May 2008. 2522 [W3C.NOTE-xmldsig-core2-20130411] 2523 Eastlake, D., Reagle, J., Solo, D., Hirsch, F., Roessler, 2524 T., Yiu, K., Datta, P., and S. Cantor, "XML Signature 2525 Syntax and Processing Version 2.0", World Wide Web 2526 Consortium Note NOTE-xmldsig-core2-20130411, April 2013, 2527 . 2529 [W3C.REC-xmlenc-core-20021210] 2530 Eastlake, D. and J. Reagle, "XML Encryption Syntax and 2531 Processing", World Wide Web Consortium Recommendation REC- 2532 xmlenc-core-20021210, December 2002, 2533 . 2535 [W3C.REC-xmlenc-core1-20130411] 2536 Eastlake, D., Reagle, J., Hirsch, F., and T. Roessler, 2537 "XML Encryption Syntax and Processing Version 1.1", World 2538 Wide Web Consortium Recommendation REC-xmlenc-core1- 2539 20130411, April 2013, 2540 . 2542 Appendix A. Algorithm Identifier Cross-Reference 2544 This appendix contains tables cross-referencing the cryptographic 2545 algorithm identifier values defined in this specification with the 2546 equivalent identifiers used by other standards and software packages. 2547 See XML DSIG [RFC3275], XML DSIG 2.0 2548 [W3C.NOTE-xmldsig-core2-20130411], XML Encryption 2549 [W3C.REC-xmlenc-core-20021210], XML Encryption 1.1 2550 [W3C.REC-xmlenc-core1-20130411], and Java Cryptography Architecture 2551 [JCA] for more information about the names defined by those 2552 documents. 2554 A.1. Digital Signature/MAC Algorithm Identifier Cross-Reference 2556 This section contains a table cross-referencing the JWS digital 2557 signature and MAC "alg" (algorithm) values defined in this 2558 specification with the equivalent identifiers used by other standards 2559 and software packages. 2561 +-----+-------------------------------+--------------+--------------+ 2562 | JWS | XML DSIG | JCA | OID | 2563 +-----+-------------------------------+--------------+--------------+ 2564 | HS2 | http://www.w3.org/2001/04/xml | HmacSHA256 | 1.2.840.1135 | 2565 | 56 | dsig-more#hmac-sha256 | | 49.2.9 | 2566 | HS3 | http://www.w3.org/2001/04/xml | HmacSHA384 | 1.2.840.1135 | 2567 | 84 | dsig-more#hmac-sha384 | | 49.2.10 | 2568 | HS5 | http://www.w3.org/2001/04/xml | HmacSHA512 | 1.2.840.1135 | 2569 | 12 | dsig-more#hmac-sha512 | | 49.2.11 | 2570 | RS2 | http://www.w3.org/2001/04/xml | SHA256withRS | 1.2.840.1135 | 2571 | 56 | dsig-more#rsa-sha256 | A | 49.1.1.11 | 2572 | RS3 | http://www.w3.org/2001/04/xml | SHA384withRS | 1.2.840.1135 | 2573 | 84 | dsig-more#rsa-sha384 | A | 49.1.1.12 | 2574 | RS5 | http://www.w3.org/2001/04/xml | SHA512withRS | 1.2.840.1135 | 2575 | 12 | dsig-more#rsa-sha512 | A | 49.1.1.13 | 2576 | ES2 | http://www.w3.org/2001/04/xml | SHA256withEC | 1.2.840.1004 | 2577 | 56 | dsig-more#ecdsa-sha256 | DSA | 5.4.3.2 | 2578 | ES3 | http://www.w3.org/2001/04/xml | SHA384withEC | 1.2.840.1004 | 2579 | 84 | dsig-more#ecdsa-sha384 | DSA | 5.4.3.3 | 2580 | ES5 | http://www.w3.org/2001/04/xml | SHA512withEC | 1.2.840.1004 | 2581 | 12 | dsig-more#ecdsa-sha512 | DSA | 5.4.3.4 | 2582 | PS2 | http://www.w3.org/2007/05/xml | SHA256withRS | 1.2.840.1135 | 2583 | 56 | dsig-more#sha256-rsa-MGF1 | AandMGF1 | 49.1.1.10 | 2584 | PS3 | http://www.w3.org/2007/05/xml | SHA384withRS | 1.2.840.1135 | 2585 | 84 | dsig-more#sha384-rsa-MGF1 | AandMGF1 | 49.1.1.10 | 2586 | PS5 | http://www.w3.org/2007/05/xml | SHA512withRS | 1.2.840.1135 | 2587 | 12 | dsig-more#sha512-rsa-MGF1 | AandMGF1 | 49.1.1.10 | 2588 +-----+-------------------------------+--------------+--------------+ 2590 A.2. Key Management Algorithm Identifier Cross-Reference 2592 This section contains a table cross-referencing the JWE "alg" 2593 (algorithm) values defined in this specification with the equivalent 2594 identifiers used by other standards and software packages. 2596 +-------+------------------------+--------------------+-------------+ 2597 | JWE | XML ENC | JCA | OID | 2598 +-------+------------------------+--------------------+-------------+ 2599 | RSA1_ | http://www.w3.org/2001 | RSA/ECB/PKCS1Paddi | 1.2.840.113 | 2600 | 5 | /04/xmlenc#rsa-1_5 | ng | 549.1.1.1 | 2601 | RSA-O | http://www.w3.org/2001 | RSA/ECB/OAEPWithSH | 1.2.840.113 | 2602 | AEP | /04/xmlenc#rsa-oaep-mg | A-1AndMGF1Padding | 549.1.1.7 | 2603 | | f1p | | | 2604 | RSA-O | http://www.w3.org/2009 | RSA/ECB/OAEPWithSH | 1.2.840.113 | 2605 | AEP-2 | /xmlenc11#rsa-oaep & | A-256AndMGF1Paddin | 549.1.1.7 | 2606 | 56 | http://www.w3.org/200 | g& | | 2607 | | 9/xmlenc11#mgf1sha256 | MGF1ParameterSpec | | 2608 | | | .SHA256 | | 2609 | ECDH- | http://www.w3.org/2009 | ECDH | 1.3.132.1.1 | 2610 | ES | /xmlenc11#ECDH-ES | | 2 | 2611 | A128K | http://www.w3.org/2001 | AESWrap | 2.16.840.1. | 2612 | W | /04/xmlenc#kw-aes128 | | 101.3.4.1.5 | 2613 | A192K | http://www.w3.org/2001 | AESWrap | 2.16.840.1. | 2614 | W | /04/xmlenc#kw-aes192 | | 101.3.4.1.2 | 2615 | | | | 5 | 2616 | A256K | http://www.w3.org/2001 | AESWrap | 2.16.840.1. | 2617 | W | /04/xmlenc#kw-aes256 | | 101.3.4.1.4 | 2618 | | | | 5 | 2619 +-------+------------------------+--------------------+-------------+ 2621 A.3. Content Encryption Algorithm Identifier Cross-Reference 2623 This section contains a table cross-referencing the JWE "enc" 2624 (encryption algorithm) values defined in this specification with the 2625 equivalent identifiers used by other standards and software packages. 2627 For the composite algorithms "A128CBC-HS256", "A192CBC-HS384", and 2628 "A256CBC-HS512", the corresponding AES CBC algorithm identifiers are 2629 listed. 2631 +---------+-------------------------+--------------+----------------+ 2632 | JWE | XML ENC | JCA | OID | 2633 +---------+-------------------------+--------------+----------------+ 2634 | A128CBC | http://www.w3.org/2001/ | AES/CBC/PKCS | 2.16.840.1.101 | 2635 | -HS256 | 04/xmlenc#aes128-cbc | 5Padding | .3.4.1.2 | 2636 | A192CBC | http://www.w3.org/2001/ | AES/CBC/PKCS | 2.16.840.1.101 | 2637 | -HS384 | 04/xmlenc#aes192-cbc | 5Padding | .3.4.1.22 | 2638 | A256CBC | http://www.w3.org/2001/ | AES/CBC/PKCS | 2.16.840.1.101 | 2639 | -HS512 | 04/xmlenc#aes256-cbc | 5Padding | .3.4.1.42 | 2640 | A128GCM | http://www.w3.org/2009/ | AES/GCM/NoPa | 2.16.840.1.101 | 2641 | | xmlenc11#aes128-gcm | dding | .3.4.1.6 | 2642 | A192GCM | http://www.w3.org/2009/ | AES/GCM/NoPa | 2.16.840.1.101 | 2643 | | xmlenc11#aes192-gcm | dding | .3.4.1.26 | 2644 | A256GCM | http://www.w3.org/2009/ | AES/GCM/NoPa | 2.16.840.1.101 | 2645 | | xmlenc11#aes256-gcm | dding | .3.4.1.46 | 2646 +---------+-------------------------+--------------+----------------+ 2648 Appendix B. Test Cases for AES_CBC_HMAC_SHA2 Algorithms 2650 The following test cases can be used to validate implementations of 2651 the AES_CBC_HMAC_SHA2 algorithms defined in Section 5.2. They are 2652 also intended to correspond to test cases that may appear in a future 2653 version of [I-D.mcgrew-aead-aes-cbc-hmac-sha2], demonstrating that 2654 the cryptographic computations performed are the same. 2656 The variable names are those defined in Section 5.2. All values are 2657 hexadecimal. 2659 B.1. Test Cases for AES_128_CBC_HMAC_SHA_256 2661 AES_128_CBC_HMAC_SHA_256 2663 K = 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 2664 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 2666 MAC_KEY = 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 2668 ENC_KEY = 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 2670 P = 41 20 63 69 70 68 65 72 20 73 79 73 74 65 6d 20 2671 6d 75 73 74 20 6e 6f 74 20 62 65 20 72 65 71 75 2672 69 72 65 64 20 74 6f 20 62 65 20 73 65 63 72 65 2673 74 2c 20 61 6e 64 20 69 74 20 6d 75 73 74 20 62 2674 65 20 61 62 6c 65 20 74 6f 20 66 61 6c 6c 20 69 2675 6e 74 6f 20 74 68 65 20 68 61 6e 64 73 20 6f 66 2676 20 74 68 65 20 65 6e 65 6d 79 20 77 69 74 68 6f 2677 75 74 20 69 6e 63 6f 6e 76 65 6e 69 65 6e 63 65 2679 IV = 1a f3 8c 2d c2 b9 6f fd d8 66 94 09 23 41 bc 04 2681 A = 54 68 65 20 73 65 63 6f 6e 64 20 70 72 69 6e 63 2682 69 70 6c 65 20 6f 66 20 41 75 67 75 73 74 65 20 2683 4b 65 72 63 6b 68 6f 66 66 73 2685 AL = 00 00 00 00 00 00 01 50 2687 E = c8 0e df a3 2d df 39 d5 ef 00 c0 b4 68 83 42 79 2688 a2 e4 6a 1b 80 49 f7 92 f7 6b fe 54 b9 03 a9 c9 2689 a9 4a c9 b4 7a d2 65 5c 5f 10 f9 ae f7 14 27 e2 2690 fc 6f 9b 3f 39 9a 22 14 89 f1 63 62 c7 03 23 36 2691 09 d4 5a c6 98 64 e3 32 1c f8 29 35 ac 40 96 c8 2692 6e 13 33 14 c5 40 19 e8 ca 79 80 df a4 b9 cf 1b 2693 38 4c 48 6f 3a 54 c5 10 78 15 8e e5 d7 9d e5 9f 2694 bd 34 d8 48 b3 d6 95 50 a6 76 46 34 44 27 ad e5 2695 4b 88 51 ff b5 98 f7 f8 00 74 b9 47 3c 82 e2 db 2697 M = 65 2c 3f a3 6b 0a 7c 5b 32 19 fa b3 a3 0b c1 c4 2698 e6 e5 45 82 47 65 15 f0 ad 9f 75 a2 b7 1c 73 ef 2700 T = 65 2c 3f a3 6b 0a 7c 5b 32 19 fa b3 a3 0b c1 c4 2702 B.2. Test Cases for AES_192_CBC_HMAC_SHA_384 2704 K = 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 2705 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 2706 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 2708 MAC_KEY = 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 2709 10 11 12 13 14 15 16 17 2711 ENC_KEY = 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 2712 28 29 2a 2b 2c 2d 2e 2f 2714 P = 41 20 63 69 70 68 65 72 20 73 79 73 74 65 6d 20 2715 6d 75 73 74 20 6e 6f 74 20 62 65 20 72 65 71 75 2716 69 72 65 64 20 74 6f 20 62 65 20 73 65 63 72 65 2717 74 2c 20 61 6e 64 20 69 74 20 6d 75 73 74 20 62 2718 65 20 61 62 6c 65 20 74 6f 20 66 61 6c 6c 20 69 2719 6e 74 6f 20 74 68 65 20 68 61 6e 64 73 20 6f 66 2720 20 74 68 65 20 65 6e 65 6d 79 20 77 69 74 68 6f 2721 75 74 20 69 6e 63 6f 6e 76 65 6e 69 65 6e 63 65 2723 IV = 1a f3 8c 2d c2 b9 6f fd d8 66 94 09 23 41 bc 04 2725 A = 54 68 65 20 73 65 63 6f 6e 64 20 70 72 69 6e 63 2726 69 70 6c 65 20 6f 66 20 41 75 67 75 73 74 65 20 2727 4b 65 72 63 6b 68 6f 66 66 73 2729 AL = 00 00 00 00 00 00 01 50 2731 E = ea 65 da 6b 59 e6 1e db 41 9b e6 2d 19 71 2a e5 2732 d3 03 ee b5 00 52 d0 df d6 69 7f 77 22 4c 8e db 2733 00 0d 27 9b dc 14 c1 07 26 54 bd 30 94 42 30 c6 2734 57 be d4 ca 0c 9f 4a 84 66 f2 2b 22 6d 17 46 21 2735 4b f8 cf c2 40 0a dd 9f 51 26 e4 79 66 3f c9 0b 2736 3b ed 78 7a 2f 0f fc bf 39 04 be 2a 64 1d 5c 21 2737 05 bf e5 91 ba e2 3b 1d 74 49 e5 32 ee f6 0a 9a 2738 c8 bb 6c 6b 01 d3 5d 49 78 7b cd 57 ef 48 49 27 2739 f2 80 ad c9 1a c0 c4 e7 9c 7b 11 ef c6 00 54 e3 2741 M = 84 90 ac 0e 58 94 9b fe 51 87 5d 73 3f 93 ac 20 2742 75 16 80 39 cc c7 33 d7 45 94 f8 86 b3 fa af d4 2743 86 f2 5c 71 31 e3 28 1e 36 c7 a2 d1 30 af de 57 2745 T = 84 90 ac 0e 58 94 9b fe 51 87 5d 73 3f 93 ac 20 2746 75 16 80 39 cc c7 33 d7 2748 B.3. Test Cases for AES_256_CBC_HMAC_SHA_512 2750 K = 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 2751 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 2752 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 2753 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 2755 MAC_KEY = 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 2756 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 2758 ENC_KEY = 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 2759 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 2761 P = 41 20 63 69 70 68 65 72 20 73 79 73 74 65 6d 20 2762 6d 75 73 74 20 6e 6f 74 20 62 65 20 72 65 71 75 2763 69 72 65 64 20 74 6f 20 62 65 20 73 65 63 72 65 2764 74 2c 20 61 6e 64 20 69 74 20 6d 75 73 74 20 62 2765 65 20 61 62 6c 65 20 74 6f 20 66 61 6c 6c 20 69 2766 6e 74 6f 20 74 68 65 20 68 61 6e 64 73 20 6f 66 2767 20 74 68 65 20 65 6e 65 6d 79 20 77 69 74 68 6f 2768 75 74 20 69 6e 63 6f 6e 76 65 6e 69 65 6e 63 65 2770 IV = 1a f3 8c 2d c2 b9 6f fd d8 66 94 09 23 41 bc 04 2772 A = 54 68 65 20 73 65 63 6f 6e 64 20 70 72 69 6e 63 2773 69 70 6c 65 20 6f 66 20 41 75 67 75 73 74 65 20 2774 4b 65 72 63 6b 68 6f 66 66 73 2776 AL = 00 00 00 00 00 00 01 50 2778 E = 4a ff aa ad b7 8c 31 c5 da 4b 1b 59 0d 10 ff bd 2779 3d d8 d5 d3 02 42 35 26 91 2d a0 37 ec bc c7 bd 2780 82 2c 30 1d d6 7c 37 3b cc b5 84 ad 3e 92 79 c2 2781 e6 d1 2a 13 74 b7 7f 07 75 53 df 82 94 10 44 6b 2782 36 eb d9 70 66 29 6a e6 42 7e a7 5c 2e 08 46 a1 2783 1a 09 cc f5 37 0d c8 0b fe cb ad 28 c7 3f 09 b3 2784 a3 b7 5e 66 2a 25 94 41 0a e4 96 b2 e2 e6 60 9e 2785 31 e6 e0 2c c8 37 f0 53 d2 1f 37 ff 4f 51 95 0b 2786 be 26 38 d0 9d d7 a4 93 09 30 80 6d 07 03 b1 f6 2788 M = 4d d3 b4 c0 88 a7 f4 5c 21 68 39 64 5b 20 12 bf 2789 2e 62 69 a8 c5 6a 81 6d bc 1b 26 77 61 95 5b c5 2790 fd 30 a5 65 c6 16 ff b2 f3 64 ba ec e6 8f c4 07 2791 53 bc fc 02 5d de 36 93 75 4a a1 f5 c3 37 3b 9c 2793 T = 4d d3 b4 c0 88 a7 f4 5c 21 68 39 64 5b 20 12 bf 2794 2e 62 69 a8 c5 6a 81 6d bc 1b 26 77 61 95 5b c5 2796 Appendix C. Example ECDH-ES Key Agreement Computation 2798 This example uses ECDH-ES Key Agreement and the Concat KDF to derive 2799 the Content Encryption Key (CEK) in the manner described in 2800 Section 4.6. In this example, the ECDH-ES Direct Key Agreement mode 2801 ("alg" value "ECDH-ES") is used to produce an agreed upon key for AES 2802 GCM with a 128 bit key ("enc" value "A128GCM"). 2804 In this example, a sender Alice is encrypting content to a recipient 2805 Bob. The sender (Alice) generates an ephemeral key for the key 2806 agreement computation. Alice's ephemeral key (in JWK format) used 2807 for the key agreement computation in this example (including the 2808 private part) is: 2810 {"kty":"EC", 2811 "crv":"P-256", 2812 "x":"gI0GAILBdu7T53akrFmMyGcsF3n5dO7MmwNBHKW5SV0", 2813 "y":"SLW_xSffzlPWrHEVI30DHM_4egVwt3NQqeUD7nMFpps", 2814 "d":"0_NxaRPUMQoAJt50Gz8YiTr8gRTwyEaCumd-MToTmIo" 2815 } 2817 The recipient's (Bob's) key (in JWK format) used for the key 2818 agreement computation in this example (including the private part) 2819 is: 2821 {"kty":"EC", 2822 "crv":"P-256", 2823 "x":"weNJy2HscCSM6AEDTDg04biOvhFhyyWvOHQfeF_PxMQ", 2824 "y":"e8lnCO-AlStT-NJVX-crhB7QRYhiix03illJOVAOyck", 2825 "d":"VEmDZpDXXK8p8N0Cndsxs924q6nS1RXFASRl6BfUqdw" 2826 } 2828 Header Parameter values used in this example are as follows. In this 2829 example, the "apu" (agreement PartyUInfo) parameter value is the 2830 base64url encoding of the UTF-8 string "Alice" and the "apv" 2831 (agreement PartyVInfo) parameter value is the base64url encoding of 2832 the UTF-8 string "Bob". The "epk" parameter is used to communicate 2833 the sender's (Alice's) ephemeral public key value to the recipient 2834 (Bob). 2836 {"alg":"ECDH-ES", 2837 "enc":"A128GCM", 2838 "apu":"QWxpY2U", 2839 "apv":"Qm9i", 2840 "epk": 2841 {"kty":"EC", 2842 "crv":"P-256", 2843 "x":"gI0GAILBdu7T53akrFmMyGcsF3n5dO7MmwNBHKW5SV0", 2844 "y":"SLW_xSffzlPWrHEVI30DHM_4egVwt3NQqeUD7nMFpps" 2845 } 2846 } 2848 The resulting Concat KDF [NIST.800-56A] parameter values are: 2850 Z 2851 This is set to the ECDH-ES key agreement output. (This value is 2852 often not directly exposed by libraries, due to NIST security 2853 requirements, and only serves as an input to a KDF.) In this 2854 example, Z is following the octet sequence (using JSON array 2855 notation): 2856 [158, 86, 217, 29, 129, 113, 53, 211, 114, 131, 66, 131, 191, 132, 2857 38, 156, 251, 49, 110, 163, 218, 128, 106, 72, 246, 218, 167, 121, 2858 140, 254, 144, 196]. 2860 keydatalen 2861 This value is 128 - the number of bits in the desired output key 2862 (because "A128GCM" uses a 128 bit key). 2864 AlgorithmID 2865 This is set to the octets representing the 32 bit big endian value 2866 7 - [0, 0, 0, 7] - the number of octets in the AlgorithmID content 2867 "A128GCM", followed, by the octets representing the UTF-8 string 2868 "A128GCM" - [65, 49, 50, 56, 71, 67, 77]. 2870 PartyUInfo 2871 This is set to the octets representing the 32 bit big endian value 2872 5 - [0, 0, 0, 5] - the number of octets in the PartyUInfo content 2873 "Alice", followed, by the octets representing the UTF-8 string 2874 "Alice" - [65, 108, 105, 99, 101]. 2876 PartyVInfo 2877 This is set to the octets representing the 32 bit big endian value 2878 3 - [0, 0, 0, 3] - the number of octets in the PartyUInfo content 2879 "Bob", followed, by the octets representing the UTF-8 string "Bob" 2880 - [66, 111, 98]. 2882 SuppPubInfo 2883 This is set to the octets representing the 32 bit big endian value 2884 128 - [0, 0, 0, 128] - the keydatalen value. 2886 SuppPrivInfo 2887 This is set to the empty octet sequence. 2889 Concatenating the parameters AlgorithmID through SuppPubInfo results 2890 in an OtherInfo value of: 2891 [0, 0, 0, 7, 65, 49, 50, 56, 71, 67, 77, 0, 0, 0, 5, 65, 108, 105, 2892 99, 101, 0, 0, 0, 3, 66, 111, 98, 0, 0, 0, 128] 2894 Concatenating the round number 1 ([0, 0, 0, 1]), Z, and the OtherInfo 2895 value results in the Concat KDF round 1 hash input of: 2896 [0, 0, 0, 1, 2897 158, 86, 217, 29, 129, 113, 53, 211, 114, 131, 66, 131, 191, 132, 38, 2898 156, 251, 49, 110, 163, 218, 128, 106, 72, 246, 218, 167, 121, 140, 2899 254, 144, 196, 2900 0, 0, 0, 7, 65, 49, 50, 56, 71, 67, 77, 0, 0, 0, 5, 65, 108, 105, 99, 2901 101, 0, 0, 0, 3, 66, 111, 98, 0, 0, 0, 128] 2903 The resulting derived key, which is the first 128 bits of the round 1 2904 hash output is: 2905 [86, 170, 141, 234, 248, 35, 109, 32, 92, 34, 40, 205, 113, 167, 16, 2906 26] 2908 The base64url encoded representation of this derived key is: 2910 VqqN6vgjbSBcIijNcacQGg 2912 Appendix D. Acknowledgements 2914 Solutions for signing and encrypting JSON content were previously 2915 explored by Magic Signatures [MagicSignatures], JSON Simple Sign 2916 [JSS], Canvas Applications [CanvasApp], JSON Simple Encryption [JSE], 2917 and JavaScript Message Security Format [I-D.rescorla-jsms], all of 2918 which influenced this draft. 2920 The Authenticated Encryption with AES-CBC and HMAC-SHA 2921 [I-D.mcgrew-aead-aes-cbc-hmac-sha2] specification, upon which the 2922 AES_CBC_HMAC_SHA2 algorithms are based, was written by David A. 2923 McGrew and Kenny Paterson. The test cases for AES_CBC_HMAC_SHA2 are 2924 based upon those for [I-D.mcgrew-aead-aes-cbc-hmac-sha2] by John 2925 Foley. 2927 Matt Miller wrote Using JavaScript Object Notation (JSON) Web 2928 Encryption (JWE) for Protecting JSON Web Key (JWK) Objects 2930 [I-D.miller-jose-jwe-protected-jwk], which the password-based 2931 encryption content of this draft is based upon. 2933 This specification is the work of the JOSE Working Group, which 2934 includes dozens of active and dedicated participants. In particular, 2935 the following individuals contributed ideas, feedback, and wording 2936 that influenced this specification: 2938 Dirk Balfanz, Richard Barnes, John Bradley, Brian Campbell, Breno de 2939 Medeiros, Vladimir Dzhuvinov, Yaron Y. Goland, Dick Hardt, Joe 2940 Hildebrand, Jeff Hodges, Edmund Jay, James Manger, Matt Miller, Tony 2941 Nadalin, Axel Nennker, John Panzer, Emmanuel Raviart, Eric Rescorla, 2942 Nat Sakimura, Jim Schaad, Hannes Tschofenig, and Sean Turner. 2944 Jim Schaad and Karen O'Donoghue chaired the JOSE working group and 2945 Sean Turner, Stephen Farrell, and Kathleen Moriarty served as 2946 Security area directors during the creation of this specification. 2948 Appendix E. Document History 2950 [[ to be removed by the RFC Editor before publication as an RFC ]] 2952 -29 2954 o Replaced the terms JWS Header, JWE Header, and JWT Header with a 2955 single JOSE Header term defined in the JWS specification. This 2956 also enabled a single Header Parameter definition to be used and 2957 reduced other areas of duplication between specifications. 2959 -28 2961 o Specified the use of PKCS #7 padding with AES CBC, rather than 2962 PKCS #5. (PKCS #7 is a superset of PKCS #5, and is appropriate 2963 for the 16 octet blocks used by AES CBC.) 2965 o Revised the introduction to the Security Considerations section. 2966 Also introduced additional subsection headings for security 2967 considerations items and moved a few security consideration items 2968 from here to the JWS and JWE drafts. 2970 -27 2972 o Described additional security considerations. 2974 o Updated the JCA and XMLENC parameters for "RSA-OAEP-256" and the 2975 JCA parameters for "A128KW", "A192KW", "A256KW", and "ECDH-ES". 2977 -26 2979 o Added algorithm identifier "RSA-OAEP-256" for RSAES OAEP using 2980 SHA-256 and MGF1 with SHA-256. 2982 o Clarified that the ECDSA signature values R and S are represented 2983 as octet sequences as defined in Section 2.3.7 of SEC1 [SEC1]. 2985 o Noted that octet sequences are depicted using JSON array notation. 2987 o Updated references, including to W3C specifications. 2989 -25 2991 o Corrected an external section number reference that had changed. 2993 -24 2995 o Replaced uses of the term "associated data" wherever it was used 2996 to refer to a data value with "additional authenticated data", 2997 since both terms were being used as synonyms, causing confusion. 2999 o Updated the JSON reference to RFC 7159. 3001 -23 3003 o No changes were made, other than to the version number and date. 3005 -22 3007 o Corrected RFC 2119 terminology usage. 3009 o Replaced references to draft-ietf-json-rfc4627bis with RFC 7158. 3011 -21 3013 o Compute the PBES2 salt parameter as (UTF8(Alg) || 0x00 || Salt 3014 Input), where the "p2s" Header Parameter encodes the Salt Input 3015 value and Alg is the "alg" Header Parameter value. 3017 o Changed some references from being normative to informative, 3018 addressing issue #90. 3020 -20 3022 o Replaced references to RFC 4627 with draft-ietf-json-rfc4627bis, 3023 addressing issue #90. 3025 -19 3027 o Used tables to show the correspondence between algorithm 3028 identifiers and algorithm descriptions and parameters in the 3029 algorithm definition sections, addressing issue #183. 3031 o Changed the "Implementation Requirements" registry field names to 3032 "JOSE Implementation Requirements" to make it clear that these 3033 implementation requirements apply only to JWS and JWE 3034 implementations. 3036 -18 3038 o Changes to address editorial and minor issues #129, #134, #135, 3039 #158, #161, #185, #186, and #187. 3041 o Added and used Description registry fields. 3043 -17 3045 o Explicitly named all the logical components of a JWS and JWE and 3046 defined the processing rules and serializations in terms of those 3047 components, addressing issues #60, #61, and #62. 3049 o Removed processing steps in algorithm definitions that duplicated 3050 processing steps in JWS or JWE, addressing issue #56. 3052 o Replaced verbose repetitive phases such as "base64url encode the 3053 octets of the UTF-8 representation of X" with mathematical 3054 notation such as "BASE64URL(UTF8(X))". 3056 o Terms used in multiple documents are now defined in one place and 3057 incorporated by reference. Some lightly used or obvious terms 3058 were also removed. This addresses issue #58. 3060 o Changes to address minor issue #53. 3062 -16 3064 o Added a DataLen prefix to the AlgorithmID value in the Concat KDF 3065 computation. 3067 o Added OIDs for encryption algorithms, additional signature 3068 algorithm OIDs, and additional XML DSIG/ENC URIs in the algorithm 3069 cross-reference tables. 3071 o Changes to address editorial and minor issues #28, #36, #39, #52, 3072 #53, #55, #127, #128, #136, #137, #141, #150, #151, #152, and 3073 #155. 3075 -15 3077 o Changed statements about rejecting JWSs to statements about 3078 validation failing, addressing issue #35. 3080 o Stated that changes of implementation requirements are only 3081 permitted on a Specification Required basis, addressing issue #38. 3083 o Made "oct" a required key type, addressing issue #40. 3085 o Updated the example ECDH-ES key agreement values. 3087 o Changes to address editorial and minor issues #34, #37, #49, #63, 3088 #123, #124, #125, #130, #132, #133, #138, #139, #140, #142, #143, 3089 #144, #145, #148, #149, #150, and #162. 3091 -14 3093 o Removed "PBKDF2" key type and added "p2s" and "p2c" header 3094 parameters for use with the PBES2 algorithms. 3096 o Made the RSA private key parameters that are there to enable 3097 optimizations be RECOMMENDED rather than REQUIRED. 3099 o Added algorithm identifiers for AES algorithms using 192 bit keys 3100 and for RSASSA-PSS using HMAC SHA-384. 3102 o Added security considerations about key lifetimes, addressing 3103 issue #18. 3105 o Added an example ECDH-ES key agreement computation. 3107 -13 3109 o Added key encryption with AES GCM as specified in 3110 draft-jones-jose-aes-gcm-key-wrap-01, addressing issue #13. 3112 o Added security considerations text limiting the number of times 3113 that an AES GCM key can be used for key encryption or direct 3114 encryption, per Section 8.3 of NIST SP 800-38D, addressing issue 3115 #28. 3117 o Added password-based key encryption as specified in 3118 draft-miller-jose-jwe-protected-jwk-02. 3120 -12 3121 o In the Direct Key Agreement case, the Concat KDF AlgorithmID is 3122 set to the octets of the UTF-8 representation of the "enc" header 3123 parameter value. 3125 o Restored the "apv" (agreement PartyVInfo) parameter. 3127 o Moved the "epk", "apu", and "apv" Header Parameter definitions to 3128 be with the algorithm descriptions that use them. 3130 o Changed terminology from "block encryption" to "content 3131 encryption". 3133 -11 3135 o Removed the Encrypted Key value from the AAD computation since it 3136 is already effectively integrity protected by the encryption 3137 process. The AAD value now only contains the representation of 3138 the JWE Encrypted Header. 3140 o Removed "apv" (agreement PartyVInfo) since it is no longer used. 3142 o Added more information about the use of PartyUInfo during key 3143 agreement. 3145 o Use the keydatalen as the SuppPubInfo value for the Concat KDF 3146 when doing key agreement, as RFC 2631 does. 3148 o Added algorithm identifiers for RSASSA-PSS with SHA-256 and SHA- 3149 512. 3151 o Added a Parameter Information Class value to the JSON Web Key 3152 Parameters registry, which registers whether the parameter conveys 3153 public or private information. 3155 -10 3157 o Changed the JWE processing rules for multiple recipients so that a 3158 single AAD value contains the header parameters and encrypted key 3159 values for all the recipients, enabling AES GCM to be safely used 3160 for multiple recipients. 3162 -09 3164 o Expanded the scope of the JWK parameters to include private and 3165 symmetric key representations, as specified by 3166 draft-jones-jose-json-private-and-symmetric-key-00. 3168 o Changed term "JWS Secured Input" to "JWS Signing Input". 3170 o Changed from using the term "byte" to "octet" when referring to 8 3171 bit values. 3173 o Specified that AES Key Wrap uses the default initial value 3174 specified in Section 2.2.3.1 of RFC 3394. This addressed issue 3175 #19. 3177 o Added Key Management Mode definitions to terminology section and 3178 used the defined terms to provide clearer key management 3179 instructions. This addressed issue #5. 3181 o Replaced "A128CBC+HS256" and "A256CBC+HS512" with "A128CBC-HS256" 3182 and "A256CBC-HS512". The new algorithms perform the same 3183 cryptographic computations as [I-D.mcgrew-aead-aes-cbc-hmac-sha2], 3184 but with the Initialization Vector and Authentication Tag values 3185 remaining separate from the Ciphertext value in the output 3186 representation. Also deleted the header parameters "epu" 3187 (encryption PartyUInfo) and "epv" (encryption PartyVInfo), since 3188 they are no longer used. 3190 o Changed from using the term "Integrity Value" to "Authentication 3191 Tag". 3193 -08 3195 o Changed the name of the JWK key type parameter from "alg" to 3196 "kty". 3198 o Replaced uses of the term "AEAD" with "Authenticated Encryption", 3199 since the term AEAD in the RFC 5116 sense implied the use of a 3200 particular data representation, rather than just referring to the 3201 class of algorithms that perform authenticated encryption with 3202 associated data. 3204 o Applied editorial improvements suggested by Jeff Hodges. Many of 3205 these simplified the terminology used. 3207 o Added seriesInfo information to Internet Draft references. 3209 -07 3211 o Added a data length prefix to PartyUInfo and PartyVInfo values. 3213 o Changed the name of the JWK RSA modulus parameter from "mod" to 3214 "n" and the name of the JWK RSA exponent parameter from "xpo" to 3215 "e", so that the identifiers are the same as those used in RFC 3216 3447. 3218 o Made several local editorial changes to clean up loose ends left 3219 over from to the decision to only support block encryption methods 3220 providing integrity. 3222 -06 3224 o Removed the "int" and "kdf" parameters and defined the new 3225 composite Authenticated Encryption algorithms "A128CBC+HS256" and 3226 "A256CBC+HS512" to replace the former uses of AES CBC, which 3227 required the use of separate integrity and key derivation 3228 functions. 3230 o Included additional values in the Concat KDF calculation -- the 3231 desired output size and the algorithm value, and optionally 3232 PartyUInfo and PartyVInfo values. Added the optional header 3233 parameters "apu" (agreement PartyUInfo), "apv" (agreement 3234 PartyVInfo), "epu" (encryption PartyUInfo), and "epv" (encryption 3235 PartyVInfo). 3237 o Changed the name of the JWK RSA exponent parameter from "exp" to 3238 "xpo" so as to allow the potential use of the name "exp" for a 3239 future extension that might define an expiration parameter for 3240 keys. (The "exp" name is already used for this purpose in the JWT 3241 specification.) 3243 o Applied changes made by the RFC Editor to RFC 6749's registry 3244 language to this specification. 3246 -05 3248 o Support both direct encryption using a shared or agreed upon 3249 symmetric key, and the use of a shared or agreed upon symmetric 3250 key to key wrap the CMK. Specifically, added the "alg" values 3251 "dir", "ECDH-ES+A128KW", and "ECDH-ES+A256KW" to finish filling in 3252 this set of capabilities. 3254 o Updated open issues. 3256 -04 3258 o Added text requiring that any leading zero bytes be retained in 3259 base64url encoded key value representations for fixed-length 3260 values. 3262 o Added this language to Registration Templates: "This name is case 3263 sensitive. Names that match other registered names in a case 3264 insensitive manner SHOULD NOT be accepted." 3266 o Described additional open issues. 3268 o Applied editorial suggestions. 3270 -03 3272 o Always use a 128 bit "authentication tag" size for AES GCM, 3273 regardless of the key size. 3275 o Specified that use of a 128 bit IV is REQUIRED with AES CBC. It 3276 was previously RECOMMENDED. 3278 o Removed key size language for ECDSA algorithms, since the key size 3279 is implied by the algorithm being used. 3281 o Stated that the "int" key size must be the same as the hash output 3282 size (and not larger, as was previously allowed) so that its size 3283 is defined for key generation purposes. 3285 o Added the "kdf" (key derivation function) header parameter to 3286 provide crypto agility for key derivation. The default KDF 3287 remains the Concat KDF with the SHA-256 digest function. 3289 o Clarified that the "mod" and "exp" values are unsigned. 3291 o Added Implementation Requirements columns to algorithm tables and 3292 Implementation Requirements entries to algorithm registries. 3294 o Changed AES Key Wrap to RECOMMENDED. 3296 o Moved registries JSON Web Signature and Encryption Header 3297 Parameters and JSON Web Signature and Encryption Type Values to 3298 the JWS specification. 3300 o Moved JSON Web Key Parameters registry to the JWK specification. 3302 o Changed registration requirements from RFC Required to 3303 Specification Required with Expert Review. 3305 o Added Registration Template sections for defined registries. 3307 o Added Registry Contents sections to populate registry values. 3309 o No longer say "the UTF-8 representation of the JWS Secured Input 3310 (which is the same as the ASCII representation)". Just call it 3311 "the ASCII representation of the JWS Secured Input". 3313 o Added "Collision Resistant Namespace" to the terminology section. 3315 o Numerous editorial improvements. 3317 -02 3319 o For AES GCM, use the "additional authenticated data" parameter to 3320 provide integrity for the header, encrypted key, and ciphertext 3321 and use the resulting "authentication tag" value as the JWE 3322 Authentication Tag. 3324 o Defined minimum required key sizes for algorithms without 3325 specified key sizes. 3327 o Defined KDF output key sizes. 3329 o Specified the use of PKCS #5 padding with AES CBC. 3331 o Generalized text to allow key agreement to be employed as an 3332 alternative to key wrapping or key encryption. 3334 o Clarified that ECDH-ES is a key agreement algorithm. 3336 o Required implementation of AES-128-KW and AES-256-KW. 3338 o Removed the use of "A128GCM" and "A256GCM" for key wrapping. 3340 o Removed "A512KW" since it turns out that it's not a standard 3341 algorithm. 3343 o Clarified the relationship between "typ" header parameter values 3344 and MIME types. 3346 o Generalized language to refer to Message Authentication Codes 3347 (MACs) rather than Hash-based Message Authentication Codes (HMACs) 3348 unless in a context specific to HMAC algorithms. 3350 o Established registries: JSON Web Signature and Encryption Header 3351 Parameters, JSON Web Signature and Encryption Algorithms, JSON Web 3352 Signature and Encryption "typ" Values, JSON Web Key Parameters, 3353 and JSON Web Key Algorithm Families. 3355 o Moved algorithm-specific definitions from JWK to JWA. 3357 o Reformatted to give each member definition its own section 3358 heading. 3360 -01 3361 o Moved definition of "alg":"none" for JWSs here from the JWT 3362 specification since this functionality is likely to be useful in 3363 more contexts that just for JWTs. 3365 o Added Advanced Encryption Standard (AES) Key Wrap Algorithm using 3366 512 bit keys ("A512KW"). 3368 o Added text "Alternatively, the Encoded JWS Signature MAY be 3369 base64url decoded to produce the JWS Signature and this value can 3370 be compared with the computed HMAC value, as this comparison 3371 produces the same result as comparing the encoded values". 3373 o Corrected the Magic Signatures reference. 3375 o Made other editorial improvements suggested by JOSE working group 3376 participants. 3378 -00 3380 o Created the initial IETF draft based upon 3381 draft-jones-json-web-signature-04 and 3382 draft-jones-json-web-encryption-02 with no normative changes. 3384 o Changed terminology to no longer call both digital signatures and 3385 HMACs "signatures". 3387 Author's Address 3389 Michael B. Jones 3390 Microsoft 3392 Email: mbj@microsoft.com 3393 URI: http://self-issued.info/