Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-introspection-01.txt

Sergey Beryozkin <sberyozkin@gmail.com> Mon, 01 December 2014 10:56 UTC

Return-Path: <sberyozkin@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E470E1A1B36 for <oauth@ietfa.amsl.com>; Mon, 1 Dec 2014 02:56:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 NZPgUzUM4SWz for <oauth@ietfa.amsl.com>; Mon, 1 Dec 2014 02:56:34 -0800 (PST)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 254B21A1B35 for <oauth@ietf.org>; Mon, 1 Dec 2014 02:56:34 -0800 (PST)
Received: by mail-wg0-f43.google.com with SMTP id l18so13679239wgh.30 for <oauth@ietf.org>; Mon, 01 Dec 2014 02:56:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=QfrhXgcmklJf46VjY3fXaWmKpmZ4sL5Bv+ILGtXOR+I=; b=xonyafRhWbGl2VFzCUp3Su5CYUEL4moDUlosMFouMD6Gknt4zVLdKmqroyJHTKTLXl lVo5FzKQoa39/Aa3J3HNH/G1fOQF/z+nEHkoHfbNmbajU5rUiBzMxGw5rA6bbaHJlONh 624tYdLgOBCdPL4ggdh8LGMJAcCqay8Rjj3mn5Su9lZkFrXuqXCnF78b4JDWVLAc57L9 9WISNaFUfqwGB2Bcrsuoi71peKQDXheBeYBPzdrRt+y4t2d89y9HBrEnZuCqn7Cx4fAm NnilDY3jN708rSI1N4ewNNl75R7KMXvLvPMIaNs8k9QVcNT9eFOy8Y3vba/YoPHnjlAI tvnw==
X-Received: by 10.180.88.33 with SMTP id bd1mr81977634wib.10.1417431392939; Mon, 01 Dec 2014 02:56:32 -0800 (PST)
Received: from [10.36.226.2] ([80.169.137.63]) by mx.google.com with ESMTPSA id fk12sm7369126wic.6.2014.12.01.02.56.31 for <oauth@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Dec 2014 02:56:32 -0800 (PST)
Message-ID: <547C495F.1010402@gmail.com>
Date: Mon, 01 Dec 2014 10:56:31 +0000
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: oauth@ietf.org
References: <20141201024133.16302.20230.idtracker@ietfa.amsl.com>
In-Reply-To: <20141201024133.16302.20230.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/wqJ_Y4MrNyoJN-EX-0rccwtXBno
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-introspection-01.txt
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Dec 2014 10:56:36 -0000

Hi Justin

Nicely written text, as usual.
Few comments:
- I haven't found a reference to a data format of POST requests.
I'm presuming it is going to be a form payload (would mean the server 
code can write more or less the same code dealing with POST & GET queries) ?
- consider directly specifying an optional 'client_ip' property
- consider adding an optional request_method (or request_verb) hint, a 
given scope can be restricted to say GET only, can be useful when a 
protected resource is written to support GET and POST over the same 
resource_id URI;

The text that the endpoint may support other parameters (such a client 
ip address) covers the last 2 parameters, but I guess it would be more 
inter-operable to 'promote' the parameters that may be of general use.

Thanks, Sergey




On 01/12/14 02:41, internet-drafts@ietf.org wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Web Authorization Protocol Working Group of the IETF.
>
>          Title           : OAuth 2.0 Token Introspection
>          Author          : Justin Richer
> 	Filename        : draft-ietf-oauth-introspection-01.txt
> 	Pages           : 10
> 	Date            : 2014-11-30
>
> Abstract:
>     This specification defines a method for a protected resource to query
>     an OAuth 2.0 authorization server to determine the active state of an
>     OAuth 2.0 token and to determine meta-information about this token.
>     OAuth 2.0 deployments can use this method to convey information about
>     the authorization context of the token from the authorization server
>     to the protected resource.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-oauth-introspection/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-oauth-introspection-01
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-introspection-01
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>