Hi Deb, We are unable to verify this erratum that the submitter marked as editorial, so we changed the Type 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/). Please see the discussion below for details.
You may review the report at: https://www.rfc-editor.org/errata/eid8458. Information on how to verify errata reports can be found at: https://www.rfc-editor.org/how-to-verify/. Further information on errata can be found at: https://www.rfc-editor.org/errata.php. Thank you! RFC Editor/mc > On Jun 14, 2025, at 6:18 AM, Justin Richer <jric...@mit.edu> wrote: > > This is not an error and the errata should be rejected. As per the ABNF > definition in https://www.rfc-editor.org/rfc/rfc5234.html#section-21 the name > contains "alphabetics, digits, and hyphens (dashes)", and not underscores. I > believe the commenter is expecting the ABNF rule name of code-verifier to > match the parameter name of code_verifier, but they do not need to be the > same. While this is confusing, the text is correct as it stands. > > - Justin > From: RFC Errata System <rfc-edi...@rfc-editor.org> > Sent: Friday, June 13, 2025 6:12 AM > To: rfc-edi...@rfc-editor.org <rfc-edi...@rfc-editor.org> > Cc: Jeffrey S Walden <jwal...@mit.edu>; n-sakim...@nri.co.jp > <n-sakim...@nri.co.jp>; n...@google.com <n...@google.com>; oauth@ietf.org > <oauth@ietf.org> > Subject: [OAUTH-WG] [Editorial Errata Reported] RFC7636 (8458) The > following errata report has been submitted for RFC7636, > "Proof Key for Code Exchange by OAuth Public Clients". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid8458 > > -------------------------------------- > Type: Editorial > Reported by: Jeff Walden <jwal...@mit.edu> > > Section: 4.2 > > Original Text > ------------- > code-challenge = 43*128unreserved > > Corrected Text > -------------- > code_challenge = 43*128unreserved > > Notes > ----- > The ABNF accidentally uses a hyphen/dash rather than an underscore in the > code_challenge name in its rule. > > Instructions: > ------------- > This erratum is currently posted as "Reported". (If it is spam, it > will be removed shortly by the RFC Production Center.) Please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > will log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC7636 (draft-ietf-oauth-spop-15) > -------------------------------------- > Title : Proof Key for Code Exchange by OAuth Public Clients > Publication Date : September 2015 > Author(s) : N. Sakimura, Ed., J. Bradley, N. Agarwal > Category : PROPOSED STANDARD > Source : Web Authorization Protocol > Stream : IETF > Verifying Party : IESG > > _______________________________________________ > OAuth mailing list -- oauth@ietf.org > To unsubscribe send an email to oauth-le...@ietf.org _______________________________________________ OAuth mailing list -- oauth@ietf.org To unsubscribe send an email to oauth-le...@ietf.org
