The query parameter method was not moved to an appendix, for the reasons that
Dick and you stated. The reality is, that it's the most used method, and it
would be a disservice to developers not to describe it in the body of the spec
(with appropriate caveats, of course).
Best wishes,
-- Mike
From: David Recordon [mailto:record...@gmail.com]
Sent: Wednesday, May 23, 2012 11:47 PM
To: Mike Jones; Julian Reschke
Cc: Mark Nottingham; oauth@ietf.org
Subject: Re: [OAUTH-WG] FYI - Text resolving DISCUSS issue about Bearer URI
Query Parameter method
I'm confused by this change given the access_token (or oauth_token) parameter
being the most widely deployed usage of the protocol over the past eighteen
months:
* https://developers.facebook.com/docs/reference/api/
* https://developers.google.com/accounts/docs/OAuth2WebServer#callinganapi
* http://msdn.microsoft.com/en-us/library/live/hh243647#response
* http://develop.github.com/p/oauth.html
--David
On Wed, May 23, 2012 at 11:35 PM, Julian Reschke
<julian.resc...@gmx.de<mailto:julian.resc...@gmx.de>> wrote:
On 2012-05-18 09:15, Julian Reschke wrote:
...
Did you consider to *also* move the whole section into an appendix, so
that it's status is also reflected by the document structure?
Best regards, Julian
Hi, it would be awesome to see feedback on this (it has been mentioned during
IETF LC multiple times).
Best regards, Julian
_______________________________________________
OAuth mailing list
OAuth@ietf.org<mailto:OAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
