IETF Logo Mail Archive

Re: [OAUTH-WG] Token Transfer Protocol

Marius Scurtescu <mscurtescu@google.com> Mon, 18 October 2010 23:19 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 182133A6B17 for <oauth@core3.amsl.com>; Mon, 18 Oct 2010 16:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.088
X-Spam-Level:
X-Spam-Status: No, score=-104.088 tagged_above=-999 required=5 tests=[AWL=1.889, 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 K1WoA7W6IAay for <oauth@core3.amsl.com>; Mon, 18 Oct 2010 16:18:43 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 086E93A6AB6 for <oauth@ietf.org>; Mon, 18 Oct 2010 16:18:42 -0700 (PDT)
Received: from kpbe11.cbf.corp.google.com (kpbe11.cbf.corp.google.com [172.25.105.75]) by smtp-out.google.com with ESMTP id o9INKAPA012049 for <oauth@ietf.org>; Mon, 18 Oct 2010 16:20:11 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1287444011; bh=ykSbik6gUo3bEg5xXqH+CYRexf4=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type:Content-Transfer-Encoding; b=O60f0Qb+xR7o5xk+4OpiAf1vdupLXYKgblI6qBsTCmSBvcU90nc6cMolJrqm9E+j3 qqT01N+tyuQ/8f/avUr8g==
Received: from yxt3 (yxt3.prod.google.com [10.190.5.195]) by kpbe11.cbf.corp.google.com with ESMTP id o9INK96A013094 for <oauth@ietf.org>; Mon, 18 Oct 2010 16:20:09 -0700
Received: by yxt3 with SMTP id 3so931377yxt.34 for <oauth@ietf.org>; Mon, 18 Oct 2010 16:20:09 -0700 (PDT)
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 :content-transfer-encoding; bh=jcwO8vSN+HmMYCNUjydMuERZ9JwwpkdnVNHgW0co6XQ=; b=hnaR7ONfOCn/M6f6/p5LmXLTHX6S/KHI0sFfA55G4iIWlF5I+nMBq1zZVRH8Mqy2EA +dZWypK1GDRUxmIwuzuA==
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:content-transfer-encoding; b=IcZ1yxhkbfdPvPmZOKgo4TwuAHIzOK+Q0JxMVvhSzO3BGvs2Fo+R0cAAoFRSaQbpSr lpI2D46C+1nw120pDzHg==
Received: by 10.100.37.7 with SMTP id k7mr3340093ank.85.1287444008863; Mon, 18 Oct 2010 16:20:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.101.123.19 with HTTP; Mon, 18 Oct 2010 16:19:48 -0700 (PDT)
In-Reply-To: <4CBC6FC0.5040708@cs.uni-goettingen.de>
References: <4CBC6FC0.5040708@cs.uni-goettingen.de>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Mon, 18 Oct 2010 16:19:48 -0700
Message-ID: <AANLkTikOMNONDddnWs_u8Xtuz_cPLtwmLb1J4ALfzbBB@mail.gmail.com>
To: Niklas Neumann <niklas.neumann@cs.uni-goettingen.de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Token Transfer Protocol
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, 18 Oct 2010 23:19:04 -0000

Trying to imagine a real world use case.

For example, section 2.2, how would the public terminal know that a
user device exists, let alone where?

Thanks,
Marius



On Mon, Oct 18, 2010 at 9:03 AM, Niklas Neumann
<niklas.neumann@cs.uni-goettingen.de> wrote:
> Hello everybody,
>
> I am currently working on a projected related to authentication and secure
> token transfer between multiple devices. As such we are employing a simple
> protocol that handles token transfers independent of the actual type of
> token. We have adapted the protocol to be used with OAuth tokens and
> submitted it as an Internet Draft:
> http://tools.ietf.org/html/draft-neumann-oauth-token-transfer
>
> I was wondering if there is interest in employing such a protocol in cases
> where the HTTP redirection schemes of OAuth are not available or not working
> well (e.g. desktop applications without access to a user agent or
> authentication from a different device/application than the one accessing
> the consumer).
>
> Compared to other proposals such as
> draft-dehora-farrell-oauth-accesstoken-creds the STTP is more heavyweight
> but in turn it also has more options. With regards to authentication we
> didn't use SASL for complexity reasons in our work initialy but I don't see
> any reason not to include it if this is deemed more appropriate.
>
> The work that the draft is based on is still ongoing. Please understand the
> draft as no more than a discussion proposal on how OAuth could be opened to
> non-web-based environments and scenarios that involve multiple devices
> without overloading the OAuth specification itself. I am happy to further
> improve the draft if you think this might be a viable option.
>
> Best regards
>  Niklas
>
> --
> Niklas Neumann - University of Goettingen, Institute of Computer Science
> http://user.informatik.uni-goettingen.de/~nneuman1/
> Tel: +49 551 39-172053
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

v2.23.0 | Report a Bug | By Email