Re: [OAUTH-WG] proposed agenda for second interim meeting

Peter Saint-Andre <stpeter@stpeter.im> Wed, 03 February 2010 20:00 UTC

Return-Path: <stpeter@stpeter.im>
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 D0EE928C1BB for <oauth@core3.amsl.com>; Wed, 3 Feb 2010 12:00:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.732
X-Spam-Level:
X-Spam-Status: No, score=-2.732 tagged_above=-999 required=5 tests=[AWL=-0.133, 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 iA2ze4E6D+FI for <oauth@core3.amsl.com>; Wed, 3 Feb 2010 12:00:35 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 9FE2D28C194 for <oauth@ietf.org>; Wed, 3 Feb 2010 12:00:24 -0800 (PST)
Received: from dhcp-64-101-72-234.cisco.com (dhcp-64-101-72-234.cisco.com [64.101.72.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 82A7740332 for <oauth@ietf.org>; Wed, 3 Feb 2010 13:01:07 -0700 (MST)
Message-ID: <4B69D601.3080209@stpeter.im>
Date: Wed, 03 Feb 2010 13:01:05 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: oauth@ietf.org
References: <4B69066C.5050809@stpeter.im> <90C41DD21FB7C64BB94121FBBC2E723437DFBA2A70@P3PW5EX1MB01.EX1.SECURESERVER.NET> <62C93B79-9FF8-4D26-B1A7-7A79C122CC0E@gmail.com> <90C41DD21FB7C64BB94121FBBC2E723437DFBA2B78@P3PW5EX1MB01.EX1.SECURESERVER.NET> <A08279DC79B11C48AD587060CD93977112D4DE2C@TK5EX14MBXC103.redmond.corp.microsoft.com> <90C41DD21FB7C64BB94121FBBC2E723437DFBA2BB7@P3PW5EX1MB01.EX1.SECURESERVER.NET> <371693C7-5694-4E30-87EF-B8859B72D437@gmail.com> <90C41DD21FB7C64BB94121FBBC2E723437DFBA2BE2@P3PW5EX1MB01.EX1.SECURESERVER.NET> <BF53F610-E385-4BCE-B696-AE79423A0FF0@gmail.com> <90C41DD21FB7C64BB94121FBBC2E723437DFBA2C32@P3PW5EX1MB01.EX1.SECURESERVER.NET> <652E65C5-CA92-41AF-B6A1-85A6AC84F54A@gmail.com>
In-Reply-To: <652E65C5-CA92-41AF-B6A1-85A6AC84F54A@gmail.com>
X-Enigmail-Version: 1.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms030003040306050704090908"
Subject: Re: [OAUTH-WG] proposed agenda for second interim meeting
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: Wed, 03 Feb 2010 20:00:36 -0000

<hat type='chair'/>

On 2/3/10 12:46 PM, Dick Hardt wrote:

> Wanting to discuss technical details when there does not seem to be
> consensus on the problem we are solving was my Titanic reference.

We have two dangers here:

1. The Scylla of designing technologies before we fully understand the
problem space and its associated requirements.

2. The Charybdis of discussing the problem space and its associated
requirements but never designing any technologies.

We are attempting to steer a safe course between these two dangers.
Although I tend to the side of those who fear Scylla more than
Charybdis, in my opinion (not consensus that I am declaring as co-chair)
we have enough sense of the problem space regarding authentication that
we can at least have a productive discussion about
draft-ietf-oauth-authentication-01 at tomorrow's interim meeting.
However, in parallel I think we need to keep sifting through various use
cases, and Blaine's stub of a feature matrix is a good first step that
needs more attention before the interim meeting we'll hold two weeks
from tomorrow (February 18). Remember, these interim meetings are
intended to air open issues and get us closer to agreement on problems,
terminology, architecture, use cases, requirements, and possible
technical solutions, all as a way of preparing for the in-person meeting
in Anaheim. IMHO we need to keep working in several directions at once,
so let's keep building out our wiki pages and updating the relevant
Internet-Drafts and sifting through use cases and working through open
issues on this list. Perhaps that's not a perfect process, but I think
it's the best we can do for now. If you disagree, feel free to do so on
list or off. :)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/