Re: [OAUTH-WG] IANA registry for error codes of RFC6749 section 5.2?

Benjamin Kaduk <kaduk@mit.edu> Mon, 14 October 2019 03:58 UTC

Return-Path: <kaduk@mit.edu>
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 B743D12008F for <oauth@ietfa.amsl.com>; Sun, 13 Oct 2019 20:58:38 -0700 (PDT)
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 dS8I6v1r8mwA for <oauth@ietfa.amsl.com>; Sun, 13 Oct 2019 20:58:37 -0700 (PDT)
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 1A3BD12001A for <oauth@ietf.org>; Sun, 13 Oct 2019 20:58:36 -0700 (PDT)
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 x9E3wWA8012565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 13 Oct 2019 23:58:35 -0400
Date: Sun, 13 Oct 2019 20:58:32 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Ludwig Seitz <ludwig.seitz@ri.se>
Cc: Justin Richer <jricher@mit.edu>, "oauth@ietf.org" <oauth@ietf.org>
Message-ID: <20191014035832.GE61805@kduck.mit.edu>
References: <08fd478d-233b-25e8-cb53-e2546596c329@ri.se> <FAAA32AB-8EAB-405E-9AEE-4E78A53018CD@mit.edu> <16a411cd-c50a-1827-cfef-82b53cc7101e@ri.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <16a411cd-c50a-1827-cfef-82b53cc7101e@ri.se>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/yoaxlPDisWWfpkJKyJsLC0Xzb2g>
Subject: Re: [OAUTH-WG] IANA registry for error codes of RFC6749 section 5.2?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 14 Oct 2019 03:58:39 -0000

On Fri, Oct 11, 2019 at 08:17:07AM +0200, Ludwig Seitz wrote:
> On 10/10/2019 17:02, Justin Richer wrote:
> > They are in that registry as the “token endpoint response” error codes. 
> > RFC8628 adds new ones.
> > 
> > I think that 6749 failed to put in the base ones.
> > 
> > — Justin
> 
> That would explain my confusion.
> 
> Errata-worthy?

I think it's not strictly necessary; we can just register the values using
the Specification Required procedure (I sent mail to kick things off
already:
https://mailarchive.ietf.org/arch/msg/oauth-ext-review/4WaM6n6JetFsLI6_T9S8wNVqP74

-Ben