| < draft-jones-json-web-signature-json-serialization-00.txt | draft-jones-json-web-signature-json-serialization-01.txt > | |||
|---|---|---|---|---|
| JOSE Working Group M. Jones | JOSE Working Group M. Jones | |||
| Internet-Draft Microsoft | Internet-Draft Microsoft | |||
| Intended status: Standards Track J. Bradley | Intended status: Standards Track J. Bradley | |||
| Expires: September 6, 2012 independent | Expires: September 13, 2012 independent | |||
| N. Sakimura | N. Sakimura | |||
| Nomura Research Institute | Nomura Research Institute | |||
| March 5, 2012 | March 12, 2012 | |||
| JSON Web Signature JSON Serialization (JWS-JS) | JSON Web Signature JSON Serialization (JWS-JS) | |||
| draft-jones-json-web-signature-json-serialization-00 | draft-jones-json-web-signature-json-serialization-01 | |||
| Abstract | Abstract | |||
| The JSON Web Signature JSON Serialization (JWS-JS) is a means of | The JSON Web Signature JSON Serialization (JWS-JS) is a means of | |||
| representing content secured with digital signatures or Hash-based | representing content secured with digital signatures or Hash-based | |||
| Message Authentication Codes (HMACs) using JSON data structures. | Message Authentication Codes (HMACs) using JSON data structures. | |||
| This specification describes a means of representing secured content | This specification describes a means of representing secured content | |||
| as a JSON data object (as opposed to the JWS specification, which | as a JSON data object (as opposed to the JWS specification, which | |||
| uses a compact serialization with a URL-safe representation). It | uses a compact serialization with a URL-safe representation). It | |||
| enables multiple digital signatures and/or HMACs to be applied to the | enables multiple digital signatures and/or HMACs to be applied to the | |||
| skipping to change at page 2, line 4 ¶ | skipping to change at page 2, line 4 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on September 6, 2012. | This Internet-Draft will expire on September 13, 2012. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2012 IETF Trust and the persons identified as the | Copyright (c) 2012 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 4, line 17 ¶ | skipping to change at page 4, line 17 ¶ | |||
| The JSON Web Signature JSON Serialization (JWS-JS) is a format for | The JSON Web Signature JSON Serialization (JWS-JS) is a format for | |||
| representing content secured with digital signatures or Hash-based | representing content secured with digital signatures or Hash-based | |||
| Message Authentication Codes (HMACs) as a JSON [RFC4627] object. It | Message Authentication Codes (HMACs) as a JSON [RFC4627] object. It | |||
| enables multiple digital signatures and/or HMACs to be applied to the | enables multiple digital signatures and/or HMACs to be applied to the | |||
| same content (unlike JWS [JWS]). The digital signature and HMAC | same content (unlike JWS [JWS]). The digital signature and HMAC | |||
| mechanisms used are independent of the type of content being secured, | mechanisms used are independent of the type of content being secured, | |||
| allowing arbitrary content to be secured. Cryptographic algorithms | allowing arbitrary content to be secured. Cryptographic algorithms | |||
| and identifiers used with this specification are enumerated in the | and identifiers used with this specification are enumerated in the | |||
| separate JSON Web Algorithms (JWA) [JWA] specification. The JSON | separate JSON Web Algorithms (JWA) [JWA] specification. The JSON | |||
| Serialization for related encryption functionality is described in | Serialization for related encryption functionality is described in | |||
| the separate JSON Web Encryption JSON Serialization [JWE-JS] | the separate JSON Web Encryption JSON Serialization (JWE-JS) [JWE-JS] | |||
| specification. | specification. | |||
| 2. Terminology | 2. Terminology | |||
| This specification uses the same terminology as the JSON Web | This specification uses the same terminology as the JSON Web | |||
| Signature (JWS) [JWS] specification. | Signature (JWS) [JWS] specification. | |||
| 3. JSON Serialization | 3. JSON Serialization | |||
| The JSON Serialization represents secured content as a JSON object | The JSON Serialization represents secured content as a JSON object | |||
| skipping to change at page 6, line 34 ¶ | skipping to change at page 6, line 34 ¶ | |||
| 6. Security Considerations | 6. Security Considerations | |||
| The security considerations for this specification are the same as | The security considerations for this specification are the same as | |||
| those for the JSON Web Signature (JWS) [JWS] specification. | those for the JSON Web Signature (JWS) [JWS] specification. | |||
| 7. References | 7. References | |||
| 7.1. Normative References | 7.1. Normative References | |||
| [JWA] Jones, M., "JSON Web Algorithms (JWA)", January 2012. | [JWA] Jones, M., "JSON Web Algorithms (JWA)", March 2012. | |||
| [JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web | [JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web | |||
| Signature (JWS)", January 2012. | Signature (JWS)", March 2012. | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
| [RFC4627] Crockford, D., "The application/json Media Type for | [RFC4627] Crockford, D., "The application/json Media Type for | |||
| JavaScript Object Notation (JSON)", RFC 4627, July 2006. | JavaScript Object Notation (JSON)", RFC 4627, July 2006. | |||
| 7.2. Informative References | 7.2. Informative References | |||
| [JSS] Bradley, J. and N. Sakimura (editor), "JSON Simple Sign", | [JSS] Bradley, J. and N. Sakimura (editor), "JSON Simple Sign", | |||
| September 2010. | September 2010. | |||
| [JWE-JS] Jones, M., "JSON Web Encryption JSON Serialization | [JWE-JS] Jones, M., "JSON Web Encryption JSON Serialization | |||
| (JWE-JS)", March 2012. | (JWE-JS)", March 2012. | |||
| [MagicSignatures] | [MagicSignatures] | |||
| Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic | Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic | |||
| Signatures", August 2010. | Signatures", January 2011. | |||
| Appendix A. Acknowledgements | Appendix A. Acknowledgements | |||
| JSON serializations for secured content were previously explored by | JSON serializations for secured content were previously explored by | |||
| Magic Signatures [MagicSignatures] and JSON Simple Sign [JSS]. | Magic Signatures [MagicSignatures] and JSON Simple Sign [JSS]. | |||
| Appendix B. Document History | Appendix B. Document History | |||
| -01 | ||||
| o Corrected the Magic Signatures reference. | ||||
| -00 | -00 | |||
| o Created the initial version incorporating JOSE working group input | o Created the initial version incorporating JOSE working group input | |||
| and drawing from the JSON Serialization previously proposed in | and drawing from the JSON Serialization previously proposed in | |||
| draft-jones-json-web-token-01. | draft-jones-json-web-token-01. | |||
| Authors' Addresses | Authors' Addresses | |||
| Michael B. Jones | Michael B. Jones | |||
| Microsoft | Microsoft | |||
| End of changes. 9 change blocks. | ||||
| 8 lines changed or deleted | 12 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||