Re: [OAUTH-WG] Change grant_type="none" to something less confusing

Brian Eaton <beaton@google.com> Fri, 16 July 2010 22:30 UTC

Return-Path: <beaton@google.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 221F03A685E for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 15:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.824
X-Spam-Level:
X-Spam-Status: No, score=-105.824 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 6re16M480o8d for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 15:30:19 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 666A13A6823 for <oauth@ietf.org>; Fri, 16 Jul 2010 15:30:19 -0700 (PDT)
Received: from hpaq7.eem.corp.google.com (hpaq7.eem.corp.google.com [172.25.149.7]) by smtp-out.google.com with ESMTP id o6GMUUfD030325 for <oauth@ietf.org>; Fri, 16 Jul 2010 15:30:31 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1279319431; bh=RSanxpZxjGEglobOua6KcNwKc74=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=oBb0xsB5oOOIRLwym+u0B0ahvUadiLXMAV5RMkO/KM0ky3feuIMiRqWGQFi707tzh OYQlHGlKRInHlUaufYSIw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=BvxYRfcevbIHWrSahgCss0f3mapXUhrAMY+or/4Zab5hg2CSbE4KcyrF98nIwDH+O BtB62cE/IujQ5IrjLQ5ZQ==
Received: from pwi5 (pwi5.prod.google.com [10.241.219.5]) by hpaq7.eem.corp.google.com with ESMTP id o6GMUSps018117 for <oauth@ietf.org>; Fri, 16 Jul 2010 15:30:29 -0700
Received: by pwi5 with SMTP id 5so987956pwi.19 for <oauth@ietf.org>; Fri, 16 Jul 2010 15:30:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.232.21 with SMTP id e21mr2416424wfh.92.1279319428219; Fri, 16 Jul 2010 15:30:28 -0700 (PDT)
Received: by 10.142.193.19 with HTTP; Fri, 16 Jul 2010 15:30:28 -0700 (PDT)
In-Reply-To: <32537D24-A84A-482C-8B9B-ECA14CB5325C@hueniverse.com>
References: <1279297826.11628.61.camel@localhost.localdomain> <AANLkTinRE0My8GRTVrBM9cwyCWgrpeYQzul3YBp_Z-8A@mail.gmail.com> <5F922BD8-22C9-4E87-9D5B-BAC0529F94C7@hueniverse.com> <AANLkTimAeHyKBAWnia9UU88WvyrFr6GimPrXFEDf_2p1@mail.gmail.com> <32537D24-A84A-482C-8B9B-ECA14CB5325C@hueniverse.com>
Date: Fri, 16 Jul 2010 15:30:28 -0700
Message-ID: <AANLkTin-kVa4GjON4SeqVykcpoi66qFk84-d8QBwz-Eu@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Change grant_type="none" to something less confusing
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 22:30:25 -0000

On Fri, Jul 16, 2010 at 3:27 PM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
> The client authentication can be used to retrieve a grant previously arranged.

Really?

Who is going to implement that?

I'm pretty sure that if the only inputs to the protocol are a client
name and a client password, the output is going to be an
authentication credential that belongs to the client.