<div dir="ltr"><div class="gmail_default" style="font-size:small">First of all, excellent start! Thnks to Torsten and his DG colleagues.</div><div class="gmail_default" style="font-size:small">==========================</div>
<div class="gmail_default" style="font-size:small">Section 3.2: “The RP shall register to a certain MNO or another entity MNOs delegated this task to once and obtain the right to access the desired MNOs’ ID services. To enable this autonomy of relying parties and OpenID Providers (the MNO‘s) dynamic client registration must be possible.”</div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Why? I’m in favor of dynamic registration, but in the typical use case, suppose I’m an RP, I want to register an app with TMO and have it work on Orange, why is a traditional RP registration process with TMO not possible?</div>
<div class="gmail_default" style="font-size:small">==========================</div><div class="gmail_default" style="font-size:small">A little worried about the software statement in a public client, where it can be easily stolen; not sure I understand what it accomplishes.</div>
<div class="gmail_default" style="font-size:small">==========================</div><div class="gmail_default" style="font-size:small">It would be more readable if the references were by title not by name, e.g. “OIDC Discovery” rather than ”[3]”</div>
<div class="gmail_default" style="font-size:small">==========================</div><div class="gmail_default" style="font-size:small">Section 4: This is all about web apps, and I see that there’s value-add in defining an advanced discovery process that can return an OP to support a standard OIDC flow, where the OP is doesn’t depend on which telco the RP registered with… Do we have any ambition to support the native-app case? That’s where the real developer pain is. </div>
<div class="gmail_default" style="font-size:small">===========================</div><div class="gmail_default" style="font-size:small">Section 4. “In this example, the RP is a web application, which asked the user to enter his msisdn”. Ideally, it should be possible for the software to get the identifier from the phone hardware?</div>
<div class="gmail_default" style="font-size:small">===========================</div><div class="gmail_default" style="font-size:small">Generally, I was hoping there to be some back-channel magic that would be enabled by involvement of GSMA members. The SIM or equivalent already constitutes some sort of an identity assertion so I’d hope that could be used, for example simplify discovery. Any chances?</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jul 27, 2014 at 12:33 PM, Torsten Lodderstedt <span dir="ltr"><<a href="mailto:torsten@lodderstedt.net" target="_blank">torsten@lodderstedt.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Hi Tim,</div><div><br></div><div>why don't you just post your comments here?</div><div><br></div>
<div>regards,</div><div>Torsten.</div><div><br>Am 27.07.2014 um 21:08 schrieb Tim Bray <<a href="mailto:tbray@textuality.com" target="_blank">tbray@textuality.com</a>>:<br><br></div><div><div class="h5"><blockquote type="cite">
<div><div dir="ltr"><div class="gmail_default" style="font-size:small">Thanks! I started reading this and immediately had a couple of comments I wanted to make. Perhaps this could migrate into a comment-friendly form like a wiki or Google doc or something soon?</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jul 27, 2014 at 11:14 AM, Torsten Lodderstedt <span dir="ltr"><<a href="mailto:torsten@lodderstedt.net" target="_blank">torsten@lodderstedt.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Deutsche Telekom has prepared an initial proposal for this working group. Please find the document here: <a href="http://openid.bitbucket.org/Mobile_Profile_initial_draft_016.pdf" target="_blank">http://openid.bitbucket.org/<u></u>Mobile_Profile_initial_draft_<u></u>016.pdf</a><br>
<br>
The main purpose of this document is to facilitate the discusion within the group about the challenges with have to cope with and the assumptions we base our work upon. It also sketches a potential solution (which is certainly open for discussions).<br>
<br>
"See" you on Tuesday.<br>
<br>
best regards,<br>
Torsten.<br>
______________________________<u></u>_________________<br>
Openid-specs-mobile-profile mailing list<br>
<a href="mailto:Openid-specs-mobile-profile@lists.openid.net" target="_blank">Openid-specs-mobile-profile@<u></u>lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile" target="_blank">http://lists.openid.net/<u></u>mailman/listinfo/openid-specs-<u></u>mobile-profile</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>- Tim Bray (If you’d like to send me a private message, see <a href="https://keybase.io/timbray" target="_blank">https://keybase.io/timbray</a>)</div>
</div>
</div>
</div></blockquote></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>- Tim Bray (If you’d like to send me a private message, see <a href="https://keybase.io/timbray" target="_blank">https://keybase.io/timbray</a>)</div>
</div>
</div>