< draft-ietf-jose-json-web-key-00.txt		draft-ietf-jose-json-web-key-01.txt >
	JOSE Working Group M. Jones		JOSE Working Group M. Jones
	Internet-Draft Microsoft		Internet-Draft Microsoft
	Intended status: Standards Track January 16, 2012		Intended status: Standards Track March 12, 2012
	Expires: July 19, 2012		Expires: September 13, 2012
	JSON Web Key (JWK)		JSON Web Key (JWK)
	draft-ietf-jose-json-web-key-00		draft-ietf-jose-json-web-key-01
	Abstract		Abstract
	A JSON Web Key (JWK) is a JSON data structure that represents a set		A JSON Web Key (JWK) is a JSON data structure that represents a set
	of public keys.		of public keys.
	Requirements Language		Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	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 July 19, 2012.		This Internet-Draft will expire on September 13, 2012.
	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 7, line 25 ¶		skipping to change at page 7, line 25 ¶
	No IANA actions are required by this specification.		No IANA actions are required by this specification.
	7. Security Considerations		7. Security Considerations
	TBD		TBD
	8. Open Issues and Things To Be Done (TBD)		8. Open Issues and Things To Be Done (TBD)
	The following items remain to be done in this draft:		The following items remain to be done in this draft:
			o Consider how additional key families would be added.
	o Write the Security Considerations section.		o Write the Security Considerations section.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[FIPS.186-3]		[FIPS.186-3]
	National Institute of Standards and Technology, "Digital		National Institute of Standards and Technology, "Digital
	Signature Standard (DSS)", FIPS PUB 186-3, June 2009.		Signature Standard (DSS)", FIPS PUB 186-3, June 2009.
	skipping to change at page 8, line 8 ¶		skipping to change at page 8, line 8 ¶
	[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.
	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)", January 2012.		Encryption (JWE)", March 2012.
	[JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web		[JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web
	Signature (JWS)", January 2012.		Signature (JWS)", March 2012.
	[MagicSignatures]		[MagicSignatures]
	Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic		Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic
	Signatures", August 2010.		Signatures", January 2011.
	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
	in Magic Signatures [MagicSignatures].		in Magic Signatures [MagicSignatures].
	Appendix B. Document History		Appendix B. Document History
			-01
			o Corrected the Magic Signatures reference.
	-00		-00
	o Created the initial IETF draft based upon		o Created the initial IETF draft based upon
	draft-jones-json-web-key-03 with no normative changes.		draft-jones-json-web-key-03 with no normative changes.
	Author's Address		Author's Address
	Michael B. Jones		Michael B. Jones
	Microsoft		Microsoft
End of changes. 8 change blocks.
	7 lines changed or deleted		13 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/