[OAUTH-WG] [Editorial Errata Reported] RFC9126 (7254)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 18 November 2022 18:23 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
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 B8376C152560 for <oauth@ietfa.amsl.com>; Fri, 18 Nov 2022 10:23:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.646
X-Spam-Level:
X-Spam-Status: No, score=-1.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g0nPe9EgVYIj for <oauth@ietfa.amsl.com>; Fri, 18 Nov 2022 10:23:46 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDAF3C1524D4 for <oauth@ietf.org>; Fri, 18 Nov 2022 10:23:46 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id CAB7755F7E; Fri, 18 Nov 2022 10:23:46 -0800 (PST)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: joseph@heenan.me.uk, torsten@lodderstedt.net, bcampbell@pingidentity.com, nat@sakimura.org, dave@tonge.org, panva.ip@gmail.com, oauth@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20221118182346.CAB7755F7E@rfcpa.amsl.com>
Date: Fri, 18 Nov 2022 10:23:46 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/ObjyQhxNrMeMRFI9iGc3PfHtw4w>
Subject: [OAUTH-WG] [Editorial Errata Reported] RFC9126 (7254)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.39
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, 18 Nov 2022 18:23:50 -0000

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/eid7254

--------------------------------------
Type: Editorial
Reported by: Joseph Heenan <joseph@heenan.me.uk>

Section: 1.1

Original Text
-------------
POST /as/par HTTP/1.1
Host: as.example.com
Content-Type: application/x-www-form-urlencoded

&response_type=code
&client_id=CLIENT1234&state=duk681S8n00GsJpe7n9boxdzen
<...>

Corrected Text
--------------
POST /as/par HTTP/1.1
Host: as.example.com
Content-Type: application/x-www-form-urlencoded

response_type=code
&client_id=CLIENT1234&state=duk681S8n00GsJpe7n9boxdzen
<...>

Notes
-----
In the 'Introductory Example', the POST body to the par endpoint contains an unnecessary '&' at the start. (It's perhaps technically valid, but could potentially confuse readers.)

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