[OAUTH-WG] [Technical Errata Reported] RFC6749 (5234)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 12 January 2018 11:57 UTC

To: dick.hardt@gmail.com, Kathleen.Moriarty.ietf@gmail.com, ekr@rtfm.com, Hannes.Tschofenig@gmx.net, rifaat.ietf@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: randip.malakar@gmail.com, oauth@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20180112115640.EC930B80C15@rfc-editor.org>
Date: Fri, 12 Jan 2018 03:56:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/4ioA0pdMXRCVzden4j3yN-NdbyY>
Subject: [OAUTH-WG] [Technical Errata Reported] RFC6749 (5234)
Precedence: list

The following errata report has been submitted for RFC6749,
"The OAuth 2.0 Authorization Framework".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5234

--------------------------------------
Type: Technical
Reported by: Randip Kumar Malakar <randip.malakar@gmail.com>

Section: 2.1.

Original Text
-------------
   public
      Clients incapable of maintaining the confidentiality of their
      credentials (e.g., clients executing on the device used by the
      resource owner, such as an installed native application or a web
      browser-based application), and incapable of secure client
      authentication via any other means.

Corrected Text
--------------
   public
      Clients incapable of maintaining the confidentiality of their
      credentials (e.g., clients executing on the device used by the
      third-party (not resource owner but another end user), such as an
      installed native application or a web
      browser-based application), and incapable of secure client
      authentication via any other means.

Notes
-----
I think in case of public client type, it should state as "e.g. the clients executing on the device used by third-party and not the actual resource owner" as mentioned in the original RFC. I let the author or experts to review my remark. Thanks.

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. 

--------------------------------------
RFC6749 (draft-ietf-oauth-v2-31)
--------------------------------------
Title               : The OAuth 2.0 Authorization Framework
Publication Date    : October 2012
Author(s)           : D. Hardt, Ed.
Category            : PROPOSED STANDARD
Source              : Web Authorization Protocol
Area                : Security
Stream              : IETF
Verifying Party     : IESG

[OAUTH-WG] [Technical Errata Reported] RFC6749 (5… RFC Errata System
Re: [OAUTH-WG] [Technical Errata Reported] RFC674… John Bradley