How about turn the MUST to a SHOULD for using the x_ prefix?

EHL

> -----Original Message-----
> From: Marius Scurtescu [mailto:mscurte...@google.com]
> Sent: Wednesday, January 26, 2011 1:32 PM
> To: Eran Hammer-Lahav
> Cc: oauth@ietf.org
> Subject: Re: [OAUTH-WG] I-D Action:draft-ietf-oauth-v2-12.txt
> 
> On Wed, Jan 26, 2011 at 9:48 AM, Eran Hammer-Lahav
> <e...@hueniverse.com> wrote:
> > This is not aimed at anyone in particular.
> >
> > Replying +1 is not justification for a major breaking change. This was 
> > raised
> in the past and consensus was that this is not a major concern. Over the past
> 10 months not a single actual issue was raised about conflicts in legacy
> platforms. If you have an *actual* issue with a platform, please provide the
> full details, including why known mechanisms such as Apache rewrite rules
> can't solve the it.
> 
> I just raised an actual issue.
> 
> Because OAuth 2 parameters are not prefixed, starting with v11 the spec
> requires all other parameters to use the "x_" prefix. Google cannot comply
> with that.
> 
> Dropping the x_ requirement is good enough IMO. If you are worried about
> that, then you are probably afraid of an actual issue as well.
> 
> 
> Marius
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Reply via email to