<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-oauth-device-flow" target="https://datatracker.ietf.org/doc/html/draft-ietf-oauth-device-flow-12">
   <front>
      <title>OAuth 2.0 Device Flow for Browserless and Input Constrained Devices</title>
      <author initials="W." surname="Denniss" fullname="William Denniss">
         <organization>Google</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="August" day="1" year="2018" />
      <abstract>
	 <t>   This OAuth 2.0 authorization flow for browserless and input-
   constrained devices, often referred to as the device flow, enables
   OAuth clients to request user authorization from devices that have an
   Internet connection, but don&#x27;t have an easy input method (such as a
   smart TV, media console, picture frame, or printer), or lack a
   suitable browser for a more traditional OAuth flow.  This
   authorization flow instructs the user to perform the authorization
   request on a secondary device, such as a smartphone.  There is no
   requirement for communication between the constrained device and the
   user&#x27;s secondary device.

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