<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Seems these might be device specific and best left to profiles to define<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> openid-specs-ab-bounces@lists.openid.net [mailto:openid-specs-ab-bounces@lists.openid.net]
<b>On Behalf Of </b>George Fletcher<br>
<b>Sent:</b> Wednesday, October 19, 2011 12:01 PM<br>
<b>To:</b> openid-specs-ab@lists.openid.net<br>
<b>Subject:</b> [Openid-specs-ab] Messages - 3.1.2 additional display parameter options<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Helvetica","sans-serif"">Per my action item Monday from ... here is a possible write up for additional options for the display parameter. Currently OpenID Connect defines one value
'none' which means that the request MUST be handled without showing any UI to the user. Facebook defines (page, iframe, popup, touch, wap) some of which are also in the OpenID UI Extension. I'm not sure we want to support iframe so I didn't include it in
the list below. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif"">page</span><br>
<span style="font-family:"Helvetica","sans-serif""> The Authorization Server SHOULD display authentication and consent UI consistent with a full browser page view. If the display parameter is not specified this is the default display mode.</span><br>
<br>
<span style="font-family:"Helvetica","sans-serif"">popup</span><br>
<span style="font-family:"Helvetica","sans-serif""> The Authorization Server SHOULD display authentication and consent UI consistent with a popup browser window. The popup browser window SHOULD conform to N x N pixels.</span><br>
<br>
<span style="font-family:"Helvetica","sans-serif"">touch</span><br>
<span style="font-family:"Helvetica","sans-serif""> The Authorization Server SHOULD display authentication and consent UI consistent with a device that leverages a touch interface. The Authorization Server MAY attempt to detect the device touch and further
customize the interface.</span><br>
<br>
<span style="font-family:"Helvetica","sans-serif"">wap</span><br>
<span style="font-family:"Helvetica","sans-serif""> The Authorization Server SHOULD display authentication and consent UI consistent with a "feature phone" type display.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Helvetica","sans-serif""><br>
Note that the semantics are slightly different as these values are more hints from the client where as 'none' is a "command". Would it make sense to move the 'none' feature of display to the 'prompt' parameter? It seems to me that the semantics fit better.
The main point of 'none' is that we don't want to ask the user any questions. The fact that no UI is displayed is a side effect of not asking the user for any input.<br>
<br>
Thanks,<br>
George</span><o:p></o:p></p>
</div>
</body>
</html>