Re: [OAUTH-WG] draft-ietf-oauth-revocation

Torsten Lodderstedt <torsten@lodderstedt.net> Sun, 03 February 2013 13:12 UTC

Return-Path: <torsten@lodderstedt.net>
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 DD38721F854C for <oauth@ietfa.amsl.com>; Sun, 3 Feb 2013 05:12:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.462
X-Spam-Level:
X-Spam-Status: No, score=-1.462 tagged_above=-999 required=5 tests=[AWL=0.787, BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EDEkev4d5lW2 for <oauth@ietfa.amsl.com>; Sun, 3 Feb 2013 05:12:51 -0800 (PST)
Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.31.40]) by ietfa.amsl.com (Postfix) with ESMTP id F210521F853E for <oauth@ietf.org>; Sun, 3 Feb 2013 05:12:50 -0800 (PST)
Received: from [79.253.33.56] (helo=[192.168.71.36]) by smtprelay02.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1U1zNJ-0003a9-KB; Sun, 03 Feb 2013 14:12:49 +0100
Message-ID: <510E624D.202@lodderstedt.net>
Date: Sun, 03 Feb 2013 14:12:45 +0100
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows NT 6.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <510E5FB5.10803@lodderstedt.net> <510E61AB.20808@gmx.net>
In-Reply-To: <510E61AB.20808@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Df-Sender: dG9yc3RlbkBsb2RkZXJzdGVkdC1vbmxpbmUuZGU=
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] draft-ietf-oauth-revocation
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: Sun, 03 Feb 2013 13:12:52 -0000

Hi Hannes,

Am 03.02.2013 14:10, schrieb Hannes Tschofenig:
> Hi Torsten,
>
>
> On 02/03/2013 03:01 PM, Torsten Lodderstedt wrote:
>> - invalid_token error code: I propose to use the new error code
>> "invalid_parameter" (as suggested by Peter and George). I don't see the
>> need to register it (see
>> http://www.ietf.org/mail-archive/web/oauth/current/msg10604.html) but
>> would like to get your advice.
>
> If you define a new error code (which 'invalid_parameter' is) then it 
> would make sense to register it.

ok.

> The mail exchange you reference refers to re-using an existing error 
> code (namely invalid_request).

You also mention registering a new error code there. I was not sure what 
way you prefer, reusing invalid_request or introducing a new error code.

regards,
Torsten.


>
> Ciao
> Hannes