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

Benjamin Kaduk <kaduk@mit.edu> Sun, 10 November 2019 03:30 UTC

Return-Path: <kaduk@mit.edu>
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 E83131200FB for <oauth-ext-review@ietfa.amsl.com>; Sat, 9 Nov 2019 19:30:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Vhl2plipaOvE for <oauth-ext-review@ietfa.amsl.com>; Sat, 9 Nov 2019 19:30:45 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13E771200F6 for <oauth-ext-review@ietf.org>; Sat, 9 Nov 2019 19:30:44 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id xAA3Uf0q006428 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <oauth-ext-review@ietf.org>; Sat, 9 Nov 2019 22:30:43 -0500
Date: Sat, 9 Nov 2019 19:30:40 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: oauth-ext-review@ietf.org
Message-ID: <20191110033040.GX47216@kduck.mit.edu>
References: <20191014035721.GD61805@kduck.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20191014035721.GD61805@kduck.mit.edu>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth-ext-review/YUZdfiKbclb71zm7Cw66gb18rF0>
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: Sun, 10 Nov 2019 03:30:47 -0000

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