Re: [OAUTH-WG] Error Registry Consensus Call

Nat Sakimura <sakimura@gmail.com> Mon, 07 May 2012 23:55 UTC

Return-Path: <sakimura@gmail.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 47E8F21F8543 for <oauth@ietfa.amsl.com>; Mon, 7 May 2012 16:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvU4zNbRwZZm for <oauth@ietfa.amsl.com>; Mon, 7 May 2012 16:55:43 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5B7CD21F8533 for <oauth@ietf.org>; Mon, 7 May 2012 16:55:43 -0700 (PDT)
Received: by bkty8 with SMTP id y8so5005530bkt.31 for <oauth@ietf.org>; Mon, 07 May 2012 16:55:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=rBHmx3XLpB7G4qpsPSlsypUuxVA3fOODKnEPNtP0bt0=; b=xShCJrw9MKknopvePAP4iOl3CSXMnB9zWQcA+cm96TgT7PLxUWfuHlFrCu5rLuDw+u CwZiBNXu3Dly4qQooNbCodnaln6QeqFDKqAmBXqdtKR1To+KqZmZEu3Bmfs7E0pUsp8m T28ZSGQVlh3W6QTTpd+E8SPo+be/e0XUadwYyghjRZfUOG5bZ+EaC0NlRDBYXx2BaZQD ShIfEfEqb/IseUG4z1YtRdL8wFHhFIEovVQy48R+86bnfB0ZaIyhHcxKYuQwUmEV14TV Shw/zamiwHIgdHwuo4lWvA9Eq/Er/9JmwsFi2Jw5Hehafxpvv0rF2qzJxhOL62/BdUU3 vUbg==
MIME-Version: 1.0
Received: by 10.204.154.18 with SMTP id m18mr6535034bkw.23.1336434942410; Mon, 07 May 2012 16:55:42 -0700 (PDT)
Received: by 10.204.240.143 with HTTP; Mon, 7 May 2012 16:55:42 -0700 (PDT)
In-Reply-To: <53E17703-C3BD-48A1-8CB6-BD0D3795DD77@gmx.net>
References: <53E17703-C3BD-48A1-8CB6-BD0D3795DD77@gmx.net>
Date: Tue, 8 May 2012 01:55:42 +0200
Message-ID: <CABzCy2Bkriia=rrahHfi9MGxc5snFVfKM0otyQPqkuBEF3KRDw@mail.gmail.com>
From: Nat Sakimura <sakimura@gmail.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Error Registry Consensus Call
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 07 May 2012 23:55:44 -0000

I prefer single repository.

On Tue, May 8, 2012 at 12:48 AM, Hannes Tschofenig
<hannes.tschofenig@gmx.net> wrote:
> Hi all,
>
> there is an open issue concerning draft-ietf-oauth-v2-bearer-19 that may impact draft-ietf-oauth-v2-26 (depending on it's resolution) and we would like to get feedback from the working group about it.
>
> Here is the issue: When a client makes an access to a protected resources then things may go wrong and an error may be returned in response. draft-ietf-oauth-v2-bearer talks about this behavior.
>
> That's great but these error codes need to be registered somewhere. Note that the registry can be created in one document while the values can be registered by many documents.
>
> So, where should the registry be?
>
> There are two choices.
>
> a) A new OAuth errors registry goes into draft-ietf-oauth-v2-bearer.
>
> b) draft-ietf-oauth-v2 expands the scope of the existing OAuth Errors registry to encompass errors returned from resource servers.
>
> Currently, draft-ietf-oauth-v2 creates registries for error codes only for the exchanges from A-to-D (symbols used from Figure 1 of draft-ietf-oauth-v2), but excludes registration of errors from flows E-F.
>
> We must create a registry for error codes from flows E-F.  In which document do we want to create this registry?
>
> So, give us your feedback whether you have a preference by the end of the week.
>
> Ciao
> Hannes & Derek
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth



-- 
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en