IETF Logo Mail Archive

Re: [OAUTH-WG] 4.2 Access Token Response in draft 8

Eran Hammer-Lahav <eran@hueniverse.com> Wed, 16 June 2010 03:27 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 B516A3A67AD for <oauth@core3.amsl.com>; Tue, 15 Jun 2010 20:27:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level:
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[AWL=0.427, BAYES_00=-2.599]
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 U34PrnWrdMdu for <oauth@core3.amsl.com>; Tue, 15 Jun 2010 20:27:36 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 7854A3A66B4 for <oauth@ietf.org>; Tue, 15 Jun 2010 20:27:36 -0700 (PDT)
Received: (qmail 13185 invoked from network); 16 Jun 2010 03:27:40 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 16 Jun 2010 03:27:39 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Tue, 15 Jun 2010 20:27:39 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Nat <sakimura@gmail.com>
Date: Tue, 15 Jun 2010 20:27:28 -0700
Thread-Topic: [OAUTH-WG] 4.2 Access Token Response in draft 8
Thread-Index: AcsNAQ1JFLJCPPnqTQapIsz8Ve3E0wAAsinw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343B3EBB6C32@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <AANLkTiklqt70rJqY5E8BLcqTWhIuxX1SJrGjdFeTkXfS@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343B3EBB6C2E@P3PW5EX1MB01.EX1.SECURESERVER.NET> <A0A9E031-7DCC-48B5-AF23-7F17FF6A15B6@gmail.com>
In-Reply-To: <A0A9E031-7DCC-48B5-AF23-7F17FF6A15B6@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: oauth <oauth@ietf.org>
Subject: Re: [OAUTH-WG] 4.2 Access Token Response in draft 8
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: Wed, 16 Jun 2010 03:27:37 -0000

-09

-----Original Message-----
From: Nat [mailto:sakimura@gmail.com] 
Sent: Tuesday, June 15, 2010 8:08 PM
To: Eran Hammer-Lahav
Cc: oauth
Subject: Re: [OAUTH-WG] 4.2 Access Token Response in draft 8

I am looking forward to the extension mechanism. Is it coming in draft 10?

=nat @ Tokyo via iPhone

On 2010/06/16, at 11:52, Eran Hammer-Lahav <eran@hueniverse.com> wrote:

> There is nothing in the spec to prevent other parameters. There will 
> be specific methods to extend the protocol.
>
> EHL
>
> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf 
> Of Nat Sakimura
> Sent: Tuesday, June 15, 2010 6:27 PM
> To: oauth
> Subject: [OAUTH-WG] 4.2 Access Token Response in draft 8
>
> It is my understanding that access token response may contain other 
> parameters than what is stated there.
> Sometimes, mutually understanding server and client may want to 
> exchange other parameters on top of it and is legitimate, IMHO.
>
> Is this understanding correct?
>
>
> --
> Nat Sakimura (=nat)
> http://www.sakimura.org/en/
> http://twitter.com/_nat_en
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

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