March 2, 2014
Updated JOSE and JWT drafts have been published that fix a few instances of incorrect uses of RFC 2119 requirements language, such as changing an occurrence of “MUST not†to “MUST NOTâ€. These drafts also reference the newly completed JSON specification – RFC 7158.
The specifications are available at:
- http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-22
- http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-22
- http://tools.ietf.org/html/draft-ietf-jose-json-web-key-22
- http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-22
- http://tools.ietf.org/html/draft-ietf-oauth-json-web-token-17
HTML formatted versions are also available at:
- http://self-issued.info/docs/draft-ietf-jose-json-web-signature-22.html
- http://self-issued.info/docs/draft-ietf-jose-json-web-encryption-22.html
- http://self-issued.info/docs/draft-ietf-jose-json-web-key-22.html
- http://self-issued.info/docs/draft-ietf-jose-json-web-algorithms-22.html
- http://self-issued.info/docs/draft-ietf-oauth-json-web-token-17.html
No Comments » Posted under Claims & Cryptography & JSON & OAuth & Specifications
Leave a Reply
You must be logged in to post a comment.
