All,

Please note that this errata report has been removed.  As stated at 
http://www.rfc-editor.org/errata.php:

"Errata are for the RFCs as available from rfc-editor.org.

We have sent separate mail regarding this error to 
[email protected].

Thank you.

RFC Editor/mf

On Oct 6, 2017, at 8:41 AM, RFC Errata System <[email protected]> wrote:

> The following errata report has been submitted for RFC8252,
> "OAuth 2.0 for Native Apps".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5147
> 
> --------------------------------------
> Type: Editorial
> Reported by: Brian Vosburgh <[email protected]>
> 
> Section: 6
> 
> Original Text
> -------------
> Native apps needing user authorization create an authorization
>   request URI with the authorization code grant type per Section 4.1 of
>   OAuth 2.0 [RFC6749], using a redirect URI capable of being received
>   by the native app.
> 
> Corrected Text
> --------------
> 
> 
> Notes
> -----
> The embedded link for the text "Section 4.1" points at Section 4.1 of *this* 
> RFC (i.e. https://tools.ietf.org/html/rfc8252#section-4.1); but, given the 
> context of the surrounding text, it should point at Section 4.1 of *RFC6749* 
> (i.e. https://tools.ietf.org/html/rfc6749#section-4.1).
> 
> 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. 
> 
> --------------------------------------
> RFC8252 (draft-ietf-oauth-native-apps-12)
> --------------------------------------
> Title               : OAuth 2.0 for Native Apps
> Publication Date    : October 2017
> Author(s)           : W. Denniss, J. Bradley
> Category            : BEST CURRENT PRACTICE
> Source              : Web Authorization Protocol
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
> 

_______________________________________________
OAuth mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/oauth

Reply via email to