> -----Original Message----- > From: Marius Scurtescu [mailto:[email protected]] > Sent: Sunday, April 18, 2010 1:38 PM
> Also, when implementing OAuth 2.0 people will take into account existing > parameters and will avoid them, they will chose other parameter names (if > possible). If the next version of OAuth, let's call it 2.1, adds a few new > parameters, how can we chose them so they don't collide with extra > parameters used by 2.0 implementations? By defining an extension policy. Anything that is not in the core spec is an extension. How about we first figure this out? If we can agree on an extension policy, we can see if it mitigates your concerns. EHL _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
