Re: [OAUTH-WG] Implementation Support and Community

Igor Faynberg <igor.faynberg@alcatel-lucent.com> Fri, 24 August 2012 03:14 UTC

Return-Path: <igor.faynberg@alcatel-lucent.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 9498A21F866C for <oauth@ietfa.amsl.com>; Thu, 23 Aug 2012 20:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.333
X-Spam-Level:
X-Spam-Status: No, score=-7.333 tagged_above=-999 required=5 tests=[AWL=-1.540, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_URI_CONS7=0.306, URI_NOVOWEL=0.5]
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 vLAcNiVKyI87 for <oauth@ietfa.amsl.com>; Thu, 23 Aug 2012 20:14:37 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 8B69B21F8668 for <oauth@ietf.org>; Thu, 23 Aug 2012 20:14:37 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q7O3Ea1D006052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <oauth@ietf.org>; Thu, 23 Aug 2012 22:14:36 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q7O3EZpi003435 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <oauth@ietf.org>; Thu, 23 Aug 2012 22:14:36 -0500
Received: from [135.244.41.244] (faynberg.lra.lucent.com [135.244.41.244]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q7O3EZgU016079; Thu, 23 Aug 2012 22:14:35 -0500 (CDT)
Message-ID: <5036F19A.7070703@alcatel-lucent.com>
Date: Thu, 23 Aug 2012 23:14:34 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: oauth@ietf.org
References: <50364056.4000400@mitre.org> <D5FD7EB9-BFC5-44F7-9FFF-0165477C79F7@ve7jtb.com> <26F5345A-064F-4330-A274-A90CFC653978@xmlgrrl.com>
In-Reply-To: <26F5345A-064F-4330-A274-A90CFC653978@xmlgrrl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: Re: [OAUTH-WG] Implementation Support and Community
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
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: Fri, 24 Aug 2012 03:14:38 -0000

An interesting thought!

It is true that interoperability testing is a requirement for an 
advancement of a Proposed Standard to Draft Standard, so surely OAuth 
interoperability testing must take place. I I don't recall test suits 
defined per se in the IETF. Not that it has not happened--it simply has 
not happened in the groups I worked in or followed.    I remember SIP 
bake-offs progressing well, but not tested to a specific test case set.

Very roughly, the use case document does identify pre- and post 
conditions, but this may not provide enough granularity. Maybe it can be 
used as a starting point though.

Igor

On 8/23/2012 10:49 PM, Eve Maler wrote:
> Perhaps relatedly, in the UMA group we've been defining feature tests for interoperability testing, and since UMA uses OAuth, we wondered if any OAuth feature tests exist; we couldn't find any. That might be another activity worthy of being taken up by such a community. (Both UMA and OpenID Connect are using the OSIS.idcommons.net wiki for interop testing.)
>
> 	Eve
>
> On 23 Aug 2012, at 7:51 AM, John Bradley<ve7jtb@ve7jtb.com>  wrote:
>
>> The openID foundation is in a position of promoting OAuth 2 now as a significant dependency of openID Connect and other work.
>>
>> I can ask the board if there is a interest in hosting something specific for OAuth 2.
>>
>> I agree with Justin, now that the core spec is done there needs to be some consideration put to marketing and support by someone.
>> This WG has new work items to progress so we probably don't want to get bogged down with that in this group.
>>
>> I will wait to see the discussion on this here before asking OIDF or anyone else if they want to set something up.
>>
>> John B.
>> On 2012-08-23, at 10:38 AM, Justin Richer wrote:
>>
>>> With the core specs basically out the door and seeing wider adoption and publicity, the OAuth community is going to start to get more questions about "how do I do X?", and many of these are questions that have been answered before or seem "obvious" to those of us who have been up to our ears in the spec for the past few years. Nevertheless, these are important questions to support for the wellbeing of the protocol community, but where should they be asked?
>>>
>>> When the OAuth community lived on a simple Google Group, these kinds of questions make sense. But I'd argue that the IETF list is not really the right place for them. This list, and the IETF in general, seems to be best suited for *building* the protocol, not for the *use* and *support* of said protocol once it's built.
>>>
>>> The problem is that, as of right now, we don't have anywhere to point people where they could get a "real" answer.
>>>
>>> This opens a larger question of who might "sponsor" or "host" such a community. Anything like that needs moderators, and more importantly, needs experts willing to answer the questions. Some options I can think of:
>>>
>>> - Revive the google groups list for these kinds of questions/discussions
>>> - Start a new list/forum, linked to oauth.net
>>> - Point everyone to StackOverflow with an "oauth" tag
>>>
>>>
>>> -- Justin (who is not volunteering himself to host or moderate the group)
>>> _______________________________________________
>>> 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
>
> Eve Maler                                  http://www.xmlgrrl.com/blog
> +1 425 345 6756                         http://www.twitter.com/xmlgrrl
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth