IETF Logo Mail Archive

Re: [OAUTH-WG] Signatures, Why?

Brian Eaton <beaton@google.com> Tue, 16 March 2010 17:51 UTC

Return-Path: <beaton@google.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 105DF3A68E8 for <oauth@core3.amsl.com>; Tue, 16 Mar 2010 10:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.965
X-Spam-Level:
X-Spam-Status: No, score=-105.965 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 STB8xOS9S-4p for <oauth@core3.amsl.com>; Tue, 16 Mar 2010 10:51:07 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.33.17]) by core3.amsl.com (Postfix) with ESMTP id 5EF6F3A697D for <oauth@ietf.org>; Tue, 16 Mar 2010 10:50:59 -0700 (PDT)
Received: from spaceape11.eur.corp.google.com (spaceape11.eur.corp.google.com [172.28.16.145]) by smtp-out.google.com with ESMTP id o2GHp6V7008311 for <oauth@ietf.org>; Tue, 16 Mar 2010 17:51:06 GMT
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1268761866; bh=e48KFsxqhLGm9PJBJZKrMzWnmQw=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=SORn7jK25QPDSDS1LoDXIggF60peGXJXJTfNIZz43hgoK3zGVYZAL97YHXwM5O8t2 2HW9u5Lf/Up2oaoXtfDNA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=VkQbxRS1vEApYCYMefSxouZRY/x2dGAdsx7ouw4xrPfQvomoZVBlnP7INRTId/sMf fLjixQrXWZKPjDQ0AXjXA==
Received: from vws10 (vws10.prod.google.com [10.241.21.138]) by spaceape11.eur.corp.google.com with ESMTP id o2GHocIJ014795 for <oauth@ietf.org>; Tue, 16 Mar 2010 10:51:05 -0700
Received: by vws10 with SMTP id 10so108074vws.18 for <oauth@ietf.org>; Tue, 16 Mar 2010 10:51:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.124.15 with SMTP id s15mr17686vcr.60.1268761864954; Tue, 16 Mar 2010 10:51:04 -0700 (PDT)
In-Reply-To: <4B9EB99F.1050609@lodderstedt.net>
References: <d37b4b431003041200n1fc6cc5au83194aca28763b0d@mail.gmail.com> <4B99B2DD.3000405@stpeter.im> <4B99D783.1090905@lodderstedt.net> <4B9EB99F.1050609@lodderstedt.net>
Date: Tue, 16 Mar 2010 10:51:04 -0700
Message-ID: <daf5b9571003161051s42e6245dp819260f894a17e8d@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Paul Lindner <lindner@inuus.com>, Eve Maler <eve@xmlgrrl.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Signatures, Why?
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, 16 Mar 2010 17:51:10 -0000

On Mon, Mar 15, 2010 at 3:50 PM, Torsten Lodderstedt
<torsten@lodderstedt.net> wrote:
> Hi all,
>
> I composed a detailed summary at
> http://trac.tools.ietf.org/wg/oauth/trac/wiki/SignaturesWhy. Please review
> it.

We didn't talk about the signed identity claims use case.  Some
background on that is in this thread:

http://www.ietf.org/mail-archive/web/oauth/current/msg00530.html

Paul - does OpenSocial still need signed identity claims?

Eve - does UMA still need signed identity claims, or are you handling
that outside of the OAuth spec?

Cheers,
Brian

v2.23.0 | Report a Bug | By Email