< draft-jones-jose-jwe-json-serialization-03.txt		draft-jones-jose-jwe-json-serialization-04.txt >
	JOSE Working Group M. Jones		JOSE Working Group M. Jones
	Internet-Draft Microsoft		Internet-Draft Microsoft
	Intended status: Standards Track November 6, 2012		Intended status: Standards Track December 27, 2012
	Expires: May 10, 2013		Expires: June 30, 2013
	JSON Web Encryption JSON Serialization (JWE-JS)		JSON Web Encryption JSON Serialization (JWE-JS)
	draft-jones-jose-jwe-json-serialization-03		draft-jones-jose-jwe-json-serialization-04
	Abstract		Abstract
	The JSON Web Encryption JSON Serialization (JWE-JS) is a means of		The JSON Web Encryption JSON Serialization (JWE-JS) is a means of
	representing encrypted content using JavaScript Object Notation		representing encrypted content using JavaScript Object Notation
	(JSON) data structures. This specification describes a means of		(JSON) 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
	JWE specification, which uses a compact serialization with a URL-safe		JWE specification, which uses a compact serialization with a URL-safe
	representation). It enables the same content to be encrypted to		representation). It enables the same content to be encrypted to
	multiple parties (unlike JWE). Cryptographic algorithms and		multiple parties (unlike JWE). Cryptographic algorithms and
	skipping to change at page 1, line 41 ¶		skipping to change at page 1, line 41 ¶
	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 May 10, 2013.		This Internet-Draft will expire on June 30, 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 2, line 27 ¶		skipping to change at page 2, line 27 ¶
	3. JSON Serialization . . . . . . . . . . . . . . . . . . . . . . 3		3. JSON Serialization . . . . . . . . . . . . . . . . . . . . . . 3
	4. Example JWE-JS . . . . . . . . . . . . . . . . . . . . . . . . 5		4. Example JWE-JS . . . . . . . . . . . . . . . . . . . . . . . . 5
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
	6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6		6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6		7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	7.1. Normative References . . . . . . . . . . . . . . . . . . . 6		7.1. Normative References . . . . . . . . . . . . . . . . . . . 6
	7.2. Informative References . . . . . . . . . . . . . . . . . . 7		7.2. Informative References . . . . . . . . . . . . . . . . . . 7
	Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 7		Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 7
	Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 7		Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 7
	Appendix C. Document History . . . . . . . . . . . . . . . . . . . 7		Appendix C. Document History . . . . . . . . . . . . . . . . . . . 7
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9
	1. Introduction		1. Introduction
	The JSON Web Encryption JSON Serialization (JWE-JS) is a format for		The JSON Web Encryption JSON Serialization (JWE-JS) is a format for
	representing encrypted content as a JavaScript Object Notation (JSON)		representing encrypted content as a JavaScript Object Notation (JSON)
	[RFC4627] object. It enables the same content to be encrypted to		[RFC4627] object. It enables the same content to be encrypted to
	multiple parties (unlike JWE [JWE].) The encryption mechanisms are		multiple parties (unlike JWE [JWE].) The encryption mechanisms are
	independent of the type of content being encrypted. Cryptographic		independent of the type of content being encrypted. Cryptographic
	algorithms and identifiers used with this specification are described		algorithms and identifiers used with this specification are described
	in the separate JSON Web Algorithms (JWA) [JWA] specification. The		in the separate JSON Web Algorithms (JWA) [JWA] specification. The
	skipping to change at page 6, line 48 ¶		skipping to change at page 6, line 48 ¶
	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 Encryption (JWE) [JWE] specification.		those for the JSON Web Encryption (JWE) [JWE] specification.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[JWA] Jones, M., "JSON Web Algorithms (JWA)", November 2012.		[JWA] Jones, M., "JSON Web Algorithms (JWA)",
			draft-ietf-jose-json-web-algorithms (work in progress),
			December 2012.
	[JWE] Jones, M., Rescorla, E., and J. Hildebrand, "JSON Web		[JWE] Jones, M., Rescorla, E., and J. Hildebrand, "JSON Web
	Encryption (JWE)", November 2012.		Encryption (JWE)", draft-ietf-jose-json-web-encryption
			(work in progress), December 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
	[I-D.rescorla-jsms]		[I-D.rescorla-jsms]
	Rescorla, E. and J. Hildebrand, "JavaScript Message		Rescorla, E. and J. Hildebrand, "JavaScript Message
	Security Format", draft-rescorla-jsms-00 (work in		Security Format", draft-rescorla-jsms-00 (work in
	progress), March 2011.		progress), March 2011.
	[JSE] Bradley, J. and N. Sakimura (editor), "JSON Simple		[JSE] Bradley, J. and N. Sakimura (editor), "JSON Simple
	Encryption", September 2010.		Encryption", September 2010.
	[JWS-JS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web		[JWS-JS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web
	Signature JSON Serialization (JWS-JS)", November 2012.		Signature JSON Serialization (JWS-JS)",
			draft-jones-jose-jws-json-serialization (work in
			progress), December 2012.
	Appendix A. Acknowledgements		Appendix A. Acknowledgements
	JSON serializations for encrypted content were previously explored by		JSON serializations for encrypted content were previously explored by
	JSON Simple Encryption [JSE] and JavaScript Message Security Format		JSON Simple Encryption [JSE] and JavaScript Message Security Format
	[I-D.rescorla-jsms].		[I-D.rescorla-jsms].
	Appendix B. Open Issues		Appendix B. Open Issues
	[[ 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 JWE spec.		o Track changes that occur in the JWE 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 ]]
			-04
			o Added seriesInfo information to Internet Draft references.
	-03		-03
	o Updated values for example AES CBC calculations.		o Updated values for example AES CBC calculations.
	-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.
	o Promoted Initialization Vector from being a header parameter to		o Promoted Initialization Vector from being a header parameter to
	being a top-level JWE element. This saves approximately 16 bytes		being a top-level JWE element. This saves approximately 16 bytes
	in the compact serialization, which is a significant savings for		in the compact serialization, which is a significant savings for
	some use cases. Promoting the Initialization Vector out of the		some use cases. Promoting the Initialization Vector out of the
	header also avoids repeating this shared value in the JSON		header also avoids repeating this shared value in the JSON
	serialization.		serialization.
	skipping to change at page 8, line 39 ¶		skipping to change at page 8, line 49 ¶
	draft-jones-json-web-encryption-json-serialization-02		draft-jones-json-web-encryption-json-serialization-02
	o Updated examples to track updated algorithm properties in the JWA		o Updated examples to track updated algorithm properties in the JWA
	spec.		spec.
	o Tracked editorial changes made to the JWE spec.		o Tracked editorial changes made to the JWE spec.
	draft-jones-json-web-encryption-json-serialization-01		draft-jones-json-web-encryption-json-serialization-01
	o Tracked changes between JOSE JWE draft -00 and -01, which added an		o Tracked changes between JOSE JWE draft -00 and -01, which added an
	integrity check for non-AEAD algorithms.		integrity check for non-Authenticated Encryption algorithms.
	draft-jones-json-web-encryption-json-serialization-00		draft-jones-json-web-encryption-json-serialization-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.
	Author's Address		Author's Address
	Michael B. Jones		Michael B. Jones
	Microsoft		Microsoft
	Email: mbj@microsoft.com		Email: mbj@microsoft.com
End of changes. 11 change blocks.
	10 lines changed or deleted		18 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/