The following errata report has been submitted for RFC6750, "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6161 -------------------------------------- Type: Editorial Reported by: Herbert Valerio Riedel <[email protected]> Section: 4 Original Text ------------- 4. Example Access Token Response Typically, a bearer token is returned to the client as part of an OAuth 2.0 [RFC6749] access token response. An example of such a response is: HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 Corrected Text -------------- 4. Example Access Token Response Typically, a bearer token is returned to the client as part of an OAuth 2.0 [RFC6749] access token response. An example of such a response is: HTTP/1.1 200 OK Content-Type: application/json Notes ----- The IANA registration (see https://tools.ietf.org/html/rfc8259#section-11) does not support any parameters for the `application/json` media type. The `charset=UTF-8` parameter used in the example is therefore non-compliant and ought to be omitted. 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. -------------------------------------- RFC6750 (draft-ietf-oauth-v2-bearer-23) -------------------------------------- Title : The OAuth 2.0 Authorization Framework: Bearer Token Usage Publication Date : October 2012 Author(s) : M. Jones, D. Hardt 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
