<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.denniss-oauth-device-flow" target="https://datatracker.ietf.org/doc/html/draft-denniss-oauth-device-flow-00">
   <front>
      <title>OAuth 2.0 Device Flow</title>
      <author initials="W." surname="Denniss" fullname="William Denniss">
         <organization>Google</organization>
      </author>
      <author initials="S." surname="Myrseth" fullname="Stein Myrseth">
         <organization>Forgerock</organization>
      </author>
      <author initials="J." surname="Bradley" fullname="John Bradley">
         <organization>Ping Identity</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="November" day="4" year="2015" />
      <abstract>
	 <t>   The device flow is suitable for OAuth 2.0 clients executing on
   devices which do not have an easy data-entry method (e.g., game
   consoles, TVs, picture frames, and media hubs), but where the end-
   user has separate access to a user-agent on another computer or
   device (e.g., desktop computer, a laptop, a smart phone, or a
   tablet).

   Note: This version of the document is a continuation of an earlier,
   long expired draft.  The content of the expired draft has been copied
   almost unmodified.  The goal of the work on this document is to
   capture deployment experience.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-denniss-oauth-device-flow-00" />
   
</reference>
