[OAUTH-WG] [Editorial Errata Reported] RFC6750 (6161)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 08 May 2020 13:15 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 770343A0966 for <oauth@ietfa.amsl.com>; Fri, 8 May 2020 06:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N78G8fJHMDLv for <oauth@ietfa.amsl.com>; Fri, 8 May 2020 06:15:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 165E83A0945 for <oauth@ietf.org>; Fri, 8 May 2020 06:15:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 44CDBF4074D; Fri, 8 May 2020 06:15:15 -0700 (PDT)
To: mbj@microsoft.com, dick.hardt@gmail.com, rdd@cert.org, kaduk@mit.edu, Hannes.Tschofenig@gmx.net, rifaat.ietf@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: hvr@gnu.org, oauth@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200508131515.44CDBF4074D@rfc-editor.org>
Date: Fri, 08 May 2020 06:15:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/cEni8oIben1eJUh9wS2avcki-BE>
Subject: [OAUTH-WG] [Editorial Errata Reported] RFC6750 (6161)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 May 2020 13:15:26 -0000

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 <hvr@gnu.org>

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