Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization header

Lukas Rosenstock <lr@lukasrosenstock.net> Thu, 15 July 2010 17:36 UTC

Return-Path: <lr@lukasrosenstock.net>
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 28AC43A67BD for <oauth@core3.amsl.com>; Thu, 15 Jul 2010 10:36:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.141
X-Spam-Level:
X-Spam-Status: No, score=-1.141 tagged_above=-999 required=5 tests=[AWL=0.836, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 5Q2OLY2sszFa for <oauth@core3.amsl.com>; Thu, 15 Jul 2010 10:36:19 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 235C03A6A95 for <oauth@ietf.org>; Thu, 15 Jul 2010 10:36:19 -0700 (PDT)
Received: by qwe5 with SMTP id 5so326686qwe.31 for <oauth@ietf.org>; Thu, 15 Jul 2010 10:36:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.45.213 with SMTP id g21mr3420394qaf.382.1279215386102; Thu, 15 Jul 2010 10:36:26 -0700 (PDT)
Received: by 10.229.100.135 with HTTP; Thu, 15 Jul 2010 10:36:25 -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 19:36:25 +0200
Message-ID: <AANLkTikM3FS2CXUhA2wFBo9ffeLLOsHn__tkOV815qqK@mail.gmail.com>
From: Lukas Rosenstock <lr@lukasrosenstock.net>
To: Justin Richer <jricher@mitre.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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:36:20 -0000

+1 for both

2010/7/15 Justin Richer <jricher@mitre.org>:
> +1 on OAuth2 header, and I also want to see oauth2_token in URI and form
> parameter methods.
>
> 1.0 clients will talk to systems that support both oauth2 and oauth1
> simultaneously. Most likely on the same PR endpoints as well. Since the
> protocols are not backwards compatible, they should be able to coexist.
>
>  -- Justin
>