IETF Logo Mail Archive

Re: [OAUTH-WG] New service provider that supports OAuth 2.0

Brian Eaton <beaton@google.com> Fri, 23 April 2010 17:07 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 71B0A3A6829 for <oauth@core3.amsl.com>; Fri, 23 Apr 2010 10:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.76
X-Spam-Level:
X-Spam-Status: No, score=-101.76 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 UkfEQ4lqIcpt for <oauth@core3.amsl.com>; Fri, 23 Apr 2010 10:07:28 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 775BC3A67EF for <oauth@ietf.org>; Fri, 23 Apr 2010 10:07:28 -0700 (PDT)
Received: from hpaq14.eem.corp.google.com (hpaq14.eem.corp.google.com [10.3.21.14]) by smtp-out.google.com with ESMTP id o3NH7GOl006673 for <oauth@ietf.org>; Fri, 23 Apr 2010 19:07:16 +0200
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1272042436; bh=dBRc0nFsDfxGmwXr3HI4Bxx7Qb0=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=F3zVQUBDNPFIbQaV8LaaukxzG1gYD/bKx804jgAKo4Yibkznv71vh1Q67oh778Uqu lENPFd3FrKUCy8eNhQ0WQ==
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=KNjuj2dcb2XRF43zdW/iChrQ9X+PTBmSCgn7Xt7/IJRlnLbooIVo73BelhFxM8jbn 84qx4zmCWv762NlXnPCxg==
Received: from pxi18 (pxi18.prod.google.com [10.243.27.18]) by hpaq14.eem.corp.google.com with ESMTP id o3NH7EpO005087 for <oauth@ietf.org>; Fri, 23 Apr 2010 19:07:15 +0200
Received: by pxi18 with SMTP id 18so936175pxi.29 for <oauth@ietf.org>; Fri, 23 Apr 2010 10:07:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.209.17 with SMTP id h17mr218097wfg.303.1272042433635; Fri, 23 Apr 2010 10:07:13 -0700 (PDT)
Received: by 10.142.202.10 with HTTP; Fri, 23 Apr 2010 10:07:13 -0700 (PDT)
In-Reply-To: <2513A610118CC14C8E622C376C8DEC93D54D66E0B5@SC-MBXC1.TheFacebook.com>
References: <C7F49997.2BF3F%atom@yahoo-inc.com> <137315b9d471f0b8c28d76a393cb31ef@mail.gmail.com> <1272034508.9646.46.camel@localhost.localdomain> <2513A610118CC14C8E622C376C8DEC93D54D66E0B5@SC-MBXC1.TheFacebook.com>
Date: Fri, 23 Apr 2010 10:07:13 -0700
Message-ID: <g2ydaf5b9571004231007xfb1d39c5p1a29b5fd5d08c987@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Luke Shepard <lshepard@facebook.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] New service provider that supports OAuth 2.0
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: Fri, 23 Apr 2010 17:07:29 -0000

On Fri, Apr 23, 2010 at 10:03 AM, Luke Shepard <lshepard@facebook.com> wrote:
> I agree that this is a risk, but we are doing everything we can to mitigate it. The version of OAuth we
> pushed on Wednesday is up to date as of Eran's Monday draft - I think that should be taken as a
> sign of honest good faith to stay in sync here. There will no doubt be some churn as the spec evolves.
> I promise to try to raise any issues we see early so that if Facebook ends up not supporting some
> piece of the spec, the reasons are obvious.

This is going to be really critical to making sure that we have a
mature OAuth 2.0 spec.  Thanks.

v2.23.0 | Report a Bug | By Email