< draft-ietf-jose-json-web-key-05.txt		draft-ietf-jose-json-web-key-06.txt >
	JOSE Working Group M. Jones		JOSE Working Group M. Jones
	Internet-Draft Microsoft		Internet-Draft Microsoft
	Intended status: Standards Track July 30, 2012		Intended status: Standards Track October 15, 2012
	Expires: January 31, 2013		Expires: April 18, 2013
	JSON Web Key (JWK)		JSON Web Key (JWK)
	draft-ietf-jose-json-web-key-05		draft-ietf-jose-json-web-key-06
	Abstract		Abstract
	A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data		A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data
	structure that represents a public key. This specification also		structure that represents a public key. This specification also
	defines a JSON Web Key Set (JWK Set) JSON data structure for		defines a JSON Web Key Set (JWK Set) JSON data structure for
	representing a set of JWKs. Cryptographic algorithms and identifiers		representing a set of JWKs. Cryptographic algorithms and identifiers
	for use with this specification are described in the separate JSON		for use with this specification are described in the separate JSON
	Web Algorithms (JWA) specification.		Web Algorithms (JWA) specification.
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	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 January 31, 2013.		This Internet-Draft will expire on April 18, 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 25 ¶		skipping to change at page 2, line 25 ¶
	4.3. "kid" (Key ID) Parameter . . . . . . . . . . . . . . . . . 5		4.3. "kid" (Key ID) Parameter . . . . . . . . . . . . . . . . . 5
	5. JSON Web Key Set (JWK Set) Format . . . . . . . . . . . . . . 6		5. JSON Web Key Set (JWK Set) Format . . . . . . . . . . . . . . 6
	5.1. "keys" (JSON Web Key Set) Parameter . . . . . . . . . . . 6		5.1. "keys" (JSON Web Key Set) Parameter . . . . . . . . . . . 6
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
	6.1. JSON Web Key Parameters Registry . . . . . . . . . . . . . 7		6.1. JSON Web Key Parameters Registry . . . . . . . . . . . . . 7
	6.1.1. Registration Template . . . . . . . . . . . . . . . . 7		6.1.1. Registration Template . . . . . . . . . . . . . . . . 7
	6.1.2. Initial Registry Contents . . . . . . . . . . . . . . 7		6.1.2. Initial Registry Contents . . . . . . . . . . . . . . 7
	6.2. JSON Web Key Set Parameters Registry . . . . . . . . . . . 8		6.2. JSON Web Key Set Parameters Registry . . . . . . . . . . . 8
	6.2.1. Registration Template . . . . . . . . . . . . . . . . 8		6.2.1. Registration Template . . . . . . . . . . . . . . . . 8
	6.2.2. Initial Registry Contents . . . . . . . . . . . . . . 8		6.2.2. Initial Registry Contents . . . . . . . . . . . . . . 8
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 9		7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	8. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 9		8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9		8.1. Normative References . . . . . . . . . . . . . . . . . . . 9
	9.1. Normative References . . . . . . . . . . . . . . . . . . . 9		8.2. Informative References . . . . . . . . . . . . . . . . . . 9
	9.2. Informative References . . . . . . . . . . . . . . . . . . 10
	Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 10		Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 10
	Appendix B. Document History . . . . . . . . . . . . . . . . . . 10		Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 10
			Appendix C. Document History . . . . . . . . . . . . . . . . . . 10
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12
	1. Introduction		1. Introduction
	A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) [RFC4627]		A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) [RFC4627]
	data structure that represents a public key. This specification also		data structure that represents a public key. This specification also
	defines a JSON Web Key Set (JWK Set) JSON data structure for		defines a JSON Web Key Set (JWK Set) JSON data structure for
	representing a set of JWKs. Cryptographic algorithms and identifiers		representing a set of JWKs. Cryptographic algorithms and identifiers
	for use with this specification are described in the separate JSON		for use with this specification are described in the separate JSON
	Web Algorithms (JWA) [JWA] specification.		Web Algorithms (JWA) [JWA] specification.
	skipping to change at page 4, line 33 ¶		skipping to change at page 4, line 33 ¶
	"use":"enc",		"use":"enc",
	"kid":"1"},		"kid":"1"},
	{"alg":"RSA",		{"alg":"RSA",
	"mod": "0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx		"mod": "0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx
	4cbbfAAtVT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMs		4cbbfAAtVT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMs
	tn64tZ_2W-5JsGY4Hc5n9yBXArwl93lqt7_RN5w6Cf0h4QyQ5v-65YGjQR0_FDW2		tn64tZ_2W-5JsGY4Hc5n9yBXArwl93lqt7_RN5w6Cf0h4QyQ5v-65YGjQR0_FDW2
	QvzqY368QQMicAtaSqzs8KJZgnYb9c7d0zgdAZHzu6qMQvRL5hajrn1n91CbOpbI		QvzqY368QQMicAtaSqzs8KJZgnYb9c7d0zgdAZHzu6qMQvRL5hajrn1n91CbOpbI
	SD08qNLyrdkt-bFTWhAI4vMQFh6WeZu0fM4lFd2NcRwr3XPksINHaQ-G_xBniIqb		SD08qNLyrdkt-bFTWhAI4vMQFh6WeZu0fM4lFd2NcRwr3XPksINHaQ-G_xBniIqb
	w0Ls1jF44-csFCur-kEgU8awapJzKnqDKgw",		w0Ls1jF44-csFCur-kEgU8awapJzKnqDKgw",
	"exp":"AQAB",		"xpo":"AQAB",
	"kid":"2011-04-29"}		"kid":"2011-04-29"}
	]		]
	}		}
	4. JSON Web Key (JWK) Format		4. JSON Web Key (JWK) Format
	A JSON Web Key (JWK) is a JSON object containing specific members, as		A JSON Web Key (JWK) is a JSON object containing specific members, as
	specified below. Those members that are common to all key types are		specified below. Those members that are common to all key types are
	defined below.		defined below.
	skipping to change at page 5, line 21 ¶		skipping to change at page 5, line 21 ¶
	distinct. Member names SHOULD either be registered in the IANA JSON		distinct. Member names SHOULD either be registered in the IANA JSON
	Web Key Parameters registry Section 6.1 or be URIs that contain a		Web Key Parameters registry Section 6.1 or be URIs that contain a
	Collision Resistant Namespace.		Collision Resistant Namespace.
	4.1. "alg" (Algorithm Family) Parameter		4.1. "alg" (Algorithm Family) Parameter
	The "alg" (algorithm family) member identifies the cryptographic		The "alg" (algorithm family) member identifies the cryptographic
	algorithm family used with the key. "alg" values SHOULD either be		algorithm family used with the key. "alg" values SHOULD either be
	registered in the IANA JSON Web Key Algorithm Families registry [JWA]		registered in the IANA JSON Web Key Algorithm Families registry [JWA]
	or be a URI that contains a Collision Resistant Namespace. The "alg"		or be a URI that contains a Collision Resistant Namespace. The "alg"
	value is a case sensitive string.		value is a case sensitive string. This member is REQUIRED.
	A list of defined "alg" values can be found in the IANA JSON Web Key		A list of defined "alg" values can be found in the IANA JSON Web Key
	Algorithm Families registry [JWA]; the initial contents of this		Algorithm Families registry [JWA]; the initial contents of this
	registry is the values defined in Section 5.1 of the JSON Web		registry are the values defined in Section 5.1 of the JSON Web
	Algorithms (JWA) [JWA] specification.		Algorithms (JWA) [JWA] specification.
	Additional members used with these "alg" values can be found in the		Additional members used with these "alg" values can be found in the
	IANA JSON Web Key Parameters registry Section 6.1; the initial		IANA JSON Web Key Parameters registry Section 6.1; the initial
	contents of this registry is the values defined in Sections 5.2 and		contents of this registry are the values defined in Sections 5.2 and
	5.3 of the JSON Web Algorithms (JWA) [JWA] specification.		5.3 of the JSON Web Algorithms (JWA) [JWA] specification.
	4.2. "use" (Key Use) Parameter		4.2. "use" (Key Use) Parameter
	The "use" (key use) member identifies the intended use of the key.		The "use" (key use) member identifies the intended use of the key.
	Values defined by this specification are:		Values defined by this specification are:
	o "sig" (signature)		o "sig" (signature)
	o "enc" (encryption)		o "enc" (encryption)
	Other values MAY be used. The "use" value is a case sensitive		Other values MAY be used. The "use" value is a case sensitive
	string. This member is OPTIONAL.		string. This member is OPTIONAL.
	4.3. "kid" (Key ID) Parameter		4.3. "kid" (Key ID) Parameter
	The "kid" (key ID) member can be used to match a specific key. This		The "kid" (key ID) member can be used to match a specific key. This
	can be used, for instance, to choose among a set of keys within the		can be used, for instance, to choose among a set of keys within a JWK
	JWK during key rollover. The interpretation of the "kid" value is		Set during key rollover. The interpretation of the "kid" value is
	unspecified. Key ID values within a JWK Set need not be unique. The		unspecified. Key ID values within a JWK Set need not be unique. The
	"kid" value is a case sensitive string. This member is OPTIONAL.		"kid" value is a case sensitive string. This member is OPTIONAL.
	When used with JWS or JWE, the "kid" value MAY be used to match a JWS		When used with JWS or JWE, the "kid" value MAY be used to match a JWS
	or JWE "kid" header parameter value.		or JWE "kid" header parameter value.
	In some contexts, different keys using the same Key ID value might be		In some contexts, different keys using the same Key ID value might be
	present, with the keys being disambiguated using other information,		present, with the keys being disambiguated using other information,
	such as the "alg" or "use" values. For example, imagine "kid" values		such as the "alg" or "use" values. For example, imagine "kid" values
	like "Current", "Upcoming", and "Deprecated", used for key rollover		like "Current", "Upcoming", and "Deprecated", used for key rollover
	skipping to change at page 6, line 45 ¶		skipping to change at page 6, line 45 ¶
	The value of the "keys" (JSON Web Key Set) member is an array of JSON		The value of the "keys" (JSON Web Key Set) member is an array of JSON
	Web Key (JWK) values. This member is REQUIRED.		Web Key (JWK) values. This member is REQUIRED.
	6. IANA Considerations		6. IANA Considerations
	The following registration procedure is used for all the registries		The following registration procedure is used for all the registries
	established by this specification.		established by this specification.
	Values are registered with a Specification Required [RFC5226] after a		Values are registered with a Specification Required [RFC5226] after a
	two week review period on the [TBD]@ietf.org mailing list, on the		two-week review period on the [TBD]@ietf.org mailing list, on the
	advice of one or more Designated Experts. However, to allow for the		advice of one or more Designated Experts. However, to allow for the
	allocation of values prior to publication, the Designated Expert(s)		allocation of values prior to publication, the Designated Expert(s)
	may approve registration once they are satisfied that such a		may approve registration once they are satisfied that such a
	specification will be published.		specification will be published.
	Registration requests must be sent to the [TBD]@ietf.org mailing list		Registration requests must be sent to the [TBD]@ietf.org mailing list
	for review and comment, with an appropriate subject (e.g., "Request		for review and comment, with an appropriate subject (e.g., "Request
	for access token type: example"). [[ Note to RFC-EDITOR: The name of		for access token type: example"). [[ Note to RFC-EDITOR: The name of
	the mailing list should be determined in consultation with the IESG		the mailing list should be determined in consultation with the IESG
	and IANA. Suggested name: jose-reg-review. ]]		and IANA. Suggested name: jose-reg-review. ]]
	Within the review period, the Designated Expert(s) will either		Within the review period, the Designated Expert(s) will either
	approve or deny the registration request, communicating this decision		approve or deny the registration request, communicating this decision
	to the review list and IANA. Denials should include an explanation		to the review list and IANA. Denials should include an explanation
	and, if applicable, suggestions as to how to make the request		and, if applicable, suggestions as to how to make the request
	successful.		successful.
	IANA must only accept registry updates from the Designated Expert(s),		IANA must only accept registry updates from the Designated Expert(s)
	and should direct all requests for registration to the review mailing		and should direct all requests for registration to the review mailing
	list.		list.
	6.1. JSON Web Key Parameters Registry		6.1. JSON Web Key Parameters Registry
	This specification establishes the IANA JSON Web Key Parameters		This specification establishes the IANA JSON Web Key Parameters
	registry for reserved JWK parameter names. The registry records the		registry for reserved JWK parameter names. The registry records the
	reserved parameter name and a reference to the specification that		reserved parameter name and a reference to the specification that
	defines it. This specification registers the parameter names defined		defines it. This specification registers the parameter names defined
	in Section 4.		in Section 4.
	6.1.1. Registration Template		6.1.1. Registration Template
	Parameter Name:		Parameter Name:
	The name requested (e.g., "example"). This name is case		The name requested (e.g., "example"). This name is case
	sensitive. Names that match other registered names in a case		sensitive. Names that match other registered names in a case
	insensitive manner SHOULD NOT be accepted.		insensitive manner SHOULD NOT be accepted.
	Change Controller:		Change Controller:
	For standards-track RFCs, state "IETF". For others, give the name		For Standards Track RFCs, state "IETF". For others, give the name
	of the responsible party. Other details (e.g., postal address,		of the responsible party. Other details (e.g., postal address,
	e-mail address, home page URI) may also be included.		email address, home page URI) may also be included.
	Specification Document(s):		Specification Document(s):
	Reference to the document that specifies the parameter, preferably		Reference to the document(s) that specify the parameter,
	including a URI that can be used to retrieve a copy of the		preferably including URI(s) that can be used to retrieve copies of
	document. An indication of the relevant sections may also be		the document(s). An indication of the relevant sections may also
	included, but is not required.		be included but is not required.
	6.1.2. Initial Registry Contents		6.1.2. Initial Registry Contents
	o Parameter Name: "alg"		o Parameter Name: "alg"
	o Change Controller: IETF		o Change Controller: IETF
	o Specification Document(s): Section 4.1 of [[ this document ]]		o Specification Document(s): Section 4.1 of [[ this document ]]
	o Parameter Name: "use"		o Parameter Name: "use"
	o Change Controller: IETF		o Change Controller: IETF
	o Specification Document(s): Section 4.2 of [[ this document ]]		o Specification Document(s): Section 4.2 of [[ this document ]]
	o Parameter Name: "kid"		o Parameter Name: "kid"
	o Change Controller: IETF		o Change Controller: IETF
	o Specification Document(s): Section 4.3 of [[ this document ]]		o Specification Document(s): Section 4.3 of [[ this document ]]
	6.2. JSON Web Key Set Parameters Registry		6.2. JSON Web Key Set Parameters Registry
	This specification establishes the IANA JSON Web Key Set Parameters		This specification establishes the IANA JSON Web Key Set Parameters
	registry for reserved JWK Set parameter names. The registry records		registry for reserved JWK Set parameter names. The registry records
	the reserved parameter name and a reference to the specification that		the reserved parameter name and a reference to the specification that
	defines it. This specification registers the parameter names defined		defines it. This specification registers the parameter names defined
	in Section 5.		in Section 5.
	6.2.1. Registration Template		6.2.1. Registration Template
	Parameter Name:		Parameter Name:
	The name requested (e.g., "example"). This name is case		The name requested (e.g., "example"). This name is case
	sensitive. Names that match other registered names in a case		sensitive. Names that match other registered names in a case
	insensitive manner SHOULD NOT be accepted.		insensitive manner SHOULD NOT be accepted.
	Change Controller:		Change Controller:
	For standards-track RFCs, state "IETF". For others, give the name		For Standards Track RFCs, state "IETF". For others, give the name
	of the responsible party. Other details (e.g., postal address,		of the responsible party. Other details (e.g., postal address,
	e-mail address, home page URI) may also be included.		email address, home page URI) may also be included.
	Specification Document(s):		Specification Document(s):
	Reference to the document that specifies the parameter, preferably		Reference to the document(s) that specify the parameter,
	including a URI that can be used to retrieve a copy of the		preferably including URI(s) that can be used to retrieve copies of
	document. An indication of the relevant sections may also be		the document(s). An indication of the relevant sections may also
	included, but is not required.		be included but is not required.
	6.2.2. Initial Registry Contents		6.2.2. Initial Registry Contents
	o Parameter Name: "keys"		o Parameter Name: "keys"
	o Change Controller: IETF		o Change Controller: IETF
	o Specification Document(s): Section 5.1 of [[ this document ]]		o Specification Document(s): Section 5.1 of [[ this document ]]
	7. Security Considerations		7. Security Considerations
	All of the security issues faced by any cryptographic application		All of the security issues faced by any cryptographic application
	must be faced by a JWS/JWE/JWK agent. Among these issues are		must be faced by a JWS/JWE/JWK agent. Among these issues are
	protecting the user's private key, preventing various attacks, and		protecting the user's private key, preventing various attacks, and
	helping the user avoid mistakes such as inadvertently encrypting a		helping the user avoid mistakes such as inadvertently encrypting a
	message for the wrong recipient. The entire list of security		message for the wrong recipient. The entire list of security
	considerations is beyond the scope of this document, but some		considerations is beyond the scope of this document, but some
	skipping to change at page 9, line 26 ¶		skipping to change at page 9, line 20 ¶
	received.		received.
	Per Section 4.3, applications should not assume that "kid" values are		Per Section 4.3, applications should not assume that "kid" values are
	unique within a JWK Set.		unique within a JWK Set.
	The security considerations in XML DSIG 2.0		The security considerations in XML DSIG 2.0
	[W3C.CR-xmldsig-core2-20120124], about public key representations		[W3C.CR-xmldsig-core2-20120124], about public key representations
	also apply to this specification, other than those that are XML		also apply to this specification, other than those that are XML
	specific.		specific.
	8. Open Issues		8. References
	[[ to be removed by the RFC editor before publication as an RFC ]]
	The following items remain to be considered or done in this draft:
	o There was a request to define the key use value "both". This
	would seem to be semantically redundant, since omitting a key use
	value effectively allows unconstrained use of the key. For what
	it's worth, omitting the use parameter is how XMLDSIG expresses
	the same thing, so we're currently parallel to XMLDSIG.
	Furthermore, legitimizing the use of a single key for both signing
	and encryption seems like it may be a bad idea, since there's a
	potential vulnerability with using the same key for both signing
	and encryption.
	9. References
	9.1. Normative References		8.1. Normative References
	[JWA] Jones, M., "JSON Web Algorithms (JWA)", July 2012.		[JWA] Jones, M., "JSON Web Algorithms (JWA)", October 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.
	[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data		[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
	Encodings", RFC 4648, October 2006.		Encodings", RFC 4648, October 2006.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	May 2008.		May 2008.
	[W3C.CR-xmldsig-core2-20120124]		[W3C.CR-xmldsig-core2-20120124]
	Solo, D., Datta, P., Hirsch, F., Cantor, S., Reagle, J.,		Roessler, T., Yiu, K., Solo, D., Reagle, J., Datta, P.,
	Roessler, T., Eastlake, D., and K. Yiu, "XML Signature		Eastlake, D., Hirsch, F., and S. Cantor, "XML Signature
	Syntax and Processing Version 2.0", World Wide Web		Syntax and Processing Version 2.0", World Wide Web
	Consortium CR CR-xmldsig-core2-20120124, January 2012,		Consortium CR CR-xmldsig-core2-20120124, January 2012,
	<http://www.w3.org/TR/2012/CR-xmldsig-core2-20120124>.		<http://www.w3.org/TR/2012/CR-xmldsig-core2-20120124>.
	9.2. Informative References		8.2. Informative References
	[JWE] Jones, M., Rescorla, E., and J. Hildebrand, "JSON Web		[JWE] Jones, M., Rescorla, E., and J. Hildebrand, "JSON Web
	Encryption (JWE)", July 2012.		Encryption (JWE)", October 2012.
	[JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web		[JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web
	Signature (JWS)", July 2012.		Signature (JWS)", October 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.
	[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally		[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
	Unique IDentifier (UUID) URN Namespace", RFC 4122,		Unique IDentifier (UUID) URN Namespace", RFC 4122,
	July 2005.		July 2005.
	Appendix A. Acknowledgements		Appendix A. Acknowledgements
	A JSON representation for RSA public keys was previously introduced		A JSON representation for RSA public keys was previously introduced
	by John Panzer, Ben Laurie, and Dirk Balfanz in Magic Signatures		by John Panzer, Ben Laurie, and Dirk Balfanz in Magic Signatures
	[MagicSignatures].		[MagicSignatures].
	Appendix B. Document History		Jim Schaad and Karen O'Donoghue chaired the JOSE working group and
			Sean Turner and Stephen Farrell served as Security area directors
			during the creation of this specification.
			Appendix B. Open Issues
			[[ to be removed by the RFC editor before publication as an RFC ]]
			The following items remain to be considered or done in this draft:
			o No known open issues.
			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 ]]
			-06
			o Changed the name of the JWK RSA exponent parameter from "exp" to
			"xpo" so as to allow the potential use of the name "exp" for a
			future extension that might define an expiration parameter for
			keys. (The "exp" name is already used for this purpose in the JWT
			specification.)
			o Clarify that the "alg" (algorithm family) member is REQUIRED.
			o Correct an instance of "JWK" that should have been "JWK Set".
			o Applied changes made by the RFC Editor to RFC 6749's registry
			language to this specification.
	-05		-05
	o Indented artwork elements to better distinguish them from the body		o Indented artwork elements to better distinguish them from the body
	text.		text.
	-04		-04
	o Refer to the registries as the primary sources of defined values		o Refer to the registries as the primary sources of defined values
	and then secondarily reference the sections defining the initial		and then secondarily reference the sections defining the initial
	contents of the registries.		contents of the registries.
	o Normatively reference XML DSIG 2.0 [W3C.CR-xmldsig-core2-20120124]		o Normatively reference XML DSIG 2.0 [W3C.CR-xmldsig-core2-20120124]
End of changes. 35 change blocks.
	62 lines changed or deleted		67 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/