<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Helvetica, Arial, sans-serif">So I think we have to
      different use cases here...<br>
      <br>
      1. The capabilities of the device/how the UI is being displayed. I
      agree with Marius that 'embedded' is another designation that is
      useful. I'm fine with additional values being defined in profiles,
      but we have some that we know are in use today and I think we
      should just go ahead and include them. I suppose it is possible
      that a device could have no UI capability and hence would need an
      option of 'none'. However, I think that is a different flow from
      what is currently described (at least the way I read it).<br>
      <br>
      2. The OpenID checkid_immediate flow. I think we should support
      this case as well. This is where the RP doesn't want any user
      interaction. For this semantic I think it makes more sense to
      designate this as a value for the 'prompt' parameter. We can use
      'none' here, but it would probably be best to have different
      values.<br>
      <br>
      Marius, did you mean 'embedded' to imply that the device has no
      UI? or a limited kind of UI capability,<br>
      <br>
      Thanks,<br>
      George<br>
    </font><br>
    On 10/19/11 3:40 PM, Anthony Nadalin wrote:
    <blockquote
cite="mid:B26C1EF377CB694EAB6BDDC8E624B6E72D8310FB@SN2PRD0302MB137.namprd03.prod.outlook.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <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]-->
      <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">
                <a class="moz-txt-link-abbreviated" href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a>
                [<a class="moz-txt-link-freetext" href="mailto:openid-specs-ab-bounces@lists.openid.net">mailto:openid-specs-ab-bounces@lists.openid.net</a>]
                <b>On Behalf Of </b>George Fletcher<br>
                <b>Sent:</b> Wednesday, October 19, 2011 12:01 PM<br>
                <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><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>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Chief Architect                   AIM:  gffletch
Identity Services Engineering     Work: <a class="moz-txt-link-abbreviated" href="mailto:george.fletcher@teamaol.com">george.fletcher@teamaol.com</a>
AOL Inc.                          Home: <a class="moz-txt-link-abbreviated" href="mailto:gffletch@aol.com">gffletch@aol.com</a>
Mobile: +1-703-462-3494           Blog: <a class="moz-txt-link-freetext" href="http://practicalid.blogspot.com">http://practicalid.blogspot.com</a>
Office: +1-703-265-2544           Twitter: <a class="moz-txt-link-freetext" href="http://twitter.com/gffletch">http://twitter.com/gffletch</a>
</pre>
  </body>
</html>