Re: [OAUTH-WG] Status update

Nat <sakimura@gmail.com> Thu, 17 June 2010 23:41 UTC

Return-Path: <sakimura@gmail.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 90FC03A6B47 for <oauth@core3.amsl.com>; Thu, 17 Jun 2010 16:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 G4DOL3VjVDgl for <oauth@core3.amsl.com>; Thu, 17 Jun 2010 16:41:56 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 212433A6B3F for <oauth@ietf.org>; Thu, 17 Jun 2010 16:41:56 -0700 (PDT)
Received: by pwj8 with SMTP id 8so226749pwj.31 for <oauth@ietf.org>; Thu, 17 Jun 2010 16:41:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date:cc; bh=Amq+57uhpJwOkyWzhUwLSGFYhogrCFW3D84UmTwYeZ4=; b=V4rK6lkiZ88dF22kUNnaJOzwdragDnESqYbTgHeY2it0YkR3YIY0Gayh4MK6iqEjS5 GHImnHvFyxvr8Sdopmw/3VC/c4qxtVc/opGqUTvtKZTeRXXEJmvv0OLkE8d7EmIemT3O NkdSH8QANn4o5iq91EdIzFb2lC9X8jitOIWGE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc; b=WyOMAnbJesOObm7jlzE7h4AcjCxJl9Tfl2ml0WWP0QWoSIBfO9VkN7akpgG2aH/3Bb 1w0WxfHLk7cEo3IM0IEvSxGQKxvl0N67pRcwOyuPIqrnDDtssuptamz0ick8IdyWYm91 MNfdcWfDAQR/ueJEH8B/A5rWRcXFa4uFCulKQ=
Received: by 10.115.135.24 with SMTP id m24mr190455wan.129.1276818118746; Thu, 17 Jun 2010 16:41:58 -0700 (PDT)
Received: from [192.168.2.4] (pd846f3.tokynt01.ap.so-net.ne.jp [111.216.70.243]) by mx.google.com with ESMTPS id 33sm101061994wad.8.2010.06.17.16.41.56 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 17 Jun 2010 16:41:57 -0700 (PDT)
References: <90C41DD21FB7C64BB94121FBBC2E72343B3EBB71D3@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Message-Id: <35F209BF-D22B-4C3F-919F-15EAD4844A15@gmail.com>
From: Nat <sakimura@gmail.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343B3EBB71D3@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Content-Type: text/plain; charset="Shift_JIS"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (7E18)
Mime-Version: 1.0 (iPhone Mail 7E18)
Date: Fri, 18 Jun 2010 08:42:21 +0900
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Status update
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: Thu, 17 Jun 2010 23:41:58 -0000

What about the 'request_url' indirection (without sig and enc)?

On 2010/06/18, at 6:36, Eran Hammer-Lahav <eran@hueniverse.com> wrote:

> With the exception of extensibility, I consider draft -08 to be  
> feature complete. This means that the draft contains all the  
> features and components needed and other then editorial work is  
> close to finished. I plan to finish work on the -09 draft by Mon or  
> Tue next week which will include the extensibility text, additional  
> editorial work, and resolution of the proposal to simplify the end- 
> user authorization endpoint. At that point, I intend to ask for an  
> interim last-call on the normative language (i.e. the implementation  
> details).
>
>
>
> Note that this last-call isn’t really a WG last call. The spec can c 
> hange after that. But it will be a useful milestone to figure out if 
>  the draft’s implementation details are stable and can be considered 
>  complete.
>
>
>
> All of this of course requires the approval of the chairs.
>
>
>
> EHL
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth