JSON Object Signing and Encryption (JOSE) -20 drafts have been published that incorporate the changes agreed to on last week's JOSE working group call. Hopefully this brings us to the point of Working Group Last Call.
The only normative changes were to change the name of the "use_details" JWK member to "key_ops" and to clarify that "use" is meant for public key use cases, "key_ops" is meant for use cases in which public, private, or symmetric keys may be present, and that "use" and "key_ops" should not be used together. The drafts, including JSON Web Token (JWT), now also reference draft-ietf-json-rfc4627bis, rather than RFC 4627. The drafts are available at: * http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-20 * http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-20 * http://tools.ietf.org/html/draft-ietf-jose-json-web-key-20 * http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-20 * http://tools.ietf.org/html/draft-ietf-oauth-json-web-token-15 HTML formatted versions are also available at: * http://self-issued.info/docs/draft-ietf-jose-json-web-signature-20.html * http://self-issued.info/docs/draft-ietf-jose-json-web-encryption-20.html * http://self-issued.info/docs/draft-ietf-jose-json-web-key-20.html * http://self-issued.info/docs/draft-ietf-jose-json-web-algorithms-20.html * http://self-issued.info/docs/draft-ietf-oauth-json-web-token-15.html This notification has also been posted at http://self-issued.info/?p=1168 and on Twitter as @selfissued. -- Mike
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
