Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization header
Torsten Lodderstedt <torsten@lodderstedt.net> Thu, 15 July 2010 06:22 UTC
Return-Path: <torsten@lodderstedt.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 695A33A69D0 for <oauth@core3.amsl.com>; Wed, 14 Jul 2010 23:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.059
X-Spam-Level:
X-Spam-Status: No, score=-2.059 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 2Kz9QKlakK4l for <oauth@core3.amsl.com>; Wed, 14 Jul 2010 23:22:56 -0700 (PDT)
Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.31.24]) by core3.amsl.com (Postfix) with ESMTP id 8415D3A681A for <oauth@ietf.org>; Wed, 14 Jul 2010 23:22:56 -0700 (PDT)
Received: from [79.253.14.82] (helo=[192.168.71.23]) by smtprelay01.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1OZHqb-0003ev-JR; Thu, 15 Jul 2010 08:23:05 +0200
Message-ID: <4C3EA944.1060302@lodderstedt.net>
Date: Thu, 15 Jul 2010 08:23:00 +0200
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Brian Eaton <beaton@google.com>
References: <AANLkTim6az--AdwmEoew2pz3kEjhc_GyEaiyo_0UhSRr@mail.gmail.com>
In-Reply-To: <AANLkTim6az--AdwmEoew2pz3kEjhc_GyEaiyo_0UhSRr@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Df-Sender: torsten@lodderstedt-online.de
Cc: 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 06:22:57 -0000
+1 for "OAuth2" Brian Eaton schrieb: > Draft 10 switched from "Token" scheme in the authorization header to > "OAuth". I'd rather we didn't reuse OAuth. 'OAuth2' would be great. > "Token" is ugly as sin, but is better than "OAuth". > > Spec section: http://tools.ietf.org/html/draft-ietf-oauth-v2-10#page-30 > > The problem with reusing "OAuth" is that there are existing > implementations in the wild that have special behavior implemented for > OAuth authorization headers. Since OAuth2 headers don't have the same > semantics, we're going to break those implementations. We shouldn't > reuse "OAuth" for the same reasons we shouldn't reuse "Negotiate", > "NTLM", "Digest", or "Basic. > > Cheers, > Brian > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth >
- [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