<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>In which case, back to your original question:</div><div><br></div><div><blockquote type="cite"><blockquote type="cite">Are there poeple who are interested in discussing OpenID Mobile profile sort of thing? <br></blockquote></blockquote></div><div><br></div><div>My answer would be "Yes".</div><div><br></div><div><br></div><br><div><div>On Jan 29, 2009, at 22:14, Nat Sakimura wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">There are two issues involved. <br><br>1) URL length etc. limitations<br>2) User interface<br><br>1) has impact on 2). <br><br>For instance, we want to avoid the users pressing buttons when redirecting. <br>And, in many cases, we do not have javascript. <br> This means we are left with GET and this URL length limitation becomes an issue. <br><br>2) cannot be solved globally because it could very well be somewhat dependent on <br>the carrier implementation and handset capability. <br> For most of the phones in Japan, we can get unique <br>id for each handset at http level fairly securely so we can depend on it to <br>avoid any typing (not even username etc.). This was one of the factor why <br>m-commerce got so popular in Japan. <br> <br>In many other markets, e.g., the U.S., this is not granted. Thus, some other means <br>are required. I know, WIl Tan of Maleysia is working something on iPhone in this regard. <br>Essentially, it needs to be solved per carrier or per handset class <br> (e.g., mid-p enabled phones, etc.), I think. <br><br>=nat<br><br><div class="gmail_quote">On Fri, Jan 30, 2009 at 2:56 PM, Johannes Ernst <span dir="ltr"><jernst+<a href="http://openid.net">openid.net</a>@<a href="http://netmesh.us">netmesh.us</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style="">Are you talking about URL length limitations for the identifiers that users need to enter, or for URLs that are being sent around as part of the protocol?<div> <br></div><div>IMHO the most important question to ask for mobile devices is: can we do without "typing" anything?</div><div><br></div><div><div><div><div></div><div class="Wj3C7c"><div>On Jan 29, 2009, at 16:56, Nat Sakimura wrote:</div> <br></div></div><blockquote type="cite"><div><div></div><div class="Wj3C7c">Hi. <br><br>Are there poeple who are interested in discussing OpenID Mobile profile sort of thing? <br>Mobile phones has unique challenges of being restricted in URL length etc. <br> OpenID as it stands now has very lengthy URLs in both requests and responses and it sometimes does not fit into the restrictions. <br> SAML world has defined artifact binding to cope with it. IMHO, OpenID should define something like that also. <br> <br>In Japan, there are bunch of people (including mobile carriers) who wants to do it. <br><br>Are there interest here as well? <br clear="all"> <br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br> </div></div><div class="Ih2E3d"> _______________________________________________<br>specs mailing list<br><a href="mailto:specs@openid.net" target="_blank">specs@openid.net</a><br><a href="http://openid.net/mailman/listinfo/specs" target="_blank">http://openid.net/mailman/listinfo/specs</a><br> </div></blockquote></div><br></div></div></blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br></blockquote></div><br></body></html>