< draft-jones-jose-jws-json-serialization-02.txt   draft-jones-jose-jws-json-serialization-03.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: April 18, 2013 independent Expires: May 10, 2013 independent
N. Sakimura N. Sakimura
Nomura Research Institute Nomura Research Institute
October 15, 2012 November 6, 2012
JSON Web Signature JSON Serialization (JWS-JS) JSON Web Signature JSON Serialization (JWS-JS)
draft-jones-jose-jws-json-serialization-02 draft-jones-jose-jws-json-serialization-03
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 Message representing content secured with digital signatures or Message
Authentication Codes (MACs) using JavaScript Object Notation (JSON) Authentication Codes (MACs) using JavaScript Object Notation (JSON)
data structures. This specification describes a means of data structures. This specification describes a means of
representing secured content as a JSON data object (as opposed to the representing secured content as a JSON data object (as opposed to the
JWS specification, which uses a compact serialization with a URL-safe JWS specification, which uses a compact serialization with a URL-safe
representation). It enables multiple digital signatures and/or MACs representation). It enables multiple digital signatures and/or MACs
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 April 18, 2013. This Internet-Draft will expire on May 10, 2013.
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 5, line 43 skipping to change at page 5, line 43
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)", October 2012. [JWA] Jones, M., "JSON Web Algorithms (JWA)", November 2012.
[JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web [JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web
Signature (JWS)", October 2012. Signature (JWS)", November 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)", October 2012. (JWE-JS)", November 2012.
[MagicSignatures] [MagicSignatures]
Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic
Signatures", January 2011. 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].
skipping to change at page 6, line 37 skipping to change at page 6, line 37
[[ to be removed by the RFC editor before publication as an RFC ]] [[ to be removed by the RFC editor before publication as an RFC ]]
The following items remain to be considered or done in this draft: The following items remain to be considered or done in this draft:
o Track changes that occur in the JWS spec. o Track changes that occur in the JWS spec.
Appendix C. Document History Appendix C. Document History
[[ to be removed by the RFC editor before publication as an RFC ]] [[ to be removed by the RFC editor before publication as an RFC ]]
-03
o Updated references.
-02 -02
o Changed to use an array of structures for per-recipient values, o Changed to use an array of structures for per-recipient values,
rather than a set of parallel arrays. rather than a set of parallel arrays.
-01 -01
o Generalized language to refer to Message Authentication Codes o Generalized language to refer to Message Authentication Codes
(MACs) rather than Hash-based Message Authentication Codes (MACs) rather than Hash-based Message Authentication Codes
(HMACs). (HMACs).
 End of changes. 8 change blocks. 
7 lines changed or deleted 11 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/