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

Eran Hammer-Lahav <eran@hueniverse.com> Tue, 15 June 2010 07:16 UTC

Return-Path: <eran@hueniverse.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 279B33A69A8 for <oauth@core3.amsl.com>; Tue, 15 Jun 2010 00:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[AWL=0.497, BAYES_00=-2.599, 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 SsMBWrr8LFrZ for <oauth@core3.amsl.com>; Tue, 15 Jun 2010 00:16:46 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id 36EEF3A686E for <oauth@ietf.org>; Tue, 15 Jun 2010 00:16:46 -0700 (PDT)
Received: (qmail 11881 invoked from network); 15 Jun 2010 07:16:50 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.20) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 15 Jun 2010 07:16:50 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT002.EX1.SECURESERVER.NET ([72.167.180.20]) with mapi; Tue, 15 Jun 2010 00:16:51 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Date: Tue, 15 Jun 2010 00:16:56 -0700
Thread-Topic: [OAUTH-WG] OAuth meeting notes on -05 (with updates)
Thread-Index: AcsMV/7gjq1VfnrsSO+UKF60cMEnQQAArMFA
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343B3EBB68E8@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <90C41DD21FB7C64BB94121FBBC2E72343B3EBB68D9@P3PW5EX1MB01.EX1.SECURESERVER.NET> <CE5D9E50-D912-471C-BDCE-AA907365A795@lodderstedt.net>
In-Reply-To: <CE5D9E50-D912-471C-BDCE-AA907365A795@lodderstedt.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_90C41DD21FB7C64BB94121FBBC2E72343B3EBB68E8P3PW5EX1MB01E_"
MIME-Version: 1.0
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 07:16:47 -0000

How they communicate is out of scope.

EHL

From: Torsten Lodderstedt [mailto:torsten@lodderstedt.net]
Sent: Monday, June 14, 2010 11:57 PM
To: Eran Hammer-Lahav
Cc: OAuth WG (oauth@ietf.org)
Subject: Re: [OAUTH-WG] OAuth meeting notes on -05 (with updates)



- 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<mailto:eran@hueniverse.com>>:
- Explain that the separation between the authorization server and resource server is out of scope