The following errata report has been rejected for RFC7519, "JSON Web Token (JWT)".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6622 -------------------------------------- Status: Rejected Type: Editorial Reported by: Padmanarayanan SR <[email protected]> Date Reported: 2021-06-25 Rejected by: Benjamin Kaduk (IESG) 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. --VERIFIER NOTES-- The "text" publication format (the only official format for RFCs prior to 8650) does not include HTML links, so the "original text" section of this report does not match the version of the RFC that this tool is used for. Accordingly, the submission has to be rejected as invalid. -------------------------------------- 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
