Re: [oauth-ext-review] request to register RFC 6749's "Extensions Error"s

Brian Campbell <bcampbell@pingidentity.com> Mon, 11 November 2019 16:54 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth-ext-review@ietfa.amsl.com
Delivered-To: oauth-ext-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8BCA1208BA for <oauth-ext-review@ietfa.amsl.com>; Mon, 11 Nov 2019 08:54:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=pingidentity.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cy0bTCv63ZbB for <oauth-ext-review@ietfa.amsl.com>; Mon, 11 Nov 2019 08:54:42 -0800 (PST)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3ED71209DE for <oauth-ext-review@ietf.org>; Mon, 11 Nov 2019 08:54:36 -0800 (PST)
Received: by mail-pf1-x432.google.com with SMTP id 3so11032044pfb.10 for <oauth-ext-review@ietf.org>; Mon, 11 Nov 2019 08:54:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xi6MaXY3fZm+wMHgp5/ko7bGwwMrRn2EDz/XvfNYm18=; b=AXuQKuVUyyzFoBmJbwxszLcHdy7yvx+NbAe4akhZbwOfMwesmydpgsbhLLrW8RQDmN FhgiqoD1VWlmWH4RIavnWSXDPJmMj4KSMPHA7K+gJrH2+4cWsBs5uvIsD3nd+FMDfdPI A4MiwfuVPxufmkk4luw0yuZUikFRtPWeSfgCinZOMb8vBnfvep4rGjmcTPmJauU3B/ga 3p1WiWbIuKEpmIoWreOAOQWnX9W6qXVmHczdxzbNBYTW5Cuhx1llSfmvORwxDPUvms92 pGjgxNs9xv41ubHJboR7nJrVMYlChry5p2z9EOtZyw5UhBE5kyljbEY4PT2RAOAYCOCu m7sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xi6MaXY3fZm+wMHgp5/ko7bGwwMrRn2EDz/XvfNYm18=; b=JrTrZamI9XVepdqJAjY/68ZlOeonzmcOW3TgJXoNUF767AqYAKOw6Y02QfeDI/+VC6 J3ym8tXEAv+13Kt6pQNom02MQOyRg+h9OJ1bXwai1Gm2yPwv96nqG6CQfhMTpYHAT/fm Ps0+D8kIzWi0oD3KxRoZZGJzKaYA23WuIa7sQ0woOiI+YA7/BiKo674PidtgKpEw/qNn uyz/PPOufraKtZGlXBYqD3F82bODa+CEfqJVJBJNJSeL5gASeo4Omx4XDM7ZL7YnatZ4 P5dOFyXIhOePwexKzTXwIusMoxPH5sR4GM1AFNcSlrjv1JSdSXDS4Jo0ddkNLYD3fdqU +TyA==
X-Gm-Message-State: APjAAAXsUnQLtRpWyQYUKucFofPDtaRFICOld4EN54HDLI/NEhXwjRCK K4fBiMkcd3WdrhJ+XqqFlO1zpe6kDs94LFV7ecLFH6PV3CzwzT6Ec8Y9dkIW2txlvu0MrLYZg/W CWXdwT3FiSPhepvwvzPvxx7Qq+tno
X-Google-Smtp-Source: APXvYqxkI38rkrW11+cOOemVW5VFMvS5lZRw8/1BqhicjpjnbPM2FHJaVSVexyWKEYdHjTjigmsCG7nYPBrvktY8IEY=
X-Received: by 2002:a63:6782:: with SMTP id b124mr30930629pgc.220.1573491275867; Mon, 11 Nov 2019 08:54:35 -0800 (PST)
MIME-Version: 1.0
References: <20191014035721.GD61805@kduck.mit.edu> <20191110033040.GX47216@kduck.mit.edu>
In-Reply-To: <20191110033040.GX47216@kduck.mit.edu>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Mon, 11 Nov 2019 09:54:09 -0700
Message-ID: <CA+k3eCTXk5jduPFcsVN_dD_kdQUxSLNjdHqL71gUzYyET=XxnA@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: oauth-ext-review@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008e4515059714fce4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth-ext-review/yAdR5YFQRkRYSUJvA1fUtlsLrXo>
Subject: Re: [oauth-ext-review] request to register RFC 6749's "Extensions Error"s
X-BeenThere: oauth-ext-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Review of proposed IANA registrations for OAuth." <oauth-ext-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth-ext-review>, <mailto:oauth-ext-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth-ext-review/>
List-Post: <mailto:oauth-ext-review@ietf.org>
List-Help: <mailto:oauth-ext-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth-ext-review>, <mailto:oauth-ext-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Nov 2019 16:54:48 -0000

I'm no expert* but I believe these registrations should be made to
retroactively correct for what seems to have been an omission in RFC 6749.
Offhand I guess I'd favor something like you mentioned along the lines of
"OAuth 2.0 core protocol" as the "Protocol Extension".

* Hannes is the only one according to
https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#extensions-error

On Sat, Nov 9, 2019 at 8:30 PM Benjamin Kaduk <kaduk@mit.edu> wrote:

> Hi Experts,
>
> Do you have any thoughts on these registrations?
> I note that https://www.rfc-editor.org/errata/eid5873 attempts to
> enumerate
> the error values in question.
>
> Thanks,
>
> Ben
>
> On Sun, Oct 13, 2019 at 08:57:24PM -0700, Benjamin Kaduk wrote:
> > RFC 6749 establishes the OAuth Extensions Error Registry
> > (https://tools.ietf.org/html/rfc6749#section-11.4) but includes only a
> > Registration Template and not initial registry contents.
> > I request that the error values from the base protocol spec (as listed,
> > from Sections 4.1.2.1, 4.2.2.1, 5.2, and 7.2) be listed in the registry,
> > with "usage location" determined from the corresponding section of the
> > document, change controller "IESG", and reference RFC 6749.  Advice for
> how
> > to list the "Protocol Extension" column is welcome; I am undecided
> between
> > leaving it empty and something like "OAuth 2.0 core protocol".
> >
> > Thanks,
> >
> > Ben
>
> _______________________________________________
> oauth-ext-review mailing list
> oauth-ext-review@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth-ext-review
>

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._