[OAUTH-WG] new sponsorship, time available for WG

Dick Hardt <dick.hardt@gmail.com> Wed, 24 March 2010 05:26 UTC

Return-Path: <dick.hardt@gmail.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 B77003A6D49 for <oauth@core3.amsl.com>; Tue, 23 Mar 2010 22:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[AWL=-0.185, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 11xTrRvxY6aZ for <oauth@core3.amsl.com>; Tue, 23 Mar 2010 22:26:31 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 55C573A6D59 for <oauth@ietf.org>; Tue, 23 Mar 2010 22:19:24 -0700 (PDT)
Received: by pwi10 with SMTP id 10so3816682pwi.31 for <oauth@ietf.org>; Tue, 23 Mar 2010 22:18:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:content-type :content-transfer-encoding:subject:date:message-id:to:mime-version :x-mailer; bh=gpKMkBf3M8gpUWnbDbiQfH4027M05QCywtg3jVmNXq8=; b=r78MJKH9rsVoMw1+xc7yM8d8tiDL0HPYInB0TEMupx+R3aXc4I7/DSi6V6IeMD4ZFG 2JaB5Z8oAGblUm1xS5vSaU3epGjQuTg2MyocO7xW0YjbAuCkXvqIvFaIwAFATjrGDgOd tv8eVxhM9QKstdJsS1cA84kRoal6wWiPvbU+c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=om2xCZgFAwn/oDNY2qb2lgdFF7JqwBKpJDpOXUlKjIbBG1FdbabjyyI26Olb3obhfE 56H50kVq8FRoQCxTv9tcFtTR3ytMmUiDjolf4kHXFVD1nUezFGx4ZrILGOe+EphEBnPD /hLU5bVAZ/LRFwko+0FsTdmeJUrRepHQ+jjv8=
Received: by 10.141.3.14 with SMTP id f14mr3422455rvi.50.1269407937705; Tue, 23 Mar 2010 22:18:57 -0700 (PDT)
Received: from [192.168.1.105] (64-46-1-217.dyn.novuscom.net [64.46.1.217]) by mx.google.com with ESMTPS id 22sm2696358pzk.5.2010.03.23.22.18.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 23 Mar 2010 22:18:56 -0700 (PDT)
From: Dick Hardt <dick.hardt@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 23 Mar 2010 22:18:54 -0700
Message-Id: <84C54659-24DA-42C3-BDE3-AC378851CD6F@gmail.com>
To: OAuth WG <oauth@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1077)
X-Mailer: Apple Mail (2.1077)
Subject: [OAUTH-WG] new sponsorship, time available for WG
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, 24 Mar 2010 05:26:32 -0000

Microsoft recently offered to sponsor me to work on OAuth. For the past few months I have participated in the WG on my own time, but I am now able to devote a significant amount of time to this WG.

I'd be happy to work on merging client signature support with WRAP. My preference would be to start with that draft rather than draft-recordon-oauth2 given all the capabilities that David decided to drop. Alternatively I will continue to provide criticism and author chunks of text if David is willing to include them in draft-recordon-oauth2.

At the IETF post meeting this week,  there was discussion of working on both draft-hardt-oauth and draft-recordon-oauth2.  David's draft has garnered much discussion, much of it comments on what was dropped from WRAP. Similarly, if draft-hardt-oauth was revised to include signatures, it likely would also generate discussion. Seems like a waste for the WG to be providing comments on two documents.

I'm unsure of the correct process: is it the chairs, the editor or a WG consensus call to decide where to start.