%% You should probably cite draft-tschofenig-oauth-hotk-03 instead of this revision. @techreport{tschofenig-oauth-hotk-00, number = {draft-tschofenig-oauth-hotk-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-tschofenig-oauth-hotk/00/}, author = {Hannes Tschofenig}, title = {{The OAuth 2.0 Authorization Framework: Holder-of-the-Key Token Usage}}, pagetotal = 15, year = 2012, month = jul, day = 9, abstract = {OAuth 2.0 deployments currently rely on bearer tokens for securing access to protected resources. Bearer tokens require Transport Layer Security to be used between an OAuth client and the resource server when presenting the access token in order to get access. The security model is based on proof-of-possession of the access token: access token storage and transfer has to be done with care to prevent leakage. There are, however, use cases that require a more active involvement of the OAuth client to offer increased security, particularly against token leakage. This document specifies an OAuth security framework using ephemeral asymmetric credentials that are bound to the access token. A client can create these key pairs dynamically and use them, after they are bound to an access token by the authorization server, in communication interactions with resource servers. This document is discussed at https://www.ietf.org/mailman/listinfo/oauth. This initial version of the specification shall serve as a discussion starter.}, }