From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf
Of Dick Hardt
Sent: Sunday, April 18, 2010 9:33 PM
To: OAuth WG
Subject: [OAUTH-WG] Clarification: Authorization scheme :: Token vs
OAuth
I recall some earlier discussion on calling the scheme Token
-
From: Marius Scurtescu [mailto:mscurte...@google.com]
Sent: Monday, April 19, 2010 10:06 AM
To: Eran Hammer-Lahav
Cc: Dick Hardt; OAuth WG
Subject: Re: [OAUTH-WG] Clarification: Authorization scheme :: Token vs
OAuth
Isn't Token as a scheme to generic/ambiguous?
If a protected
-Original Message-
From: Marius Scurtescu [mailto:mscurte...@google.com]
Sent: Monday, April 19, 2010 2:07 PM
To: Eran Hammer-Lahav
Cc: OAuth WG
Subject: Re: [OAUTH-WG] Clarification: Authorization scheme :: Token vs
OAuth
On Mon, Apr 19, 2010 at 11:06 AM, Eran Hammer-Lahav
e
I recall some earlier discussion on calling the scheme Token vs OAuth and see
that it is now Token per the example:
Authorization: Token token=vF9dft4qmT
Would explain or point out the logic of using Token rather than OAuth?
A related question: is the scheme case
