Re: [OAUTH-WG] Rechartering

Justin Richer <jricher@mitre.org> Tue, 14 September 2010 14:46 UTC

Return-Path: <jricher@mitre.org>
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 31B9C3A69DD for <oauth@core3.amsl.com>; Tue, 14 Sep 2010 07:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.765
X-Spam-Level:
X-Spam-Status: No, score=-5.765 tagged_above=-999 required=5 tests=[AWL=-0.655, BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
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 3pq2dfl01pUP for <oauth@core3.amsl.com>; Tue, 14 Sep 2010 07:46:27 -0700 (PDT)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 9EA2A3A691A for <oauth@ietf.org>; Tue, 14 Sep 2010 07:46:13 -0700 (PDT)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o8EEkbU7003045 for <oauth@ietf.org>; Tue, 14 Sep 2010 10:46:38 -0400
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o8EEkbrb003031; Tue, 14 Sep 2010 10:46:37 -0400
Received: from [129.83.50.65] (129.83.50.65) by imchub1.MITRE.ORG (129.83.29.73) with Microsoft SMTP Server id 8.2.254.0; Tue, 14 Sep 2010 10:46:37 -0400
From: Justin Richer <jricher@mitre.org>
To: "igor.faynberg@alcatel-lucent.com" <igor.faynberg@alcatel-lucent.com>
In-Reply-To: <4C8F4357.1050804@alcatel-lucent.com>
References: <4C8C17F9.9050908@gmx.net> <4C8C1BA1.1020902@gmx.net> <4C8F4357.1050804@alcatel-lucent.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 14 Sep 2010 10:46:36 -0400
Message-ID: <1284475596.19104.81.camel@localhost.localdomain>
MIME-Version: 1.0
X-Mailer: Evolution 2.28.3
Content-Transfer-Encoding: 7bit
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Rechartering
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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 14:46:29 -0000

> 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.

This is what I'd had in mind when I brought up the implementers guide. I
think we're seeing some common collections of stuff, profiles based on
real use cases. So a person saying "I want to build a PR server that
supports the webserver grant profile and the display extension", or
someone saying "I want to build a client for the Facebook collection of
stuff" will have a document that tells them exactly what to do at each
step. The spec itself splits things out into their normative places, but
someone building a component is going to want to just know what
arguments to put on each request.

 -- Justin