The following errata report has been submitted for RFC7519, "JSON Web Token (JWT)".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6622 -------------------------------------- Type: Editorial Reported by: Padmanarayanan SR <[email protected]> Section: 11 Original Text ------------- All the security considerations in the JWS specification also apply to JWT, as do the JWE security considerations when encryption is employed. In particular, Sections <a href="#section-10.12">10.12</a> Corrected Text -------------- All the security considerations in the JWS specification also apply to JWT, as do the JWE security considerations when encryption is employed. In particular, Sections <a href="/doc/html/rfc7515#section-10.12">10.12</a> Notes ----- The link appears to be broken. It is intended to point to rfc7515#section-10.12 whereas it is pointing to the non-existent section of the same document. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7519 (draft-ietf-oauth-json-web-token-32) -------------------------------------- Title : JSON Web Token (JWT) Publication Date : May 2015 Author(s) : M. Jones, J. Bradley, N. Sakimura Category : PROPOSED STANDARD Source : Web Authorization Protocol Area : Security Stream : IETF Verifying Party : IESG _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
