< draft-ietf-jose-json-web-key-04.txt		draft-ietf-jose-json-web-key-05.txt >
	JOSE Working Group M. Jones		JOSE Working Group M. Jones
	Internet-Draft Microsoft		Internet-Draft Microsoft
	Intended status: Standards Track July 16, 2012		Intended status: Standards Track July 30, 2012
	Expires: January 17, 2013		Expires: January 31, 2013
	JSON Web Key (JWK)		JSON Web Key (JWK)
	draft-ietf-jose-json-web-key-04		draft-ietf-jose-json-web-key-05
	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 17, 2013.		This Internet-Draft will expire on January 31, 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 4, line 16 ¶		skipping to change at page 4, line 16 ¶
	3. Example JSON Web Key Set		3. Example JSON Web Key Set
	The following example JWK Set contains two public keys represented as		The following example JWK Set contains two public keys represented as
	JWKs: one using an Elliptic Curve algorithm and a second one using an		JWKs: one using an Elliptic Curve algorithm and a second one using an
	RSA algorithm. The first specifies that the key is to be used for		RSA algorithm. The first specifies that the key is to be used for
	encryption. Both provide a Key ID for key matching purposes. In		encryption. Both provide a Key ID for key matching purposes. In
	both cases, integers are represented using the base64url encoding of		both cases, integers are represented using the base64url encoding of
	their big endian representations. (Long lines are broken are for		their big endian representations. (Long lines are broken are for
	display purposes only.)		display purposes only.)
	{"keys":
	[
	{"alg":"EC",
	"crv":"P-256",
	"x":"MKBCTNIcKUSDii11ySs3526iDZ8AiTo7Tu6KPAqv7D4",
	"y":"4Etl6SRW2YiLUrN5vfvVHuhp7x8PxltmWWlbbM4IFyM",
	"use":"enc",
	"kid":"1"},
	{"alg":"RSA",		{"keys":
	"mod": "0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx		[
	4cbbfAAtVT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMs		{"alg":"EC",
	tn64tZ_2W-5JsGY4Hc5n9yBXArwl93lqt7_RN5w6Cf0h4QyQ5v-65YGjQR0_FDW2		"crv":"P-256",
	QvzqY368QQMicAtaSqzs8KJZgnYb9c7d0zgdAZHzu6qMQvRL5hajrn1n91CbOpbI		"x":"MKBCTNIcKUSDii11ySs3526iDZ8AiTo7Tu6KPAqv7D4",
	SD08qNLyrdkt-bFTWhAI4vMQFh6WeZu0fM4lFd2NcRwr3XPksINHaQ-G_xBniIqb		"y":"4Etl6SRW2YiLUrN5vfvVHuhp7x8PxltmWWlbbM4IFyM",
	w0Ls1jF44-csFCur-kEgU8awapJzKnqDKgw",		"use":"enc",
	"exp":"AQAB",		"kid":"1"},
	"kid":"2011-04-29"}
	]		{"alg":"RSA",
	}		"mod": "0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx
			4cbbfAAtVT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMs
			tn64tZ_2W-5JsGY4Hc5n9yBXArwl93lqt7_RN5w6Cf0h4QyQ5v-65YGjQR0_FDW2
			QvzqY368QQMicAtaSqzs8KJZgnYb9c7d0zgdAZHzu6qMQvRL5hajrn1n91CbOpbI
			SD08qNLyrdkt-bFTWhAI4vMQFh6WeZu0fM4lFd2NcRwr3XPksINHaQ-G_xBniIqb
			w0Ls1jF44-csFCur-kEgU8awapJzKnqDKgw",
			"exp":"AQAB",
			"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.
	In addition to the common parameters, each JWK will have members that		In addition to the common parameters, each JWK will have members that
	are specific to the key being represented. These members represent		are specific to the key being represented. These members represent
	the parameters of the key. Section 5 of the JSON Web Algorithms		the parameters of the key. Section 5 of the JSON Web Algorithms
	skipping to change at page 10, line 16 ¶		skipping to change at page 10, line 16 ¶
	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]
	Reagle, J., Hirsch, F., Cantor, S., Roessler, T.,		Solo, D., Datta, P., Hirsch, F., Cantor, S., Reagle, J.,
	Eastlake, D., Yiu, K., Solo, D., and P. Datta, "XML		Roessler, T., Eastlake, D., and K. Yiu, "XML Signature
	Signature Syntax and Processing Version 2.0", World Wide		Syntax and Processing Version 2.0", World Wide Web
	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		9.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)", July 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)", July 2012.
	skipping to change at page 10, line 48 ¶		skipping to change at page 10, line 48 ¶
	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		Appendix B. 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 ]]
			-05
			o Indented artwork elements to better distinguish them from the body
			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]
	for its security considerations.		for its security considerations.
	o Added this language to Registration Templates: "This name is case		o Added this language to Registration Templates: "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."
End of changes. 8 change blocks.
	27 lines changed or deleted		33 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/