< draft-ietf-jose-json-web-encryption-22.txt		draft-ietf-jose-json-web-encryption-23.txt >
	JOSE Working Group M. Jones		JOSE Working Group M. Jones
	Internet-Draft Microsoft		Internet-Draft Microsoft
	Intended status: Standards Track E. Rescorla		Intended status: Standards Track E. Rescorla
	Expires: September 3, 2014 RTFM		Expires: September 4, 2014 RTFM
	J. Hildebrand		J. Hildebrand
	Cisco		Cisco
	March 2, 2014		March 3, 2014
	JSON Web Encryption (JWE)		JSON Web Encryption (JWE)
	draft-ietf-jose-json-web-encryption-22		draft-ietf-jose-json-web-encryption-23
	Abstract		Abstract
	JSON Web Encryption (JWE) represents encrypted content using		JSON Web Encryption (JWE) represents encrypted content using
	JavaScript Object Notation (JSON) based data structures.		JavaScript Object Notation (JSON) based data structures.
	Cryptographic algorithms and identifiers for use with this		Cryptographic algorithms and identifiers for use with this
	specification are described in the separate JSON Web Algorithms (JWA)		specification are described in the separate JSON Web Algorithms (JWA)
	specification and IANA registries defined by that specification.		specification and IANA registries defined by that specification.
	Related digital signature and MAC capabilities are described in the		Related digital signature and MAC capabilities are described in the
	separate JSON Web Signature (JWS) specification.		separate JSON Web Signature (JWS) specification.
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	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 3, 2014.		This Internet-Draft will expire on September 4, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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 15, line 33 ¶		skipping to change at page 15, line 33 ¶
	4.1.10. "typ" (Type) Header Parameter		4.1.10. "typ" (Type) Header Parameter
	This parameter has the same meaning, syntax, and processing rules as		This parameter has the same meaning, syntax, and processing rules as
	the "typ" Header Parameter defined in Section 4.1.8 of [JWS], except		the "typ" Header Parameter defined in Section 4.1.8 of [JWS], except
	that the type is of this complete JWE object.		that the type is of this complete JWE object.
	4.1.11. "cty" (Content Type) Header Parameter		4.1.11. "cty" (Content Type) Header Parameter
	This parameter has the same meaning, syntax, and processing rules as		This parameter has the same meaning, syntax, and processing rules as
	the "cty" Header Parameter defined in Section 4.1.9 of [JWS], except		the "cty" Header Parameter defined in Section 4.1.9 of [JWS], except
	that the type is of the secured content (the payload).		that the type is of the secured content (the plaintext).
	4.1.12. "crit" (Critical) Header Parameter		4.1.12. "crit" (Critical) Header Parameter
	This parameter has the same meaning, syntax, and processing rules as		This parameter has the same meaning, syntax, and processing rules as
	the "crit" Header Parameter defined in Section 4.1.10 of [JWS],		the "crit" Header Parameter defined in Section 4.1.10 of [JWS],
	except that JWE Header Parameters are being referred to, rather than		except that JWE Header Parameters are being referred to, rather than
	JWS Header Parameters.		JWS Header Parameters.
	4.2. Public Header Parameter Names		4.2. Public Header Parameter Names
	skipping to change at page 45, line 44 ¶		skipping to change at page 45, line 44 ¶
	Hannes Tschofenig, and Sean Turner.		Hannes Tschofenig, and Sean Turner.
	Jim Schaad and Karen O'Donoghue chaired the JOSE working group and		Jim Schaad and Karen O'Donoghue chaired the JOSE working group and
	Sean Turner and Stephen Farrell served as Security area directors		Sean Turner and Stephen Farrell served as Security area directors
	during the creation of this specification.		during the creation of this specification.
	Appendix D. Document History		Appendix D. 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 ]]
	-22		-23
			o Corrected a use of the word "payload" to "plaintext".
			-22
	o Corrected RFC 2119 terminology usage.		o Corrected RFC 2119 terminology usage.
	o Replaced references to draft-ietf-json-rfc4627bis with RFC 7158.		o Replaced references to draft-ietf-json-rfc4627bis with RFC 7158.
	-21		-21
	o Changed some references from being normative to informative,		o Changed some references from being normative to informative,
	addressing issue #90.		addressing issue #90.
	o Applied review comments to the JSON Serialization section,		o Applied review comments to the JSON Serialization section,
	addressing issue #178.		addressing issue #178.
	-20		-20
	o Made terminology definitions more consistent, addressing issue		o Made terminology definitions more consistent, addressing issue
	#165.		#165.
End of changes. 8 change blocks.
	6 lines changed or deleted		10 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/