Re: [OAUTH-WG] Document Management Issue (Signatures)
Lukas Rosenstock <lr@lukasrosenstock.net> Mon, 27 September 2010 21:43 UTC
Return-Path: <lr@lukasrosenstock.net>
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 C7E4B3A6DD6 for <oauth@core3.amsl.com>; Mon, 27 Sep 2010 14:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.464
X-Spam-Level:
X-Spam-Status: No, score=-1.464 tagged_above=-999 required=5 tests=[AWL=0.512, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 HKPvRePKrgGX for <oauth@core3.amsl.com>; Mon, 27 Sep 2010 14:43:42 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 20A3F3A6BC5 for <oauth@ietf.org>; Mon, 27 Sep 2010 14:43:30 -0700 (PDT)
Received: by qwc9 with SMTP id 9so4209145qwc.31 for <oauth@ietf.org>; Mon, 27 Sep 2010 14:43:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.114.163 with SMTP id e35mr5943221qaq.140.1285623780908; Mon, 27 Sep 2010 14:43:00 -0700 (PDT)
Received: by 10.229.221.9 with HTTP; Mon, 27 Sep 2010 14:43:00 -0700 (PDT)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343D460DB374@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <3D3C75174CB95F42AD6BCC56E5555B45031BA596@FIESEXC015.nsn-intra.net> <DB4FC8C2-816C-4527-8EC4-BC22B171B34C@oracle.com> <90C41DD21FB7C64BB94121FBBC2E72343D460DB374@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Mon, 27 Sep 2010 23:43:00 +0200
Message-ID: <AANLkTim-5hYzBqzXYK=qZaK3HXiLyzE5XqFAJuPCYo5S@mail.gmail.com>
From: Lukas Rosenstock <lr@lukasrosenstock.net>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: multipart/alternative; boundary="00c09ffb5584c69e5d0491449c03"
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Document Management Issue (Signatures)
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, 27 Sep 2010 21:43:44 -0000
2010/9/27 Eran Hammer-Lahav <eran@hueniverse.com> > I would also be happy with the core only dealing with **getting** a token, > and moving all text about **using** a token to other documents. This will > produce three parts: > > > > 1. Getting a document > > 2. Using bearer tokens > > 3. Using cryptographic tokens > > Won't there be any scenarios in which signatures are required for getting a token, like in OAuth 1 (the request is signed with the client id/secret)?
- [OAUTH-WG] Document Management Issue (Signatures) Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [OAUTH-WG] Document Management Issue (Signatu… Phil Hunt
- Re: [OAUTH-WG] Document Management Issue (Signatu… Eran Hammer-Lahav
- Re: [OAUTH-WG] Document Management Issue (Signatu… Eran Hammer-Lahav
- Re: [OAUTH-WG] Document Management Issue (Signatu… Lukas Rosenstock
- Re: [OAUTH-WG] Document Management Issue (Signatu… Eran Hammer-Lahav