Re: [OAUTH-WG] [Editorial Errata Reported] RFC9126 (7410)

Chris Smiley <csmiley@amsl.com> Wed, 26 April 2023 00:46 UTC

Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
From: Chris Smiley <csmiley@amsl.com>
In-Reply-To: <20230331195602.1C6AD4C288@rfcpa.amsl.com>
Date: Tue, 25 Apr 2023 17:45:19 -0700
Cc: adrii.deinega@gmail.com, Torsten Lodderstedt <torsten@lodderstedt.net>, bcampbell@pingidentity.com, nat@sakimura.org, dave@tonge.org, panva.ip@gmail.com, oauth@ietf.org, RFC Errata System <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <71E9AC25-8377-4052-9DAF-B238785EDDC7@amsl.com>
References: <20230331195602.1C6AD4C288@rfcpa.amsl.com>
To: Roman Danyliw <rdd@cert.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/wjBeHZUNK50R6st-sYDZRA6dwxU>
Subject: Re: [OAUTH-WG] [Editorial Errata Reported] RFC9126 (7410)
Precedence: list

Hi Roman,

We are unable to verify this erratum that the submitter marked as editorial. 
Please note that we have changed the “Type” of the following errata 
report to “Technical”. As Stream Approver, please review and set the 
Status and Type accordingly (see the definitions at 
https://www.rfc-editor.org/errata-definitions/).

You may review the report at: 
https://www.rfc-editor.org/errata/eid7410

Please see https://www.rfc-editor.org/how-to-verify/ for further 
information on how to verify errata reports.

Further information on errata can be found at: 
https://www.rfc-editor.org/errata.php.

Thank you.

RFC Editor/cs


> On Mar 31, 2023, at 12:56 PM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC9126,
> "OAuth 2.0 Pushed Authorization Requests".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7410
> 
> --------------------------------------
> Type: Editorial
> Reported by: Andrii Deinega <adrii.deinega@gmail.com>
> 
> Section: 1.1
> 
> Original Text
> -------------
> Uses "urn:example:bwc4JK-ESC0w8acc191e-Y1LTC2" in two examples.
> 
> Corrected Text
> --------------
> Use "urn:ietf:params:oauth:request_uri:bwc4JK-ESC0w8acc191e-Y1LTC2"
> instead.
> 
> Notes
> -----
> Some may find the use of "urn:example:" a bit misleading.
> 
> 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. 
> 
> --------------------------------------
> RFC9126 (draft-ietf-oauth-par-10)
> --------------------------------------
> Title               : OAuth 2.0 Pushed Authorization Requests
> Publication Date    : September 2021
> Author(s)           : T. Lodderstedt, B. Campbell, N. Sakimura, D. Tonge, F. Skokan
> Category            : PROPOSED STANDARD
> Source              : Web Authorization Protocol
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
>

[OAUTH-WG] [Editorial Errata Reported] RFC9126 (7… RFC Errata System
Re: [OAUTH-WG] [Editorial Errata Reported] RFC912… Chris Smiley