Return-Path: 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 08FEE3A68C7 for ; Fri, 2 Jul 2010 17:48:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.32 X-Spam-Level: X-Spam-Status: No, score=-17.32 tagged_above=-999 required=5 tests=[AWL=0.278, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_DEF_WHITELIST=-15] 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 EIILMeQQeJVg for ; Fri, 2 Jul 2010 17:48:44 -0700 (PDT) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by core3.amsl.com (Postfix) with ESMTP id 6848E3A68AF for ; Fri, 2 Jul 2010 17:48:44 -0700 (PDT) Received: from SNV-EXPF01.ds.corp.yahoo.com (snv-expf01.ds.corp.yahoo.com [207.126.227.250]) by mrout1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o630kl36093726; Fri, 2 Jul 2010 17:46:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:x-mimeole:content-class:mime-version: content-type:subject:date:message-id:in-reply-to:x-ms-has-attach: x-ms-tnef-correlator:thread-topic:thread-index:references:from:to:cc:return-path:x-originalarrivaltime; b=jJ5xkd/JANxhPJ6EEVZZLkdrhl/OoBS5h1N27V85Pedep9VEnEjIvlbE35CZdmpZ Received: from SNV-EXVS08.ds.corp.yahoo.com ([207.126.227.8]) by SNV-EXPF01.ds.corp.yahoo.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 2 Jul 2010 17:46:47 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB1A49.36F11C36" Date: Fri, 2 Jul 2010 17:46:46 -0700 Message-ID: <012AB2B223CB3F4BB846962876F47217059B69FB@SNV-EXVS08.ds.corp.yahoo.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [OAUTH-WG] Underscore, dash, green, blue Thread-Index: AcsaNGx5G+AwSVAcRjKYLXgtx+M57wAFK4TQ References: <90C41DD21FB7C64BB94121FBBC2E72343B3ED4C2E7@P3PW5EX1MB01.EX1.SECURESERVER.NET> <0E0C7232-0C39-4D2A-9918-FCD68F27E789@photobucket.com><90C41DD21FB7C64BB94121FBBC2E72343B3ED4C3D7@P3PW5EX1MB01.EX1.SECURESERVER.NET><0B379746-ED5A-4402-A8E6-1CF7D72ECE53@facebook.com><90C41DD21FB7C64BB94121FBBC2E72343B3ED4C456@P3PW5EX1MB01.EX1.SECURESERVER.NET> <90C41DD21FB7C64BB94121FBBC2E72343B3ED4C476@P3PW5EX1MB01.EX1.SECURESERVER.NET> From: "William Mills" To: , "Eran Hammer-Lahav" X-OriginalArrivalTime: 03 Jul 2010 00:46:47.0515 (UTC) FILETIME=[376F0AB0:01CB1A49] Cc: oauth@ietf.org Subject: Re: [OAUTH-WG] Underscore, dash, green, blue X-BeenThere: oauth@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2010 00:48:47 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CB1A49.36F11C36 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable +1 for _ =20 I don't find HTTP header names having dashes confusing, because they all do. ________________________________ From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of Joseph Smarr Sent: Friday, July 02, 2010 3:16 PM To: Eran Hammer-Lahav Cc: OAuth WG (oauth@ietf.org) Subject: Re: [OAUTH-WG] Underscore, dash, green, blue =09 =09 Just remember that dashes are problematic for JavaScript, since oauth_token is a valid variable name, but oauth-token is not. So unless you're sure this will never be a problem, +1 to underscores everywhere. I know HTTP headers normally use dash, but if you want to use dashes for headers and underscores everywhere, you have the burden of proof that this won't cause too much confusion...=20 Thanks, js =09 =09 On Thu, Jul 1, 2010 at 11:25 AM, Eran Hammer-Lahav wrote: =09 The 1.0 install base is small enough to ignore. Looking at the interest and community around 2.0 makes such considerations marginal. =09 There is no problem with underscores in headers, it is just unusual. =09 EHL =09 > -----Original Message----- > From: Marius Scurtescu [mailto:mscurtescu@google.com] > Sent: Thursday, July 01, 2010 11:19 AM > To: Eran Hammer-Lahav =09 > Cc: Luke Shepard; OAuth WG (oauth@ietf.org) > Subject: Re: [OAUTH-WG] Underscore, dash, green, blue > > 3 - all underscores. > > If underscores are a big issue with headers then we should consider 1 > - all dashes. The problem with all dashes is that it is counterintuitive for > people that know OAuth 1. > > Marius > > > > On Thu, Jul 1, 2010 at 11:01 AM, Eran Hammer-Lahav > wrote: > > > > > >> -----Original Message----- > >> From: Luke Shepard [mailto:lshepard@facebook.com] > >> Sent: Thursday, July 01, 2010 10:58 AM > >> To: Eran Hammer-Lahav > >> Cc: Justin Hart; Pelle Braendgaard; OAuth WG (oauth@ietf.org) > >> Subject: Re: [OAUTH-WG] Underscore, dash, green, blue > >> > >> Don't really care, but to pick one - underscores throughout. > >> > >> Why not headers? > > > > Historically, HTTP headers use dashes and not underscores, but there is > nothing to prevent us from using underscores throughout. > > > > EHL > > > >> On Jul 1, 2010, at 9:23 AM, Eran Hammer-Lahav wrote: > >> > >> > That's wasn't an option for a reason. Beside offending my esthetic > >> sensibility :-) having the same parameter use a different name > >> between the header and endpoint makes registration of extension > >> parameters much harder. For example, if we used this scheme, the > >> 'error-uri' parameter would require two registration requests, one > >> for 'error-uri' and another for 'error_uri'. > >> > > >> > EHL > >> > > >> >> -----Original Message----- > >> >> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On > >> >> Behalf Of Justin Hart > >> >> Sent: Thursday, July 01, 2010 7:10 AM > >> >> To: Pelle Braendgaard > >> >> Cc: OAuth WG (oauth@ietf.org) > >> >> Subject: Re: [OAUTH-WG] Underscore, dash, green, blue > >> >> > >> >> +1 for underscores except header keys. > >> >> ---- > >> >> -- Justin Hart > >> >> -- jhart@photobucket.com > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> On Jul 1, 2010, at 7:39 AM, Pelle Braendgaard wrote: > >> >> > >> >>> I already implemented 09 but it was a (very tiny) bit of a hassle > >> >>> to have to convert underscores. > >> >>> > >> >>> So I also agree with 3 except headers > >> >>> > >> >>> On Thu, Jul 1, 2010 at 2:41 AM, Lukas Rosenstock > >> >>> > >> >> wrote: > >> >>>> 3 except headers. > >> >>>> > >> >>>> 2010/7/1 Eran Hammer-Lahav : > >> >>>>> First, sorry about this. J > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> I do my best not to ask the group this kind of questions and > >> >>>>> just pick something on my own, but I can't decide so I'll run a > >> >>>>> quick vote (yes, a VOTE - I can't imagine seeking a consensus call on > this). > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> -09 uses underscores for parameter names (except for in the > >> >>>>> headers) and dashes for parameter values. This seems like an > >> >>>>> odd > >> selection. > >> >>>>> Before, it used dashes for header parameter names, and > >> >>>>> underscore everywhere else. Not great either. > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> So... > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> The changes my OCD can live with: > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> 1. Use dashes throughout > >> >>>>> > >> >>>>> 2. Use underscores for all parameter names (headers included), > >> >>>>> dashes for all values > >> >>>>> > >> >>>>> 3. Use underscores throughout > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> I want to get this done with in a day because people are > >> >>>>> writing code for > >> >>>>> -09 and I'd like to stop making changes beyond editorial. I > >> >>>>> just think that having different styles between the endpoint > >> >>>>> parameters and header parameters is broken. > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> EHL > >> >>>>> > >> >>>>> _______________________________________________ > >> >>>>> OAuth mailing list > >> >>>>> OAuth@ietf.org > >> >>>>> https://www.ietf.org/mailman/listinfo/oauth > >> >>>>> > >> >>>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> -- > >> >>>> http://lukasrosenstock.net/ > >> >>>> _______________________________________________ > >> >>>> OAuth mailing list > >> >>>> OAuth@ietf.org > >> >>>> https://www.ietf.org/mailman/listinfo/oauth > >> >>>> > >> >>> > >> >>> > >> >>> > >> >>> -- > >> >>> http://agree2.com - Reach Agreement! > >> >>> http://stakeventures.com - My blog about startups and agile > >> >>> banking > _______________________________________________ > >> >>> OAuth mailing list > >> >>> OAuth@ietf.org > >> >>> https://www.ietf.org/mailman/listinfo/oauth > >> >> > >> >> _______________________________________________ > >> >> OAuth mailing list > >> >> OAuth@ietf.org > >> >> https://www.ietf.org/mailman/listinfo/oauth > >> > _______________________________________________ > >> > OAuth mailing list > >> > OAuth@ietf.org > >> > https://www.ietf.org/mailman/listinfo/oauth > > > > _______________________________________________ > > OAuth mailing list > > OAuth@ietf.org > > https://www.ietf.org/mailman/listinfo/oauth > > _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth =09 ------_=_NextPart_001_01CB1A49.36F11C36 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
+1 for _
 
I don't find HTTP header names having dashes = confusing,=20 because they all do.

From: oauth-bounces@ietf.org=20 [mailto:oauth-bounces@ietf.org] On Behalf Of Joseph=20 Smarr
Sent: Friday, July 02, 2010 3:16 PM
To: Eran = Hammer-Lahav
Cc: OAuth WG = (oauth@ietf.org)
Subject: Re:=20 [OAUTH-WG] Underscore, dash, green, blue

Just remember that dashes are problematic for JavaScript, = since=20 oauth_token is a valid variable name, but oauth-token is not. So = unless you're=20 sure this will never be a problem, +1 to underscores everywhere. I = know HTTP=20 headers normally use dash, but if you want to use dashes for headers = and=20 underscores everywhere, you have the burden of proof that this won't = cause too=20 much confusion...

Thanks, js

On Thu, Jul 1, 2010 at 11:25 AM, Eran = Hammer-Lahav=20 <eran@hueniverse.com> = wrote:
The 1.0 install base is small enough to ignore. = Looking at=20 the interest and community around 2.0 makes such considerations=20 marginal.

There is no problem with underscores in headers, it = is just=20 unusual.

EHL

> -----Original Message-----
> From: = Marius=20 Scurtescu [mailto:mscurtescu@google.com]
> = Sent:=20 Thursday, July 01, 2010 11:19 AM
> To: Eran = Hammer-Lahav
> Cc: Luke Shepard; OAuth WG (oauth@ietf.org)
> Subject: = Re:=20 [OAUTH-WG] Underscore, dash, green, blue
>
> 3 - all=20 underscores.
>
> If underscores are a big issue with = headers=20 then we should consider 1
> - all dashes. The problem with all = dashes=20 is that it is counterintuitive for
> people that know OAuth=20 1.
>
> Marius
>
>
>
> On Thu, = Jul 1,=20 2010 at 11:01 AM, Eran Hammer-Lahav
> <eran@hueniverse.com> = wrote:
>=20 >
> >
> >> -----Original = Message-----
>=20 >> From: Luke Shepard [mailto:lshepard@facebook.com]
> = >> Sent: Thursday, July 01, 2010 10:58 AM
> >> To: = Eran=20 Hammer-Lahav
> >> Cc: Justin Hart; Pelle Braendgaard; = OAuth WG=20 (oauth@ietf.org)
> = >>=20 Subject: Re: [OAUTH-WG] Underscore, dash, green, blue
>=20 >>
> >> Don't really care, but to pick one - = underscores=20 throughout.
> >>
> >> Why not = headers?
>=20 >
> > Historically, HTTP headers use dashes and not = underscores,=20 but there is
> nothing to prevent us from using underscores=20 throughout.
> >
> > EHL
> >
> = >> On=20 Jul 1, 2010, at 9:23 AM, Eran Hammer-Lahav wrote:
> = >>
>=20 >> > That's wasn't an option for a reason. Beside offending = my=20 esthetic
> >> sensibility :-) having the same parameter = use a=20 different name
> >> between the header and endpoint = makes=20 registration of extension
> >> parameters much harder. = For=20 example, if we used this scheme, the
> >> 'error-uri' = parameter=20 would require two registration requests, one
> >> for=20 'error-uri' and another for 'error_uri'.
> >> = >
>=20 >> > EHL
> >> >
> >> >>=20 -----Original Message-----
> >> >> From: oauth-bounces@ietf.org = [mailto:oauth-bounces@ietf.org] = On
>=20 >> >> Behalf Of Justin Hart
> >> >> = Sent:=20 Thursday, July 01, 2010 7:10 AM
> >> >> To: Pelle=20 Braendgaard
> >> >> Cc: OAuth WG (oauth@ietf.org)
> >> = >>=20 Subject: Re: [OAUTH-WG] Underscore, dash, green, blue
> = >>=20 >>
> >> >> +1 for underscores except header=20 keys.
> >> >> ----
> >> >> -- = Justin=20 Hart
> >> >> -- jhart@photobucket.com
>=20 >> >>
> >> >>
> >>=20 >>
> >> >>
> >> >>
> = >> >>
> >> >> On Jul 1, 2010, at 7:39 = AM,=20 Pelle Braendgaard wrote:
> >> >>
> >>=20 >>> I already implemented 09 but it was a (very tiny) bit = of a=20 hassle
> >> >>> to have to convert = underscores.
>=20 >> >>>
> >> >>> So I also agree = with 3=20 except headers
> >> >>>
> >> = >>>=20 On Thu, Jul 1, 2010 at 2:41 AM, Lukas Rosenstock
> >>=20 >>> <lr@lukasrosenstock.net>
= >=20 >> >> wrote:
> >> >>>> 3 except=20 headers.
> >> >>>>
> >> = >>>>=20 2010/7/1 Eran Hammer-Lahav <eran@hueniverse.com>:
> = >> >>>>> First, sorry about this. J
> = >>=20 >>>>>
> >> >>>>>
> = >>=20 >>>>>
> >> >>>>> I do my = best not=20 to ask the group this kind of questions and
> >>=20 >>>>> just pick something on my own, but I can't = decide so=20 I'll run a
> >> >>>>> quick vote (yes, a = VOTE - I=20 can't imagine seeking a consensus call on
> this).
> = >>=20 >>>>>
> >> >>>>>
> = >>=20 >>>>>
> >> >>>>> -09 uses=20 underscores for parameter names (except for in the
> >>=20 >>>>> headers) and dashes for parameter values. This = seems=20 like an
> >> >>>>> odd
> >>=20 selection.
> >> >>>>> Before, it used = dashes for=20 header parameter names, and
> >> >>>>> = underscore=20 everywhere else. Not great either.
> >>=20 >>>>>
> >> >>>>>
> = >>=20 >>>>>
> >> >>>>> = So...
>=20 >> >>>>>
> >> = >>>>>
>=20 >> >>>>>
> >> >>>>> = The=20 changes my OCD can live with:
> >> = >>>>>
>=20 >> >>>>>
> >> = >>>>>
>=20 >> >>>>> 1. Use dashes throughout
> = >>=20 >>>>>
> >> >>>>> 2. Use=20 underscores for all parameter names (headers included),
> = >>=20 >>>>> dashes for all values
> >>=20 >>>>>
> >> >>>>> 3. Use=20 underscores throughout
> >> >>>>>
> = >> >>>>>
> >> = >>>>>
>=20 >> >>>>> I want to get this done with in a day = because=20 people are
> >> >>>>> writing code = for
>=20 >> >>>>> -09 and I'd like to stop making = changes beyond=20 editorial.  I
> >> >>>>> just think = that=20 having different styles between the endpoint
> >>=20 >>>>> parameters and header parameters is = broken.
>=20 >> >>>>>
> >> = >>>>>
>=20 >> >>>>>
> >> >>>>>=20 EHL
> >> >>>>>
> >>=20 >>>>> = _______________________________________________
>=20 >> >>>>> OAuth mailing list
> >>=20 >>>>> OAuth@ietf.org
> >>=20 >>>>> https://www.ietf.org/mailman/listinfo/oauth
>=20 >> >>>>>
> >> = >>>>>
>=20 >> >>>>
> >> >>>>
> = >>=20 >>>>
> >> >>>> --
> = >>=20 >>>> http://lukasrosenstock.net/
> >>=20 >>>> = _______________________________________________
>=20 >> >>>> OAuth mailing list
> >>=20 >>>> OAuth@ietf.org
>=20 >> >>>> https://www.ietf.org/mailman/listinfo/oauth
>=20 >> >>>>
> >> >>>
> = >>=20 >>>
> >> >>>
> >> = >>>=20 --
> >> >>> http://agree2.com - Reach Agreement!
> = >>=20 >>> http://stakeventures.com - My blog about = startups and=20 agile
> >> >>> banking
>=20 _______________________________________________
> >>=20 >>> OAuth mailing list
> >> >>> OAuth@ietf.org
> >>=20 >>> https://www.ietf.org/mailman/listinfo/oauth
>=20 >> >>
> >> >>=20 _______________________________________________
> >> = >>=20 OAuth mailing list
> >> >> OAuth@ietf.org
> >> = >> https://www.ietf.org/mailman/listinfo/oauth
>=20 >> > = _______________________________________________
>=20 >> > OAuth mailing list
> >> > OAuth@ietf.org
> >> = > https://www.ietf.org/mailman/listinfo/oauth
>=20 >
> > = _______________________________________________
>=20 > OAuth mailing list
> > OAuth@ietf.org
> > https://www.ietf.org/mailman/listinfo/oauth
>=20 >
_______________________________________________
OAuth = mailing=20 list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
=

------_=_NextPart_001_01CB1A49.36F11C36--