idnits 2.17.1 draft-ietf-jose-json-web-key-16.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 15, 2013) is 3847 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'ECMAScript' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.X690.1994' ** Downref: Normative reference to an Historic RFC: RFC 1421 ** Obsolete normative reference: RFC 2818 (Obsoleted by RFC 9110) ** Obsolete normative reference: RFC 4627 (Obsoleted by RFC 7158, RFC 7159) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) -- Obsolete informational reference (is this intentional?): RFC 3447 (Obsoleted by RFC 8017) Summary: 5 errors (**), 0 flaws (~~), 1 warning (==), 5 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 September 15, 2013 5 Expires: March 19, 2014 7 JSON Web Key (JWK) 8 draft-ietf-jose-json-web-key-16 10 Abstract 12 A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data 13 structure that represents a cryptographic key. This specification 14 also defines a JSON Web Key Set (JWK Set) JSON data structure for 15 representing a set of JWKs. Cryptographic algorithms and identifiers 16 for use with this specification are described in the separate JSON 17 Web Algorithms (JWA) specification and IANA registries defined by 18 that specification. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on March 19, 2014. 37 Copyright Notice 39 Copyright (c) 2013 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 4 56 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 3. JSON Web Key (JWK) Format . . . . . . . . . . . . . . . . . . 5 58 3.1. "kty" (Key Type) Parameter . . . . . . . . . . . . . . . . 5 59 3.2. "use" (Key Use) Parameter . . . . . . . . . . . . . . . . 6 60 3.3. "alg" (Algorithm) Parameter . . . . . . . . . . . . . . . 6 61 3.4. "kid" (Key ID) Parameter . . . . . . . . . . . . . . . . . 6 62 3.5. "x5u" (X.509 URL) Parameter . . . . . . . . . . . . . . . 6 63 3.6. "x5t" (X.509 Certificate SHA-1 Thumbprint) Parameter . . . 7 64 3.7. "x5c" (X.509 Certificate Chain) Parameter . . . . . . . . 7 65 4. JSON Web Key Set (JWK Set) Format . . . . . . . . . . . . . . 7 66 4.1. "keys" Parameter . . . . . . . . . . . . . . . . . . . . . 8 67 5. String Comparison Rules . . . . . . . . . . . . . . . . . . . 8 68 6. Encrypted JWK and Encrypted JWK Set Formats . . . . . . . . . 8 69 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 70 7.1. JSON Web Key Parameters Registry . . . . . . . . . . . . . 10 71 7.1.1. Registration Template . . . . . . . . . . . . . . . . 10 72 7.1.2. Initial Registry Contents . . . . . . . . . . . . . . 11 73 7.2. JSON Web Key Use Registry . . . . . . . . . . . . . . . . 11 74 7.2.1. Registration Template . . . . . . . . . . . . . . . . 12 75 7.2.2. Initial Registry Contents . . . . . . . . . . . . . . 12 76 7.3. JSON Web Key Set Parameters Registry . . . . . . . . . . . 12 77 7.3.1. Registration Template . . . . . . . . . . . . . . . . 12 78 7.3.2. Initial Registry Contents . . . . . . . . . . . . . . 13 79 7.4. JSON Web Signature and Encryption Type Values 80 Registration . . . . . . . . . . . . . . . . . . . . . . . 13 81 7.4.1. Registry Contents . . . . . . . . . . . . . . . . . . 13 82 7.5. Media Type Registration . . . . . . . . . . . . . . . . . 14 83 7.5.1. Registry Contents . . . . . . . . . . . . . . . . . . 14 84 8. Security Considerations . . . . . . . . . . . . . . . . . . . 15 85 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 86 9.1. Normative References . . . . . . . . . . . . . . . . . . . 15 87 9.2. Informative References . . . . . . . . . . . . . . . . . . 17 88 Appendix A. Example JSON Web Key Sets . . . . . . . . . . . . . . 17 89 A.1. Example Public Keys . . . . . . . . . . . . . . . . . . . 17 90 A.2. Example Private Keys . . . . . . . . . . . . . . . . . . . 18 91 A.3. Example Symmetric Keys . . . . . . . . . . . . . . . . . . 20 92 Appendix B. Example Use of "x5c" (X.509 Certificate Chain) 93 Parameter . . . . . . . . . . . . . . . . . . . . . . 20 94 Appendix C. Acknowledgements . . . . . . . . . . . . . . . . . . 21 95 Appendix D. Document History . . . . . . . . . . . . . . . . . . 22 96 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 25 98 1. Introduction 100 A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) [RFC4627] 101 data structure that represents a cryptographic key. This 102 specification also defines a JSON Web Key Set (JWK Set) JSON data 103 structure for representing a set of JWKs. Cryptographic algorithms 104 and identifiers for use with this specification are described in the 105 separate JSON Web Algorithms (JWA) [JWA] specification and IANA 106 registries defined by that specification. 108 Goals for this specification do not include representing certificate 109 chains, representing certified keys, and replacing X.509 110 certificates. 112 JWKs and JWK Sets are used in the JSON Web Signature (JWS) [JWS] and 113 JSON Web Encryption (JWE) [JWE] specifications. 115 Names defined by this specification are short because a core goal is 116 for the resulting representations to be compact. 118 1.1. Notational Conventions 120 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 121 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 122 document are to be interpreted as described in Key words for use in 123 RFCs to Indicate Requirement Levels [RFC2119]. If these words are 124 used without being spelled in uppercase then they are to be 125 interpreted with their normal natural language meanings. 127 2. Terminology 129 JSON Web Key (JWK) A JSON object that represents a cryptographic 130 key. 132 JSON Web Key Set (JWK Set) A JSON object that contains an array of 133 JWKs as the value of its "keys" member. 135 Base64url Encoding Base64 encoding using the URL- and filename-safe 136 character set defined in Section 5 of RFC 4648 [RFC4648], with all 137 trailing '=' characters omitted (as permitted by Section 3.2). 138 (See Appendix C of [JWS] for notes on implementing base64url 139 encoding without padding.) 141 Collision Resistant Name A name in a namespace that enables names to 142 be allocated in a manner such that they are highly unlikely to 143 collide with other names. Examples of collision resistant 144 namespaces include: Domain Names, Object Identifiers (OIDs) as 145 defined in the ITU-T X.660 and X.670 Recommendation series, and 146 Universally Unique IDentifiers (UUIDs) [RFC4122]. When using an 147 administratively delegated namespace, the definer of a name needs 148 to take reasonable precautions to ensure they are in control of 149 the portion of the namespace they use to define the name. 151 3. JSON Web Key (JWK) Format 153 A JSON Web Key (JWK) is a JSON object containing specific members, as 154 specified below. Those members that are common to multiple key types 155 are defined below. 157 In addition to the common parameters, each JWK will have members that 158 are specific to the kind of key being represented. These members 159 represent the parameters of the key. Section 5 of the JSON Web 160 Algorithms (JWA) [JWA] specification defines multiple kinds of 161 cryptographic keys and their associated members. 163 The member names within a JWK MUST be unique; recipients MUST either 164 reject JWKs with duplicate member names or use a JSON parser that 165 returns only the lexically last duplicate member name, as specified 166 in Section 15.12 (The JSON Object) of ECMAScript 5.1 [ECMAScript]. 168 Additional members MAY be present in the JWK. If not understood by 169 implementations encountering them, they MUST be ignored. Member 170 names used for representing key parameters for different kinds of 171 keys need not be distinct. Any new member name SHOULD either be 172 registered in the IANA JSON Web Key Parameters registry defined in 173 Section 7.1 or be a value that contains a Collision Resistant Name. 175 3.1. "kty" (Key Type) Parameter 177 The "kty" (key type) member identifies the cryptographic algorithm 178 family used with the key. "kty" values SHOULD either be registered in 179 the IANA JSON Web Key Types registry defined in [JWA] or be a value 180 that contains a Collision Resistant Name. The "kty" value is a case 181 sensitive string. Use of this member is REQUIRED. 183 A list of defined "kty" values can be found in the IANA JSON Web Key 184 Types registry defined in [JWA]; the initial contents of this 185 registry are the values defined in Section 5.1 of the JSON Web 186 Algorithms (JWA) [JWA] specification. 188 Additional members used with these "kty" values can be found in the 189 IANA JSON Web Key Parameters registry defined in Section 7.1; the 190 initial contents of this registry are the values defined in Sections 191 5.2 and 5.3 of the JSON Web Algorithms (JWA) [JWA] specification. 193 3.2. "use" (Key Use) Parameter 195 The "use" (key use) member identifies the intended use of the key. 196 Values defined by this specification are: 198 o "sig" (signature or MAC operation) 200 o "enc" (encryption) 202 Other values MAY be used. Key Use values can be registered in the 203 IANA JSON Web Key Use registry defined in Section 7.2. The "use" 204 value is a case sensitive string. A "use" member SHOULD be present, 205 unless the application uses another means or convention to determine 206 the intended key usage. 208 When a key is used to wrap another key and a key use designation for 209 the first key is desired, the "enc" (encryption) key use value SHOULD 210 be used, since key wrapping is a kind of encryption. (The "alg" 211 member can be used to specify the particular kind of encryption to be 212 performed, when desired.) 214 3.3. "alg" (Algorithm) Parameter 216 The "alg" (algorithm) member identifies the algorithm intended for 217 use with the key. The values used SHOULD either be registered in the 218 IANA JSON Web Signature and Encryption Algorithms registry defined in 219 [JWA] or be a value that contains a Collision Resistant Name. Use of 220 this member is OPTIONAL. 222 3.4. "kid" (Key ID) Parameter 224 The "kid" (key ID) member can be used to match a specific key. This 225 can be used, for instance, to choose among a set of keys within a JWK 226 Set during key rollover. The interpretation of the "kid" value is 227 unspecified. When "kid" values are used within a JWK Set, different 228 keys within the JWK Set SHOULD use distinct "kid" values. The "kid" 229 value is a case sensitive string. Use of this member is OPTIONAL. 231 When used with JWS or JWE, the "kid" value can be used to match a JWS 232 or JWE "kid" header parameter value. 234 3.5. "x5u" (X.509 URL) Parameter 236 The "x5u" (X.509 URL) member is a URI [RFC3986] that refers to a 237 resource for an X.509 public key certificate or certificate chain 238 [RFC5280]. The identified resource MUST provide a representation of 239 the certificate or certificate chain that conforms to RFC 5280 240 [RFC5280] in PEM encoded form [RFC1421]. The key in the first 241 certificate MUST match the bare public key represented by other 242 members of the JWK. The protocol used to acquire the resource MUST 243 provide integrity protection; an HTTP GET request to retrieve the 244 certificate MUST use TLS [RFC2818] [RFC5246]; the identity of the 245 server MUST be validated, as per Section 3.1 of HTTP Over TLS 246 [RFC2818]. Use of this member is OPTIONAL. 248 3.6. "x5t" (X.509 Certificate SHA-1 Thumbprint) Parameter 250 The "x5t" (X.509 Certificate SHA-1 Thumbprint) member is a base64url 251 encoded SHA-1 thumbprint (a.k.a. digest) of the DER encoding of an 252 X.509 certificate [RFC5280]. The key in the certificate MUST match 253 the bare public key represented by other members of the JWK. Use of 254 this member is OPTIONAL. 256 If, in the future, certificate thumbprints need to be computed using 257 hash functions other than SHA-1, it is suggested that additional 258 related JWK parameters be defined for that purpose. For example, it 259 is suggested that a new "x5t#S256" (X.509 Certificate Thumbprint 260 using SHA-256) JWK parameter could be defined by registering it in 261 the IANA JSON Web Key Parameters registry defined in Section 7.1. 263 3.7. "x5c" (X.509 Certificate Chain) Parameter 265 The "x5c" (X.509 Certificate Chain) member contains a chain of one or 266 more PKIX certificates [RFC5280]. The certificate chain is 267 represented as a JSON array of certificate value strings. Each 268 string in the array is a base64 encoded ([RFC4648] Section 4 -- not 269 base64url encoded) DER [ITU.X690.1994] PKIX certificate value. The 270 PKIX certificate containing the key value MUST be the first 271 certificate. This MAY be followed by additional certificates, with 272 each subsequent certificate being the one used to certify the 273 previous one. The key in the first certificate MUST match the bare 274 public key represented by other members of the JWK. Use of this 275 member is OPTIONAL. 277 4. JSON Web Key Set (JWK Set) Format 279 A JSON Web Key Set (JWK Set) is a JSON object that contains an array 280 of JWK values as the value of its "keys" member. 282 The member names within a JWK Set MUST be unique; recipients MUST 283 either reject JWK Sets with duplicate member names or use a JSON 284 parser that returns only the lexically last duplicate member name, as 285 specified in Section 15.12 (The JSON Object) of ECMAScript 5.1 286 [ECMAScript]. 288 Additional members MAY be present in the JWK Set. If not understood 289 by implementations encountering them, they MUST be ignored. 290 Parameters for representing additional properties of JWK Sets SHOULD 291 either be registered in the IANA JSON Web Key Set Parameters registry 292 defined in Section 7.3 or be a value that contains a Collision 293 Resistant Name. 295 Implementations SHOULD ignore JWKs within a JWK Set that use "kty" 296 (key type) values that are not understood by them. 298 4.1. "keys" Parameter 300 The value of the "keys" member is an array of JWK values. By 301 default, the order of the JWK values within the array does not imply 302 an order of preference among them, although applications of JWK Sets 303 can choose to assign a meaning to the order for their purposes, if 304 desired. Use of this member is REQUIRED. 306 5. String Comparison Rules 308 Processing a JWK inevitably requires comparing known strings to 309 values in JSON objects. For example, in checking what the key type 310 is, the Unicode string encoding "kty" will be checked against the 311 member names in the JWK to see if there is a matching name. 313 Comparisons between JSON strings and other Unicode strings MUST be 314 performed by comparing Unicode code points without normalization as 315 specified in the String Comparison Rules in Section 5.3 of [JWS]. 317 6. Encrypted JWK and Encrypted JWK Set Formats 319 JWKs containing non-public key material will need to be encrypted in 320 some contexts to prevent the disclosure of private or symmetric key 321 values to unintended parties. The use of an Encrypted JWK, which is 322 a JWE with a JWK as its plaintext value, is RECOMMENED for this 323 purpose. The processing of Encrypted JWKs is identical to the 324 processing of other JWEs. A "cty" (content type) header parameter 325 value of "JWK" MUST be used to indicate that the content of the JWE 326 is a JWK, unless the application knows that the encrypted content is 327 a JWK by another means or convention. 329 JWK Sets containing non-public key material will similarly need to be 330 encrypted. The use of an Encrypted JWK Set, which is a JWE with a 331 JWK Set as its plaintext value, is RECOMMENED for this purpose. The 332 processing of Encrypted JWK Sets is identical to the processing of 333 other JWEs. A "cty" (content type) header parameter value of 334 "JWK-SET" MUST be used to indicate that the content of the JWE is a 335 JWK Set, unless the application knows that the encrypted content is a 336 JWK Set by another means or convention. 338 7. IANA Considerations 340 The following registration procedure is used for all the registries 341 established by this specification. 343 Values are registered with a Specification Required [RFC5226] after a 344 two-week review period on the [TBD]@ietf.org mailing list, on the 345 advice of one or more Designated Experts. However, to allow for the 346 allocation of values prior to publication, the Designated Expert(s) 347 may approve registration once they are satisfied that such a 348 specification will be published. 350 Registration requests must be sent to the [TBD]@ietf.org mailing list 351 for review and comment, with an appropriate subject (e.g., "Request 352 for access token type: example"). [[ Note to the RFC Editor: The name 353 of the mailing list should be determined in consultation with the 354 IESG and IANA. Suggested name: jose-reg-review. ]] 356 Within the review period, the Designated Expert(s) will either 357 approve or deny the registration request, communicating this decision 358 to the review list and IANA. Denials should include an explanation 359 and, if applicable, suggestions as to how to make the request 360 successful. Registration requests that are undetermined for a period 361 longer than 21 days can be brought to the IESG's attention (using the 362 iesg@iesg.org mailing list) for resolution. 364 Criteria that should be applied by the Designated Expert(s) includes 365 determining whether the proposed registration duplicates existing 366 functionality, determining whether it is likely to be of general 367 applicability or whether it is useful only for a single application, 368 and whether the registration makes sense. 370 IANA must only accept registry updates from the Designated Expert(s) 371 and should direct all requests for registration to the review mailing 372 list. 374 It is suggested that multiple Designated Experts be appointed who are 375 able to represent the perspectives of different applications using 376 this specification, in order to enable broadly-informed review of 377 registration decisions. In cases where a registration decision could 378 be perceived as creating a conflict of interest for a particular 379 Expert, that Expert should defer to the judgment of the other 380 Expert(s). 382 7.1. JSON Web Key Parameters Registry 384 This specification establishes the IANA JSON Web Key Parameters 385 registry for JWK parameter names. The registry records the parameter 386 name, the key type(s) that the parameter is used with, and a 387 reference to the specification that defines it. It also records 388 whether the parameter conveys public or private information. This 389 specification registers the parameter names defined in Section 3. 390 The same JWK parameter name may be registered multiple times, 391 provided that duplicate parameter registrations are only for key type 392 specific JWK parameters; in this case, the meaning of the duplicate 393 parameter name is disambiguated by the "kty" value of the JWK 394 containing it. 396 7.1.1. Registration Template 398 Parameter Name: 399 The name requested (e.g., "example"). Because a core goal of this 400 specification is for the resulting representations to be compact, 401 it is RECOMMENDED that the name be short -- not to exceed 8 402 characters without a compelling reason to do so. This name is 403 case sensitive. Names may not match other registered names in a 404 case insensitive manner unless the Designated Expert(s) state that 405 there is a compelling reason to allow an exception in this 406 particular case. 408 Used with "kty" Value(s): 409 The key type parameter value(s) that the parameter name is to be 410 used with, or the value "*" if the parameter value is used with 411 all key types. 413 Parameter Information Class: 414 Registers whether the parameter conveys public or private 415 information. Its value must be one the words Public or Private. 417 Change Controller: 418 For Standards Track RFCs, state "IESG". For others, give the name 419 of the responsible party. Other details (e.g., postal address, 420 email address, home page URI) may also be included. 422 Specification Document(s): 423 Reference to the document(s) that specify the parameter, 424 preferably including URI(s) that can be used to retrieve copies of 425 the document(s). An indication of the relevant sections may also 426 be included but is not required. 428 7.1.2. Initial Registry Contents 430 o Parameter Name: "kty" 431 o Used with "kty" Value(s): * 432 o Parameter Information Class: Public 433 o Change Controller: IESG 434 o Specification Document(s): Section 3.1 of [[ this document ]] 436 o Parameter Name: "use" 437 o Used with "kty" Value(s): * 438 o Parameter Information Class: Public 439 o Change Controller: IESG 440 o Specification Document(s): Section 3.2 of [[ this document ]] 442 o Parameter Name: "alg" 443 o Used with "kty" Value(s): * 444 o Parameter Information Class: Public 445 o Change Controller: IESG 446 o Specification Document(s): Section 3.3 of [[ this document ]] 448 o Parameter Name: "kid" 449 o Used with "kty" Value(s): * 450 o Parameter Information Class: Public 451 o Change Controller: IESG 452 o Specification Document(s): Section 3.4 of [[ this document ]] 454 o Parameter Name: "x5u" 455 o Used with "kty" Value(s): * 456 o Parameter Information Class: Public 457 o Change Controller: IESG 458 o Specification Document(s): Section 3.5 of [[ this document ]] 460 o Parameter Name: "x5t" 461 o Used with "kty" Value(s): * 462 o Parameter Information Class: Public 463 o Change Controller: IESG 464 o Specification Document(s): Section 3.6 of [[ this document ]] 466 o Parameter Name: "x5c" 467 o Used with "kty" Value(s): * 468 o Parameter Information Class: Public 469 o Change Controller: IESG 470 o Specification Document(s): Section 3.7 of [[ this document ]] 472 7.2. JSON Web Key Use Registry 474 This specification establishes the IANA JSON Web Key Use registry for 475 JWK "use" member values. The registry records the key use value and 476 a reference to the specification that defines it. This specification 477 registers the parameter names defined in Section 3.2. 479 7.2.1. Registration Template 481 Use Member Value: 482 The name requested (e.g., "example"). Because a core goal of this 483 specification is for the resulting representations to be compact, 484 it is RECOMMENDED that the name be short -- not to exceed 8 485 characters without a compelling reason to do so. This name is 486 case sensitive. Names may not match other registered names in a 487 case insensitive manner unless the Designated Expert(s) state that 488 there is a compelling reason to allow an exception in this 489 particular case. 491 Change Controller: 492 For Standards Track RFCs, state "IESG". For others, give the name 493 of the responsible party. Other details (e.g., postal address, 494 email address, home page URI) may also be included. 496 Specification Document(s): 497 Reference to the document(s) that specify the parameter, 498 preferably including URI(s) that can be used to retrieve copies of 499 the document(s). An indication of the relevant sections may also 500 be included but is not required. 502 7.2.2. Initial Registry Contents 504 o Use Member Value: "sig" 505 o Change Controller: IESG 506 o Specification Document(s): Section 3.2 of [[ this document ]] 508 o Use Member Value: "enc" 509 o Change Controller: IESG 510 o Specification Document(s): Section 3.2 of [[ this document ]] 512 7.3. JSON Web Key Set Parameters Registry 514 This specification establishes the IANA JSON Web Key Set Parameters 515 registry for JWK Set parameter names. The registry records the 516 parameter name and a reference to the specification that defines it. 517 This specification registers the parameter names defined in 518 Section 4. 520 7.3.1. Registration Template 521 Parameter Name: 522 The name requested (e.g., "example"). Because a core goal of this 523 specification is for the resulting representations to be compact, 524 it is RECOMMENDED that the name be short -- not to exceed 8 525 characters without a compelling reason to do so. This name is 526 case sensitive. Names may not match other registered names in a 527 case insensitive manner unless the Designated Expert(s) state that 528 there is a compelling reason to allow an exception in this 529 particular case. 531 Change Controller: 532 For Standards Track RFCs, state "IESG". For others, give the name 533 of the responsible party. Other details (e.g., postal address, 534 email address, home page URI) may also be included. 536 Specification Document(s): 537 Reference to the document(s) that specify the parameter, 538 preferably including URI(s) that can be used to retrieve copies of 539 the document(s). An indication of the relevant sections may also 540 be included but is not required. 542 7.3.2. Initial Registry Contents 544 o Parameter Name: "keys" 545 o Change Controller: IESG 546 o Specification Document(s): Section 4.1 of [[ this document ]] 548 7.4. JSON Web Signature and Encryption Type Values Registration 550 7.4.1. Registry Contents 552 This specification registers the "JWK" and "JWK-SET" type values in 553 the IANA JSON Web Signature and Encryption Type Values registry 554 defined in [JWS], which can be used to indicate, respectively, that 555 the content is a JWK or a JWK Set. 557 o "typ" Header Parameter Value: "JWK" 558 o Abbreviation for MIME Type: application/jwk+json 559 o Change Controller: IESG 560 o Specification Document(s): Section 3 of [[ this document ]] 562 o "typ" Header Parameter Value: "JWK-SET" 563 o Abbreviation for MIME Type: application/jwk-set+json 564 o Change Controller: IESG 565 o Specification Document(s): Section 4 of [[ this document ]] 567 7.5. Media Type Registration 569 7.5.1. Registry Contents 571 This specification registers the "application/jwk+json" and 572 "application/jwk-set+json" Media Types [RFC2046] in the MIME Media 573 Types registry [IANA.MediaTypes], which can be used to indicate, 574 respectively, that the content is a JWK or a JWK Set. 576 o Type Name: application 577 o Subtype Name: jwk+json 578 o Required Parameters: n/a 579 o Optional Parameters: n/a 580 o Encoding considerations: 8bit; application/jwk+json values are 581 represented as JSON object; UTF-8 encoding SHOULD be employed for 582 the JSON object. 583 o Security Considerations: See the Security Considerations section 584 of [[ this document ]] 585 o Interoperability Considerations: n/a 586 o Published Specification: [[ this document ]] 587 o Applications that use this media type: TBD 588 o Additional Information: Magic number(s): n/a, File extension(s): 589 n/a, Macintosh file type code(s): n/a 590 o Person & email address to contact for further information: Michael 591 B. Jones, mbj@microsoft.com 592 o Intended Usage: COMMON 593 o Restrictions on Usage: none 594 o Author: Michael B. Jones, mbj@microsoft.com 595 o Change Controller: IESG 597 o Type Name: application 598 o Subtype Name: jwk-set+json 599 o Required Parameters: n/a 600 o Optional Parameters: n/a 601 o Encoding considerations: 8bit; application/jwk-set+json values are 602 represented as a JSON Object; UTF-8 encoding SHOULD be employed 603 for the JSON object. 604 o Security Considerations: See the Security Considerations section 605 of [[ this document ]] 606 o Interoperability Considerations: n/a 607 o Published Specification: [[ this document ]] 608 o Applications that use this media type: TBD 609 o Additional Information: Magic number(s): n/a, File extension(s): 610 n/a, Macintosh file type code(s): n/a 611 o Person & email address to contact for further information: Michael 612 B. Jones, mbj@microsoft.com 614 o Intended Usage: COMMON 615 o Restrictions on Usage: none 616 o Author: Michael B. Jones, mbj@microsoft.com 617 o Change Controller: IESG 619 8. Security Considerations 621 All of the security issues faced by any cryptographic application 622 must be faced by a JWS/JWE/JWK agent. Among these issues are 623 protecting the user's private and symmetric keys, preventing various 624 attacks, and helping the user avoid mistakes such as inadvertently 625 encrypting a message for the wrong recipient. The entire list of 626 security considerations is beyond the scope of this document, but 627 some significant considerations are listed here. 629 A key is no more trustworthy than the method by which it was 630 received. 632 Private and symmetric keys MUST be protected from disclosure to 633 unintended parties. One recommended means of doing so is to encrypt 634 JWKs or JWK Sets containing them by using the JWK or JWK Set value as 635 the plaintext of a JWE. 637 The security considerations in RFC 3447 [RFC3447] and RFC 6030 638 [RFC6030] about protecting private and symmetric keys also apply to 639 this specification. 641 The security considerations in XML DSIG 2.0 642 [W3C.CR-xmldsig-core2-20120124], about key representations also apply 643 to this specification, other than those that are XML specific. 645 The TLS Requirements in [JWS] also apply to this specification. 647 9. References 649 9.1. Normative References 651 [ECMAScript] 652 Ecma International, "ECMAScript Language Specification, 653 5.1 Edition", ECMA 262, June 2011. 655 [IANA.MediaTypes] 656 Internet Assigned Numbers Authority (IANA), "MIME Media 657 Types", 2005. 659 [ITU.X690.1994] 660 International Telecommunications Union, "Information 661 Technology - ASN.1 encoding rules: Specification of Basic 662 Encoding Rules (BER), Canonical Encoding Rules (CER) and 663 Distinguished Encoding Rules (DER)", ITU-T Recommendation 664 X.690, 1994. 666 [JWA] Jones, M., "JSON Web Algorithms (JWA)", 667 draft-ietf-jose-json-web-algorithms (work in progress), 668 September 2013. 670 [JWE] Jones, M., Rescorla, E., and J. Hildebrand, "JSON Web 671 Encryption (JWE)", draft-ietf-jose-json-web-encryption 672 (work in progress), September 2013. 674 [JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web 675 Signature (JWS)", draft-ietf-jose-json-web-signature (work 676 in progress), September 2013. 678 [RFC1421] Linn, J., "Privacy Enhancement for Internet Electronic 679 Mail: Part I: Message Encryption and Authentication 680 Procedures", RFC 1421, February 1993. 682 [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 683 Extensions (MIME) Part Two: Media Types", RFC 2046, 684 November 1996. 686 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 687 Requirement Levels", BCP 14, RFC 2119, March 1997. 689 [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. 691 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 692 Resource Identifier (URI): Generic Syntax", STD 66, 693 RFC 3986, January 2005. 695 [RFC4627] Crockford, D., "The application/json Media Type for 696 JavaScript Object Notation (JSON)", RFC 4627, July 2006. 698 [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data 699 Encodings", RFC 4648, October 2006. 701 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 702 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 703 May 2008. 705 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 706 (TLS) Protocol Version 1.2", RFC 5246, August 2008. 708 [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., 709 Housley, R., and W. Polk, "Internet X.509 Public Key 710 Infrastructure Certificate and Certificate Revocation List 711 (CRL) Profile", RFC 5280, May 2008. 713 [W3C.CR-xmldsig-core2-20120124] 714 Eastlake, D., Reagle, J., Yiu, K., Solo, D., Datta, P., 715 Hirsch, F., Cantor, S., and T. Roessler, "XML Signature 716 Syntax and Processing Version 2.0", World Wide Web 717 Consortium CR CR-xmldsig-core2-20120124, January 2012, 718 . 720 9.2. Informative References 722 [MagicSignatures] 723 Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic 724 Signatures", January 2011. 726 [RFC3447] Jonsson, J. and B. Kaliski, "Public-Key Cryptography 727 Standards (PKCS) #1: RSA Cryptography Specifications 728 Version 2.1", RFC 3447, February 2003. 730 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 731 Unique IDentifier (UUID) URN Namespace", RFC 4122, 732 July 2005. 734 [RFC6030] Hoyer, P., Pei, M., and S. Machani, "Portable Symmetric 735 Key Container (PSKC)", RFC 6030, October 2010. 737 Appendix A. Example JSON Web Key Sets 739 A.1. Example Public Keys 741 The following example JWK Set contains two public keys represented as 742 JWKs: one using an Elliptic Curve algorithm and a second one using an 743 RSA algorithm. The first specifies that the key is to be used for 744 encryption. The second specifies that the key is to be used with the 745 "RS256" algorithm. Both provide a Key ID for key matching purposes. 746 In both cases, integers are represented using the base64url encoding 747 of their big endian representations. (Long lines are broken are for 748 display purposes only.) 749 {"keys": 750 [ 751 {"kty":"EC", 752 "crv":"P-256", 753 "x":"MKBCTNIcKUSDii11ySs3526iDZ8AiTo7Tu6KPAqv7D4", 754 "y":"4Etl6SRW2YiLUrN5vfvVHuhp7x8PxltmWWlbbM4IFyM", 755 "use":"enc", 756 "kid":"1"}, 758 {"kty":"RSA", 759 "n": "0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx 760 4cbbfAAtVT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMs 761 tn64tZ_2W-5JsGY4Hc5n9yBXArwl93lqt7_RN5w6Cf0h4QyQ5v-65YGjQR0_FDW2 762 QvzqY368QQMicAtaSqzs8KJZgnYb9c7d0zgdAZHzu6qMQvRL5hajrn1n91CbOpbI 763 SD08qNLyrdkt-bFTWhAI4vMQFh6WeZu0fM4lFd2NcRwr3XPksINHaQ-G_xBniIqb 764 w0Ls1jF44-csFCur-kEgU8awapJzKnqDKgw", 765 "e":"AQAB", 766 "alg":"RS256", 767 "kid":"2011-04-29"} 768 ] 769 } 771 A.2. Example Private Keys 773 The following example JWK Set contains two keys represented as JWKs 774 containing both public and private key values: one using an Elliptic 775 Curve algorithm and a second one using an RSA algorithm. This 776 example extends the example in the previous section, adding private 777 key values. (Line breaks are for display purposes only.) 778 {"keys": 779 [ 780 {"kty":"EC", 781 "crv":"P-256", 782 "x":"MKBCTNIcKUSDii11ySs3526iDZ8AiTo7Tu6KPAqv7D4", 783 "y":"4Etl6SRW2YiLUrN5vfvVHuhp7x8PxltmWWlbbM4IFyM", 784 "d":"870MB6gfuTJ4HtUnUvYMyJpr5eUZNP4Bk43bVdj3eAE", 785 "use":"enc", 786 "kid":"1"}, 788 {"kty":"RSA", 789 "n":"0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx4 790 cbbfAAtVT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMst 791 n64tZ_2W-5JsGY4Hc5n9yBXArwl93lqt7_RN5w6Cf0h4QyQ5v-65YGjQR0_FDW2Q 792 vzqY368QQMicAtaSqzs8KJZgnYb9c7d0zgdAZHzu6qMQvRL5hajrn1n91CbOpbIS 793 D08qNLyrdkt-bFTWhAI4vMQFh6WeZu0fM4lFd2NcRwr3XPksINHaQ-G_xBniIqbw 794 0Ls1jF44-csFCur-kEgU8awapJzKnqDKgw", 795 "e":"AQAB", 796 "d":"X4cTteJY_gn4FYPsXB8rdXix5vwsg1FLN5E3EaG6RJoVH-HLLKD9 797 M7dx5oo7GURknchnrRweUkC7hT5fJLM0WbFAKNLWY2vv7B6NqXSzUvxT0_YSfqij 798 wp3RTzlBaCxWp4doFk5N2o8Gy_nHNKroADIkJ46pRUohsXywbReAdYaMwFs9tv8d 799 _cPVY3i07a3t8MN6TNwm0dSawm9v47UiCl3Sk5ZiG7xojPLu4sbg1U2jx4IBTNBz 800 nbJSzFHK66jT8bgkuqsk0GjskDJk19Z4qwjwbsnn4j2WBii3RL-Us2lGVkY8fkFz 801 me1z0HbIkfz0Y6mqnOYtqc0X4jfcKoAC8Q", 802 "p":"83i-7IvMGXoMXCskv73TKr8637FiO7Z27zv8oj6pbWUQyLPQBQxtPV 803 nwD20R-60eTDmD2ujnMt5PoqMrm8RfmNhVWDtjjMmCMjOpSXicFHj7XOuVIYQyqV 804 WlWEh6dN36GVZYk93N8Bc9vY41xy8B9RzzOGVQzXvNEvn7O0nVbfs", 805 "q":"3dfOR9cuYq-0S-mkFLzgItgMEfFzB2q3hWehMuG0oCuqnb3vobLyum 806 qjVZQO1dIrdwgTnCdpYzBcOfW5r370AFXjiWft_NGEiovonizhKpo9VVS78TzFgx 807 kIdrecRezsZ-1kYd_s1qDbxtkDEgfAITAG9LUnADun4vIcb6yelxk", 808 "dp":"G4sPXkc6Ya9y8oJW9_ILj4xuppu0lzi_H7VTkS8xj5SdX3coE0oim 809 YwxIi2emTAue0UOa5dpgFGyBJ4c8tQ2VF402XRugKDTP8akYhFo5tAA77Qe_Nmtu 810 YZc3C3m3I24G2GvR5sSDxUyAN2zq8Lfn9EUms6rY3Ob8YeiKkTiBj0", 811 "dq":"s9lAH9fggBsoFR8Oac2R_E2gw282rT2kGOAhvIllETE1efrA6huUU 812 vMfBcMpn8lqeW6vzznYY5SSQF7pMdC_agI3nG8Ibp1BUb0JUiraRNqUfLhcQb_d9 813 GF4Dh7e74WbRsobRonujTYN1xCaP6TO61jvWrX-L18txXw494Q_cgk", 814 "qi":"GyM_p6JrXySiz1toFgKbWV-JdI3jQ4ypu9rbMWx3rQJBfmt0FoYzg 815 UIZEVFEcOqwemRN81zoDAaa-Bk0KWNGDjJHZDdDmFhW3AN7lI-puxk_mHZGJ11rx 816 yR8O55XLSe3SPmRfKwZI6yU24ZxvQKFYItdldUKGzO6Ia6zTKhAVRU", 817 "alg":"RS256", 818 "kid":"2011-04-29"} 819 ] 820 } 822 A.3. Example Symmetric Keys 824 The following example JWK Set contains two symmetric keys represented 825 as JWKs: one designated as being for use with the AES Key Wrap 826 algorithm and a second one that is an HMAC key. (Line breaks are for 827 display purposes only.) 829 {"keys": 830 [ 831 {"kty":"oct", 832 "alg":"A128KW", 833 "k":"GawgguFyGrWKav7AX4VKUg"}, 835 {"kty":"oct", 836 "k":"AyM1SysPpbyDfgZld3umj1qzKObwVMkoqQ-EstJQLr_T-1qS0gZH75 837 aKtMN3Yj0iPS4hcgUuTwjAzZr1Z9CAow", 838 "kid":"HMAC key used in JWS A.1 example"} 839 ] 840 } 842 Appendix B. Example Use of "x5c" (X.509 Certificate Chain) Parameter 843 The following is an example of a JWK with a RSA signing key 844 represented both as a bare public key and as an X.509 certificate 845 using the "x5c" parameter: 847 {"kty":"RSA", 848 "use":"sig", 849 "kid":"1b94c", 850 "n":"vrjOfz9Ccdgx5nQudyhdoR17V-IubWMeOZCwX_jj0hgAsz2J_pqYW08 851 PLbK_PdiVGKPrqzmDIsLI7sA25VEnHU1uCLNwBuUiCO11_-7dYbsr4iJmG0Q 852 u2j8DsVyT1azpJC_NG84Ty5KKthuCaPod7iI7w0LK9orSMhBEwwZDCxTWq4a 853 YWAchc8t-emd9qOvWtVMDC2BXksRngh6X5bUYLy6AyHKvj-nUy1wgzjYQDwH 854 MTplCoLtU-o-8SNnZ1tmRoGE9uJkBLdh5gFENabWnU5m1ZqZPdwS-qo-meMv 855 VfJb6jJVWRpl2SUtCnYG2C32qvbWbjZ_jBPD5eunqsIo1vQ", 856 "e":"AQAB", 857 "x5c": 858 ["MIIDQjCCAiqgAwIBAgIGATz/FuLiMA0GCSqGSIb3DQEBBQUAMGIxCzAJB 859 gNVBAYTAlVTMQswCQYDVQQIEwJDTzEPMA0GA1UEBxMGRGVudmVyMRwwGgYD 860 VQQKExNQaW5nIElkZW50aXR5IENvcnAuMRcwFQYDVQQDEw5CcmlhbiBDYW1 861 wYmVsbDAeFw0xMzAyMjEyMzI5MTVaFw0xODA4MTQyMjI5MTVaMGIxCzAJBg 862 NVBAYTAlVTMQswCQYDVQQIEwJDTzEPMA0GA1UEBxMGRGVudmVyMRwwGgYDV 863 QQKExNQaW5nIElkZW50aXR5IENvcnAuMRcwFQYDVQQDEw5CcmlhbiBDYW1w 864 YmVsbDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL64zn8/QnH 865 YMeZ0LncoXaEde1fiLm1jHjmQsF/449IYALM9if6amFtPDy2yvz3YlRij66 866 s5gyLCyO7ANuVRJx1NbgizcAblIgjtdf/u3WG7K+IiZhtELto/A7Fck9Ws6 867 SQvzRvOE8uSirYbgmj6He4iO8NCyvaK0jIQRMMGQwsU1quGmFgHIXPLfnpn 868 fajr1rVTAwtgV5LEZ4Iel+W1GC8ugMhyr4/p1MtcIM42EA8BzE6ZQqC7VPq 869 PvEjZ2dbZkaBhPbiZAS3YeYBRDWm1p1OZtWamT3cEvqqPpnjL1XyW+oyVVk 870 aZdklLQp2Btgt9qr21m42f4wTw+Xrp6rCKNb0CAwEAATANBgkqhkiG9w0BA 871 QUFAAOCAQEAh8zGlfSlcI0o3rYDPBB07aXNswb4ECNIKG0CETTUxmXl9KUL 872 +9gGlqCz5iWLOgWsnrcKcY0vXPG9J1r9AqBNTqNgHq2G03X09266X5CpOe1 873 zFo+Owb1zxtp3PehFdfQJ610CDLEaS9V9Rqp17hCyybEpOGVwe8fnk+fbEL 874 2Bo3UPGrpsHzUoaGpDftmWssZkhpBJKVMJyf/RuP2SmmaIzmnw9JiSlYhzo 875 4tpzd5rFXhjRbg4zW9C+2qok+2+qDM1iJ684gPHMIY8aLWrdgQTxkumGmTq 876 gawR+N5MDtdPTEQ0XfIBc2cJEUyMTY5MPvACWpkA6SdS4xSvdXK3IVfOWA=="] 877 } 879 Appendix C. Acknowledgements 881 A JSON representation for RSA public keys was previously introduced 882 by John Panzer, Ben Laurie, and Dirk Balfanz in Magic Signatures 883 [MagicSignatures]. 885 This specification is the work of the JOSE Working Group, which 886 includes dozens of active and dedicated participants. In particular, 887 the following individuals contributed ideas, feedback, and wording 888 that influenced this specification: 890 Dirk Balfanz, Richard Barnes, John Bradley, Brian Campbell, Breno de 891 Medeiros, Joe Hildebrand, Edmund Jay, Ben Laurie, James Manger, Matt 892 Miller, Tony Nadalin, Axel Nennker, John Panzer, Eric Rescorla, Nat 893 Sakimura, Jim Schaad, Paul Tarjan, Hannes Tschofenig, and Sean 894 Turner. 896 Jim Schaad and Karen O'Donoghue chaired the JOSE working group and 897 Sean Turner and Stephen Farrell served as Security area directors 898 during the creation of this specification. 900 Appendix D. Document History 902 [[ to be removed by the RFC Editor before publication as an RFC ]] 904 -16 906 o Changes to address editorial and minor issues #41, #42, #43, #47, 907 #51, #67, #71, #76, #80, #83, #84, #85, #86, #87, and #88. 909 -15 911 o Changes to address editorial issues #48, #64, #65, #66, and #91. 913 -14 915 o Relaxed language introducing key parameters since some parameters 916 are applicable to multiple, but not all, key types. 918 -13 920 o Applied spelling and grammar corrections. 922 -12 924 o Stated that recipients MUST either reject JWKs and JWK Sets with 925 duplicate member names or use a JSON parser that returns only the 926 lexically last duplicate member name. 928 -11 930 o Stated that when "kid" values are used within a JWK Set, different 931 keys within the JWK Set SHOULD use distinct "kid" values. 933 o Added optional "x5u" (X.509 URL), "x5t" (X.509 Certificate 934 Thumbprint), and "x5c" (X.509 Certificate Chain) JWK parameters. 936 o Added section on Encrypted JWK and Encrypted JWK Set Formats. 938 o Added a Parameter Information Class value to the JSON Web Key 939 Parameters registry, which registers whether the parameter conveys 940 public or private information. 942 o Registered "application/jwk+json" and "application/jwk-set+json" 943 MIME types and "JWK" and "JWK-SET" typ header parameter values, 944 addressing issue #21. 946 -10 948 o No changes were made, other than to the version number and date. 950 -09 952 o Expanded the scope of the JWK specification to include private and 953 symmetric key representations, as specified by 954 draft-jones-jose-json-private-and-symmetric-key-00. 956 o Defined that members that are not understood must be ignored. 958 -08 960 o Changed the name of the JWK key type parameter from "alg" to "kty" 961 to enable use of "alg" to indicate the particular algorithm that 962 the key is intended to be used with. 964 o Clarified statements of the form "This member is OPTIONAL" to "Use 965 of this member is OPTIONAL". 967 o Referenced String Comparison Rules in JWS. 969 o Added seriesInfo information to Internet Draft references. 971 -07 973 o Changed the name of the JWK RSA modulus parameter from "mod" to 974 "n" and the name of the JWK RSA exponent parameter from "xpo" to 975 "e", so that the identifiers are the same as those used in RFC 976 3447. 978 -06 980 o Changed the name of the JWK RSA exponent parameter from "exp" to 981 "xpo" so as to allow the potential use of the name "exp" for a 982 future extension that might define an expiration parameter for 983 keys. (The "exp" name is already used for this purpose in the JWT 984 specification.) 986 o Clarify that the "alg" (algorithm family) member is REQUIRED. 988 o Correct an instance of "JWK" that should have been "JWK Set". 990 o Applied changes made by the RFC Editor to RFC 6749's registry 991 language to this specification. 993 -05 995 o Indented artwork elements to better distinguish them from the body 996 text. 998 -04 1000 o Refer to the registries as the primary sources of defined values 1001 and then secondarily reference the sections defining the initial 1002 contents of the registries. 1004 o Normatively reference XML DSIG 2.0 [W3C.CR-xmldsig-core2-20120124] 1005 for its security considerations. 1007 o Added this language to Registration Templates: "This name is case 1008 sensitive. Names that match other registered names in a case 1009 insensitive manner SHOULD NOT be accepted." 1011 o Described additional open issues. 1013 o Applied editorial suggestions. 1015 -03 1017 o Clarified that "kid" values need not be unique within a JWK Set. 1019 o Moved JSON Web Key Parameters registry to the JWK specification. 1021 o Added "Collision Resistant Namespace" to the terminology section. 1023 o Changed registration requirements from RFC Required to 1024 Specification Required with Expert Review. 1026 o Added Registration Template sections for defined registries. 1028 o Added Registry Contents sections to populate registry values. 1030 o Numerous editorial improvements. 1032 -02 1034 o Simplified JWK terminology to get replace the "JWK Key Object" and 1035 "JWK Container Object" terms with simply "JSON Web Key (JWK)" and 1036 "JSON Web Key Set (JWK Set)" and to eliminate potential confusion 1037 between single keys and sets of keys. As part of this change, the 1038 top-level member name for a set of keys was changed from "jwk" to 1039 "keys". 1041 o Clarified that values with duplicate member names MUST be 1042 rejected. 1044 o Established JSON Web Key Set Parameters registry. 1046 o Explicitly listed non-goals in the introduction. 1048 o Moved algorithm-specific definitions from JWK to JWA. 1050 o Reformatted to give each member definition its own section 1051 heading. 1053 -01 1055 o Corrected the Magic Signatures reference. 1057 -00 1059 o Created the initial IETF draft based upon 1060 draft-jones-json-web-key-03 with no normative changes. 1062 Author's Address 1064 Michael B. Jones 1065 Microsoft 1067 Email: mbj@microsoft.com 1068 URI: http://self-issued.info/