Re: [OAUTH-WG] [Editorial Errata Reported] RFC6749 (7631)

Aaron Parecki <aaron@parecki.com> Tue, 05 September 2023 13:49 UTC

Return-Path: <aaron@parecki.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 C6B2FC151552 for <oauth@ietfa.amsl.com>; Tue, 5 Sep 2023 06:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=parecki.com
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 ZUEm_zIg9eAZ for <oauth@ietfa.amsl.com>; Tue, 5 Sep 2023 06:49:06 -0700 (PDT)
Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 C974EC151542 for <oauth@ietf.org>; Tue, 5 Sep 2023 06:49:06 -0700 (PDT)
Received: by mail-vs1-xe30.google.com with SMTP id ada2fe7eead31-44d60bb6aa5so1090492137.2 for <oauth@ietf.org>; Tue, 05 Sep 2023 06:49:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parecki.com; s=google; t=1693921745; x=1694526545; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/QaHaxangYP7uo1Y/KNlEja259KLu1AFvR0SV7VD4Ls=; b=jkvfFlQqyilkm8Y85h8n4yeh3r9ogOiqN8gDsXGBghH9pWMEs4FuvWPuicV0PPEXv8 oUpxx7ky2gu8PnQd0BSHfGkwUwDVjXEktqTZC0nTH661Y2ZAYD2Qq/7TyZ9sApOdnF+3 p1JCcpzl1UaM7ru9fzzPPZKRbwKrzc+g1OM23AbU8DkD4qrWRb/Y6ie+e4vHVJMsJbDe DYWkzDr7etTMxHB9YpyIudf4VJhS9bhPW/DFwC+nSM3Cgcq5sPSZkAWPXh4fByTYk7Pp GYblzfVnrgi1j0N5nt/utpS8yFZ2Wp7nHcYPYoo7YyIF9LMOGUO7ROyhqushctnlQ5ie /nNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693921745; x=1694526545; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/QaHaxangYP7uo1Y/KNlEja259KLu1AFvR0SV7VD4Ls=; b=UQDcbeD5gmxcwBFh0LgKit1q9iWZI8NZhnhDUZXcuxvtvpkRlN/sgM7aM3yjBcEL7w tt8CS894wYzXhTHgUN1gZF8CjkA6EONYwpRvwF5r1wQelMNS8+KzkgAFlgA1V65asdcf dWzdP26ZlU3piQrGY7pZfQ3re7MT1KgKC/wyvKUIrP0Cj/cQ0EBv/tYxmSLqy/tgq7MJ V7ufYzpvqHI0LZvT34DPKPLV4tMRN2jaHLvH7ZFDwgh7jT04kpvje5eyCuEuF2NSbpwB 0cOV8cmkKfDDihtdLje18yPrkvvjlOEAwQuSRxAMmNluvcogHZwD/r5DrYqzGtHfjvJ3 HGbg==
X-Gm-Message-State: AOJu0YywyuI9y6WpHoSfLkvFqJ+mZ6iWY37W03Aeq19xj0eQqZsxX9BX UKkkRG/J8YANUgFy+DUbnpoSGrS0rAGF18lZr98=
X-Google-Smtp-Source: AGHT+IFOjh1JJDQYp8O3rHhQByS4HLc7KM2YGXZMF7G7rwqPSsv7gNX3yY5nnJC53PgT+6lNQIlTKQ==
X-Received: by 2002:a67:f69a:0:b0:44e:d937:d28b with SMTP id n26-20020a67f69a000000b0044ed937d28bmr9761605vso.10.1693921745054; Tue, 05 Sep 2023 06:49:05 -0700 (PDT)
Received: from mail-vk1-f177.google.com (mail-vk1-f177.google.com. [209.85.221.177]) by smtp.gmail.com with ESMTPSA id g25-20020a67d499000000b0044d5ca61496sm2134704vsj.0.2023.09.05.06.49.04 for <oauth@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Sep 2023 06:49:04 -0700 (PDT)
Received: by mail-vk1-f177.google.com with SMTP id 71dfb90a1353d-48d0eafcd9bso594260e0c.0 for <oauth@ietf.org>; Tue, 05 Sep 2023 06:49:04 -0700 (PDT)
X-Received: by 2002:a05:6122:2162:b0:490:e790:a15b with SMTP id j2-20020a056122216200b00490e790a15bmr6828526vkr.10.1693921744060; Tue, 05 Sep 2023 06:49:04 -0700 (PDT)
MIME-Version: 1.0
References: <20230905125958.79674B3AF4@rfcpa.amsl.com>
In-Reply-To: <20230905125958.79674B3AF4@rfcpa.amsl.com>
From: Aaron Parecki <aaron@parecki.com>
Date: Tue, 05 Sep 2023 06:48:52 -0700
X-Gmail-Original-Message-ID: <CAGBSGjqAtXi=4DYLaSSF5BT3APELt=ss7ihEX46MNoC6rOKbpQ@mail.gmail.com>
Message-ID: <CAGBSGjqAtXi=4DYLaSSF5BT3APELt=ss7ihEX46MNoC6rOKbpQ@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: daiusa3@icloud.com, oauth@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d5072e06049ce3c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Y3crIlxMtdEwFjLVcACYZEO8obg>
Subject: Re: [OAUTH-WG] [Editorial Errata Reported] RFC6749 (7631)
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: Tue, 05 Sep 2023 13:49:10 -0000

I agree with this errata, it should have been "authorization code". This
sentence was also removed from OAuth 2.1, since the PKCE code
challenge/code verifier mechanism is a more complete protection against
authorization code substitution.

Aaron

On Tue, Sep 5, 2023 at 6:00 AM RFC Errata System <rfc-editor@rfc-editor.org>
wrote:

> The following errata report has been submitted for RFC6749,
> "The OAuth 2.0 Authorization Framework".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7631
>
> --------------------------------------
> Type: Editorial
> Reported by: Daiki Usami <daiusa3@icloud.com>
>
> Section: 3.2.1
>
> Original Text
> -------------
> This protects the client from substitution of the authentication code.
>
> Corrected Text
> --------------
> This protects the client from substitution of the authorization code.
>
> Notes
> -----
> It will be a bit confusing to figure out if it is a MAC or an
> authorization code.
>
> 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 mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>