idnits 2.17.1 draft-ietf-jose-json-web-key-08.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 (December 27, 2012) is 4136 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4627 (Obsoleted by RFC 7158, RFC 7159) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- No information found for draft-ietf-jose-json-private-and-symmetric-key - is the name correct? Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 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 December 27, 2012 5 Expires: June 30, 2013 7 JSON Web Key (JWK) 8 draft-ietf-jose-json-web-key-08 10 Abstract 12 A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data 13 structure that represents a public key. This specification also 14 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. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on June 30, 2013. 36 Copyright Notice 38 Copyright (c) 2012 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 3 55 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. Example JSON Web Key Set . . . . . . . . . . . . . . . . . . . 4 57 4. JSON Web Key (JWK) Format . . . . . . . . . . . . . . . . . . 4 58 4.1. "kty" (Key Type) Parameter . . . . . . . . . . . . . . . . 5 59 4.2. "use" (Key Use) Parameter . . . . . . . . . . . . . . . . 5 60 4.3. "alg" (Algorithm) Parameter . . . . . . . . . . . . . . . 5 61 4.4. "kid" (Key ID) Parameter . . . . . . . . . . . . . . . . . 6 62 5. JSON Web Key Set (JWK Set) Format . . . . . . . . . . . . . . 6 63 5.1. "keys" (JSON Web Key Set) Parameter . . . . . . . . . . . 6 64 6. String Comparison Rules . . . . . . . . . . . . . . . . . . . 7 65 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 66 7.1. JSON Web Key Parameters Registry . . . . . . . . . . . . . 7 67 7.1.1. Registration Template . . . . . . . . . . . . . . . . 8 68 7.1.2. Initial Registry Contents . . . . . . . . . . . . . . 8 69 7.2. JSON Web Key Set Parameters Registry . . . . . . . . . . . 8 70 7.2.1. Registration Template . . . . . . . . . . . . . . . . 9 71 7.2.2. Initial Registry Contents . . . . . . . . . . . . . . 9 72 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 73 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 74 9.1. Normative References . . . . . . . . . . . . . . . . . . . 10 75 9.2. Informative References . . . . . . . . . . . . . . . . . . 10 76 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 11 77 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 11 78 Appendix C. Document History . . . . . . . . . . . . . . . . . . 11 79 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13 81 1. Introduction 83 A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) [RFC4627] 84 data structure that represents a public key. This specification also 85 defines a JSON Web Key Set (JWK Set) JSON data structure for 86 representing a set of JWKs. Cryptographic algorithms and identifiers 87 for use with this specification are described in the separate JSON 88 Web Algorithms (JWA) [JWA] specification. 90 Goals for this specification do not include representing private 91 keys, representing symmetric keys, representing certificate chains, 92 representing certified keys, and replacing X.509 certificates. 93 However the JSON Private and Symmetric Key [JPSK] specification does 94 extend this specification to define JSON representations of private 95 keys and symmetric keys. 97 JWKs and JWK Sets are used in the JSON Web Signature (JWS) [JWS] and 98 JSON Web Encryption (JWE) [JWE] specifications. 100 1.1. Notational Conventions 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in Key words for use in 105 RFCs to Indicate Requirement Levels [RFC2119]. 107 2. Terminology 109 JSON Web Key (JWK) A JSON object that represents a public key. 111 JSON Web Key Set (JWK Set) A JSON object that contains an array of 112 JWKs as the value of its "keys" member. 114 Base64url Encoding The URL- and filename-safe Base64 encoding 115 described in RFC 4648 [RFC4648], Section 5, with the (non URL- 116 safe) '=' padding characters omitted, as permitted by Section 3.2. 117 (See Appendix C of [JWS] for notes on implementing base64url 118 encoding without padding.) 120 Collision Resistant Namespace A namespace that allows names to be 121 allocated in a manner such that they are highly unlikely to 122 collide with other names. For instance, collision resistance can 123 be achieved through administrative delegation of portions of the 124 namespace or through use of collision-resistant name allocation 125 functions. Examples of Collision Resistant Namespaces include: 126 Domain Names, Object Identifiers (OIDs) as defined in the ITU-T 127 X.660 and X.670 Recommendation series, and Universally Unique 128 IDentifiers (UUIDs) [RFC4122]. When using an administratively 129 delegated namespace, the definer of a name needs to take 130 reasonable precautions to ensure they are in control of the 131 portion of the namespace they use to define the name. 133 3. Example JSON Web Key Set 135 The following example JWK Set contains two public keys represented as 136 JWKs: one using an Elliptic Curve algorithm and a second one using an 137 RSA algorithm. The first specifies that the key is to be used for 138 encryption. The second specifies that the key is to be used with the 139 "RS256" algorithm. Both provide a Key ID for key matching purposes. 140 In both cases, integers are represented using the base64url encoding 141 of their big endian representations. (Long lines are broken are for 142 display purposes only.) 144 {"keys": 145 [ 146 {"kty":"EC", 147 "crv":"P-256", 148 "x":"MKBCTNIcKUSDii11ySs3526iDZ8AiTo7Tu6KPAqv7D4", 149 "y":"4Etl6SRW2YiLUrN5vfvVHuhp7x8PxltmWWlbbM4IFyM", 150 "use":"enc", 151 "kid":"1"}, 153 {"kty":"RSA", 154 "n": "0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx 155 4cbbfAAtVT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMs 156 tn64tZ_2W-5JsGY4Hc5n9yBXArwl93lqt7_RN5w6Cf0h4QyQ5v-65YGjQR0_FDW2 157 QvzqY368QQMicAtaSqzs8KJZgnYb9c7d0zgdAZHzu6qMQvRL5hajrn1n91CbOpbI 158 SD08qNLyrdkt-bFTWhAI4vMQFh6WeZu0fM4lFd2NcRwr3XPksINHaQ-G_xBniIqb 159 w0Ls1jF44-csFCur-kEgU8awapJzKnqDKgw", 160 "e":"AQAB", 161 "alg":"RS256", 162 "kid":"2011-04-29"} 163 ] 164 } 166 4. JSON Web Key (JWK) Format 168 A JSON Web Key (JWK) is a JSON object containing specific members, as 169 specified below. Those members that are common to all key types are 170 defined below. 172 In addition to the common parameters, each JWK will have members that 173 are specific to the key being represented. These members represent 174 the parameters of the key. Section 5 of the JSON Web Algorithms 175 (JWA) [JWA] specification defines multiple kinds of public keys and 176 their associated members. 178 The member names within a JWK MUST be unique; objects with duplicate 179 member names MUST be rejected. 181 Additional members MAY be present in the JWK. If present, they MUST 182 be understood by implementations using them. Member names used for 183 representing key parameters for different kinds of keys need not be 184 distinct. Any new member name SHOULD either be registered in the 185 IANA JSON Web Key Parameters registry Section 7.1 or be a value that 186 contains a Collision Resistant Namespace. 188 4.1. "kty" (Key Type) Parameter 190 The "kty" (key type) member identifies the cryptographic algorithm 191 family used with the key. "kty" values SHOULD either be registered in 192 the IANA JSON Web Key Types registry [JWA] or be a value that 193 contains a Collision Resistant Namespace. The "kty" value is a case 194 sensitive string. Use of this member is REQUIRED. 196 A list of defined "kty" values can be found in the IANA JSON Web Key 197 Types registry [JWA]; the initial contents of this registry are the 198 values defined in Section 5.1 of the JSON Web Algorithms (JWA) [JWA] 199 specification. 201 Additional members used with these "kty" values can be found in the 202 IANA JSON Web Key Parameters registry Section 7.1; the initial 203 contents of this registry are the values defined in Sections 5.2 and 204 5.3 of the JSON Web Algorithms (JWA) [JWA] specification. 206 4.2. "use" (Key Use) Parameter 208 The "use" (key use) member identifies the intended use of the key. 209 Values defined by this specification are: 211 o "sig" (signature) 213 o "enc" (encryption) 215 Other values MAY be used. The "use" value is a case sensitive 216 string. Use of this member is OPTIONAL. 218 4.3. "alg" (Algorithm) Parameter 220 The "alg" (algorithm) member identifies the algorithm intended for 221 use with the key. The values used in this field are the same as 222 those used in the JWS [JWS] and JWE [JWE] "alg" and "enc" header 223 parameters; these values can be found in the JSON Web Signature and 224 Encryption Algorithms registry [JWA]. Use of this member is 225 OPTIONAL. 227 4.4. "kid" (Key ID) Parameter 229 The "kid" (key ID) member can be used to match a specific key. This 230 can be used, for instance, to choose among a set of keys within a JWK 231 Set during key rollover. The interpretation of the "kid" value is 232 unspecified. Key ID values within a JWK Set need not be unique. The 233 "kid" value is a case sensitive string. Use of this member is 234 OPTIONAL. 236 When used with JWS or JWE, the "kid" value MAY be used to match a JWS 237 or JWE "kid" header parameter value. 239 In some contexts, different keys using the same Key ID value might be 240 present, with the keys being disambiguated using other information, 241 such as the "kty" or "use" values. For example, imagine "kid" values 242 like "Current", "Upcoming", and "Deprecated", used for key rollover 243 guidance. One could apply a label to all keys where the 244 classification fits. If there are multiple "Current" keys, then in 245 this example, they might be differentiated either by having different 246 "kty" or "use" values, or some combination of both. As one example, 247 there might only be one current RSA signing key and one current 248 Elliptic Curve signing key, but both would be "Current". 250 5. JSON Web Key Set (JWK Set) Format 252 A JSON Web Key Set (JWK Set) is a JSON object that contains an array 253 of JSON Web Key values as the value of its "keys" member. 255 The member names within a JWK Set MUST be unique; objects with 256 duplicate member names MUST be rejected. 258 Additional members MAY be present in the JWK Set. If present, they 259 MUST be understood by implementations using them. Parameters for 260 representing additional properties of JWK Sets SHOULD either be 261 registered in the IANA JSON Web Key Set Parameters registry 262 Section 7.2 or be a value that contains a Collision Resistant 263 Namespace. 265 5.1. "keys" (JSON Web Key Set) Parameter 267 The value of the "keys" (JSON Web Key Set) member is an array of JSON 268 Web Key (JWK) values. Use of this member is REQUIRED. 270 6. String Comparison Rules 272 Processing a JWK inevitably requires comparing known strings to 273 values in JSON objects. For example, in checking what the key type 274 is, the Unicode string encoding "kty" will be checked against the 275 member names in the JWK to see if there is a matching name. 277 Comparisons between JSON strings and other Unicode strings MUST be 278 performed by comparing Unicode code points without normalization as 279 specified in the String Comparison Rules in Section 5.3 of [JWS]. 281 7. IANA Considerations 283 The following registration procedure is used for all the registries 284 established by this specification. 286 Values are registered with a Specification Required [RFC5226] after a 287 two-week review period on the [TBD]@ietf.org mailing list, on the 288 advice of one or more Designated Experts. However, to allow for the 289 allocation of values prior to publication, the Designated Expert(s) 290 may approve registration once they are satisfied that such a 291 specification will be published. 293 Registration requests must be sent to the [TBD]@ietf.org mailing list 294 for review and comment, with an appropriate subject (e.g., "Request 295 for access token type: example"). [[ Note to RFC-EDITOR: The name of 296 the mailing list should be determined in consultation with the IESG 297 and IANA. Suggested name: jose-reg-review. ]] 299 Within the review period, the Designated Expert(s) will either 300 approve or deny the registration request, communicating this decision 301 to the review list and IANA. Denials should include an explanation 302 and, if applicable, suggestions as to how to make the request 303 successful. 305 IANA must only accept registry updates from the Designated Expert(s) 306 and should direct all requests for registration to the review mailing 307 list. 309 7.1. JSON Web Key Parameters Registry 311 This specification establishes the IANA JSON Web Key Parameters 312 registry for reserved JWK parameter names. The registry records the 313 reserved parameter name and a reference to the specification that 314 defines it. This specification registers the parameter names defined 315 in Section 4. The same JWK parameter name may be registered multiple 316 times, provided that duplicate parameter registrations are only for 317 algorithm-specific JWK parameters; in this case, the meaning of the 318 duplicate parameter name is disambiguated by the "kty" value of the 319 JWK containing it. 321 7.1.1. Registration Template 323 Parameter Name: 324 The name requested (e.g., "example"). This name is case 325 sensitive. Names that match other registered names in a case 326 insensitive manner SHOULD NOT be accepted. 328 Change Controller: 329 For Standards Track RFCs, state "IETF". For others, give the name 330 of the responsible party. Other details (e.g., postal address, 331 email address, home page URI) may also be included. 333 Specification Document(s): 334 Reference to the document(s) that specify the parameter, 335 preferably including URI(s) that can be used to retrieve copies of 336 the document(s). An indication of the relevant sections may also 337 be included but is not required. 339 7.1.2. Initial Registry Contents 341 o Parameter Name: "kty" 342 o Change Controller: IETF 343 o Specification Document(s): Section 4.1 of [[ this document ]] 345 o Parameter Name: "use" 346 o Change Controller: IETF 347 o Specification Document(s): Section 4.2 of [[ this document ]] 349 o Parameter Name: "alg" 350 o Change Controller: IETF 351 o Specification Document(s): Section 4.3 of [[ this document ]] 353 o Parameter Name: "kid" 354 o Change Controller: IETF 355 o Specification Document(s): Section 4.4 of [[ this document ]] 357 7.2. JSON Web Key Set Parameters Registry 359 This specification establishes the IANA JSON Web Key Set Parameters 360 registry for reserved JWK Set parameter names. The registry records 361 the reserved parameter name and a reference to the specification that 362 defines it. This specification registers the parameter names defined 363 in Section 5. 365 7.2.1. Registration Template 367 Parameter Name: 368 The name requested (e.g., "example"). This name is case 369 sensitive. Names that match other registered names in a case 370 insensitive manner SHOULD NOT be accepted. 372 Change Controller: 373 For Standards Track RFCs, state "IETF". For others, give the name 374 of the responsible party. Other details (e.g., postal address, 375 email address, home page URI) may also be included. 377 Specification Document(s): 378 Reference to the document(s) that specify the parameter, 379 preferably including URI(s) that can be used to retrieve copies of 380 the document(s). An indication of the relevant sections may also 381 be included but is not required. 383 7.2.2. Initial Registry Contents 385 o Parameter Name: "keys" 386 o Change Controller: IETF 387 o Specification Document(s): Section 5.1 of [[ this document ]] 389 8. Security Considerations 391 All of the security issues faced by any cryptographic application 392 must be faced by a JWS/JWE/JWK agent. Among these issues are 393 protecting the user's private and symmetric keys, preventing various 394 attacks, and helping the user avoid mistakes such as inadvertently 395 encrypting a message for the wrong recipient. The entire list of 396 security considerations is beyond the scope of this document. 398 A key is no more trustworthy than the method by which it was 399 received. 401 Per Section 4.4, applications should not assume that "kid" values are 402 unique within a JWK Set. 404 The security considerations in XML DSIG 2.0 405 [W3C.CR-xmldsig-core2-20120124], about public key representations 406 also apply to this specification, other than those that are XML 407 specific. 409 9. References 410 9.1. Normative References 412 [JWA] Jones, M., "JSON Web Algorithms (JWA)", 413 draft-ietf-jose-json-web-algorithms (work in progress), 414 December 2012. 416 [JWE] Jones, M., Rescorla, E., and J. Hildebrand, "JSON Web 417 Encryption (JWE)", draft-ietf-jose-json-web-encryption 418 (work in progress), December 2012. 420 [JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web 421 Signature (JWS)", draft-ietf-jose-json-web-signature (work 422 in progress), December 2012. 424 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 425 Requirement Levels", BCP 14, RFC 2119, March 1997. 427 [RFC4627] Crockford, D., "The application/json Media Type for 428 JavaScript Object Notation (JSON)", RFC 4627, July 2006. 430 [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data 431 Encodings", RFC 4648, October 2006. 433 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 434 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 435 May 2008. 437 [W3C.CR-xmldsig-core2-20120124] 438 Yiu, K., Solo, D., Eastlake, D., Datta, P., Hirsch, F., 439 Reagle, J., Cantor, S., and T. Roessler, "XML Signature 440 Syntax and Processing Version 2.0", World Wide Web 441 Consortium CR CR-xmldsig-core2-20120124, January 2012, 442 . 444 9.2. Informative References 446 [JPSK] Jones, M., "JSON Private and Symmetric Key", 447 draft-ietf-jose-json-private-and-symmetric-key (work in 448 progress), December 2012. 450 [MagicSignatures] 451 Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic 452 Signatures", January 2011. 454 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 455 Unique IDentifier (UUID) URN Namespace", RFC 4122, 456 July 2005. 458 Appendix A. Acknowledgements 460 A JSON representation for RSA public keys was previously introduced 461 by John Panzer, Ben Laurie, and Dirk Balfanz in Magic Signatures 462 [MagicSignatures]. 464 This specification is the work of the JOSE Working Group, which 465 includes dozens of active and dedicated participants. In particular, 466 the following individuals contributed ideas, feedback, and wording 467 that influenced this specification: 469 Dirk Balfanz, Richard Barnes, John Bradley, Brian Campbell, Breno de 470 Medeiros, Joe Hildebrand, Edmund Jay, Ben Laurie, James Manger, Tony 471 Nadalin, Axel Nennker, John Panzer, Eric Rescorla, Nat Sakimura, Jim 472 Schaad, Paul Tarjan, Hannes Tschofenig, and Sean Turner. 474 Jim Schaad and Karen O'Donoghue chaired the JOSE working group and 475 Sean Turner and Stephen Farrell served as Security area directors 476 during the creation of this specification. 478 Appendix B. Open Issues 480 [[ to be removed by the RFC editor before publication as an RFC ]] 482 The following items remain to be considered or done in this draft: 484 o No known open issues. 486 Appendix C. Document History 488 [[ to be removed by the RFC editor before publication as an RFC ]] 490 -08 492 o Changed the name of the JWK key type parameter from "alg" to "kty" 493 to enable use of "alg" to indicate the particular algorithm that 494 the key is intended to be used with. 496 o Clarified statements of the form "This member is OPTIONAL" to "Use 497 of this member is OPTIONAL". 499 o Referenced String Comparison Rules in JWS. 501 o Added seriesInfo information to Internet Draft references. 503 -07 504 o Changed the name of the JWK RSA modulus parameter from "mod" to 505 "n" and the name of the JWK RSA exponent parameter from "xpo" to 506 "e", so that the identifiers are the same as those used in RFC 507 3447. 509 -06 511 o Changed the name of the JWK RSA exponent parameter from "exp" to 512 "xpo" so as to allow the potential use of the name "exp" for a 513 future extension that might define an expiration parameter for 514 keys. (The "exp" name is already used for this purpose in the JWT 515 specification.) 517 o Clarify that the "alg" (algorithm family) member is REQUIRED. 519 o Correct an instance of "JWK" that should have been "JWK Set". 521 o Applied changes made by the RFC Editor to RFC 6749's registry 522 language to this specification. 524 -05 526 o Indented artwork elements to better distinguish them from the body 527 text. 529 -04 531 o Refer to the registries as the primary sources of defined values 532 and then secondarily reference the sections defining the initial 533 contents of the registries. 535 o Normatively reference XML DSIG 2.0 [W3C.CR-xmldsig-core2-20120124] 536 for its security considerations. 538 o Added this language to Registration Templates: "This name is case 539 sensitive. Names that match other registered names in a case 540 insensitive manner SHOULD NOT be accepted." 542 o Described additional open issues. 544 o Applied editorial suggestions. 546 -03 548 o Clarified that "kid" values need not be unique within a JWK Set. 550 o Moved JSON Web Key Parameters registry to the JWK specification. 552 o Added "Collision Resistant Namespace" to the terminology section. 554 o Changed registration requirements from RFC Required to 555 Specification Required with Expert Review. 557 o Added Registration Template sections for defined registries. 559 o Added Registry Contents sections to populate registry values. 561 o Numerous editorial improvements. 563 -02 565 o Simplified JWK terminology to get replace the "JWK Key Object" and 566 "JWK Container Object" terms with simply "JSON Web Key (JWK)" and 567 "JSON Web Key Set (JWK Set)" and to eliminate potential confusion 568 between single keys and sets of keys. As part of this change, the 569 top-level member name for a set of keys was changed from "jwk" to 570 "keys". 572 o Clarified that values with duplicate member names MUST be 573 rejected. 575 o Established JSON Web Key Set Parameters registry. 577 o Explicitly listed non-goals in the introduction. 579 o Moved algorithm-specific definitions from JWK to JWA. 581 o Reformatted to give each member definition its own section 582 heading. 584 -01 586 o Corrected the Magic Signatures reference. 588 -00 590 o Created the initial IETF draft based upon 591 draft-jones-json-web-key-03 with no normative changes. 593 Author's Address 595 Michael B. Jones 596 Microsoft 598 Email: mbj@microsoft.com 599 URI: http://self-issued.info/