IETF Logo Mail Archive

Re: [OAUTH-WG] resource server id needed?

Torsten Lodderstedt <torsten@lodderstedt.net> Fri, 16 July 2010 16:41 UTC

Return-Path: <torsten@lodderstedt.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 06B4F3A6A8A for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 09:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level:
X-Spam-Status: No, score=-2.117 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 XYzp4OTQ8ydg for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 09:41:17 -0700 (PDT)
Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.31.36]) by core3.amsl.com (Postfix) with ESMTP id C1F7F3A695B for <oauth@ietf.org>; Fri, 16 Jul 2010 09:41:16 -0700 (PDT)
Received: from p4ffd0f3a.dip.t-dialin.net ([79.253.15.58] helo=[127.0.0.1]) by smtprelay02.ispgateway.de with esmtpa (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1OZnyZ-0008Ue-6H; Fri, 16 Jul 2010 18:41:27 +0200
Message-ID: <4C408BB2.7090409@lodderstedt.net>
Date: Fri, 16 Jul 2010 18:41:22 +0200
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: Brian Eaton <beaton@google.com>
References: <C8645B85.372D8%eran@hueniverse.com> <4C3F3F6A.5000409@lodderstedt.net> <AANLkTinIjg7MIBmEIUzV9_Uo3MDb0nXvYXJcXNeLTUCe@mail.gmail.com> <4C3F9064.6060604@lodderstedt.net> <6B1F8C6947A5DC48B613C46E7B420A3A074C1804@S4DE9JSAACX.ost.t-com.de> <AANLkTimXxuZaNg9S6Q0-qn7Zqf6-W4Uy2QhkiYaYENKu@mail.gmail.com>
In-Reply-To: <AANLkTimXxuZaNg9S6Q0-qn7Zqf6-W4Uy2QhkiYaYENKu@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Df-Sender: 141509
Cc: Wolfgang.Steigerwald@telekom.de, oauth@ietf.org
Subject: Re: [OAUTH-WG] resource server id needed?
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, 16 Jul 2010 16:41:19 -0000

Am 16.07.2010 18:35, schrieb Brian Eaton:
> On Fri, Jul 16, 2010 at 4:47 AM,<Wolfgang.Steigerwald@telekom.de>  wrote:
>    
>> +1 to Thorstens statement. There are use cases beyond local deployments.
>>      
> Definitely.
>
> For example, I'm interested in deployments where neither clients nor
> resource servers need secret keys.  This makes adding new clients and
> resource servers trivial.
>
> The challenge here is that even though lots of people are interested
> in various semantics for "scope", and various types of relations
> between clients, resource servers, and authorization servers, not
> everyone has the same use cases and requirements.
>    

then we should put those use cases and requirements on the table and try 
to find a solution fulfilling these different needs. That's what (from 
my point of view) standard definition is all about.

What do you think?

regards,
Torsten.

> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

v2.35.0 | Report a Bug | By Email | System Status