Re: [dix] Google Account Authorization - slightly off topic

"Ben Laurie" <benl@google.com> Mon, 03 July 2006 13:42 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FxOge-0003Jn-3u; Mon, 03 Jul 2006 09:42:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FxOgd-0003H7-EN for dix@ietf.org; Mon, 03 Jul 2006 09:42:03 -0400
Received: from smtp-out.google.com ([216.239.45.12]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FxOgc-0003wm-1u for dix@ietf.org; Mon, 03 Jul 2006 09:42:03 -0400
Received: from death.corp.google.com (death.corp.google.com [172.24.0.123]) by smtp-out.google.com with ESMTP id k63Dfr4o025354 for <dix@ietf.org>; Mon, 3 Jul 2006 06:41:58 -0700
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:message-id:date:from:to:subject:cc:in-reply-to: mime-version:content-type:content-transfer-encoding: content-disposition:references; b=vwGsy0OA8I0rzdVWgqzDflhHEdygxgFogprXHStExQBNXMoMNwdXhUnBdOzO3kSOG QCOiXl7WoxFg9wH6Qdwmw==
Received: from smtp-out2.google.com (fpx33.prod.google.com [10.253.24.33]) by death.corp.google.com with ESMTP id k63DfoYa021958 for <dix@ietf.org>; Mon, 3 Jul 2006 06:41:50 -0700
Received: by smtp-out2.google.com with SMTP id 33so431924fpx for <dix@ietf.org>; Mon, 03 Jul 2006 06:41:50 -0700 (PDT)
Received: by 10.253.15.18 with SMTP id 18mr456723fpo; Mon, 03 Jul 2006 06:41:50 -0700 (PDT)
Received: by 10.253.14.2 with HTTP; Mon, 3 Jul 2006 06:41:50 -0700 (PDT)
Message-ID: <1b587cab0607030641n3afa4a3y7c3e87d06f38a2c4@mail.google.com>
Date: Mon, 3 Jul 2006 14:41:50 +0100
From: "Ben Laurie" <benl@google.com>
To: "Digital Identity Exchange" <dix@ietf.org>
Subject: Re: [dix] Google Account Authorization - slightly off topic
In-Reply-To: <AA509076-C82C-4FD9-BE23-9E86E70A9C1E@sxip.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20060619220742.40B85222427@laser.networkresonance.com> <p07000c00c0c5023c5dc0@12.105.228.215> <E9A9F044-1A43-4C5E-9B35-B2408B6CD8E0@sxip.com> <AA509076-C82C-4FD9-BE23-9E86E70A9C1E@sxip.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: IETF HTTP Auth <ietf-http-auth@lists.osafoundation.org>
X-BeenThere: dix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Digital Identity Exchange <dix@ietf.org>
List-Id: Digital Identity Exchange <dix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dix>, <mailto:dix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/dix>
List-Post: <mailto:dix@ietf.org>
List-Help: <mailto:dix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dix>, <mailto:dix-request@ietf.org?subject=subscribe>
Errors-To: dix-bounces@ietf.org

On 6/29/06, Dick Hardt <dick@sxip.com> wrote:
> Google rolled out some some APIs[1] to make it easier for rich clients
> [2] and websites[3] to act on behalf of a Google user. Of course this
> deepens the identity silo that is building at Google. [3] looks like
> some concepts that ekr has been talking about.
>
> Ben: hate to put you on the spot, but is Google looking to
> participate in WAE?

I will be at the WAE BoF, so, to that extent, yes. Google is certainly
interested in (some of) the problems WAE may work on.

> [1] http://code.google.com/apis/accounts/Authentication.html
> [2] http://code.google.com/apis/accounts/AuthForInstalledApps.html
> [3] http://code.google.com/apis/accounts/AuthForWebApps.html
>
>
> _______________________________________________
> dix mailing list
> dix@ietf.org
> https://www1.ietf.org/mailman/listinfo/dix
>

_______________________________________________
dix mailing list
dix@ietf.org
https://www1.ietf.org/mailman/listinfo/dix