<http://peoplesearch.in.telstra.com.au/peoplesearch/UserDetail.aspx?Employee Number=3799878> James Manger <mailto:james.h.man...@team.telstra.com> james.h.man...@team.telstra.com Chief Technology Office - Telstra Phone: +61 3 8649 2442 Mobile: +61 4 1754 1870 Web: blogs.cto.in.telstra.com.au/security/ The information contained in this e-mail is confidential. It is only intended for the recipient/s named above. If you are not an intended recipient any unauthorised use is prohibited. If you have received this e-mail in error, please notify the sender so that arrangements can be made for its retrieval or destruction. Telstra Corporation Limited ABN 33 051 775 556. From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of Mike Jones Sent: Friday, 24 September 2010 10:22 AM To: oauth@ietf.org Subject: [OAUTH-WG] JSON Web Token (JWT) Specification Draft Recognizing that there is substantial interest in representing sets of claims in JSON tokens, Yaron Goland and I have put together a draft JSON Web Token (JWT) spec for that purpose. To answer the obvious question, while this was produced independently of Dirk <http://balfanz.github.com/jsontoken-spec/draft-balfanz-jsontoken-00.html> 's JSON token proposal, both of us agree that we should come up with a unified spec. Consider this an additional point in the possible design space from which to start discussions and drive consensus. (If you read the two proposals, I think you'll find that there's already a lot in common, which is great.) Thanks to those of you who have already given us feedback to improve the draft prior to this point. Cheers, -- Mike
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
