idnits 2.17.1 draft-ietf-jose-json-web-algorithms-20.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 26 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 seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (January 20, 2014) is 3748 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 2842 -- Looks like a reference, but probably isn't: '0' on line 2842 -- Looks like a reference, but probably isn't: '7' on line 2816 -- Looks like a reference, but probably isn't: '5' on line 2822 -- Looks like a reference, but probably isn't: '65' on line 2824 -- Looks like a reference, but probably isn't: '108' on line 2824 -- Looks like a reference, but probably isn't: '105' on line 2824 -- Looks like a reference, but probably isn't: '99' on line 2824 -- Looks like a reference, but probably isn't: '101' on line 2824 -- Looks like a reference, but probably isn't: '3' on line 2827 -- Looks like a reference, but probably isn't: '66' on line 2829 -- Looks like a reference, but probably isn't: '111' on line 2829 -- Looks like a reference, but probably isn't: '98' on line 2829 -- Looks like a reference, but probably isn't: '128' on line 2832 -- 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 ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) ** Downref: Normative reference to an Informational RFC: RFC 6090 -- 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 (-05) exists of draft-mcgrew-aead-aes-cbc-hmac-sha2-02 -- Obsolete informational reference (is this intentional?): RFC 3447 (Obsoleted by RFC 8017) Summary: 5 errors (**), 0 flaws (~~), 4 warnings (==), 22 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 January 20, 2014 5 Expires: July 24, 2014 7 JSON Web Algorithms (JWA) 8 draft-ietf-jose-json-web-algorithms-20 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 July 24, 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 . . . . . . . . . 12 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 . . 16 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) Parameter . . . . . . . . . . . 20 82 4.8.1.2. "p2c" (PBES2 count) Parameter . . . . . . . . . . 20 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 . . . . . . . . . 22 89 5.2.2.1. AES_CBC_HMAC_SHA2 Encryption . . . . . . . . . . . 22 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 . . . . . . . . . . . . . . . 25 93 5.2.5. AES_256_CBC_HMAC_SHA_512 . . . . . . . . . . . . . . . 25 94 5.2.6. Content Encryption with AES_CBC_HMAC_SHA2 . . . . . . 26 95 5.3. Content Encryption with AES GCM . . . . . . . . . . . . . 26 96 6. Cryptographic Algorithms for Keys . . . . . . . . . . . . . . 27 97 6.1. "kty" (Key Type) Parameter Values . . . . . . . . . . . . 27 98 6.2. Parameters for Elliptic Curve Keys . . . . . . . . . . . . 27 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 . . . . . . . . . . . 28 102 6.2.1.3. "y" (Y Coordinate) Parameter . . . . . . . . . . . 28 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 . . . . . . . . . . . . 29 107 6.3.1.1. "n" (Modulus) Parameter . . . . . . . . . . . . . 29 108 6.3.1.2. "e" (Exponent) Parameter . . . . . . . . . . . . . 29 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 . . . . . . . 30 113 6.3.2.4. "dp" (First Factor CRT Exponent) Parameter . . . . 30 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 . . . . . . . . . . . . . . . . 33 122 7.1.2. Initial Registry Contents . . . . . . . . . . . . . . 34 123 7.2. JWE Header Parameter Names Registration . . . . . . . . . 40 124 7.2.1. Registry Contents . . . . . . . . . . . . . . . . . . 40 125 7.3. JSON Web Encryption Compression Algorithms Registry . . . 41 126 7.3.1. Registration Template . . . . . . . . . . . . . . . . 41 127 7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 42 128 7.4. JSON Web Key Types Registry . . . . . . . . . . . . . . . 42 129 7.4.1. Registration Template . . . . . . . . . . . . . . . . 42 130 7.4.2. Initial Registry Contents . . . . . . . . . . . . . . 43 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 . . . . . . . . . . . . . . . . 46 135 7.6.2. Initial Registry Contents . . . . . . . . . . . . . . 47 136 8. Security Considerations . . . . . . . . . . . . . . . . . . . 47 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 . . . . . . . . . 48 140 8.4. AES GCM Security Considerations . . . . . . . . . . . . . 48 141 8.5. Plaintext JWS Security Considerations . . . . . . . . . . 49 142 8.6. Differences between Digital Signatures and MACs . . . . . 49 143 8.7. Denial of Service Attacks . . . . . . . . . . . . . . . . 50 144 8.8. Reusing Key Material when Encrypting Keys . . . . . . . . 50 145 8.9. Password Considerations . . . . . . . . . . . . . . . . . 50 147 9. Internationalization Considerations . . . . . . . . . . . . . 51 148 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 51 149 10.1. Normative References . . . . . . . . . . . . . . . . . . . 51 150 10.2. Informative References . . . . . . . . . . . . . . . . . . 53 151 Appendix A. Algorithm Identifier Cross-Reference . . . . . . . . 55 152 A.1. Digital Signature/MAC Algorithm Identifier 153 Cross-Reference . . . . . . . . . . . . . . . . . . . . . 55 154 A.2. Key Management Algorithm Identifier Cross-Reference . . . 56 155 A.3. Content Encryption Algorithm Identifier Cross-Reference . 56 156 Appendix B. Test Cases for AES_CBC_HMAC_SHA2 Algorithms . . . . . 57 157 B.1. Test Cases for AES_128_CBC_HMAC_SHA_256 . . . . . . . . . 58 158 B.2. Test Cases for AES_192_CBC_HMAC_SHA_384 . . . . . . . . . 59 159 B.3. Test Cases for AES_256_CBC_HMAC_SHA_512 . . . . . . . . . 60 160 Appendix C. Example ECDH-ES Key Agreement Computation . . . . . . 61 161 Appendix D. Acknowledgements . . . . . . . . . . . . . . . . . . 63 162 Appendix E. Document History . . . . . . . . . . . . . . . . . . 64 163 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 72 165 1. Introduction 167 The JSON Web Algorithms (JWA) specification registers cryptographic 168 algorithms and identifiers to be used with the JSON Web Signature 169 (JWS) [JWS], JSON Web Encryption (JWE) [JWE], and JSON Web Key (JWK) 170 [JWK] specifications. It defines several IANA registries for these 171 identifiers. All these specifications utilize JavaScript Object 172 Notation (JSON) [I-D.ietf-json-rfc4627bis] based data structures. 173 This specification also describes the semantics and operations that 174 are specific to these algorithms and key types. 176 Registering the algorithms and identifiers here, rather than in the 177 JWS, JWE, and JWK specifications, is intended to allow them to remain 178 unchanged in the face of changes in the set of Required, Recommended, 179 Optional, and Deprecated algorithms over time. This also allows 180 changes to the JWS, JWE, and JWK specifications without changing this 181 document. 183 Names defined by this specification are short because a core goal is 184 for the resulting representations to be compact. 186 1.1. Notational Conventions 188 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 189 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 190 document are to be interpreted as described in Key words for use in 191 RFCs to Indicate Requirement Levels [RFC2119]. If these words are 192 used without being spelled in uppercase then they are to be 193 interpreted with their normal natural language meanings. 195 BASE64URL(OCTETS) denotes the base64url encoding of OCTETS, per 196 Section 2. 198 UTF8(STRING) denotes the octets of the UTF-8 [RFC3629] representation 199 of STRING. 201 ASCII(STRING) denotes the octets of the ASCII [USASCII] 202 representation of STRING. 204 The concatenation of two values A and B is denoted as A || B. 206 2. Terminology 208 These terms defined by the JSON Web Signature (JWS) [JWS] 209 specification are incorporated into this specification: "JSON Web 210 Signature (JWS)", "JWS Header", "JWS Payload", "JWS Signature", "JWS 211 Protected Header", "Base64url Encoding", and "JWS Signing Input". 213 These terms defined by the JSON Web Encryption (JWE) [JWE] 214 specification are incorporated into this specification: "JSON Web 215 Encryption (JWE)", "Authenticated Encryption", "Plaintext", 216 "Ciphertext", "Additional Authenticated Data (AAD)", "Authentication 217 Tag", "Content Encryption Key (CEK)", "JWE Header", "JWE Encrypted 218 Key", "JWE Initialization Vector", "JWE Ciphertext", "JWE 219 Authentication Tag", "JWE Protected Header", "Key Management Mode", 220 "Key Encryption", "Key Wrapping", "Direct Key Agreement", "Key 221 Agreement with Key Wrapping", and "Direct Encryption". 223 These terms defined by the JSON Web Key (JWK) [JWK] specification are 224 incorporated into this specification: "JSON Web Key (JWK)" and "JSON 225 Web Key Set (JWK Set)". 227 These terms are defined for use by this specification: 229 Header Parameter A name/value pair that is member of a JWS Header or 230 JWE Header. 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 Header 236 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 array will be R and the second S (with both being in big 420 endian octet order). 422 3. Submit the JWS Signing Input R, S and the public key (x, y) to 423 the ECDSA P-256 SHA-256 validator. 425 Signing and validation with the ECDSA P-384 SHA-384 and ECDSA P-521 426 SHA-512 algorithms is performed identically to the procedure for 427 ECDSA P-256 SHA-256 -- just using the corresponding hash algorithms 428 with correspondingly larger result values. For ECDSA P-384 SHA-384, 429 R and S will be 384 bits each, resulting in a 96 octet sequence. For 430 ECDSA P-521 SHA-512, R and S will be 521 bits each, resulting in a 431 132 octet sequence. 433 Examples using these algorithms are shown in Appendices A.3 and A.4 434 of [JWS]. 436 3.5. Digital Signature with RSASSA-PSS 438 This section defines the use of the RSASSA-PSS digital signature 439 algorithm as defined in Section 8.1 of RFC 3447 [RFC3447] with the 440 MGF1 mask generation function and SHA-2 hash functions, always using 441 the same hash function for both the RSASSA-PSS hash function and the 442 MGF1 hash function. The size of the salt value is the same size as 443 the hash function output. All other algorithm parameters use the 444 defaults specified in Section A.2.3 of RFC 3447. 446 A key of size 2048 bits or larger MUST be used with this algorithm. 448 The RSASSA-PSS SHA-256 digital signature is generated as follows: 449 Generate a digital signature of the JWS Signing Input using RSASSA- 450 PSS-SIGN, the SHA-256 hash function, and the MGF1 mask generation 451 function with SHA-256 with the desired private key. This is the JWS 452 signature value. 454 The following "alg" (algorithm) Header Parameter values are used to 455 indicate that the JWS Signature is a digital signature value computed 456 using the corresponding algorithm: 458 +---------------------+---------------------------------------------+ 459 | alg Parameter Value | Digital Signature Algorithm | 460 +---------------------+---------------------------------------------+ 461 | PS256 | RSASSA-PSS using SHA-256 and MGF1 with | 462 | | SHA-256 | 463 | PS384 | RSASSA-PSS using SHA-384 and MGF1 with | 464 | | SHA-384 | 465 | PS512 | RSASSA-PSS using SHA-512 and MGF1 with | 466 | | SHA-512 | 467 +---------------------+---------------------------------------------+ 469 The RSASSA-PSS SHA-256 digital signature for a JWS is validated as 470 follows: Submit the JWS Signing Input, the JWS Signature, and the 471 public key corresponding to the private key used by the signer to the 472 RSASSA-PSS-VERIFY algorithm using SHA-256 as the hash function and 473 using MGF1 as the mask generation function with SHA-256. 475 Signing and validation with the RSASSA-PSS SHA-384 and RSASSA-PSS 476 SHA-512 algorithms is performed identically to the procedure for 477 RSASSA-PSS SHA-256 -- just using the alternative hash algorithm in 478 both roles. 480 3.6. Using the Algorithm "none" 482 JWSs MAY also be created that do not provide integrity protection. 483 Such a JWS is called a "Plaintext JWS". A Plaintext JWS MUST use the 484 "alg" value "none", and is formatted identically to other JWSs, but 485 MUST use the empty octet sequence as its JWS Signature value. 486 Receivers MUST verify that the JWS Signature value is the empty octet 487 sequence. See Section 8.5 for security considerations associated 488 with using this algorithm. 490 4. Cryptographic Algorithms for Key Management 492 JWE uses cryptographic algorithms to encrypt or determine the Content 493 Encryption Key (CEK). 495 4.1. "alg" (Algorithm) Header Parameter Values for JWE 497 The table below is the set of "alg" (algorithm) Header Parameter 498 values that are defined by this specification for use with JWE. 499 These algorithms are used to encrypt the CEK, producing the JWE 500 Encrypted Key, or to use key agreement to agree upon the CEK. 502 +-------------------+-----------------+------------+----------------+ 503 | alg Parameter | Key Management | Additional | Implementation | 504 | Value | Algorithm | Header | Requirements | 505 | | | Parameters | | 506 +-------------------+-----------------+------------+----------------+ 507 | RSA1_5 | RSAES-PKCS1-V1_ | (none) | Required | 508 | | 5 | | | 509 | RSA-OAEP | RSAES using | (none) | Optional | 510 | | OAEP with | | | 511 | | default | | | 512 | | parameters | | | 513 | A128KW | AES Key Wrap | (none) | Recommended | 514 | | with default | | | 515 | | initial value | | | 516 | | using 128 bit | | | 517 | | key | | | 518 | A192KW | AES Key Wrap | (none) | Optional | 519 | | with default | | | 520 | | initial value | | | 521 | | using 192 bit | | | 522 | | key | | | 523 | A256KW | AES Key Wrap | (none) | Recommended | 524 | | with default | | | 525 | | initial value | | | 526 | | using 256 bit | | | 527 | | key | | | 528 | dir | Direct use of a | (none) | Recommended | 529 | | shared | | | 530 | | symmetric key | | | 531 | | as the CEK | | | 532 | ECDH-ES | Elliptic Curve | "epk", | Recommended+ | 533 | | Diffie-Hellman | "apu", | | 534 | | Ephemeral | "apv" | | 535 | | Static key | | | 536 | | agreement using | | | 537 | | Concat KDF | | | 538 | ECDH-ES+A128KW | ECDH-ES using | "epk", | Recommended | 539 | | Concat KDF and | "apu", | | 540 | | CEK wrapped | "apv" | | 541 | | with "A128KW" | | | 542 | ECDH-ES+A192KW | ECDH-ES using | "epk", | Optional | 543 | | Concat KDF and | "apu", | | 544 | | CEK wrapped | "apv" | | 545 | | with "A192KW" | | | 546 | ECDH-ES+A256KW | ECDH-ES using | "epk", | Recommended | 547 | | Concat KDF and | "apu", | | 548 | | CEK wrapped | "apv" | | 549 | | with "A256KW" | | | 550 | A128GCMKW | Key wrapping | "iv", | Optional | 551 | | with AES GCM | "tag" | | 552 | | using 128 bit | | | 553 | | key | | | 554 | A192GCMKW | Key wrapping | "iv", | Optional | 555 | | with AES GCM | "tag" | | 556 | | using 192 bit | | | 557 | | key | | | 558 | A256GCMKW | Key wrapping | "iv", | Optional | 559 | | with AES GCM | "tag" | | 560 | | using 256 bit | | | 561 | | key | | | 562 | PBES2-HS256+A128K | PBES2 with HMAC | "p2s", | Optional | 563 | W | SHA-256 and | "p2c" | | 564 | | "A128KW" | | | 565 | | wrapping | | | 566 | PBES2-HS384+A192K | PBES2 with HMAC | "p2s", | Optional | 567 | W | SHA-384 and | "p2c" | | 568 | | "A192KW" | | | 569 | | wrapping | | | 570 | PBES2-HS512+A256K | PBES2 with HMAC | "p2s", | Optional | 571 | W | SHA-512 and | "p2c" | | 572 | | "A256KW" | | | 573 | | wrapping | | | 574 +-------------------+-----------------+------------+----------------+ 576 The Additional Header Parameters column indicates what additional 577 Header Parameters are used by the algorithm, beyond "alg", which all 578 use. All but "dir" and "ECDH-ES" also produce a JWE Encrypted Key 579 value. 581 The use of "+" in the Implementation Requirements indicates that the 582 requirement strength is likely to be increased in a future version of 583 the specification. 585 See Appendix A.2 for a table cross-referencing the JWE "alg" 586 (algorithm) values defined in this specification with the equivalent 587 identifiers used by other standards and software packages. 589 4.2. Key Encryption with RSAES-PKCS1-V1_5 591 This section defines the specifics of encrypting a JWE CEK with 592 RSAES-PKCS1-V1_5 [RFC3447]. The "alg" Header Parameter value 593 "RSA1_5" is used for this algorithm. 595 A key of size 2048 bits or larger MUST be used with this algorithm. 597 An example using this algorithm is shown in Appendix A.2 of [JWE]. 599 4.3. Key Encryption with RSAES OAEP 601 This section defines the specifics of encrypting a JWE CEK with RSAES 602 using Optimal Asymmetric Encryption Padding (OAEP) [RFC3447], with 603 the default parameters specified by RFC 3447 in Section A.2.1. 604 (Those default parameters are using a hash function of SHA-1 and a 605 mask generation function of MGF1 with SHA-1.) The "alg" Header 606 Parameter value "RSA-OAEP" is used for this algorithm. 608 A key of size 2048 bits or larger MUST be used with this algorithm. 610 An example using this algorithm is shown in Appendix A.1 of [JWE]. 612 4.4. Key Wrapping with AES Key Wrap 614 This section defines the specifics of encrypting a JWE CEK with the 615 Advanced Encryption Standard (AES) Key Wrap Algorithm [RFC3394] using 616 the default initial value specified in Section 2.2.3.1. 618 The following "alg" (algorithm) Header Parameter values are used to 619 indicate that the JWE Encrypted Key is the result of encrypting the 620 CEK using the corresponding algorithm and key size: 622 +------------------+------------------------------------------------+ 623 | alg Parameter | Key Management Algorithm | 624 | Value | | 625 +------------------+------------------------------------------------+ 626 | A128KW | AES Key Wrap with default initial value using | 627 | | 128 bit key | 628 | A192KW | AES Key Wrap with default initial value using | 629 | | 192 bit key | 630 | A256KW | AES Key Wrap with default initial value using | 631 | | 256 bit key | 632 +------------------+------------------------------------------------+ 633 An example using this algorithm is shown in Appendix A.3 of [JWE]. 635 4.5. Direct Encryption with a Shared Symmetric Key 637 This section defines the specifics of directly performing symmetric 638 key encryption without performing a key wrapping step. In this case, 639 the shared symmetric key is used directly as the Content Encryption 640 Key (CEK) value for the "enc" algorithm. An empty octet sequence is 641 used as the JWE Encrypted Key value. The "alg" Header Parameter 642 value "dir" is used in this case. 644 Refer to the security considerations on key lifetimes in Section 8.2 645 and AES GCM in Section 8.4 when considering utilizing direct 646 encryption. 648 4.6. Key Agreement with Elliptic Curve Diffie-Hellman Ephemeral Static 649 (ECDH-ES) 651 This section defines the specifics of key agreement with Elliptic 652 Curve Diffie-Hellman Ephemeral Static [RFC6090], in combination with 653 the Concat KDF, as defined in Section 5.8.1 of [NIST.800-56A]. The 654 key agreement result can be used in one of two ways: 656 1. directly as the Content Encryption Key (CEK) for the "enc" 657 algorithm, in the Direct Key Agreement mode, or 659 2. as a symmetric key used to wrap the CEK with the "A128KW", 660 "A192KW", or "A256KW" algorithms, in the Key Agreement with Key 661 Wrapping mode. 663 A new ephemeral public key value MUST be generated for each key 664 agreement operation. 666 In Direct Key Agreement mode, the output of the Concat KDF MUST be a 667 key of the same length as that used by the "enc" algorithm. In this 668 case, the empty octet sequence is used as the JWE Encrypted Key 669 value. The "alg" Header Parameter value "ECDH-ES" is used in the 670 Direct Key Agreement mode. 672 In Key Agreement with Key Wrapping mode, the output of the Concat KDF 673 MUST be a key of the length needed for the specified key wrapping 674 algorithm. In this case, the JWE Encrypted Key is the CEK wrapped 675 with the agreed upon key. 677 The following "alg" (algorithm) Header Parameter values are used to 678 indicate that the JWE Encrypted Key is the result of encrypting the 679 CEK using the result of the key agreement algorithm as the key 680 encryption key for the corresponding key wrapping algorithm: 682 +-------------------+-----------------------------------------------+ 683 | alg Parameter | Key Management Algorithm | 684 | Value | | 685 +-------------------+-----------------------------------------------+ 686 | ECDH-ES+A128KW | ECDH-ES using Concat KDF and CEK wrapped with | 687 | | "A128KW" | 688 | ECDH-ES+A192KW | ECDH-ES using Concat KDF and CEK wrapped with | 689 | | "A192KW" | 690 | ECDH-ES+A256KW | ECDH-ES using Concat KDF and CEK wrapped with | 691 | | "A256KW" | 692 +-------------------+-----------------------------------------------+ 694 4.6.1. Header Parameters Used for ECDH Key Agreement 696 The following Header Parameter names are used for key agreement as 697 defined below. 699 4.6.1.1. "epk" (Ephemeral Public Key) Header Parameter 701 The "epk" (ephemeral public key) value created by the originator for 702 the use in key agreement algorithms. This key is represented as a 703 JSON Web Key [JWK] public key value. It MUST contain only public key 704 parameters and SHOULD contain only the minimum JWK parameters 705 necessary to represent the key; other JWK parameters included can be 706 checked for consistency and honored or can be ignored. This Header 707 Parameter MUST be present and MUST be understood and processed by 708 implementations when these algorithms are used. 710 4.6.1.2. "apu" (Agreement PartyUInfo) Header Parameter 712 The "apu" (agreement PartyUInfo) value for key agreement algorithms 713 using it (such as "ECDH-ES"), represented as a base64url encoded 714 string. When used, the PartyUInfo value contains information about 715 the sender. Use of this Header Parameter is OPTIONAL. This Header 716 Parameter MUST be understood and processed by implementations when 717 these algorithms are used. 719 4.6.1.3. "apv" (Agreement PartyVInfo) Header Parameter 721 The "apv" (agreement PartyVInfo) value for key agreement algorithms 722 using it (such as "ECDH-ES"), represented as a base64url encoded 723 string. When used, the PartyVInfo value contains information about 724 the receiver. Use of this Header Parameter is OPTIONAL. This Header 725 Parameter MUST be understood and processed by implementations when 726 these algorithms are used. 728 4.6.2. Key Derivation for ECDH Key Agreement 730 The key derivation process derives the agreed upon key from the 731 shared secret Z established through the ECDH algorithm, per Section 732 6.2.2.2 of [NIST.800-56A]. 734 Key derivation is performed using the Concat KDF, as defined in 735 Section 5.8.1 of [NIST.800-56A], where the Digest Method is SHA-256. 736 The Concat KDF parameters are set as follows: 738 Z This is set to the representation of the shared secret Z as an 739 octet sequence. 741 keydatalen This is set to the number of bits in the desired output 742 key. For "ECDH-ES", this is length of the key used by the "enc" 743 algorithm. For "ECDH-ES+A128KW", "ECDH-ES+A192KW", and 744 "ECDH-ES+A256KW", this is 128, 192, and 256, respectively. 746 AlgorithmID The AlgorithmID value is of the form Datalen || Data, 747 where Data is a variable-length string of zero or more octets, and 748 Datalen is a fixed-length, big endian 32 bit counter that 749 indicates the length (in octets) of Data. In the Direct Key 750 Agreement case, Data is set to the octets of the UTF-8 751 representation of the "enc" Header Parameter value. In the Key 752 Agreement with Key Wrapping case, Data is set to the octets of the 753 UTF-8 representation of the "alg" Header Parameter value. 755 PartyUInfo The PartyUInfo value is of the form Datalen || Data, 756 where Data is a variable-length string of zero or more octets, and 757 Datalen is a fixed-length, big endian 32 bit counter that 758 indicates the length (in octets) of Data. If an "apu" (agreement 759 PartyUInfo) Header Parameter is present, Data is set to the result 760 of base64url decoding the "apu" value and Datalen is set to the 761 number of octets in Data. Otherwise, Datalen is set to 0 and Data 762 is set to the empty octet sequence. 764 PartyVInfo The PartyVInfo value is of the form Datalen || Data, 765 where Data is a variable-length string of zero or more octets, and 766 Datalen is a fixed-length, big endian 32 bit counter that 767 indicates the length (in octets) of Data. If an "apv" (agreement 768 PartyVInfo) Header Parameter is present, Data is set to the result 769 of base64url decoding the "apv" value and Datalen is set to the 770 number of octets in Data. Otherwise, Datalen is set to 0 and Data 771 is set to the empty octet sequence. 773 SuppPubInfo This is set to the keydatalen represented as a 32 bit 774 big endian integer. 776 SuppPrivInfo This is set to the empty octet sequence. 778 Applications need to specify how the "apu" and "apv" parameters are 779 used for that application. The "apu" and "apv" values MUST be 780 distinct, when used. Applications wishing to conform to 781 [NIST.800-56A] need to provide values that meet the requirements of 782 that document, e.g., by using values that identify the sender and 783 recipient. Alternatively, applications MAY conduct key derivation in 784 a manner similar to The Diffie-Hellman Key Agreement Method 785 [RFC2631]: In that case, the "apu" field MAY either be omitted or 786 represent a random 512-bit value (analogous to PartyAInfo in 787 Ephemeral-Static mode in [RFC2631]) and the "apv" field should not be 788 present. 790 See Appendix C for an example key agreement computation using this 791 method. 793 4.7. Key Encryption with AES GCM 795 This section defines the specifics of encrypting a JWE Content 796 Encryption Key (CEK) with Advanced Encryption Standard (AES) in 797 Galois/Counter Mode (GCM) [AES] [NIST.800-38D]. 799 Use of an Initialization Vector of size 96 bits is REQUIRED with this 800 algorithm. The Initialization Vector is represented in base64url 801 encoded form as the "iv" (initialization vector) Header Parameter 802 value. 804 The Additional Authenticated Data value used is the empty octet 805 string. 807 The requested size of the Authentication Tag output MUST be 128 bits, 808 regardless of the key size. 810 The JWE Encrypted Key value is the Ciphertext output. 812 The Authentication Tag output is represented in base64url encoded 813 form as the "tag" (authentication tag) Header Parameter value. 815 The following "alg" (algorithm) Header Parameter values are used to 816 indicate that the JWE Encrypted Key is the result of encrypting the 817 CEK using the corresponding algorithm and key size: 819 +---------------------+---------------------------------------------+ 820 | alg Parameter Value | Key Management Algorithm | 821 +---------------------+---------------------------------------------+ 822 | A128GCMKW | Key wrapping with AES GCM using 128 bit key | 823 | A192GCMKW | Key wrapping with AES GCM using 192 bit key | 824 | A256GCMKW | Key wrapping with AES GCM using 256 bit key | 825 +---------------------+---------------------------------------------+ 827 4.7.1. Header Parameters Used for AES GCM Key Encryption 829 The following Header Parameters are used for AES GCM key encryption. 831 4.7.1.1. "iv" (Initialization Vector) Header Parameter 833 The "iv" (initialization vector) Header Parameter value is the 834 base64url encoded representation of the Initialization Vector value 835 used for the key encryption operation. This Header Parameter MUST be 836 present and MUST be understood and processed by implementations when 837 these algorithms are used. 839 4.7.1.2. "tag" (Authentication Tag) Header Parameter 841 The "tag" (authentication tag) Header Parameter value is the 842 base64url encoded representation of the Authentication Tag value 843 resulting from the key encryption operation. This Header Parameter 844 MUST be present and MUST be understood and processed by 845 implementations when these algorithms are used. 847 4.8. Key Encryption with PBES2 849 This section defines the specifies of performing password-based 850 encryption of a JWE CEK, by first deriving a key encryption key from 851 a user-supplied password using PBES2 schemes as specified in Section 852 6.2 of [RFC2898], then by encrypting the JWE CEK using the derived 853 key. 855 These algorithms use HMAC SHA-2 algorithms as the Pseudo-Random 856 Function (PRF) for the PBKDF2 key derivation and AES Key Wrap 857 [RFC3394] for the encryption scheme. The PBES2 password input is an 858 octet sequence; if the password to be used is represented as a text 859 string rather than an octet sequence, the UTF-8 encoding of the text 860 string MUST be used as the octet sequence. The salt MUST be provided 861 as the "p2s" Header Parameter value, and MUST be base64url decoded to 862 obtain the value. The iteration count parameter MUST be provided as 863 the "p2c" Header Parameter value. The algorithms respectively use 864 HMAC SHA-256, HMAC SHA-384, and HMAC SHA-512 as the PRF and use 128, 865 192, and 256 bit AES Key Wrap keys. Their derived-key lengths 866 respectively are 16, 24, and 32 octets. 868 The following "alg" (algorithm) Header Parameter values are used to 869 indicate that the JWE Encrypted Key is the result of encrypting the 870 CEK using the result of the corresponding password-based encryption 871 algorithm as the key encryption key for the corresponding key 872 wrapping algorithm: 874 +---------------------+---------------------------------------------+ 875 | alg Parameter Value | Key Management Algorithm | 876 +---------------------+---------------------------------------------+ 877 | PBES2-HS256+A128KW | PBES2 with HMAC SHA-256 and "A128KW" | 878 | | wrapping | 879 | PBES2-HS384+A192KW | PBES2 with HMAC SHA-384 and "A192KW" | 880 | | wrapping | 881 | PBES2-HS512+A256KW | PBES2 with HMAC SHA-512 and "A256KW" | 882 | | wrapping | 883 +---------------------+---------------------------------------------+ 885 See Appendix C of JSON Web Key (JWK) [JWK] for an example key 886 encryption computation using "PBES2-HS256+A128KW". 888 4.8.1. Header Parameters Used for PBES2 Key Encryption 890 The following Header Parameters are used for Key Encryption with 891 PBES2. 893 4.8.1.1. "p2s" (PBES2 salt) Parameter 895 The "p2s" (PBES2 salt) Header Parameter contains the PBKDF2 salt 896 value, encoded using base64url. This Header Parameter MUST be 897 present and MUST be understood and processed by implementations when 898 these algorithms are used. 900 The salt expands the possible keys that can be derived from a given 901 password. A salt value containing 8 or more octets MUST be used. A 902 new salt value MUST be generated randomly for every encryption 903 operation; see [RFC4086] for considerations on generating random 904 values. 906 4.8.1.2. "p2c" (PBES2 count) Parameter 908 The "p2c" (PBES2 count) Header Parameter contains the PBKDF2 909 iteration count, represented as a positive integer. This Header 910 Parameter MUST be present and MUST be understood and processed by 911 implementations when these algorithms are used. 913 The iteration count adds computational expense, ideally compounded by 914 the possible range of keys introduced by the salt. A minimum 915 iteration count of 1000 is RECOMMENDED. 917 5. Cryptographic Algorithms for Content Encryption 919 JWE uses cryptographic algorithms to encrypt the Plaintext. 921 5.1. "enc" (Encryption Algorithm) Header Parameter Values for JWE 923 The table below is the set of "enc" (encryption algorithm) Header 924 Parameter values that are defined by this specification for use with 925 JWE. These algorithms are used to encrypt the Plaintext, which 926 produces the Ciphertext. 928 +-------------+------------------------+------------+---------------+ 929 | enc | Content Encryption | Additional | Implementatio | 930 | Parameter | Algorithm | Header | nRequirements | 931 | Value | | Parameters | | 932 +-------------+------------------------+------------+---------------+ 933 | A128CBC-HS2 | AES_128_CBC_HMAC_SHA_2 | (none) | Required | 934 | 56 | 56 authenticated | | | 935 | | encryption algorithm, | | | 936 | | as defined in | | | 937 | | Section 5.2.3 | | | 938 | A192CBC-HS3 | AES_192_CBC_HMAC_SHA_3 | (none) | Optional | 939 | 84 | 84 authenticated | | | 940 | | encryption algorithm, | | | 941 | | as defined in | | | 942 | | Section 5.2.4 | | | 943 | A256CBC-HS5 | AES_256_CBC_HMAC_SHA_5 | (none) | Required | 944 | 12 | 12 authenticated | | | 945 | | encryption algorithm, | | | 946 | | as defined in | | | 947 | | Section 5.2.5 | | | 948 | A128GCM | AES GCM using 128 bit | (none) | Recommended | 949 | | key | | | 950 | A192GCM | AES GCM using 192 bit | (none) | Optional | 951 | | key | | | 952 | A256GCM | AES GCM using 256 bit | (none) | Recommended | 953 | | key | | | 954 +-------------+------------------------+------------+---------------+ 956 The Additional Header Parameters column indicates what additional 957 Header Parameters are used by the algorithm, beyond "enc", which all 958 use. All also use a JWE Initialization Vector value and produce JWE 959 Ciphertext and JWE Authentication Tag values. 961 See Appendix A.3 for a table cross-referencing the JWE "enc" 962 (encryption algorithm) values defined in this specification with the 963 equivalent identifiers used by other standards and software packages. 965 5.2. AES_CBC_HMAC_SHA2 Algorithms 967 This section defines a family of authenticated encryption algorithms 968 built using a composition of Advanced Encryption Standard (AES) in 969 Cipher Block Chaining (CBC) mode with PKCS #5 padding [AES] 970 [NIST.800-38A] operations and HMAC [RFC2104] [SHS] operations. This 971 algorithm family is called AES_CBC_HMAC_SHA2. It also defines three 972 instances of this family, the first using 128 bit CBC keys and HMAC 973 SHA-256, the second using 192 bit CBC keys and HMAC SHA-384, and the 974 third using 256 bit CBC keys and HMAC SHA-512. Test cases for these 975 algorithms can be found in Appendix B. 977 These algorithms are based upon Authenticated Encryption with AES-CBC 978 and HMAC-SHA [I-D.mcgrew-aead-aes-cbc-hmac-sha2], performing the same 979 cryptographic computations, but with the Initialization Vector and 980 Authentication Tag values remaining separate, rather than being 981 concatenated with the Ciphertext value in the output representation. 982 This option is discussed in Appendix B of that specification. This 983 algorithm family is a generalization of the algorithm family in 984 [I-D.mcgrew-aead-aes-cbc-hmac-sha2], and can be used to implement 985 those algorithms. 987 5.2.1. Conventions Used in Defining AES_CBC_HMAC_SHA2 989 We use the following notational conventions. 991 CBC-PKCS5-ENC(X, P) denotes the AES CBC encryption of P using PKCS 992 #5 padding using the cipher with the key X. 994 MAC(Y, M) denotes the application of the Message Authentication 995 Code (MAC) to the message M, using the key Y. 997 5.2.2. Generic AES_CBC_HMAC_SHA2 Algorithm 999 This section defines AES_CBC_HMAC_SHA2 in a manner that is 1000 independent of the AES CBC key size or hash function to be used. 1001 Section 5.2.2.1 and Section 5.2.2.2 define the generic encryption and 1002 decryption algorithms. Section 5.2.3 and Section 5.2.5 define 1003 instances of AES_CBC_HMAC_SHA2 that specify those details. 1005 5.2.2.1. AES_CBC_HMAC_SHA2 Encryption 1007 The authenticated encryption algorithm takes as input four octet 1008 strings: a secret key K, a plaintext P, associated data A, and an 1009 initialization vector IV. The authenticated ciphertext value E and 1010 the authentication tag value T are provided as outputs. The data in 1011 the plaintext are encrypted and authenticated, and the associated 1012 data are authenticated, but not encrypted. 1014 The encryption process is as follows, or uses an equivalent set of 1015 steps: 1017 1. The secondary keys MAC_KEY and ENC_KEY are generated from the 1018 input key K as follows. Each of these two keys is an octet 1019 string. 1021 MAC_KEY consists of the initial MAC_KEY_LEN octets of K, in 1022 order. 1024 ENC_KEY consists of the final ENC_KEY_LEN octets of K, in 1025 order. 1027 Here we denote the number of octets in the MAC_KEY as 1028 MAC_KEY_LEN, and the number of octets in ENC_KEY as ENC_KEY_LEN; 1029 the values of these parameters are specified by the AEAD 1030 algorithms (in Section 5.2.3 and Section 5.2.5). The number of 1031 octets in the input key K is the sum of MAC_KEY_LEN and 1032 ENC_KEY_LEN. When generating the secondary keys from K, MAC_KEY 1033 and ENC_KEY MUST NOT overlap. Note that the MAC key comes before 1034 the encryption key in the input key K; this is in the opposite 1035 order of the algorithm names in the identifier 1036 "AES_CBC_HMAC_SHA2". 1038 2. The Initialization Vector (IV) used is a 128 bit value generated 1039 randomly or pseudorandomly for use in the cipher. 1041 3. The plaintext is CBC encrypted using PKCS #5 padding using 1042 ENC_KEY as the key, and the IV. We denote the ciphertext output 1043 from this step as E. 1045 4. The octet string AL is equal to the number of bits in A expressed 1046 as a 64-bit unsigned integer in network byte order. 1048 5. A message authentication tag T is computed by applying HMAC 1049 [RFC2104] to the following data, in order: 1051 the associated data A, 1053 the initialization vector IV, 1055 the ciphertext E computed in the previous step, and 1057 the octet string AL defined above. 1059 The string MAC_KEY is used as the MAC key. We denote the output 1060 of the MAC computed in this step as M. The first T_LEN bits of M 1061 are used as T. 1063 6. The Ciphertext E and the Authentication Tag T are returned as the 1064 outputs of the authenticated encryption. 1066 The encryption process can be illustrated as follows. Here K, P, A, 1067 IV, and E denote the key, plaintext, associated data, initialization 1068 vector, and ciphertext, respectively. 1070 MAC_KEY = initial MAC_KEY_LEN bytes of K, 1072 ENC_KEY = final ENC_KEY_LEN bytes of K, 1074 E = CBC-PKCS5-ENC(ENC_KEY, P), 1076 M = MAC(MAC_KEY, A || IV || E || AL), 1078 T = initial T_LEN bytes of M. 1080 5.2.2.2. AES_CBC_HMAC_SHA2 Decryption 1082 The authenticated decryption operation has four inputs: K, A, E, and 1083 T as defined above. It has only a single output, either a plaintext 1084 value P or a special symbol FAIL that indicates that the inputs are 1085 not authentic. The authenticated decryption algorithm is as follows, 1086 or uses an equivalent set of steps: 1088 1. The secondary keys MAC_KEY and ENC_KEY are generated from the 1089 input key K as in Step 1 of Section 5.2.2.1. 1091 2. The integrity and authenticity of A and E are checked by 1092 computing an HMAC with the inputs as in Step 5 of 1093 Section 5.2.2.1. The value T, from the previous step, is 1094 compared to the first MAC_KEY length bits of the HMAC output. If 1095 those values are identical, then A and E are considered valid, 1096 and processing is continued. Otherwise, all of the data used in 1097 the MAC validation are discarded, and the AEAD decryption 1098 operation returns an indication that it failed, and the operation 1099 halts. (But see Section 10 of [JWE] for security considerations 1100 on thwarting timing attacks.) 1102 3. The value E is decrypted and the PKCS #5 padding is removed. The 1103 value IV is used as the initialization vector. The value ENC_KEY 1104 is used as the decryption key. 1106 4. The plaintext value is returned. 1108 5.2.3. AES_128_CBC_HMAC_SHA_256 1110 This algorithm is a concrete instantiation of the generic 1111 AES_CBC_HMAC_SHA2 algorithm above. It uses the HMAC message 1112 authentication code [RFC2104] with the SHA-256 hash function [SHS] to 1113 provide message authentication, with the HMAC output truncated to 128 1114 bits, corresponding to the HMAC-SHA-256-128 algorithm defined in 1115 [RFC4868]. For encryption, it uses AES in the Cipher Block Chaining 1116 (CBC) mode of operation as defined in Section 6.2 of [NIST.800-38A], 1117 with PKCS #5 padding and a 128 bit initialization vector (IV) value. 1119 The AES_CBC_HMAC_SHA2 parameters specific to AES_128_CBC_HMAC_SHA_256 1120 are: 1122 The input key K is 32 octets long. 1124 ENC_KEY_LEN is 16 octets. 1126 MAC_KEY_LEN is 16 octets. 1128 The SHA-256 hash algorithm is used for the HMAC. 1130 The HMAC-SHA-256 output is truncated to T_LEN=16 octets, by 1131 stripping off the final 16 octets. 1133 5.2.4. AES_192_CBC_HMAC_SHA_384 1135 AES_192_CBC_HMAC_SHA_384 is based on AES_128_CBC_HMAC_SHA_256, but 1136 with the following differences: 1138 The input key K is 48 octets long instead of 32. 1140 ENC_KEY_LEN is 24 octets instead of 16. 1142 MAC_KEY_LEN is 24 octets instead of 16. 1144 SHA-384 is used for the HMAC instead of SHA-256. 1146 The HMAC SHA-384 value is truncated to T_LEN=24 octets instead of 1147 16. 1149 5.2.5. AES_256_CBC_HMAC_SHA_512 1151 AES_256_CBC_HMAC_SHA_512 is based on AES_128_CBC_HMAC_SHA_256, but 1152 with the following differences: 1154 The input key K is 64 octets long instead of 32. 1156 ENC_KEY_LEN is 32 octets instead of 16. 1158 MAC_KEY_LEN is 32 octets instead of 16. 1160 SHA-512 is used for the HMAC instead of SHA-256. 1162 The HMAC SHA-512 value is truncated to T_LEN=32 octets instead of 1163 16. 1165 5.2.6. Content Encryption with AES_CBC_HMAC_SHA2 1167 The following "enc" (encryption algorithm) Header Parameter values 1168 are used to indicate that the JWE Ciphertext and JWE Authentication 1169 Tag values have been computed using the corresponding algorithm: 1171 +---------------+---------------------------------------------------+ 1172 | enc Parameter | Content Encryption Algorithm | 1173 | Value | | 1174 +---------------+---------------------------------------------------+ 1175 | A128CBC-HS256 | AES_128_CBC_HMAC_SHA_256 authenticated encryption | 1176 | | algorithm, as defined in Section 5.2.3 | 1177 | A192CBC-HS384 | AES_192_CBC_HMAC_SHA_384 authenticated encryption | 1178 | | algorithm, as defined in Section 5.2.4 | 1179 | A256CBC-HS512 | AES_256_CBC_HMAC_SHA_512 authenticated encryption | 1180 | | algorithm, as defined in Section 5.2.5 | 1181 +---------------+---------------------------------------------------+ 1183 5.3. Content Encryption with AES GCM 1185 This section defines the specifics of encrypting the JWE Plaintext 1186 with Advanced Encryption Standard (AES) in Galois/Counter Mode (GCM) 1187 [AES] [NIST.800-38D]. The "enc" Header Parameter values "A128GCM", 1188 "A192GCM", or "A256GCM" are respectively used in this case. 1190 The CEK is used as the encryption key. 1192 Use of an initialization vector of size 96 bits is REQUIRED with this 1193 algorithm. 1195 The requested size of the Authentication Tag output MUST be 128 bits, 1196 regardless of the key size. 1198 The JWE Authentication Tag is set to be the Authentication Tag value 1199 produced by the encryption. During decryption, the received JWE 1200 Authentication Tag is used as the Authentication Tag value. 1202 The following "enc" (encryption algorithm) Header Parameter values 1203 are used to indicate that the JWE Ciphertext and JWE Authentication 1204 Tag values have been computed using the corresponding algorithm and 1205 key size: 1207 +---------------------+------------------------------+ 1208 | enc Parameter Value | Content Encryption Algorithm | 1209 +---------------------+------------------------------+ 1210 | A128GCM | AES GCM using 128 bit key | 1211 | A192GCM | AES GCM using 192 bit key | 1212 | A256GCM | AES GCM using 256 bit key | 1213 +---------------------+------------------------------+ 1215 An example using this algorithm is shown in Appendix A.1 of [JWE]. 1217 6. Cryptographic Algorithms for Keys 1219 A JSON Web Key (JWK) [JWK] is a JSON data structure that represents a 1220 cryptographic key. These keys can be either asymmetric or symmetric. 1221 They can hold both public and private information about the key. 1222 This section defines the parameters for keys using the algorithms 1223 specified by this document. 1225 6.1. "kty" (Key Type) Parameter Values 1227 The table below is the set of "kty" (key type) parameter values that 1228 are defined by this specification for use in JWKs. 1230 +--------------+--------------------------------+-------------------+ 1231 | kty | Key Type | Implementation | 1232 | Parameter | | Requirements | 1233 | Value | | | 1234 +--------------+--------------------------------+-------------------+ 1235 | EC | Elliptic Curve [DSS] | Recommended+ | 1236 | RSA | RSA [RFC3447] | Required | 1237 | oct | Octet sequence (used to | Required | 1238 | | represent symmetric keys) | | 1239 +--------------+--------------------------------+-------------------+ 1241 The use of "+" in the Implementation Requirements indicates that the 1242 requirement strength is likely to be increased in a future version of 1243 the specification. 1245 6.2. Parameters for Elliptic Curve Keys 1247 JWKs can represent Elliptic Curve [DSS] keys. In this case, the 1248 "kty" member value MUST be "EC". 1250 6.2.1. Parameters for Elliptic Curve Public Keys 1252 An elliptic curve public key is represented by a pair of coordinates 1253 drawn from a finite field, which together define a point on an 1254 elliptic curve. The following members MUST be present for elliptic 1255 curve public keys: 1257 o "crv" 1259 o "x" 1261 o "y" 1263 SEC1 [SEC1] point compression is not supported for any values. 1265 6.2.1.1. "crv" (Curve) Parameter 1267 The "crv" (curve) member identifies the cryptographic curve used with 1268 the key. Curve values from [DSS] used by this specification are: 1270 o "P-256" 1272 o "P-384" 1274 o "P-521" 1276 These values are registered in the IANA JSON Web Key Elliptic Curve 1277 registry defined in Section 7.6. Additional "crv" values MAY be 1278 used, provided they are understood by implementations using that 1279 Elliptic Curve key. The "crv" value is a case-sensitive string. 1281 6.2.1.2. "x" (X Coordinate) Parameter 1283 The "x" (x coordinate) member contains the x coordinate for the 1284 elliptic curve point. It is represented as the base64url encoding of 1285 the octet string representation of the coordinate, as defined in 1286 Section 2.3.5 of SEC1 [SEC1]. The length of this octet string MUST 1287 be the full size of a coordinate for the curve specified in the "crv" 1288 parameter. For example, if the value of "crv" is "P-521", the octet 1289 string must be 66 octets long. 1291 6.2.1.3. "y" (Y Coordinate) Parameter 1293 The "y" (y coordinate) member contains the y coordinate for the 1294 elliptic curve point. It is represented as the base64url encoding of 1295 the octet string representation of the coordinate, as defined in 1296 Section 2.3.5 of SEC1 [SEC1]. The length of this octet string MUST 1297 be the full size of a coordinate for the curve specified in the "crv" 1298 parameter. For example, if the value of "crv" is "P-521", the octet 1299 string must be 66 octets long. 1301 6.2.2. Parameters for Elliptic Curve Private Keys 1303 In addition to the members used to represent Elliptic Curve public 1304 keys, the following member MUST be present to represent Elliptic 1305 Curve private keys. 1307 6.2.2.1. "d" (ECC Private Key) Parameter 1309 The "d" (ECC private key) member contains the Elliptic Curve private 1310 key value. It is represented as the base64url encoding of the octet 1311 string representation of the private key value, as defined in 1312 Sections C.4 and 2.3.7 of SEC1 [SEC1]. The length of this octet 1313 string MUST be ceiling(log-base-2(n)/8) octets (where n is the order 1314 of the curve). 1316 6.3. Parameters for RSA Keys 1318 JWKs can represent RSA [RFC3447] keys. In this case, the "kty" 1319 member value MUST be "RSA". 1321 6.3.1. Parameters for RSA Public Keys 1323 The following members MUST be present for RSA public keys. 1325 6.3.1.1. "n" (Modulus) Parameter 1327 The "n" (modulus) member contains the modulus value for the RSA 1328 public key. It is represented as the base64url encoding of the 1329 value's unsigned big endian representation as an octet sequence. The 1330 octet sequence MUST utilize the minimum number of octets to represent 1331 the value. 1333 6.3.1.2. "e" (Exponent) Parameter 1335 The "e" (exponent) member contains the exponent value for the RSA 1336 public key. It is represented as the base64url encoding of the 1337 value's unsigned big endian representation as an octet sequence. The 1338 octet sequence MUST utilize the minimum number of octets to represent 1339 the value. For instance, when representing the value 65537, the 1340 octet sequence to be base64url encoded MUST consist of the three 1341 octets [1, 0, 1]. 1343 6.3.2. Parameters for RSA Private Keys 1345 In addition to the members used to represent RSA public keys, the 1346 following members are used to represent RSA private keys. The 1347 parameter "d" is REQUIRED for RSA private keys. The others enable 1348 optimizations and SHOULD be included by producers of JWKs 1349 representing RSA private keys. If the producer includes any of the 1350 other private key parameters, then all of the others MUST be present, 1351 with the exception of "oth", which MUST only be present when more 1352 than two prime factors were used. The consumer of a JWK MAY choose 1353 to accept an RSA private key that does not contain a complete set of 1354 the private key parameters other than "d", including JWKs in which 1355 "d" is the only RSA private key parameter included. 1357 6.3.2.1. "d" (Private Exponent) Parameter 1359 The "d" (private exponent) member contains the private exponent value 1360 for the RSA private key. It is represented as the base64url encoding 1361 of the value's unsigned big endian representation as an octet 1362 sequence. The octet sequence MUST utilize the minimum number of 1363 octets to represent the value. 1365 6.3.2.2. "p" (First Prime Factor) Parameter 1367 The "p" (first prime factor) member contains the first prime factor, 1368 a positive integer. It is represented as the base64url encoding of 1369 the value's unsigned big endian representation as an octet sequence. 1370 The octet sequence MUST utilize the minimum number of octets to 1371 represent the value. 1373 6.3.2.3. "q" (Second Prime Factor) Parameter 1375 The "q" (second prime factor) member contains the second prime 1376 factor, a positive integer. It is represented as the base64url 1377 encoding of the value's unsigned big endian representation as an 1378 octet sequence. The octet sequence MUST utilize the minimum number 1379 of octets to represent the value. 1381 6.3.2.4. "dp" (First Factor CRT Exponent) Parameter 1383 The "dp" (first factor CRT exponent) member contains the Chinese 1384 Remainder Theorem (CRT) exponent of the first factor, a positive 1385 integer. It is represented as the base64url encoding of the value's 1386 unsigned big endian representation as an octet sequence. The octet 1387 sequence MUST utilize the minimum number of octets to represent the 1388 value. 1390 6.3.2.5. "dq" (Second Factor CRT Exponent) Parameter 1392 The "dq" (second factor CRT exponent) member contains the Chinese 1393 Remainder Theorem (CRT) exponent of the second factor, a positive 1394 integer. It is represented as the base64url encoding of the value's 1395 unsigned big endian representation as an octet sequence. The octet 1396 sequence MUST utilize the minimum number of octets to represent the 1397 value. 1399 6.3.2.6. "qi" (First CRT Coefficient) Parameter 1401 The "dp" (first CRT coefficient) member contains the Chinese 1402 Remainder Theorem (CRT) coefficient of the second factor, a positive 1403 integer. It is represented as the base64url encoding of the value's 1404 unsigned big endian representation as an octet sequence. The octet 1405 sequence MUST utilize the minimum number of octets to represent the 1406 value. 1408 6.3.2.7. "oth" (Other Primes Info) Parameter 1410 The "oth" (other primes info) member contains an array of information 1411 about any third and subsequent primes, should they exist. When only 1412 two primes have been used (the normal case), this parameter MUST be 1413 omitted. When three or more primes have been used, the number of 1414 array elements MUST be the number of primes used minus two. Each 1415 array element MUST be an object with the following members: 1417 6.3.2.7.1. "r" (Prime Factor) 1419 The "r" (prime factor) parameter within an "oth" array member 1420 represents the value of a subsequent prime factor, a positive 1421 integer. It is represented as the base64url encoding of the value's 1422 unsigned big endian representation as an octet sequence. The octet 1423 sequence MUST utilize the minimum number of octets to represent the 1424 value. 1426 6.3.2.7.2. "d" (Factor CRT Exponent) 1428 The "d" (Factor CRT Exponent) parameter within an "oth" array member 1429 represents the CRT exponent of the corresponding prime factor, a 1430 positive integer. It is represented as the base64url encoding of the 1431 value's unsigned big endian representation as an octet sequence. The 1432 octet sequence MUST utilize the minimum number of octets to represent 1433 the value. 1435 6.3.2.7.3. "t" (Factor CRT Coefficient) 1437 The "t" (factor CRT coefficient) parameter within an "oth" array 1438 member represents the CRT coefficient of the corresponding prime 1439 factor, a positive integer. It is represented as the base64url 1440 encoding of the value's unsigned big endian representation as an 1441 octet sequence. The octet sequence MUST utilize the minimum number 1442 of octets to represent the value. 1444 6.4. Parameters for Symmetric Keys 1446 When the JWK "kty" member value is "oct" (octet sequence), the member 1447 "k" is used to represent a symmetric key (or another key whose value 1448 is a single octet sequence). An "alg" member SHOULD also be present 1449 to identify the algorithm intended to be used with the key, unless 1450 the application uses another means or convention to determine the 1451 algorithm used. 1453 6.4.1. "k" (Key Value) Parameter 1455 The "k" (key value) member contains the value of the symmetric (or 1456 other single-valued) key. It is represented as the base64url 1457 encoding of the octet sequence containing the key value. 1459 7. IANA Considerations 1461 The following registration procedure is used for all the registries 1462 established by this specification. 1464 Values are registered with a Specification Required [RFC5226] after a 1465 two-week review period on the [TBD]@ietf.org mailing list, on the 1466 advice of one or more Designated Experts. However, to allow for the 1467 allocation of values prior to publication, the Designated Expert(s) 1468 may approve registration once they are satisfied that such a 1469 specification will be published. 1471 Registration requests must be sent to the [TBD]@ietf.org mailing list 1472 for review and comment, with an appropriate subject (e.g., "Request 1473 for access token type: example"). [[ Note to the RFC Editor: The name 1474 of the mailing list should be determined in consultation with the 1475 IESG and IANA. Suggested name: jose-reg-review. ]] 1477 Within the review period, the Designated Expert(s) will either 1478 approve or deny the registration request, communicating this decision 1479 to the review list and IANA. Denials should include an explanation 1480 and, if applicable, suggestions as to how to make the request 1481 successful. Registration requests that are undetermined for a period 1482 longer than 21 days can be brought to the IESG's attention (using the 1483 iesg@iesg.org mailing list) for resolution. 1485 Criteria that should be applied by the Designated Expert(s) includes 1486 determining whether the proposed registration duplicates existing 1487 functionality, determining whether it is likely to be of general 1488 applicability or whether it is useful only for a single application, 1489 and whether the registration makes sense. 1491 IANA must only accept registry updates from the Designated Expert(s) 1492 and should direct all requests for registration to the review mailing 1493 list. 1495 It is suggested that multiple Designated Experts be appointed who are 1496 able to represent the perspectives of different applications using 1497 this specification, in order to enable broadly-informed review of 1498 registration decisions. In cases where a registration decision could 1499 be perceived as creating a conflict of interest for a particular 1500 Expert, that Expert should defer to the judgment of the other 1501 Expert(s). 1503 7.1. JSON Web Signature and Encryption Algorithms Registry 1505 This specification establishes the IANA JSON Web Signature and 1506 Encryption Algorithms registry for values of the JWS and JWE "alg" 1507 (algorithm) and "enc" (encryption algorithm) Header Parameters. The 1508 registry records the algorithm name, the algorithm usage locations, 1509 implementation requirements, and a reference to the specification 1510 that defines it. The same algorithm name can be registered multiple 1511 times, provided that the sets of usage locations are disjoint. 1513 It is suggested that when algorithms can use keys of different 1514 lengths, that the length of the key be included in the algorithm 1515 name. This allows readers of the JSON text to easily make security 1516 consideration decisions. 1518 The implementation requirements of an algorithm MAY be changed over 1519 time by the Designated Experts(s) as the cryptographic landscape 1520 evolves, for instance, to change the status of an algorithm to 1521 Deprecated, or to change the status of an algorithm from Optional to 1522 Recommended+ or Required. Changes of implementation requirements are 1523 only permitted on a Specification Required basis, with the new 1524 specification defining the revised implementation requirements level. 1526 7.1.1. Registration Template 1527 Algorithm Name: 1528 The name requested (e.g., "example"). This name is case- 1529 sensitive. Names may not match other registered names in a case- 1530 insensitive manner unless the Designated Expert(s) state that 1531 there is a compelling reason to allow an exception in this 1532 particular case. 1534 Algorithm Description: 1535 Brief description of the Algorithm (e.g., "Example description"). 1537 Algorithm Usage Location(s): 1538 The algorithm usage location. This must be one or more of the 1539 values "alg" or "enc" if the algorithm is to be used with JWS or 1540 JWE. The value "JWK" is used if the algorithm identifier will be 1541 used as a JWK "alg" member value, but will not be used with JWS or 1542 JWE; this could be the case, for instance, for non-authenticated 1543 encryption algorithms. Other values may be used with the approval 1544 of a Designated Expert. 1546 JOSE Implementation Requirements: 1547 The algorithm implementation requirements for JWS and JWE, which 1548 must be one the words Required, Recommended, Optional, Deprecated, 1549 or Prohibited. Optionally, the word can be followed by a "+" or 1550 "-". The use of "+" indicates that the requirement strength is 1551 likely to be increased in a future version of the specification. 1552 The use of "-" indicates that the requirement strength is likely 1553 to be decreased in a future version of the specification. Any 1554 identifiers registered for non-authenticated encryption algorithms 1555 or other algorithms that are otherwise unsuitable for direct use 1556 as JWS or JWE algorithms must be registered as "Prohibited". 1558 Change Controller: 1559 For Standards Track RFCs, state "IESG". For others, give the name 1560 of the responsible party. Other details (e.g., postal address, 1561 email address, home page URI) may also be included. 1563 Specification Document(s): 1564 Reference to the document(s) that specify the parameter, 1565 preferably including URI(s) that can be used to retrieve copies of 1566 the document(s). An indication of the relevant sections may also 1567 be included but is not required. 1569 7.1.2. Initial Registry Contents 1571 o Algorithm Name: "HS256" 1572 o Algorithm Description: HMAC using SHA-256 1573 o Algorithm Usage Location(s): "alg" 1574 o JOSE Implementation Requirements: Required 1575 o Change Controller: IESG 1576 o Specification Document(s): Section 3.1 of [[ this document ]] 1578 o Algorithm Name: "HS384" 1579 o Algorithm Description: HMAC using SHA-384 1580 o Algorithm Usage Location(s): "alg" 1581 o JOSE Implementation Requirements: Optional 1582 o Change Controller: IESG 1583 o Specification Document(s): Section 3.1 of [[ this document ]] 1585 o Algorithm Name: "HS512" 1586 o Algorithm Description: HMAC using SHA-512 1587 o Algorithm Usage Location(s): "alg" 1588 o JOSE Implementation Requirements: Optional 1589 o Change Controller: IESG 1590 o Specification Document(s): Section 3.1 of [[ this document ]] 1592 o Algorithm Name: "RS256" 1593 o Algorithm Description: RSASSA-PKCS-v1_5 using SHA-256 1594 o Algorithm Usage Location(s): "alg" 1595 o JOSE Implementation Requirements: Recommended 1596 o Change Controller: IESG 1597 o Specification Document(s): Section 3.1 of [[ this document ]] 1599 o Algorithm Name: "RS384" 1600 o Algorithm Description: RSASSA-PKCS-v1_5 using SHA-384 1601 o Algorithm Usage Location(s): "alg" 1602 o JOSE Implementation Requirements: Optional 1603 o Change Controller: IESG 1604 o Specification Document(s): Section 3.1 of [[ this document ]] 1606 o Algorithm Name: "RS512" 1607 o Algorithm Description: RSASSA-PKCS-v1_5 using SHA-512 1608 o Algorithm Usage Location(s): "alg" 1609 o JOSE Implementation Requirements: Optional 1610 o Change Controller: IESG 1611 o Specification Document(s): Section 3.1 of [[ this document ]] 1613 o Algorithm Name: "ES256" 1614 o Algorithm Description: ECDSA using P-256 and SHA-256 1615 o Algorithm Usage Location(s): "alg" 1616 o JOSE Implementation Requirements: Recommended+ 1617 o Change Controller: IESG 1618 o Specification Document(s): Section 3.1 of [[ this document ]] 1619 o Algorithm Name: "ES384" 1620 o Algorithm Description: ECDSA using P-384 and SHA-384 1621 o Algorithm Usage Location(s): "alg" 1622 o JOSE Implementation Requirements: Optional 1623 o Change Controller: IESG 1624 o Specification Document(s): Section 3.1 of [[ this document ]] 1626 o Algorithm Name: "ES512" 1627 o Algorithm Description: ECDSA using P-521 and SHA-512 1628 o Algorithm Usage Location(s): "alg" 1629 o JOSE Implementation Requirements: Optional 1630 o Change Controller: IESG 1631 o Specification Document(s): Section 3.1 of [[ this document ]] 1633 o Algorithm Name: "PS256" 1634 o Algorithm Description: RSASSA-PSS using SHA-256 and MGF1 with SHA- 1635 256 1636 o Algorithm Usage Location(s): "alg" 1637 o JOSE Implementation Requirements: Optional 1638 o Change Controller: IESG 1639 o Specification Document(s): Section 3.1 of [[ this document ]] 1641 o Algorithm Name: "PS384" 1642 o Algorithm Description: RSASSA-PSS using SHA-384 and MGF1 with SHA- 1643 384 1644 o Algorithm Usage Location(s): "alg" 1645 o JOSE Implementation Requirements: Optional 1646 o Change Controller: IESG 1647 o Specification Document(s): Section 3.1 of [[ this document ]] 1649 o Algorithm Name: "PS512" 1650 o Algorithm Description: RSASSA-PSS using SHA-512 and MGF1 with SHA- 1651 512 1652 o Algorithm Usage Location(s): "alg" 1653 o JOSE Implementation Requirements: Optional 1654 o Change Controller: IESG 1655 o Specification Document(s): Section 3.1 of [[ this document ]] 1657 o Algorithm Name: "none" 1658 o Algorithm Description: No digital signature or MAC performed 1659 o Algorithm Usage Location(s): "alg" 1660 o JOSE Implementation Requirements: Optional 1661 o Change Controller: IESG 1662 o Specification Document(s): Section 3.1 of [[ this document ]] 1664 o Algorithm Name: "RSA1_5" 1665 o Algorithm Description: RSAES-PKCS1-V1_5 1666 o Algorithm Usage Location(s): "alg" 1667 o JOSE Implementation Requirements: Required 1668 o Change Controller: IESG 1669 o Specification Document(s): Section 4.1 of [[ this document ]] 1671 o Algorithm Name: "RSA-OAEP" 1672 o Algorithm Description: RSAES using OAEP with default parameters 1673 o Algorithm Usage Location(s): "alg" 1674 o JOSE Implementation Requirements: Optional 1675 o Change Controller: IESG 1676 o Specification Document(s): Section 4.1 of [[ this document ]] 1678 o Algorithm Name: "A128KW" 1679 o Algorithm Description: AES Key Wrap using 128 bit key 1680 o Algorithm Usage Location(s): "alg" 1681 o JOSE Implementation Requirements: Recommended 1682 o Change Controller: IESG 1683 o Specification Document(s): Section 4.1 of [[ this document ]] 1685 o Algorithm Name: "A192KW" 1686 o Algorithm Description: AES Key Wrap using 192 bit key 1687 o Algorithm Usage Location(s): "alg" 1688 o JOSE Implementation Requirements: Optional 1689 o Change Controller: IESG 1690 o Specification Document(s): Section 4.1 of [[ this document ]] 1692 o Algorithm Name: "A256KW" 1693 o Algorithm Description: AES Key Wrap using 256 bit key 1694 o Algorithm Usage Location(s): "alg" 1695 o JOSE Implementation Requirements: Recommended 1696 o Change Controller: IESG 1697 o Specification Document(s): Section 4.1 of [[ this document ]] 1699 o Algorithm Name: "dir" 1700 o Algorithm Description: Direct use of a shared symmetric key 1701 o Algorithm Usage Location(s): "alg" 1702 o JOSE Implementation Requirements: Recommended 1703 o Change Controller: IESG 1704 o Specification Document(s): Section 4.1 of [[ this document ]] 1706 o Algorithm Name: "ECDH-ES" 1707 o Algorithm Description: ECDH-ES using Concat KDF 1708 o Algorithm Usage Location(s): "alg" 1709 o JOSE Implementation Requirements: Recommended+ 1710 o Change Controller: IESG 1711 o Specification Document(s): Section 4.1 of [[ this document ]] 1713 o Algorithm Name: "ECDH-ES+A128KW" 1714 o Algorithm Description: ECDH-ES using Concat KDF and "A128KW" 1715 wrapping 1716 o Algorithm Usage Location(s): "alg" 1717 o JOSE Implementation Requirements: Recommended 1718 o Change Controller: IESG 1719 o Specification Document(s): Section 4.1 of [[ this document ]] 1721 o Algorithm Name: "ECDH-ES+A192KW" 1722 o Algorithm Description: ECDH-ES using Concat KDF and "A192KW" 1723 wrapping 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: "ECDH-ES+A256KW" 1730 o Algorithm Description: ECDH-ES using Concat KDF and "A256KW" 1731 wrapping 1732 o Algorithm Usage Location(s): "alg" 1733 o JOSE Implementation Requirements: Recommended 1734 o Change Controller: IESG 1735 o Specification Document(s): Section 4.1 of [[ this document ]] 1737 o Algorithm Name: "A128GCMKW" 1738 o Algorithm Description: Key wrapping with AES GCM using 128 bit key 1739 o Algorithm Usage Location(s): "alg" 1740 o JOSE Implementation Requirements: Optional 1741 o Change Controller: IESG 1742 o Specification Document(s): Section 4.7 of [[ this document ]] 1744 o Algorithm Name: "A192GCMKW" 1745 o Algorithm Description: Key wrapping with AES GCM using 192 bit key 1746 o Algorithm Usage Location(s): "alg" 1747 o JOSE Implementation Requirements: Optional 1748 o Change Controller: IESG 1749 o Specification Document(s): Section 4.7 of [[ this document ]] 1751 o Algorithm Name: "A256GCMKW" 1752 o Algorithm Description: Key wrapping with AES GCM using 256 bit key 1753 o Algorithm Usage Location(s): "alg" 1754 o JOSE Implementation Requirements: Optional 1755 o Change Controller: IESG 1756 o Specification Document(s): Section 4.7 of [[ this document ]] 1757 o Algorithm Name: "PBES2-HS256+A128KW" 1758 o Algorithm Description: PBES2 with HMAC SHA-256 and "A128KW" 1759 wrapping 1760 o Algorithm Usage Location(s): "alg" 1761 o JOSE Implementation Requirements: Optional 1762 o Change Controller: IESG 1763 o Specification Document(s): Section 4.8 of [[ this document ]] 1765 o Algorithm Name: "PBES2-HS384+A192KW" 1766 o Algorithm Description: PBES2 with HMAC SHA-384 and "A192KW" 1767 wrapping 1768 o Algorithm Usage Location(s): "alg" 1769 o JOSE Implementation Requirements: Optional 1770 o Change Controller: IESG 1771 o Specification Document(s): Section 4.8 of [[ this document ]] 1773 o Algorithm Name: "PBES2-HS512+A256KW" 1774 o Algorithm Description: PBES2 with HMAC SHA-512 and "A256KW" 1775 wrapping 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.8 of [[ this document ]] 1781 o Algorithm Name: "A128CBC-HS256" 1782 o Algorithm Description: AES_128_CBC_HMAC_SHA_256 authenticated 1783 encryption algorithm 1784 o Algorithm Usage Location(s): "enc" 1785 o JOSE Implementation Requirements: Required 1786 o Change Controller: IESG 1787 o Specification Document(s): Section 5.1 of [[ this document ]] 1789 o Algorithm Name: "A192CBC-HS384" 1790 o Algorithm Description: AES_192_CBC_HMAC_SHA_384 authenticated 1791 encryption algorithm 1792 o Algorithm Usage Location(s): "enc" 1793 o JOSE Implementation Requirements: Optional 1794 o Change Controller: IESG 1795 o Specification Document(s): Section 5.1 of [[ this document ]] 1797 o Algorithm Name: "A256CBC-HS512" 1798 o Algorithm Description: AES_256_CBC_HMAC_SHA_512 authenticated 1799 encryption algorithm 1800 o Algorithm Usage Location(s): "enc" 1801 o JOSE Implementation Requirements: Required 1802 o Change Controller: IESG 1803 o Specification Document(s): Section 5.1 of [[ this document ]] 1805 o Algorithm Name: "A128GCM" 1806 o Algorithm Description: AES GCM using 128 bit key 1807 o Algorithm Usage Location(s): "enc" 1808 o JOSE Implementation Requirements: Recommended 1809 o Change Controller: IESG 1810 o Specification Document(s): Section 5.1 of [[ this document ]] 1812 o Algorithm Name: "A192GCM" 1813 o Algorithm Description: AES GCM using 192 bit key 1814 o Algorithm Usage Location(s): "enc" 1815 o JOSE Implementation Requirements: Optional 1816 o Change Controller: IESG 1817 o Specification Document(s): Section 5.1 of [[ this document ]] 1819 o Algorithm Name: "A256GCM" 1820 o Algorithm Description: AES GCM using 256 bit key 1821 o Algorithm Usage Location(s): "enc" 1822 o JOSE Implementation Requirements: Recommended 1823 o Change Controller: IESG 1824 o Specification Document(s): Section 5.1 of [[ this document ]] 1826 7.2. JWE Header Parameter Names Registration 1828 This specification registers the Header Parameter names defined in 1829 Section 4.6.1, Section 4.7.1, and Section 4.8.1 in the IANA JSON Web 1830 Signature and Encryption Header Parameters registry defined in [JWS]. 1832 7.2.1. Registry Contents 1834 o Header Parameter Name: "epk" 1835 o Header Parameter Description: Ephemeral Public Key 1836 o Header Parameter Usage Location(s): JWE 1837 o Change Controller: IESG 1838 o Specification Document(s): Section 4.6.1.1 of [[ this document ]] 1840 o Header Parameter Name: "apu" 1841 o Header Parameter Description: Agreement PartyUInfo 1842 o Header Parameter Usage Location(s): JWE 1843 o Change Controller: IESG 1844 o Specification Document(s): Section 4.6.1.2 of [[ this document ]] 1846 o Header Parameter Name: "apv" 1847 o Header Parameter Description: Agreement PartyVInfo 1848 o Header Parameter Usage Location(s): JWE 1849 o Change Controller: IESG 1850 o Specification Document(s): Section 4.6.1.3 of [[ this document ]] 1852 o Header Parameter Name: "iv" 1853 o Header Parameter Description: Initialization Vector 1854 o Header Parameter Usage Location(s): JWE 1855 o Change Controller: IESG 1856 o Specification Document(s): Section 4.7.1.1 of [[ this document ]] 1858 o Header Parameter Name: "tag" 1859 o Header Parameter Description: Authentication Tag 1860 o Header Parameter Usage Location(s): JWE 1861 o Change Controller: IESG 1862 o Specification Document(s): Section 4.7.1.2 of [[ this document ]] 1864 o Header Parameter Name: "p2s" 1865 o Header Parameter Description: PBES2 salt 1866 o Header Parameter Usage Location(s): JWE 1867 o Change Controller: IESG 1868 o Specification Document(s): Section 4.8.1.1 of [[ this document ]] 1870 o Header Parameter Name: "p2c" 1871 o Header Parameter Description: PBES2 count 1872 o Header Parameter Usage Location(s): JWE 1873 o Change Controller: IESG 1874 o Specification Document(s): Section 4.8.1.2 of [[ this document ]] 1876 7.3. JSON Web Encryption Compression Algorithms Registry 1878 This specification establishes the IANA JSON Web Encryption 1879 Compression Algorithms registry for JWE "zip" member values. The 1880 registry records the compression algorithm value and a reference to 1881 the specification that defines it. 1883 7.3.1. Registration Template 1885 Compression Algorithm Value: 1886 The name requested (e.g., "example"). Because a core goal of this 1887 specification is for the resulting representations to be compact, 1888 it is RECOMMENDED that the name be short -- not to exceed 8 1889 characters without a compelling reason to do so. This name is 1890 case-sensitive. Names may not match other registered names in a 1891 case-insensitive manner unless the Designated Expert(s) state that 1892 there is a compelling reason to allow an exception in this 1893 particular case. 1895 Compression Algorithm Description: 1896 Brief description of the compression algorithm (e.g., "Example 1897 description"). 1899 Change Controller: 1900 For Standards Track RFCs, state "IESG". For others, give the name 1901 of the responsible party. Other details (e.g., postal address, 1902 email address, home page URI) may also be included. 1904 Specification Document(s): 1905 Reference to the document(s) that specify the parameter, 1906 preferably including URI(s) that can be used to retrieve copies of 1907 the document(s). An indication of the relevant sections may also 1908 be included but is not required. 1910 7.3.2. Initial Registry Contents 1912 o Compression Algorithm Value: "DEF" 1913 o Compression Algorithm Description: DEFLATE 1914 o Change Controller: IESG 1915 o Specification Document(s): JSON Web Encryption (JWE) [JWE] 1917 7.4. JSON Web Key Types Registry 1919 This specification establishes the IANA JSON Web Key Types registry 1920 for values of the JWK "kty" (key type) parameter. The registry 1921 records the "kty" value, implementation requirements, and a reference 1922 to the specification that defines it. 1924 The implementation requirements of a key type MAY be changed over 1925 time by the Designated Experts(s) as the cryptographic landscape 1926 evolves, for instance, to change the status of a key type to 1927 Deprecated, or to change the status of a key type from Optional to 1928 Recommended+ or Required. Changes of implementation requirements are 1929 only permitted on a Specification Required basis, with the new 1930 specification defining the revised implementation requirements level. 1932 7.4.1. Registration Template 1934 "kty" Parameter Value: 1935 The name requested (e.g., "example"). Because a core goal of this 1936 specification is for the resulting representations to be compact, 1937 it is RECOMMENDED that the name be short -- not to exceed 8 1938 characters without a compelling reason to do so. This name is 1939 case-sensitive. Names may not match other registered names in a 1940 case-insensitive manner unless the Designated Expert(s) state that 1941 there is a compelling reason to allow an exception in this 1942 particular case. 1944 Key Type Description: 1945 Brief description of the Key Type (e.g., "Example description"). 1947 Change Controller: 1948 For Standards Track RFCs, state "IESG". For others, give the name 1949 of the responsible party. Other details (e.g., postal address, 1950 email address, home page URI) may also be included. 1952 JOSE Implementation Requirements: 1953 The key type implementation requirements for JWS and JWE, which 1954 must be one the words Required, Recommended, Optional, Deprecated, 1955 or Prohibited. Optionally, the word can be followed by a "+" or 1956 "-". The use of "+" indicates that the requirement strength is 1957 likely to be increased in a future version of the specification. 1958 The use of "-" indicates that the requirement strength is likely 1959 to be decreased in a future version of the specification. 1961 Specification Document(s): 1962 Reference to the document(s) that specify the parameter, 1963 preferably including URI(s) that can be used to retrieve copies of 1964 the document(s). An indication of the relevant sections may also 1965 be included but is not required. 1967 7.4.2. Initial Registry Contents 1969 This specification registers the values defined in Section 6.1. 1971 o "kty" Parameter Value: "EC" 1972 o Key Type Description: Elliptic Curve 1973 o JOSE Implementation Requirements: Recommended+ 1974 o Change Controller: IESG 1975 o Specification Document(s): Section 6.2 of [[ this document ]] 1977 o "kty" Parameter Value: "RSA" 1978 o Key Type Description: RSA 1979 o JOSE Implementation Requirements: Required 1980 o Change Controller: IESG 1981 o Specification Document(s): Section 6.3 of [[ this document ]] 1983 o "kty" Parameter Value: "oct" 1984 o Key Type Description: Octet sequence 1985 o JOSE Implementation Requirements: Required 1986 o Change Controller: IESG 1987 o Specification Document(s): Section 6.4 of [[ this document ]] 1989 7.5. JSON Web Key Parameters Registration 1991 This specification registers the parameter names defined in Sections 1992 6.2, 6.3, and 6.4 in the IANA JSON Web Key Parameters registry 1993 defined in [JWK]. 1995 7.5.1. Registry Contents 1997 o Parameter Name: "crv" 1998 o Parameter Description: Curve 1999 o Used with "kty" Value(s): "EC" 2000 o Parameter Information Class: Public 2001 o Change Controller: IESG 2002 o Specification Document(s): Section 6.2.1.1 of [[ this document ]] 2004 o Parameter Name: "x" 2005 o Parameter Description: X Coordinate 2006 o Used with "kty" Value(s): "EC" 2007 o Parameter Information Class: Public 2008 o Change Controller: IESG 2009 o Specification Document(s): Section 6.2.1.2 of [[ this document ]] 2011 o Parameter Name: "y" 2012 o Parameter Description: Y Coordinate 2013 o Used with "kty" Value(s): "EC" 2014 o Parameter Information Class: Public 2015 o Change Controller: IESG 2016 o Specification Document(s): Section 6.2.1.3 of [[ this document ]] 2018 o Parameter Name: "d" 2019 o Parameter Description: ECC Private Key 2020 o Used with "kty" Value(s): "EC" 2021 o Parameter Information Class: Private 2022 o Change Controller: IESG 2023 o Specification Document(s): Section 6.2.2.1 of [[ this document ]] 2025 o Parameter Name: "n" 2026 o Parameter Description: Modulus 2027 o Used with "kty" Value(s): "RSA" 2028 o Parameter Information Class: Public 2029 o Change Controller: IESG 2030 o Specification Document(s): Section 6.3.1.1 of [[ this document ]] 2032 o Parameter Name: "e" 2033 o Parameter Description: Exponent 2034 o Used with "kty" Value(s): "RSA" 2035 o Parameter Information Class: Public 2036 o Change Controller: IESG 2037 o Specification Document(s): Section 6.3.1.2 of [[ this document ]] 2039 o Parameter Name: "d" 2040 o Parameter Description: Private Exponent 2041 o Used with "kty" Value(s): "RSA" 2042 o Parameter Information Class: Private 2043 o Change Controller: IESG 2044 o Specification Document(s): Section 6.3.2.1 of [[ this document ]] 2046 o Parameter Name: "p" 2047 o Parameter Description: First Prime Factor 2048 o Used with "kty" Value(s): "RSA" 2049 o Parameter Information Class: Private 2050 o Change Controller: IESG 2051 o Specification Document(s): Section 6.3.2.2 of [[ this document ]] 2053 o Parameter Name: "q" 2054 o Parameter Description: Second Prime Factor 2055 o Used with "kty" Value(s): "RSA" 2056 o Parameter Information Class: Private 2057 o Change Controller: IESG 2058 o Specification Document(s): Section 6.3.2.3 of [[ this document ]] 2060 o Parameter Name: "dp" 2061 o Parameter Description: First Factor CRT Exponent 2062 o Used with "kty" Value(s): "RSA" 2063 o Parameter Information Class: Private 2064 o Change Controller: IESG 2065 o Specification Document(s): Section 6.3.2.4 of [[ this document ]] 2067 o Parameter Name: "dq" 2068 o Parameter Description: Second Factor CRT Exponent 2069 o Used with "kty" Value(s): "RSA" 2070 o Parameter Information Class: Private 2071 o Change Controller: IESG 2072 o Specification Document(s): Section 6.3.2.5 of [[ this document ]] 2074 o Parameter Name: "qi" 2075 o Parameter Description: First CRT Coefficient 2076 o Used with "kty" Value(s): "RSA" 2077 o Parameter Information Class: Private 2078 o Change Controller: IESG 2079 o Specification Document(s): Section 6.3.2.6 of [[ this document ]] 2080 o Parameter Name: "oth" 2081 o Parameter Description: Other Primes Info 2082 o Used with "kty" Value(s): "RSA" 2083 o Parameter Information Class: Private 2084 o Change Controller: IESG 2085 o Specification Document(s): Section 6.3.2.7 of [[ this document ]] 2087 o Parameter Name: "k" 2088 o Parameter Description: Key Value 2089 o Used with "kty" Value(s): "oct" 2090 o Parameter Information Class: Private 2091 o Change Controller: IESG 2092 o Specification Document(s): Section 6.4.1 of [[ this document ]] 2094 7.6. JSON Web Key Elliptic Curve Registry 2096 This specification establishes the IANA JSON Web Key Elliptic Curve 2097 registry for JWK "crv" member values. The registry records the curve 2098 name, implementation requirements, and a reference to the 2099 specification that defines it. This specification registers the 2100 parameter names defined in Section 6.2.1.1. 2102 The implementation requirements of a curve MAY be changed over time 2103 by the Designated Experts(s) as the cryptographic landscape evolves, 2104 for instance, to change the status of a curve to Deprecated, or to 2105 change the status of a curve from Optional to Recommended+ or 2106 Required. Changes of implementation requirements are only permitted 2107 on a Specification Required basis, with the new specification 2108 defining the revised implementation requirements level. 2110 7.6.1. Registration Template 2112 Curve Name: 2113 The name requested (e.g., "example"). Because a core goal of this 2114 specification is for the resulting representations to be compact, 2115 it is RECOMMENDED that the name be short -- not to exceed 8 2116 characters without a compelling reason to do so. This name is 2117 case-sensitive. Names may not match other registered names in a 2118 case-insensitive manner unless the Designated Expert(s) state that 2119 there is a compelling reason to allow an exception in this 2120 particular case. 2122 Curve Description: 2123 Brief description of the curve (e.g., "Example description"). 2125 JOSE Implementation Requirements: 2126 The curve implementation requirements for JWS and JWE, which must 2127 be one the words Required, Recommended, Optional, Deprecated, or 2128 Prohibited. Optionally, the word can be followed by a "+" or "-". 2129 The use of "+" indicates that the requirement strength is likely 2130 to be increased in a future version of the specification. The use 2131 of "-" indicates that the requirement strength is likely to be 2132 decreased in a future version of the specification. 2134 Change Controller: 2135 For Standards Track RFCs, state "IESG". For others, give the name 2136 of the responsible party. Other details (e.g., postal address, 2137 email address, home page URI) may also be included. 2139 Specification Document(s): 2140 Reference to the document(s) that specify the parameter, 2141 preferably including URI(s) that can be used to retrieve copies of 2142 the document(s). An indication of the relevant sections may also 2143 be included but is not required. 2145 7.6.2. Initial Registry Contents 2147 o Curve Name: "P-256" 2148 o Curve Description: P-256 curve 2149 o JOSE Implementation Requirements: Recommended+ 2150 o Change Controller: IESG 2151 o Specification Document(s): Section 6.2.1.1 of [[ this document ]] 2153 o Curve Name: "P-384" 2154 o Curve Description: P-384 curve 2155 o JOSE Implementation Requirements: Optional 2156 o Change Controller: IESG 2157 o Specification Document(s): Section 6.2.1.1 of [[ this document ]] 2159 o Curve Name: "P-521" 2160 o Curve Description: P-521 curve 2161 o JOSE Implementation Requirements: Optional 2162 o Change Controller: IESG 2163 o Specification Document(s): Section 6.2.1.1 of [[ this document ]] 2165 8. Security Considerations 2167 All of the security issues faced by any cryptographic application 2168 must be faced by a JWS/JWE/JWK agent. Among these issues are 2169 protecting the user's private and symmetric keys, preventing various 2170 attacks, and helping the user avoid mistakes such as inadvertently 2171 encrypting a message for the wrong recipient. The entire list of 2172 security considerations is beyond the scope of this document, but 2173 some significant considerations are listed here. 2175 The security considerations in [AES], [DSS], [JWE], [JWK], [JWS], 2176 [NIST.800-38A], [NIST.800-38D], [NIST.800-56A], [RFC2104], [RFC3394], 2177 [RFC3447], [RFC5116], [RFC6090], and [SHS] apply to this 2178 specification. 2180 Algorithms of matching strengths should be used together whenever 2181 possible. For instance, when AES Key Wrap is used with a given key 2182 size, using the same key size is recommended when AES GCM is also 2183 used. 2185 8.1. Algorithms and Key Sizes will be Deprecated 2187 Eventually the algorithms and/or key sizes currently described in 2188 this specification will no longer be considered sufficiently secure 2189 and will be deprecated. Therefore, implementers and deployments must 2190 be prepared for this eventuality. 2192 8.2. Key Lifetimes 2194 Many algorithms have associated security considerations related to 2195 key lifetimes and/or the number of times that a key may be used. 2196 Those security considerations continue to apply when using those 2197 algorithms with JOSE data structures. 2199 8.3. RSAES-PKCS1-v1_5 Security Considerations 2201 While Section 8 of RFC 3447 [RFC3447] explicitly calls for people not 2202 to adopt RSASSA-PKCS-v1_5 for new applications and instead requests 2203 that people transition to RSASSA-PSS, this specification does include 2204 RSASSA-PKCS-v1_5, for interoperability reasons, because it commonly 2205 implemented. 2207 Keys used with RSAES-PKCS1-v1_5 must follow the constraints in 2208 Section 7.2 of RFC 3447 [RFC3447]. In particular, keys with a low 2209 public key exponent value must not be used. 2211 8.4. AES GCM Security Considerations 2213 Keys used with AES GCM must follow the constraints in Section 8.3 of 2214 [NIST.800-38D], which states: "The total number of invocations of the 2215 authenticated encryption function shall not exceed 2^32, including 2216 all IV lengths and all instances of the authenticated encryption 2217 function with the given key". In accordance with this rule, AES GCM 2218 MUST NOT be used with the same key value more than 2^32 times. 2220 An Initialization Vector value MUST never be used multiple times with 2221 the same AES GCM key. One way to prevent this is to store a counter 2222 with the key and increment it with every use. The counter can also 2223 be used to prevent exceeding the 2^32 limit above. 2225 This security consideration does not apply to the composite AES-CBC 2226 HMAC SHA-2 or AES Key Wrap algorithms. 2228 8.5. Plaintext JWS Security Considerations 2230 Plaintext JWSs (JWSs that use the "alg" value "none") provide no 2231 integrity protection. Thus, they must only be used in contexts where 2232 the payload is secured by means other than a digital signature or MAC 2233 value, or need not be secured. 2235 Implementations that support plaintext JWS objects MUST NOT accept 2236 such objects as valid unless the application specifies that it is 2237 acceptable for a specific object to not be integrity-protected. 2238 Implementations MUST NOT accept plaintext JWS objects by default. 2239 For example, the "verify" method of a hypothetical JWS software 2240 library might have a Boolean "acceptUnsigned" parameter that 2241 indicates "none" is an acceptable "alg" value. As another example, 2242 the "verify" method might take a list of algorithms that are 2243 acceptable to the application as a parameter and would reject 2244 plaintext JWS values if "none" is not in that list. 2246 In order to mitigate downgrade attacks, applications MUST NOT signal 2247 acceptance of plaintext JWS objects at a global level, and SHOULD 2248 signal acceptance on a per-object basis. For example, suppose an 2249 application accepts JWS objects over two channels, (1) HTTP and (2) 2250 HTTPS with client authentication. It requires a JWS signature on 2251 objects received over HTTP, but accepts plaintext JWS objects over 2252 HTTPS. If the application were to globally indicate that "none" is 2253 acceptable, then an attacker could provide it with an unsigned object 2254 over HTTP and still have that object successfully validate. Instead, 2255 the application needs to indicate acceptance of "none" for each 2256 object received over HTTPS (e.g., by setting "acceptUnsigned" to 2257 "true" for the first hypothetical JWS software library above), but 2258 not for each object received over HTTP. 2260 8.6. Differences between Digital Signatures and MACs 2262 While in many cases, MACs and digital signatures can be used for 2263 integrity checking, there are some significant differences between 2264 the security properties that each of them provides. These need to be 2265 taken into consideration when designing protocols and selecting the 2266 algorithms to be used in protocols. 2268 Both signatures and MACs provide for integrity checking -- verifying 2269 that the message has not been modified since the integrity value was 2270 computed. However, MACs provide for origination identification only 2271 under specific circumstances. It can normally be assumed that a 2272 private key used for a signature is only in the hands of a single 2273 entity (although perhaps a distributed entity, in the case of 2274 replicated servers); however, a MAC key needs to be in the hands of 2275 all the entities that use it for integrity computation and checking. 2276 This means that origination can only be determined if a MAC key is 2277 known only to two entities and the receiver knows that it did not 2278 create the message. MAC validation cannot be used to prove 2279 origination to a third party. 2281 8.7. Denial of Service Attacks 2283 Receiving agents that validate signatures and sending agents that 2284 encrypt messages need to be cautious of cryptographic processing 2285 usage when validating signatures and encrypting messages using keys 2286 larger than those mandated in this specification. An attacker could 2287 send certificates with keys that would result in excessive 2288 cryptographic processing, for example, keys larger than those 2289 mandated in this specification, which could swamp the processing 2290 element. Agents that use such keys without first validating the 2291 certificate to a trust anchor are advised to have some sort of 2292 cryptographic resource management system to prevent such attacks. 2294 8.8. Reusing Key Material when Encrypting Keys 2296 It is NOT RECOMMENDED to reuse the same key material (Key Encryption 2297 Key, Content Encryption Key, Initialization Vector, etc.) to encrypt 2298 multiple JWK or JWK Set objects, or to encrypt the same JWK or JWK 2299 Set object multiple times. One suggestion for preventing re-use is 2300 to always generate a new set key material for each encryption 2301 operation, based on the considerations noted in this document as well 2302 as from [RFC4086]. 2304 8.9. Password Considerations 2306 Passwords are vulnerable to a number of attacks. To help mitigate 2307 some of these limitations, this document applies principles from 2308 [RFC2898] to derive cryptographic keys from user-supplied passwords. 2310 However, the strength of the password still has a significant impact. 2311 A high-entropy password has greater resistance to dictionary attacks. 2312 [NIST-800-63-1] contains guidelines for estimating password entropy, 2313 which can help applications and users generate stronger passwords. 2315 An ideal password is one that is as large as (or larger than) the 2316 derived key length. However, passwords larger than a certain 2317 algorithm-specific size are first hashed, which reduces an attacker's 2318 effective search space to the length of the hash algorithm. It is 2319 RECOMMENDED that a password used for "PBES2-HS256+A128KW" be no 2320 shorter than 16 octets and no longer than 128 octets and a password 2321 used for "PBES2-HS512+A256KW" be no shorter than 32 octets and no 2322 longer than 128 octets long. 2324 Still, care needs to be taken in where and how password-based 2325 encryption is used. These algorithms can still be susceptible to 2326 dictionary-based attacks if the iteration count is too small; this is 2327 of particular concern if these algorithms are used to protect data 2328 that an attacker can have indefinite number of attempts to circumvent 2329 the protection, such as protected data stored on a file system. 2331 9. Internationalization Considerations 2333 Passwords obtained from users are likely to require preparation and 2334 normalization to account for differences of octet sequences generated 2335 by different input devices, locales, etc. It is RECOMMENDED that 2336 applications to perform the steps outlined in 2337 [I-D.melnikov-precis-saslprepbis] to prepare a password supplied 2338 directly by a user before performing key derivation and encryption. 2340 10. References 2342 10.1. Normative References 2344 [AES] National Institute of Standards and Technology (NIST), 2345 "Advanced Encryption Standard (AES)", FIPS PUB 197, 2346 November 2001. 2348 [DSS] National Institute of Standards and Technology, "Digital 2349 Signature Standard (DSS)", FIPS PUB 186-4, July 2013. 2351 [I-D.ietf-json-rfc4627bis] 2352 Bray, T., "The JSON Data Interchange Format", 2353 draft-ietf-json-rfc4627bis-10 (work in progress), 2354 December 2013. 2356 [I-D.melnikov-precis-saslprepbis] 2357 Saint-Andre, P. and A. Melnikov, "Preparation and 2358 Comparison of Internationalized Strings Representing 2359 Simple User Names and Passwords", 2360 draft-melnikov-precis-saslprepbis-04 (work in progress), 2361 September 2012. 2363 [JWE] Jones, M., Rescorla, E., and J. Hildebrand, "JSON Web 2364 Encryption (JWE)", draft-ietf-jose-json-web-encryption 2365 (work in progress), January 2014. 2367 [JWK] Jones, M., "JSON Web Key (JWK)", 2368 draft-ietf-jose-json-web-key (work in progress), 2369 January 2014. 2371 [JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web 2372 Signature (JWS)", draft-ietf-jose-json-web-signature (work 2373 in progress), January 2014. 2375 [NIST.800-38A] 2376 National Institute of Standards and Technology (NIST), 2377 "Recommendation for Block Cipher Modes of Operation", 2378 NIST PUB 800-38A, December 2001. 2380 [NIST.800-38D] 2381 National Institute of Standards and Technology (NIST), 2382 "Recommendation for Block Cipher Modes of Operation: 2383 Galois/Counter Mode (GCM) and GMAC", NIST PUB 800-38D, 2384 December 2001. 2386 [NIST.800-56A] 2387 National Institute of Standards and Technology (NIST), 2388 "Recommendation for Pair-Wise Key Establishment Schemes 2389 Using Discrete Logarithm Cryptography", NIST Special 2390 Publication 800-56A, Revision 2, May 2013. 2392 [RFC2104] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed- 2393 Hashing for Message Authentication", RFC 2104, 2394 February 1997. 2396 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2397 Requirement Levels", BCP 14, RFC 2119, March 1997. 2399 [RFC2898] Kaliski, B., "PKCS #5: Password-Based Cryptography 2400 Specification Version 2.0", RFC 2898, September 2000. 2402 [RFC3394] Schaad, J. and R. Housley, "Advanced Encryption Standard 2403 (AES) Key Wrap Algorithm", RFC 3394, September 2002. 2405 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 2406 10646", STD 63, RFC 3629, November 2003. 2408 [RFC4086] Eastlake, D., Schiller, J., and S. Crocker, "Randomness 2409 Requirements for Security", BCP 106, RFC 4086, June 2005. 2411 [RFC4868] Kelly, S. and S. Frankel, "Using HMAC-SHA-256, HMAC-SHA- 2412 384, and HMAC-SHA-512 with IPsec", RFC 4868, May 2007. 2414 [RFC5116] McGrew, D., "An Interface and Algorithms for Authenticated 2415 Encryption", RFC 5116, January 2008. 2417 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 2418 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 2419 May 2008. 2421 [RFC6090] McGrew, D., Igoe, K., and M. Salter, "Fundamental Elliptic 2422 Curve Cryptography Algorithms", RFC 6090, February 2011. 2424 [SEC1] Standards for Efficient Cryptography Group, "SEC 1: 2425 Elliptic Curve Cryptography", May 2009. 2427 [SHS] National Institute of Standards and Technology, "Secure 2428 Hash Standard (SHS)", FIPS PUB 180-3, October 2008. 2430 [USASCII] American National Standards Institute, "Coded Character 2431 Set -- 7-bit American Standard Code for Information 2432 Interchange", ANSI X3.4, 1986. 2434 10.2. Informative References 2436 [CanvasApp] 2437 Facebook, "Canvas Applications", 2010. 2439 [I-D.mcgrew-aead-aes-cbc-hmac-sha2] 2440 McGrew, D., Foley, J., and K. Paterson, "Authenticated 2441 Encryption with AES-CBC and HMAC-SHA", 2442 draft-mcgrew-aead-aes-cbc-hmac-sha2-02 (work in progress), 2443 July 2013. 2445 [I-D.miller-jose-jwe-protected-jwk] 2446 Miller, M., "Using JavaScript Object Notation (JSON) Web 2447 Encryption (JWE) for Protecting JSON Web Key (JWK) 2448 Objects", draft-miller-jose-jwe-protected-jwk-02 (work in 2449 progress), June 2013. 2451 [I-D.rescorla-jsms] 2452 Rescorla, E. and J. Hildebrand, "JavaScript Message 2453 Security Format", draft-rescorla-jsms-00 (work in 2454 progress), March 2011. 2456 [JCA] Oracle, "Java Cryptography Architecture", 2013. 2458 [JSE] Bradley, J. and N. Sakimura (editor), "JSON Simple 2459 Encryption", September 2010. 2461 [JSS] Bradley, J. and N. Sakimura (editor), "JSON Simple Sign", 2462 September 2010. 2464 [MagicSignatures] 2465 Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic 2466 Signatures", January 2011. 2468 [NIST-800-63-1] 2469 National Institute of Standards and Technology (NIST), 2470 "Electronic Authentication Guideline", NIST 800-63-1, 2471 December 2011. 2473 [RFC2631] Rescorla, E., "Diffie-Hellman Key Agreement Method", 2474 RFC 2631, June 1999. 2476 [RFC3275] Eastlake, D., Reagle, J., and D. Solo, "(Extensible Markup 2477 Language) XML-Signature Syntax and Processing", RFC 3275, 2478 March 2002. 2480 [RFC3447] Jonsson, J. and B. Kaliski, "Public-Key Cryptography 2481 Standards (PKCS) #1: RSA Cryptography Specifications 2482 Version 2.1", RFC 3447, February 2003. 2484 [W3C.CR-xmldsig-core2-20120124] 2485 Cantor, S., Roessler, T., Eastlake, D., Yiu, K., Reagle, 2486 J., Solo, D., Datta, P., and F. Hirsch, "XML Signature 2487 Syntax and Processing Version 2.0", World Wide Web 2488 Consortium CR CR-xmldsig-core2-20120124, January 2012, 2489 . 2491 [W3C.CR-xmlenc-core1-20120313] 2492 Eastlake, D., Reagle, J., Roessler, T., and F. Hirsch, 2493 "XML Encryption Syntax and Processing Version 1.1", World 2494 Wide Web Consortium CR CR-xmlenc-core1-20120313, 2495 March 2012, 2496 . 2498 [W3C.REC-xmlenc-core-20021210] 2499 Eastlake, D. and J. Reagle, "XML Encryption Syntax and 2500 Processing", World Wide Web Consortium Recommendation REC- 2501 xmlenc-core-20021210, December 2002, 2502 . 2504 Appendix A. Algorithm Identifier Cross-Reference 2506 This appendix contains tables cross-referencing the cryptographic 2507 algorithm identifier values defined in this specification with the 2508 equivalent identifiers used by other standards and software packages. 2509 See XML DSIG [RFC3275], XML DSIG 2.0 [W3C.CR-xmldsig-core2-20120124], 2510 XML Encryption [W3C.REC-xmlenc-core-20021210], XML Encryption 1.1 2511 [W3C.CR-xmlenc-core1-20120313], and Java Cryptography Architecture 2512 [JCA] for more information about the names defined by those 2513 documents. 2515 A.1. Digital Signature/MAC Algorithm Identifier Cross-Reference 2517 This section contains a table cross-referencing the JWS digital 2518 signature and MAC "alg" (algorithm) values defined in this 2519 specification with the equivalent identifiers used by other standards 2520 and software packages. 2522 +-----+-------------------------------+--------------+--------------+ 2523 | JWS | XML DSIG | JCA | OID | 2524 +-----+-------------------------------+--------------+--------------+ 2525 | HS2 | http://www.w3.org/2001/04/xml | HmacSHA256 | 1.2.840.1135 | 2526 | 56 | dsig-more#hmac-sha256 | | 49.2.9 | 2527 | HS3 | http://www.w3.org/2001/04/xml | HmacSHA384 | 1.2.840.1135 | 2528 | 84 | dsig-more#hmac-sha384 | | 49.2.10 | 2529 | HS5 | http://www.w3.org/2001/04/xml | HmacSHA512 | 1.2.840.1135 | 2530 | 12 | dsig-more#hmac-sha512 | | 49.2.11 | 2531 | RS2 | http://www.w3.org/2001/04/xml | SHA256withRS | 1.2.840.1135 | 2532 | 56 | dsig-more#rsa-sha256 | A | 49.1.1.11 | 2533 | RS3 | http://www.w3.org/2001/04/xml | SHA384withRS | 1.2.840.1135 | 2534 | 84 | dsig-more#rsa-sha384 | A | 49.1.1.12 | 2535 | RS5 | http://www.w3.org/2001/04/xml | SHA512withRS | 1.2.840.1135 | 2536 | 12 | dsig-more#rsa-sha512 | A | 49.1.1.13 | 2537 | ES2 | http://www.w3.org/2001/04/xml | SHA256withEC | 1.2.840.1004 | 2538 | 56 | dsig-more#ecdsa-sha256 | DSA | 5.4.3.2 | 2539 | ES3 | http://www.w3.org/2001/04/xml | SHA384withEC | 1.2.840.1004 | 2540 | 84 | dsig-more#ecdsa-sha384 | DSA | 5.4.3.3 | 2541 | ES5 | http://www.w3.org/2001/04/xml | SHA512withEC | 1.2.840.1004 | 2542 | 12 | dsig-more#ecdsa-sha512 | DSA | 5.4.3.4 | 2543 | PS2 | http://www.w3.org/2007/05/xml | SHA256withRS | 1.2.840.1135 | 2544 | 56 | dsig-more#sha256-rsa-MGF1 | AandMGF1 | 49.1.1.10 | 2545 | PS3 | http://www.w3.org/2007/05/xml | SHA384withRS | 1.2.840.1135 | 2546 | 84 | dsig-more#sha384-rsa-MGF1 | AandMGF1 | 49.1.1.10 | 2547 | PS5 | http://www.w3.org/2007/05/xml | SHA512withRS | 1.2.840.1135 | 2548 | 12 | dsig-more#sha512-rsa-MGF1 | AandMGF1 | 49.1.1.10 | 2549 +-----+-------------------------------+--------------+--------------+ 2551 A.2. Key Management Algorithm Identifier Cross-Reference 2553 This section contains a table cross-referencing the JWE "alg" 2554 (algorithm) values defined in this specification with the equivalent 2555 identifiers used by other standards and software packages. 2557 +------+------------------------+--------------------+--------------+ 2558 | JWE | XML ENC | JCA | OID | 2559 +------+------------------------+--------------------+--------------+ 2560 | RSA1 | http://www.w3.org/2001 | RSA/ECB/PKCS1Paddi | 1.2.840.1135 | 2561 | _5 | /04/xmlenc#rsa-1_5 | ng | 49.1.1.1 | 2562 | RSA- | http://www.w3.org/2001 | RSA/ECB/OAEPWithSH | 1.2.840.1135 | 2563 | OAEP | /04/xmlenc#rsa-oaep-mg | A-1AndMGF1Padding | 49.1.1.7 | 2564 | | f1p | | | 2565 | ECDH | http://www.w3.org/2009 | | 1.3.132.1.12 | 2566 | -ES | /xmlenc11#ECDH-ES | | | 2567 | A128 | http://www.w3.org/2001 | | 2.16.840.1.1 | 2568 | KW | /04/xmlenc#kw-aes128 | | 01.3.4.1.5 | 2569 | A192 | http://www.w3.org/2001 | | 2.16.840.1.1 | 2570 | KW | /04/xmlenc#kw-aes192 | | 01.3.4.1.25 | 2571 | A256 | http://www.w3.org/2001 | | 2.16.840.1.1 | 2572 | KW | /04/xmlenc#kw-aes256 | | 01.3.4.1.45 | 2573 +------+------------------------+--------------------+--------------+ 2575 A.3. Content Encryption Algorithm Identifier Cross-Reference 2577 This section contains a table cross-referencing the JWE "enc" 2578 (encryption algorithm) values defined in this specification with the 2579 equivalent identifiers used by other standards and software packages. 2581 For the composite algorithms "A128CBC-HS256", "A192CBC-HS384", and 2582 "A256CBC-HS512", the corresponding AES CBC algorithm identifiers are 2583 listed. 2585 +---------+-------------------------+--------------+----------------+ 2586 | JWE | XML ENC | JCA | OID | 2587 +---------+-------------------------+--------------+----------------+ 2588 | A128CBC | http://www.w3.org/2001/ | AES/CBC/PKCS | 2.16.840.1.101 | 2589 | -HS256 | 04/xmlenc#aes128-cbc | 5Padding | .3.4.1.2 | 2590 | A192CBC | http://www.w3.org/2001/ | AES/CBC/PKCS | 2.16.840.1.101 | 2591 | -HS384 | 04/xmlenc#aes192-cbc | 5Padding | .3.4.1.22 | 2592 | A256CBC | http://www.w3.org/2001/ | AES/CBC/PKCS | 2.16.840.1.101 | 2593 | -HS512 | 04/xmlenc#aes256-cbc | 5Padding | .3.4.1.42 | 2594 | A128GCM | http://www.w3.org/2009/ | AES/GCM/NoPa | 2.16.840.1.101 | 2595 | | xmlenc11#aes128-gcm | dding | .3.4.1.6 | 2596 | A192GCM | http://www.w3.org/2009/ | AES/GCM/NoPa | 2.16.840.1.101 | 2597 | | xmlenc11#aes192-gcm | dding | .3.4.1.26 | 2598 | A256GCM | http://www.w3.org/2009/ | AES/GCM/NoPa | 2.16.840.1.101 | 2599 | | xmlenc11#aes256-gcm | dding | .3.4.1.46 | 2600 +---------+-------------------------+--------------+----------------+ 2602 Appendix B. Test Cases for AES_CBC_HMAC_SHA2 Algorithms 2604 The following test cases can be used to validate implementations of 2605 the AES_CBC_HMAC_SHA2 algorithms defined in Section 5.2. They are 2606 also intended to correspond to test cases that may appear in a future 2607 version of [I-D.mcgrew-aead-aes-cbc-hmac-sha2], demonstrating that 2608 the cryptographic computations performed are the same. 2610 The variable names are those defined in Section 5.2. All values are 2611 hexadecimal. 2613 B.1. Test Cases for AES_128_CBC_HMAC_SHA_256 2615 AES_128_CBC_HMAC_SHA_256 2617 K = 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 2618 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 2620 MAC_KEY = 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 2622 ENC_KEY = 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 2624 P = 41 20 63 69 70 68 65 72 20 73 79 73 74 65 6d 20 2625 6d 75 73 74 20 6e 6f 74 20 62 65 20 72 65 71 75 2626 69 72 65 64 20 74 6f 20 62 65 20 73 65 63 72 65 2627 74 2c 20 61 6e 64 20 69 74 20 6d 75 73 74 20 62 2628 65 20 61 62 6c 65 20 74 6f 20 66 61 6c 6c 20 69 2629 6e 74 6f 20 74 68 65 20 68 61 6e 64 73 20 6f 66 2630 20 74 68 65 20 65 6e 65 6d 79 20 77 69 74 68 6f 2631 75 74 20 69 6e 63 6f 6e 76 65 6e 69 65 6e 63 65 2633 IV = 1a f3 8c 2d c2 b9 6f fd d8 66 94 09 23 41 bc 04 2635 A = 54 68 65 20 73 65 63 6f 6e 64 20 70 72 69 6e 63 2636 69 70 6c 65 20 6f 66 20 41 75 67 75 73 74 65 20 2637 4b 65 72 63 6b 68 6f 66 66 73 2639 AL = 00 00 00 00 00 00 01 50 2641 E = c8 0e df a3 2d df 39 d5 ef 00 c0 b4 68 83 42 79 2642 a2 e4 6a 1b 80 49 f7 92 f7 6b fe 54 b9 03 a9 c9 2643 a9 4a c9 b4 7a d2 65 5c 5f 10 f9 ae f7 14 27 e2 2644 fc 6f 9b 3f 39 9a 22 14 89 f1 63 62 c7 03 23 36 2645 09 d4 5a c6 98 64 e3 32 1c f8 29 35 ac 40 96 c8 2646 6e 13 33 14 c5 40 19 e8 ca 79 80 df a4 b9 cf 1b 2647 38 4c 48 6f 3a 54 c5 10 78 15 8e e5 d7 9d e5 9f 2648 bd 34 d8 48 b3 d6 95 50 a6 76 46 34 44 27 ad e5 2649 4b 88 51 ff b5 98 f7 f8 00 74 b9 47 3c 82 e2 db 2651 M = 65 2c 3f a3 6b 0a 7c 5b 32 19 fa b3 a3 0b c1 c4 2652 e6 e5 45 82 47 65 15 f0 ad 9f 75 a2 b7 1c 73 ef 2654 T = 65 2c 3f a3 6b 0a 7c 5b 32 19 fa b3 a3 0b c1 c4 2656 B.2. Test Cases for AES_192_CBC_HMAC_SHA_384 2658 K = 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 2659 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 2660 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 2662 MAC_KEY = 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 2663 10 11 12 13 14 15 16 17 2665 ENC_KEY = 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 2666 28 29 2a 2b 2c 2d 2e 2f 2668 P = 41 20 63 69 70 68 65 72 20 73 79 73 74 65 6d 20 2669 6d 75 73 74 20 6e 6f 74 20 62 65 20 72 65 71 75 2670 69 72 65 64 20 74 6f 20 62 65 20 73 65 63 72 65 2671 74 2c 20 61 6e 64 20 69 74 20 6d 75 73 74 20 62 2672 65 20 61 62 6c 65 20 74 6f 20 66 61 6c 6c 20 69 2673 6e 74 6f 20 74 68 65 20 68 61 6e 64 73 20 6f 66 2674 20 74 68 65 20 65 6e 65 6d 79 20 77 69 74 68 6f 2675 75 74 20 69 6e 63 6f 6e 76 65 6e 69 65 6e 63 65 2677 IV = 1a f3 8c 2d c2 b9 6f fd d8 66 94 09 23 41 bc 04 2679 A = 54 68 65 20 73 65 63 6f 6e 64 20 70 72 69 6e 63 2680 69 70 6c 65 20 6f 66 20 41 75 67 75 73 74 65 20 2681 4b 65 72 63 6b 68 6f 66 66 73 2683 AL = 00 00 00 00 00 00 01 50 2685 E = ea 65 da 6b 59 e6 1e db 41 9b e6 2d 19 71 2a e5 2686 d3 03 ee b5 00 52 d0 df d6 69 7f 77 22 4c 8e db 2687 00 0d 27 9b dc 14 c1 07 26 54 bd 30 94 42 30 c6 2688 57 be d4 ca 0c 9f 4a 84 66 f2 2b 22 6d 17 46 21 2689 4b f8 cf c2 40 0a dd 9f 51 26 e4 79 66 3f c9 0b 2690 3b ed 78 7a 2f 0f fc bf 39 04 be 2a 64 1d 5c 21 2691 05 bf e5 91 ba e2 3b 1d 74 49 e5 32 ee f6 0a 9a 2692 c8 bb 6c 6b 01 d3 5d 49 78 7b cd 57 ef 48 49 27 2693 f2 80 ad c9 1a c0 c4 e7 9c 7b 11 ef c6 00 54 e3 2695 M = 84 90 ac 0e 58 94 9b fe 51 87 5d 73 3f 93 ac 20 2696 75 16 80 39 cc c7 33 d7 45 94 f8 86 b3 fa af d4 2697 86 f2 5c 71 31 e3 28 1e 36 c7 a2 d1 30 af de 57 2699 T = 84 90 ac 0e 58 94 9b fe 51 87 5d 73 3f 93 ac 20 2700 75 16 80 39 cc c7 33 d7 2702 B.3. Test Cases for AES_256_CBC_HMAC_SHA_512 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 2707 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 2709 MAC_KEY = 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 2710 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 2712 ENC_KEY = 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 2713 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 2715 P = 41 20 63 69 70 68 65 72 20 73 79 73 74 65 6d 20 2716 6d 75 73 74 20 6e 6f 74 20 62 65 20 72 65 71 75 2717 69 72 65 64 20 74 6f 20 62 65 20 73 65 63 72 65 2718 74 2c 20 61 6e 64 20 69 74 20 6d 75 73 74 20 62 2719 65 20 61 62 6c 65 20 74 6f 20 66 61 6c 6c 20 69 2720 6e 74 6f 20 74 68 65 20 68 61 6e 64 73 20 6f 66 2721 20 74 68 65 20 65 6e 65 6d 79 20 77 69 74 68 6f 2722 75 74 20 69 6e 63 6f 6e 76 65 6e 69 65 6e 63 65 2724 IV = 1a f3 8c 2d c2 b9 6f fd d8 66 94 09 23 41 bc 04 2726 A = 54 68 65 20 73 65 63 6f 6e 64 20 70 72 69 6e 63 2727 69 70 6c 65 20 6f 66 20 41 75 67 75 73 74 65 20 2728 4b 65 72 63 6b 68 6f 66 66 73 2730 AL = 00 00 00 00 00 00 01 50 2732 E = 4a ff aa ad b7 8c 31 c5 da 4b 1b 59 0d 10 ff bd 2733 3d d8 d5 d3 02 42 35 26 91 2d a0 37 ec bc c7 bd 2734 82 2c 30 1d d6 7c 37 3b cc b5 84 ad 3e 92 79 c2 2735 e6 d1 2a 13 74 b7 7f 07 75 53 df 82 94 10 44 6b 2736 36 eb d9 70 66 29 6a e6 42 7e a7 5c 2e 08 46 a1 2737 1a 09 cc f5 37 0d c8 0b fe cb ad 28 c7 3f 09 b3 2738 a3 b7 5e 66 2a 25 94 41 0a e4 96 b2 e2 e6 60 9e 2739 31 e6 e0 2c c8 37 f0 53 d2 1f 37 ff 4f 51 95 0b 2740 be 26 38 d0 9d d7 a4 93 09 30 80 6d 07 03 b1 f6 2742 M = 4d d3 b4 c0 88 a7 f4 5c 21 68 39 64 5b 20 12 bf 2743 2e 62 69 a8 c5 6a 81 6d bc 1b 26 77 61 95 5b c5 2744 fd 30 a5 65 c6 16 ff b2 f3 64 ba ec e6 8f c4 07 2745 53 bc fc 02 5d de 36 93 75 4a a1 f5 c3 37 3b 9c 2747 T = 4d d3 b4 c0 88 a7 f4 5c 21 68 39 64 5b 20 12 bf 2748 2e 62 69 a8 c5 6a 81 6d bc 1b 26 77 61 95 5b c5 2750 Appendix C. Example ECDH-ES Key Agreement Computation 2752 This example uses ECDH-ES Key Agreement and the Concat KDF to derive 2753 the Content Encryption Key (CEK) in the manner described in 2754 Section 4.6. In this example, the ECDH-ES Direct Key Agreement mode 2755 ("alg" value "ECDH-ES") is used to produce an agreed upon key for AES 2756 GCM with a 128 bit key ("enc" value "A128GCM"). 2758 In this example, a sender Alice is encrypting content to a recipient 2759 Bob. The sender (Alice) generates an ephemeral key for the key 2760 agreement computation. Alice's ephemeral key (in JWK format) used 2761 for the key agreement computation in this example (including the 2762 private part) is: 2764 {"kty":"EC", 2765 "crv":"P-256", 2766 "x":"gI0GAILBdu7T53akrFmMyGcsF3n5dO7MmwNBHKW5SV0", 2767 "y":"SLW_xSffzlPWrHEVI30DHM_4egVwt3NQqeUD7nMFpps", 2768 "d":"0_NxaRPUMQoAJt50Gz8YiTr8gRTwyEaCumd-MToTmIo" 2769 } 2771 The recipient's (Bob's) key (in JWK format) used for the key 2772 agreement computation in this example (including the private part) 2773 is: 2775 {"kty":"EC", 2776 "crv":"P-256", 2777 "x":"weNJy2HscCSM6AEDTDg04biOvhFhyyWvOHQfeF_PxMQ", 2778 "y":"e8lnCO-AlStT-NJVX-crhB7QRYhiix03illJOVAOyck", 2779 "d":"VEmDZpDXXK8p8N0Cndsxs924q6nS1RXFASRl6BfUqdw" 2780 } 2782 Header Parameter values used in this example are as follows. In this 2783 example, the "apu" (agreement PartyUInfo) parameter value is the 2784 base64url encoding of the UTF-8 string "Alice" and the "apv" 2785 (agreement PartyVInfo) parameter value is the base64url encoding of 2786 the UTF-8 string "Bob". The "epk" parameter is used to communicate 2787 the sender's (Alice's) ephemeral public key value to the recipient 2788 (Bob). 2790 {"alg":"ECDH-ES", 2791 "enc":"A128GCM", 2792 "apu":"QWxpY2U", 2793 "apv":"Qm9i", 2794 "epk": 2795 {"kty":"EC", 2796 "crv":"P-256", 2797 "x":"gI0GAILBdu7T53akrFmMyGcsF3n5dO7MmwNBHKW5SV0", 2798 "y":"SLW_xSffzlPWrHEVI30DHM_4egVwt3NQqeUD7nMFpps" 2799 } 2800 } 2802 The resulting Concat KDF [NIST.800-56A] parameter values are: 2804 Z This is set to the ECDH-ES key agreement output. (This value is 2805 often not directly exposed by libraries, due to NIST security 2806 requirements, and only serves as an input to a KDF.) In this 2807 example, Z is the octet sequence: 2808 [158, 86, 217, 29, 129, 113, 53, 211, 114, 131, 66, 131, 191, 132, 2809 38, 156, 251, 49, 110, 163, 218, 128, 106, 72, 246, 218, 167, 121, 2810 140, 254, 144, 196]. 2812 keydatalen This value is 128 - the number of bits in the desired 2813 output key (because "A128GCM" uses a 128 bit key). 2815 AlgorithmID This is set to the octets representing the 32 bit big 2816 endian value 7 - [0, 0, 0, 7] - the number of octets in the 2817 AlgorithmID content "A128GCM", followed, by the octets 2818 representing the UTF-8 string "A128GCM" - [65, 49, 50, 56, 71, 67, 2819 77]. 2821 PartyUInfo This is set to the octets representing the 32 bit big 2822 endian value 5 - [0, 0, 0, 5] - the number of octets in the 2823 PartyUInfo content "Alice", followed, by the octets representing 2824 the UTF-8 string "Alice" - [65, 108, 105, 99, 101]. 2826 PartyVInfo This is set to the octets representing the 32 bit big 2827 endian value 3 - [0, 0, 0, 3] - the number of octets in the 2828 PartyUInfo content "Bob", followed, by the octets representing the 2829 UTF-8 string "Bob" - [66, 111, 98]. 2831 SuppPubInfo This is set to the octets representing the 32 bit big 2832 endian value 128 - [0, 0, 0, 128] - the keydatalen value. 2834 SuppPrivInfo This is set to the empty octet sequence. 2836 Concatenating the parameters AlgorithmID through SuppPubInfo results 2837 in an OtherInfo value of: 2839 [0, 0, 0, 7, 65, 49, 50, 56, 71, 67, 77, 0, 0, 0, 5, 65, 108, 105, 2840 99, 101, 0, 0, 0, 3, 66, 111, 98, 0, 0, 0, 128] 2842 Concatenating the round number 1 ([0, 0, 0, 1]), Z, and the OtherInfo 2843 value results in the Concat KDF round 1 hash input of: 2844 [0, 0, 0, 1, 2845 158, 86, 217, 29, 129, 113, 53, 211, 114, 131, 66, 131, 191, 132, 38, 2846 156, 251, 49, 110, 163, 218, 128, 106, 72, 246, 218, 167, 121, 140, 2847 254, 144, 196, 2848 0, 0, 0, 7, 65, 49, 50, 56, 71, 67, 77, 0, 0, 0, 5, 65, 108, 105, 99, 2849 101, 0, 0, 0, 3, 66, 111, 98, 0, 0, 0, 128] 2851 The resulting derived key, which is the first 128 bits of the round 1 2852 hash output is: 2853 [86, 170, 141, 234, 248, 35, 109, 32, 92, 34, 40, 205, 113, 167, 16, 2854 26] 2856 The base64url encoded representation of this derived key is: 2858 VqqN6vgjbSBcIijNcacQGg 2860 Appendix D. Acknowledgements 2862 Solutions for signing and encrypting JSON content were previously 2863 explored by Magic Signatures [MagicSignatures], JSON Simple Sign 2864 [JSS], Canvas Applications [CanvasApp], JSON Simple Encryption [JSE], 2865 and JavaScript Message Security Format [I-D.rescorla-jsms], all of 2866 which influenced this draft. 2868 The Authenticated Encryption with AES-CBC and HMAC-SHA 2869 [I-D.mcgrew-aead-aes-cbc-hmac-sha2] specification, upon which the 2870 AES_CBC_HMAC_SHA2 algorithms are based, was written by David A. 2871 McGrew and Kenny Paterson. The test cases for AES_CBC_HMAC_SHA2 are 2872 based upon those for [I-D.mcgrew-aead-aes-cbc-hmac-sha2] by John 2873 Foley. 2875 Matt Miller wrote Using JavaScript Object Notation (JSON) Web 2876 Encryption (JWE) for Protecting JSON Web Key (JWK) Objects 2877 [I-D.miller-jose-jwe-protected-jwk], which the password-based 2878 encryption content of this draft is based upon. 2880 This specification is the work of the JOSE Working Group, which 2881 includes dozens of active and dedicated participants. In particular, 2882 the following individuals contributed ideas, feedback, and wording 2883 that influenced this specification: 2885 Dirk Balfanz, Richard Barnes, John Bradley, Brian Campbell, Breno de 2886 Medeiros, Vladimir Dzhuvinov, Yaron Y. Goland, Dick Hardt, Jeff 2887 Hodges, Edmund Jay, James Manger, Matt Miller, Tony Nadalin, Axel 2888 Nennker, John Panzer, Emmanuel Raviart, Nat Sakimura, Jim Schaad, 2889 Hannes Tschofenig, and Sean Turner. 2891 Jim Schaad and Karen O'Donoghue chaired the JOSE working group and 2892 Sean Turner and Stephen Farrell served as Security area directors 2893 during the creation of this specification. 2895 Appendix E. Document History 2897 [[ to be removed by the RFC Editor before publication as an RFC ]] 2899 -20 2901 o Replaced references to RFC 4627 with draft-ietf-json-rfc4627bis, 2902 addressing issue #90. 2904 -19 2906 o Used tables to show the correspondence between algorithm 2907 identifiers and algorithm descriptions and parameters in the 2908 algorithm definition sections, addressing issue #183. 2910 o Changed the "Implementation Requirements" registry field names to 2911 "JOSE Implementation Requirements" to make it clear that these 2912 implementation requirements apply only to JWS and JWE 2913 implementations. 2915 -18 2917 o Changes to address editorial and minor issues #129, #134, #135, 2918 #158, #161, #185, #186, and #187. 2920 o Added and used Description registry fields. 2922 -17 2924 o Explicitly named all the logical components of a JWS and JWE and 2925 defined the processing rules and serializations in terms of those 2926 components, addressing issues #60, #61, and #62. 2928 o Removed processing steps in algorithm definitions that duplicated 2929 processing steps in JWS or JWE, addressing issue #56. 2931 o Replaced verbose repetitive phases such as "base64url encode the 2932 octets of the UTF-8 representation of X" with mathematical 2933 notation such as "BASE64URL(UTF8(X))". 2935 o Terms used in multiple documents are now defined in one place and 2936 incorporated by reference. Some lightly used or obvious terms 2937 were also removed. This addresses issue #58. 2939 o Changes to address minor issue #53. 2941 -16 2943 o Added a DataLen prefix to the AlgorithmID value in the Concat KDF 2944 computation. 2946 o Added OIDs for encryption algorithms, additional signature 2947 algorithm OIDs, and additional XML DSIG/ENC URIs in the algorithm 2948 cross-reference tables. 2950 o Changes to address editorial and minor issues #28, #36, #39, #52, 2951 #53, #55, #127, #128, #136, #137, #141, #150, #151, #152, and 2952 #155. 2954 -15 2956 o Changed statements about rejecting JWSs to statements about 2957 validation failing, addressing issue #35. 2959 o Stated that changes of implementation requirements are only 2960 permitted on a Specification Required basis, addressing issue #38. 2962 o Made "oct" a required key type, addressing issue #40. 2964 o Updated the example ECDH-ES key agreement values. 2966 o Changes to address editorial and minor issues #34, #37, #49, #63, 2967 #123, #124, #125, #130, #132, #133, #138, #139, #140, #142, #143, 2968 #144, #145, #148, #149, #150, and #162. 2970 -14 2972 o Removed "PBKDF2" key type and added "p2s" and "p2c" header 2973 parameters for use with the PBES2 algorithms. 2975 o Made the RSA private key parameters that are there to enable 2976 optimizations be RECOMMENDED rather than REQUIRED. 2978 o Added algorithm identifiers for AES algorithms using 192 bit keys 2979 and for RSASSA-PSS using HMAC SHA-384. 2981 o Added security considerations about key lifetimes, addressing 2982 issue #18. 2984 o Added an example ECDH-ES key agreement computation. 2986 -13 2988 o Added key encryption with AES GCM as specified in 2989 draft-jones-jose-aes-gcm-key-wrap-01, addressing issue #13. 2991 o Added security considerations text limiting the number of times 2992 that an AES GCM key can be used for key encryption or direct 2993 encryption, per Section 8.3 of NIST SP 800-38D, addressing issue 2994 #28. 2996 o Added password-based key encryption as specified in 2997 draft-miller-jose-jwe-protected-jwk-02. 2999 -12 3001 o In the Direct Key Agreement case, the Concat KDF AlgorithmID is 3002 set to the octets of the UTF-8 representation of the "enc" header 3003 parameter value. 3005 o Restored the "apv" (agreement PartyVInfo) parameter. 3007 o Moved the "epk", "apu", and "apv" Header Parameter definitions to 3008 be with the algorithm descriptions that use them. 3010 o Changed terminology from "block encryption" to "content 3011 encryption". 3013 -11 3015 o Removed the Encrypted Key value from the AAD computation since it 3016 is already effectively integrity protected by the encryption 3017 process. The AAD value now only contains the representation of 3018 the JWE Encrypted Header. 3020 o Removed "apv" (agreement PartyVInfo) since it is no longer used. 3022 o Added more information about the use of PartyUInfo during key 3023 agreement. 3025 o Use the keydatalen as the SuppPubInfo value for the Concat KDF 3026 when doing key agreement, as RFC 2631 does. 3028 o Added algorithm identifiers for RSASSA-PSS with SHA-256 and SHA- 3029 512. 3031 o Added a Parameter Information Class value to the JSON Web Key 3032 Parameters registry, which registers whether the parameter conveys 3033 public or private information. 3035 -10 3037 o Changed the JWE processing rules for multiple recipients so that a 3038 single AAD value contains the header parameters and encrypted key 3039 values for all the recipients, enabling AES GCM to be safely used 3040 for multiple recipients. 3042 -09 3044 o Expanded the scope of the JWK parameters to include private and 3045 symmetric key representations, as specified by 3046 draft-jones-jose-json-private-and-symmetric-key-00. 3048 o Changed term "JWS Secured Input" to "JWS Signing Input". 3050 o Changed from using the term "byte" to "octet" when referring to 8 3051 bit values. 3053 o Specified that AES Key Wrap uses the default initial value 3054 specified in Section 2.2.3.1 of RFC 3394. This addressed issue 3055 #19. 3057 o Added Key Management Mode definitions to terminology section and 3058 used the defined terms to provide clearer key management 3059 instructions. This addressed issue #5. 3061 o Replaced "A128CBC+HS256" and "A256CBC+HS512" with "A128CBC-HS256" 3062 and "A256CBC-HS512". The new algorithms perform the same 3063 cryptographic computations as [I-D.mcgrew-aead-aes-cbc-hmac-sha2], 3064 but with the Initialization Vector and Authentication Tag values 3065 remaining separate from the Ciphertext value in the output 3066 representation. Also deleted the header parameters "epu" 3067 (encryption PartyUInfo) and "epv" (encryption PartyVInfo), since 3068 they are no longer used. 3070 o Changed from using the term "Integrity Value" to "Authentication 3071 Tag". 3073 -08 3074 o Changed the name of the JWK key type parameter from "alg" to 3075 "kty". 3077 o Replaced uses of the term "AEAD" with "Authenticated Encryption", 3078 since the term AEAD in the RFC 5116 sense implied the use of a 3079 particular data representation, rather than just referring to the 3080 class of algorithms that perform authenticated encryption with 3081 associated data. 3083 o Applied editorial improvements suggested by Jeff Hodges. Many of 3084 these simplified the terminology used. 3086 o Added seriesInfo information to Internet Draft references. 3088 -07 3090 o Added a data length prefix to PartyUInfo and PartyVInfo values. 3092 o Changed the name of the JWK RSA modulus parameter from "mod" to 3093 "n" and the name of the JWK RSA exponent parameter from "xpo" to 3094 "e", so that the identifiers are the same as those used in RFC 3095 3447. 3097 o Made several local editorial changes to clean up loose ends left 3098 over from to the decision to only support block encryption methods 3099 providing integrity. 3101 -06 3103 o Removed the "int" and "kdf" parameters and defined the new 3104 composite Authenticated Encryption algorithms "A128CBC+HS256" and 3105 "A256CBC+HS512" to replace the former uses of AES CBC, which 3106 required the use of separate integrity and key derivation 3107 functions. 3109 o Included additional values in the Concat KDF calculation -- the 3110 desired output size and the algorithm value, and optionally 3111 PartyUInfo and PartyVInfo values. Added the optional header 3112 parameters "apu" (agreement PartyUInfo), "apv" (agreement 3113 PartyVInfo), "epu" (encryption PartyUInfo), and "epv" (encryption 3114 PartyVInfo). 3116 o Changed the name of the JWK RSA exponent parameter from "exp" to 3117 "xpo" so as to allow the potential use of the name "exp" for a 3118 future extension that might define an expiration parameter for 3119 keys. (The "exp" name is already used for this purpose in the JWT 3120 specification.) 3122 o Applied changes made by the RFC Editor to RFC 6749's registry 3123 language to this specification. 3125 -05 3127 o Support both direct encryption using a shared or agreed upon 3128 symmetric key, and the use of a shared or agreed upon symmetric 3129 key to key wrap the CMK. Specifically, added the "alg" values 3130 "dir", "ECDH-ES+A128KW", and "ECDH-ES+A256KW" to finish filling in 3131 this set of capabilities. 3133 o Updated open issues. 3135 -04 3137 o Added text requiring that any leading zero bytes be retained in 3138 base64url encoded key value representations for fixed-length 3139 values. 3141 o Added this language to Registration Templates: "This name is case 3142 sensitive. Names that match other registered names in a case 3143 insensitive manner SHOULD NOT be accepted." 3145 o Described additional open issues. 3147 o Applied editorial suggestions. 3149 -03 3151 o Always use a 128 bit "authentication tag" size for AES GCM, 3152 regardless of the key size. 3154 o Specified that use of a 128 bit IV is REQUIRED with AES CBC. It 3155 was previously RECOMMENDED. 3157 o Removed key size language for ECDSA algorithms, since the key size 3158 is implied by the algorithm being used. 3160 o Stated that the "int" key size must be the same as the hash output 3161 size (and not larger, as was previously allowed) so that its size 3162 is defined for key generation purposes. 3164 o Added the "kdf" (key derivation function) header parameter to 3165 provide crypto agility for key derivation. The default KDF 3166 remains the Concat KDF with the SHA-256 digest function. 3168 o Clarified that the "mod" and "exp" values are unsigned. 3170 o Added Implementation Requirements columns to algorithm tables and 3171 Implementation Requirements entries to algorithm registries. 3173 o Changed AES Key Wrap to RECOMMENDED. 3175 o Moved registries JSON Web Signature and Encryption Header 3176 Parameters and JSON Web Signature and Encryption Type Values to 3177 the JWS specification. 3179 o Moved JSON Web Key Parameters registry to the JWK specification. 3181 o Changed registration requirements from RFC Required to 3182 Specification Required with Expert Review. 3184 o Added Registration Template sections for defined registries. 3186 o Added Registry Contents sections to populate registry values. 3188 o No longer say "the UTF-8 representation of the JWS Secured Input 3189 (which is the same as the ASCII representation)". Just call it 3190 "the ASCII representation of the JWS Secured Input". 3192 o Added "Collision Resistant Namespace" to the terminology section. 3194 o Numerous editorial improvements. 3196 -02 3198 o For AES GCM, use the "additional authenticated data" parameter to 3199 provide integrity for the header, encrypted key, and ciphertext 3200 and use the resulting "authentication tag" value as the JWE 3201 Authentication Tag. 3203 o Defined minimum required key sizes for algorithms without 3204 specified key sizes. 3206 o Defined KDF output key sizes. 3208 o Specified the use of PKCS #5 padding with AES CBC. 3210 o Generalized text to allow key agreement to be employed as an 3211 alternative to key wrapping or key encryption. 3213 o Clarified that ECDH-ES is a key agreement algorithm. 3215 o Required implementation of AES-128-KW and AES-256-KW. 3217 o Removed the use of "A128GCM" and "A256GCM" for key wrapping. 3219 o Removed "A512KW" since it turns out that it's not a standard 3220 algorithm. 3222 o Clarified the relationship between "typ" header parameter values 3223 and MIME types. 3225 o Generalized language to refer to Message Authentication Codes 3226 (MACs) rather than Hash-based Message Authentication Codes (HMACs) 3227 unless in a context specific to HMAC algorithms. 3229 o Established registries: JSON Web Signature and Encryption Header 3230 Parameters, JSON Web Signature and Encryption Algorithms, JSON Web 3231 Signature and Encryption "typ" Values, JSON Web Key Parameters, 3232 and JSON Web Key Algorithm Families. 3234 o Moved algorithm-specific definitions from JWK to JWA. 3236 o Reformatted to give each member definition its own section 3237 heading. 3239 -01 3241 o Moved definition of "alg":"none" for JWSs here from the JWT 3242 specification since this functionality is likely to be useful in 3243 more contexts that just for JWTs. 3245 o Added Advanced Encryption Standard (AES) Key Wrap Algorithm using 3246 512 bit keys ("A512KW"). 3248 o Added text "Alternatively, the Encoded JWS Signature MAY be 3249 base64url decoded to produce the JWS Signature and this value can 3250 be compared with the computed HMAC value, as this comparison 3251 produces the same result as comparing the encoded values". 3253 o Corrected the Magic Signatures reference. 3255 o Made other editorial improvements suggested by JOSE working group 3256 participants. 3258 -00 3260 o Created the initial IETF draft based upon 3261 draft-jones-json-web-signature-04 and 3262 draft-jones-json-web-encryption-02 with no normative changes. 3264 o Changed terminology to no longer call both digital signatures and 3265 HMACs "signatures". 3267 Author's Address 3269 Michael B. Jones 3270 Microsoft 3272 Email: mbj@microsoft.com 3273 URI: http://self-issued.info/