Re: [OAUTH-WG] Facebook, OAuth, and WRAP

Brian Eaton <beaton@google.com> Mon, 30 November 2009 21:50 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 F2A0228C148 for <oauth@core3.amsl.com>; Mon, 30 Nov 2009 13:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level:
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[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 8EDNCVT-ie9x for <oauth@core3.amsl.com>; Mon, 30 Nov 2009 13:50:00 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.45.13]) by core3.amsl.com (Postfix) with ESMTP id 267B33A684C for <oauth@ietf.org>; Mon, 30 Nov 2009 13:50:00 -0800 (PST)
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id nAULnp5P006105 for <oauth@ietf.org>; Mon, 30 Nov 2009 13:49:52 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1259617792; bh=YaDmFP3vk1VI7vqMfiYw6nILqww=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=q3XY2IWsYO2LKc5o5rVxYp8owrzvpH3PwijCmp8mrmPKwFi/cKWV2ElIRLFHqvTQU wooO2ffjz7yOQ+/HmNlzg==
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:content-transfer-encoding:x-system-of-record; b=fhGHSG4/LKda6GE63qxxwkAbAde531+w8P9OjJsNl0YEfWtHxSZX3bfrIQytNkAnF NbONOqxojy+HFz2Yypjlw==
Received: from pzk7 (pzk7.prod.google.com [10.243.19.135]) by wpaz13.hot.corp.google.com with ESMTP id nAULl7cK001901 for <oauth@ietf.org>; Mon, 30 Nov 2009 13:49:49 -0800
Received: by pzk7 with SMTP id 7so6479990pzk.30 for <oauth@ietf.org>; Mon, 30 Nov 2009 13:49:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.164.2 with SMTP id m2mr341677rve.191.1259617788019; Mon, 30 Nov 2009 13:49:48 -0800 (PST)
In-Reply-To: <a9d9121c0911301144l7b08ba9l6acd358c29ae2b09@mail.gmail.com>
References: <148C596691F29F4EA6968577BE2CDFAE06A1B9FE@SC-MBXC1.TheFacebook.com> <a9d9121c0911241635p4f2cc394vefe350b2ce3daa22@mail.gmail.com> <C6B20C22-ED3A-4714-943F-FEA0A2347045@facebook.com> <a9d9121c0911301144l7b08ba9l6acd358c29ae2b09@mail.gmail.com>
Date: Mon, 30 Nov 2009 13:49:47 -0800
Message-ID: <daf5b9570911301349h1836c921o223837edd22e37d1@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Mike Malone <mjmalone@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: "oauth@ietf.org" <oauth@ietf.org>, Naitik Shah <naitik@facebook.com>, Luke Shepard <lshepard@facebook.com>
Subject: Re: [OAUTH-WG] Facebook, OAuth, and WRAP
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: Mon, 30 Nov 2009 21:50:01 -0000

On Mon, Nov 30, 2009 at 11:44 AM, Mike Malone <mjmalone@gmail.com> wrote:
>> Good point about the tokens. One of us should make a list of all the terms
>> in each spec, and then set up a mapping between the sets, to see if the
>> number of concepts is really all that different.
>
> My informal list (from a cursory read of the spec):
>  OAuth / WRAP
>  Consumer / Client
>  Request Token / Refresh Token

WRAP has no equivalent of the request token.  The closest thing is the
verification code.

>  Access Token / Access Token
>  Consumer Token / Client identifier & secret
>  OAuth Verifier / Verification Code

WRAP has a refresh token.  The closest OAuth analog is the session
handle used in the scalable OAuth extension.

Cheers,
Brian