Re: [OAUTH-WG] OAuth meeting notes on -05 (with updates)

Torsten Lodderstedt <torsten@lodderstedt.net> Tue, 15 June 2010 06:57 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 13D123A659C for <oauth@core3.amsl.com>; Mon, 14 Jun 2010 23:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level:
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 aXwJUibjibNS for <oauth@core3.amsl.com>; Mon, 14 Jun 2010 23:57:11 -0700 (PDT)
Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.31.35]) by core3.amsl.com (Postfix) with ESMTP id 163D63A6867 for <oauth@ietf.org>; Mon, 14 Jun 2010 23:57:11 -0700 (PDT)
Received: from [80.187.148.14] (helo=[10.135.145.183]) by smtprelay01.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1OOQ5B-00050N-Kg; Tue, 15 Jun 2010 08:57:13 +0200
References: <90C41DD21FB7C64BB94121FBBC2E72343B3EBB68D9@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Message-Id: <CE5D9E50-D912-471C-BDCE-AA907365A795@lodderstedt.net>
From: Torsten Lodderstedt <torsten@lodderstedt.net>
To: Eran Hammer-Lahav <eran@hueniverse.com>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343B3EBB68D9@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Content-Type: multipart/alternative; boundary="Apple-Mail-7--222419395"
Content-Transfer-Encoding: 7bit
X-Mailer: iPhone Mail (7E18)
Mime-Version: 1.0 (iPhone Mail 7E18)
Date: Tue, 15 Jun 2010 08:56:46 +0200
X-Df-Sender: 141509
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth meeting notes on -05 (with updates)
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, 15 Jun 2010 06:57:12 -0000

> - Explain that the separation between the authorization server and  
> resource server is out of scope

Why is this out of scope? I consider this a major improvement over  
Oauth 1.0.

regards,
Torsten.


Am 15.06.2010 um 08:35 schrieb Eran Hammer-Lahav <eran@hueniverse.com>:

> - Explain that the separation between the authorization server and  
> resource server is out of scope