Re: [OAUTH-WG] Native Client Extension

Marius Scurtescu <mscurtescu@google.com> Tue, 04 January 2011 22:56 UTC

Return-Path: <mscurtescu@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 628083A6A26 for <oauth@core3.amsl.com>; Tue, 4 Jan 2011 14:56:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.447
X-Spam-Level:
X-Spam-Status: No, score=-104.447 tagged_above=-999 required=5 tests=[AWL=-1.470, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 aBM1I20qp-oI for <oauth@core3.amsl.com>; Tue, 4 Jan 2011 14:56:44 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 83ADB3A6A15 for <oauth@ietf.org>; Tue, 4 Jan 2011 14:56:44 -0800 (PST)
Received: from kpbe14.cbf.corp.google.com (kpbe14.cbf.corp.google.com [172.25.105.78]) by smtp-out.google.com with ESMTP id p04MwoFg032491 for <oauth@ietf.org>; Tue, 4 Jan 2011 14:58:50 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1294181931; bh=A/SwOdnX86Z698ApD4SRbNRYji0=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=gvP7HrE1L/CY0a5pnrcZe7/TH217gbwzSNI9ZFYqAxf+LlmgZL9S0CTkEYl/HDfnz aQEW1DGixVjrSZINLJVqg==
Received: from yie19 (yie19.prod.google.com [10.243.66.19]) by kpbe14.cbf.corp.google.com with ESMTP id p04MwnMS020307 for <oauth@ietf.org>; Tue, 4 Jan 2011 14:58:49 -0800
Received: by yie19 with SMTP id 19so3711800yie.3 for <oauth@ietf.org>; Tue, 04 Jan 2011 14:58:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=jS8+rWRAm92eejvoalVi0NwkHgu8irb3Fv7/sqVPylI=; b=G7z/6E9BGjtUZ+5uPo1L8DYECxoRdRs5NolOBxZGL1Req7caaI/DrAwthQEXkAenJY 88boQdVtPWR1mKI5DD5g==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=IqMGEkg73jqVV4GdLtTVvhk4BMBeEiVASmKJHWe4eKUkZxnw9lKt7fszV3egyt24AO sHubqwZIu3DvLNyuRs7Q==
Received: by 10.100.128.13 with SMTP id a13mr2414859and.235.1294181929189; Tue, 04 Jan 2011 14:58:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.123.14 with HTTP; Tue, 4 Jan 2011 14:58:29 -0800 (PST)
In-Reply-To: <4D239DCF.4030501@lodderstedt.net>
References: <AANLkTi=YWLHV1Yi0bdKTaDaBw3X5D6Y_kk3xt7EvJHe_@mail.gmail.com> <4D239DCF.4030501@lodderstedt.net>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Tue, 04 Jan 2011 14:58:29 -0800
Message-ID: <AANLkTi=RAS5X0jUjxFzf6k1_r+79NFSFjmZs2bw2Lg3o@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Native Client Extension
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, 04 Jan 2011 22:56:45 -0000

On Tue, Jan 4, 2011 at 2:23 PM, Torsten Lodderstedt
<torsten@lodderstedt.net> wrote:
> +1
>
> I have asked myself all the time why "oob" disappeared in OAuth 2.0? Does
> Google use this feature?

Yes, we are planning to support this, exactly as described in the extension.

Marius