<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.bradley-oauth-pop-key-distribution" target="https://datatracker.ietf.org/doc/html/draft-bradley-oauth-pop-key-distribution-01">
   <front>
      <title>OAuth 2.0 Proof-of-Possession: Authorization Server to Client Key Distribution</title>
      <author initials="J." surname="Bradley" fullname="John Bradley">
         <organization>Ping Identity</organization>
      </author>
      <author initials="P." surname="Hunt" fullname="Phil Hunt">
         <organization>Oracle Corporation</organization>
      </author>
      <author initials="M. B." surname="Jones" fullname="Michael B. Jones">
         <organization>Microsoft</organization>
      </author>
      <author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
         <organization>ARM Limited</organization>
      </author>
      <date month="June" day="26" year="2014" />
      <abstract>
	 <t>   RFC 6750 specified the bearer token concept for securing access to
   protected resources.  Bearer tokens need to be protected in transit
   as well as at rest.  When a client requests access to a protected
   resource it hands-over the bearer token to the resource server.

   The OAuth 2.0 Proof-of-Possession security concept extends bearer
   token security and requires the client to demonstrate possession of a
   key when accessing a protected resource.

   This document describes how the client obtains this keying material
   from the authorization server.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-bradley-oauth-pop-key-distribution-01" />
   
</reference>
