Re: [OAUTH-WG] OAuth WG Re-Chartering

Blaine Cook <romeda@gmail.com> Mon, 19 March 2012 15:24 UTC

Return-Path: <romeda@gmail.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 9434921F8811 for <oauth@ietfa.amsl.com>; Mon, 19 Mar 2012 08:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I69nrr3NhOxJ for <oauth@ietfa.amsl.com>; Mon, 19 Mar 2012 08:24:45 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7E18C21F87F8 for <oauth@ietf.org>; Mon, 19 Mar 2012 08:24:44 -0700 (PDT)
Received: by lagj5 with SMTP id j5so5688712lag.31 for <oauth@ietf.org>; Mon, 19 Mar 2012 08:24:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=zx03ml/4Dyu3QqObb3PnxLtrxGWC2rv53k13/vy5GmE=; b=uyEx0nE/SAyTzjTgk64aRSIOnK84vQ9ouI3MQLIWszjHQOc/FuYILiFYpI0y4eBwAE 7YrnosX159EIY9NlV2gbzpwLfE2FwuwluSaBUru7FIuOne7FIV6gehz2kTLEsNOf0dpm kNOQUeJXq5sssihNWXcWroSUuWg2U05qOUUfMc9YjEvM5phauVqWJl/k8hBuTlPOVfeZ ZekV0JMBhpN6KkpY2x2ov7QNHexvxM/PMfJgN0W2VlxuPaN9X1/EXsB1O+d37RD7NTqf +quQ5+CBrKJGahxVf7Xp8bV6UXc54hYHuaG9/33IskeBE99TMOwBSqODQrVpMbtC96s8 2pAg==
Received: by 10.112.38.195 with SMTP id i3mr4874410lbk.21.1332170683351; Mon, 19 Mar 2012 08:24:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.4.166 with HTTP; Mon, 19 Mar 2012 08:24:23 -0700 (PDT)
In-Reply-To: <5710F82C0E73B04FA559560098BF95B1250DCE94E0@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
References: <B327D847-B059-41D7-A468-8B8A5DB8BFCE@gmx.net> <4E1F6AAD24975D4BA5B16804296739436641D81E@TK5EX14MBXC284.redmond.corp.microsoft.com> <5710F82C0E73B04FA559560098BF95B1250DCE94E0@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
From: Blaine Cook <romeda@gmail.com>
Date: Mon, 19 Mar 2012 15:24:23 +0000
Message-ID: <CAAz=scmv6BOYpc0_Nnixz64ZywPmBPf+2xPok4LCu5JMcY1=xw@mail.gmail.com>
To: "Zeltsan, Zachary (Zachary)" <zachary.zeltsan@alcatel-lucent.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth WG Re-Chartering
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Mon, 19 Mar 2012 15:24:47 -0000

On 15 March 2012 17:31, Zeltsan, Zachary (Zachary)
<zachary.zeltsan@alcatel-lucent.com> wrote:
> ...  Considering OpenID Connect as a motivating use case for OAuth, SWD is
> the one spec that would then be missing for this OAuth use case.

I worry that bringing OpenID Connect into OAuth (rather than building
upon OAuth) will have detrimental effects for both efforts. OAuth is
successful in part because we chose not to push OAuth-like
functionality into the OpenID umbrella (which at the time was focused
on shipping OpenID 2.0).

It seems prudent to learn from the experience of WS-*, where
everything was combined into one huge ball of standards-wax. The
result was both impenetrable and not fit for purpose due to the many
interdependencies (both social and technical) involved.

Composition has served the IETF and the internet well, and nothing
prevents the OpenID standards from being created in the context of a
new working group, or from within the OpenID foundation. Indeed, it's
been working quite well, and projects like the Account Chooser are
showing great promise and focusing on the important things (UX) rather
than specifications-for-specification's sake.

b.