Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization header
Brian Eaton <beaton@google.com> Thu, 15 July 2010 17:12 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 02C0B3A6A2A for <oauth@core3.amsl.com>; Thu, 15 Jul 2010 10:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.799
X-Spam-Level:
X-Spam-Status: No, score=-105.799 tagged_above=-999 required=5 tests=[AWL=0.178, 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 cyTrHxpXUdUj for <oauth@core3.amsl.com>; Thu, 15 Jul 2010 10:12:54 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 134A13A69C6 for <oauth@ietf.org>; Thu, 15 Jul 2010 10:12:53 -0700 (PDT)
Received: from kpbe12.cbf.corp.google.com (kpbe12.cbf.corp.google.com [172.25.105.76]) by smtp-out.google.com with ESMTP id o6FHD4aJ003668 for <oauth@ietf.org>; Thu, 15 Jul 2010 10:13:04 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1279213984; bh=IZBjR8/T7JFhjxBEjtEnuSMX+Oo=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=g645D6apONpDHdwTCDRuOFzB+LaTs1r5ODhQ93CWd3mJJqUNmRLuvDp4ou/wUQGq4 9T4bjupC3ZtOTeDIqwDzw==
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=JK07QlUuUosNzK/oUMlwwPo9/I6X/YI31XgynRx2NukEe8tnztExpJ8vFtKhPp3JV LWycKY7Q3P1eGLIVWbkHA==
Received: from pwi5 (pwi5.prod.google.com [10.241.219.5]) by kpbe12.cbf.corp.google.com with ESMTP id o6FHD2nn003556 for <oauth@ietf.org>; Thu, 15 Jul 2010 10:13:03 -0700
Received: by pwi5 with SMTP id 5so359428pwi.19 for <oauth@ietf.org>; Thu, 15 Jul 2010 10:13:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.213.14 with SMTP id l14mr25220768wfg.90.1279213976883; Thu, 15 Jul 2010 10:12:56 -0700 (PDT)
Received: by 10.142.193.19 with HTTP; Thu, 15 Jul 2010 10:12:56 -0700 (PDT)
In-Reply-To: <1279205969.18579.55.camel@localhost.localdomain>
References: <AANLkTim6az--AdwmEoew2pz3kEjhc_GyEaiyo_0UhSRr@mail.gmail.com> <1279205969.18579.55.camel@localhost.localdomain>
Date: Thu, 15 Jul 2010 10:12:56 -0700
Message-ID: <AANLkTildz62l2Me26Dlrv5nNmp8Z3P8JD1K-ChcWc5IO@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Justin Richer <jricher@mitre.org>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization header
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, 15 Jul 2010 17:12:56 -0000
On Thu, Jul 15, 2010 at 7:59 AM, Justin Richer <jricher@mitre.org> wrote: > +1 on OAuth2 header, and I also want to see oauth2_token in URI and form > parameter methods. Good point about the query parameter names needing to be unambiguous.
- [OAUTH-WG] OAuth vs OAuth2 in Authorization header Brian Eaton
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… William Mills
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Torsten Lodderstedt
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Manger, James H
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Eran Hammer-Lahav
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Eran Hammer-Lahav
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Justin Richer
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Blaine Cook
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… William Mills
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Brian Eaton
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Lukas Rosenstock
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… David Recordon
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Brian Eaton
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… William Mills
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Justin Richer
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Luke Shepard
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… John Kemp
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… David Recordon
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Eran Hammer-Lahav
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… John Kemp
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Eran Hammer-Lahav
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… William Mills
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Marius Scurtescu
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Justin Richer
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Justin Richer
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Naitik Shah
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Torsten Lodderstedt
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Naitik Shah
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… William Mills
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Manger, James H