Re: [OAUTH-WG] Rechartering

Igor Faynberg <igor.faynberg@alcatel-lucent.com> Tue, 14 September 2010 09:41 UTC

Return-Path: <igor.faynberg@alcatel-lucent.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74AD13A68A5 for <oauth@core3.amsl.com>; Tue, 14 Sep 2010 02:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.494
X-Spam-Level:
X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s8eYk44uOk9i for <oauth@core3.amsl.com>; Tue, 14 Sep 2010 02:41:22 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id B84413A6822 for <oauth@ietf.org>; Tue, 14 Sep 2010 02:41:21 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-63.lucent.com [135.3.40.63]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id o8E9fjNj022156 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Sep 2010 04:41:45 -0500 (CDT)
Received: from [135.244.228.154] (faynberg.lra.lucent.com [135.244.228.154]) by umail.lucent.com (8.13.8/TPES) with ESMTP id o8E9fhFU027767; Tue, 14 Sep 2010 04:41:44 -0500 (CDT)
Message-ID: <4C8F4357.1050804@alcatel-lucent.com>
Date: Tue, 14 Sep 2010 05:41:43 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <4C8C17F9.9050908@gmx.net> <4C8C1BA1.1020902@gmx.net>
In-Reply-To: <4C8C1BA1.1020902@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Rechartering
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 14 Sep 2010 09:41:23 -0000

Hannes,

Many thanks for putting this together.

First, I strongly believe that the work that had already been identified 
important and had started needs to be finished, and to this end I 
consider the item that Torsten had brought forth, on *token revocation*, 
to be of the highest priority. We have had a useful and comprehensive 
discussion on the list, with quite democratic "vote" for options, and 
Torsten has a draft. (Note that the options I "voted" for were not 
accepted, but I am very happy with the process, and I will review the 
drafts--and contribute to it whenever needed.) Again, to me the this is 
a single most important item that needs to be completed, and I believe 
that it can be completed fairly quickly.

Second, I am interested in the SAML interworking item. This will help 
with moving OAuth into enterprise and possibly telecom, too. Again, I 
plan to review and comment--and contribute, if required--on this item.

Third, I think the implementers guide is  absolutely essential. 
(Interestingly enough, the discussion of white spaces vs. commas in 
yesterday's thread has effectively started this work.) In my opinion, 
this item must be carried in parallel with others. I wonder if this 
should be tied up with use cases. The use cases drive the protocol 
definition and then effectively become the testing tool for the 
protocol. Thus, for every use case, the guide could show an example 
implementation.

Fourth, of course, I am interested in "identity management using OAuth."

This is not to say that I am not interested in the rest of the items. (I 
am, and I could have listed them as the fifth item.) This is only my 
personal view on priorities.

Igor
Hannes Tschofenig wrote:
> I forgot an item already, namely 'identity management using OAuth' in 
> the style of OpenID Connect.
>
> At IIW we also had a chat about an implementers guide and 
> interoperability tests. The idea of the implementers guide is create a 
> living document that captures implementation experience with different 
> programming languages and development frameworks. It was also expected 
> that implementers will bundle different profiles and different 
> extensions in their implementation and it would be useful to describe 
> their experience.
>
> In any case, I think both items are important.
>
> Ciao
> Hannes
>
> On 11.09.2010 19:59, Hannes Tschofenig wrote:
>> Hi all,
>>
>> at the Washington Internet Identity Workshop we had the chance to chat
>> about OAuth. Given the progress on the main specification we should
>> discuss WG re-chartering.
>>
>> The following items had been proposed at the meeting:
>>
>> * Messaging Signing
>> Example: 
>> http://www.ietf.org/mail-archive/web/oauth/current/msg04250.html
>>
>> * User Experience Extensions
>> Example: http://datatracker.ietf.org/doc/draft-recordon-oauth-v2-ux/
>>
>> * Artifact Binding
>> Example: http://datatracker.ietf.org/doc/draft-sakimura-oauth-requrl/
>>
>> * SAML for OAuth
>> Example: http://datatracker.ietf.org/doc/draft-campbell-oauth-saml/
>>
>> * Recommendations of commonly used Scope values
>> No draft available (to my knowledge)
>>
>> * Dynamic Client Registration
>> Example: http://www.ietf.org/id/draft-oauth-dyn-reg-v1-00.txt
>>
>> I am interested to hear
>> a) what items are important for you; we cannot work on everything at the
>> same time.
>> b) what items are you willing to co-author (requires a hard time
>> commitment)
>> c) what items are you willing to review
>> d) whether we should consider other items?
>>
>> Btw, to have your work considered you have to submit an IETF draft.
>> Please use the Web tool to upload it:
>> https://datatracker.ietf.org/idst/upload.cgi
>> Also use the following filename convention:
>> draft-[author last name]-oauth-[some short name]-[version#].txt
>>
>> Ciao
>> Hannes
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth