<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Feb 26, 2018 at 10:35 AM, Phil Hunt via Openid-specs-risc <span dir="ltr"><<a href="mailto:openid-specs-risc@lists.openid.net" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">openid-specs-risc@lists.openid.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word">Hi,<div><br></div><div>Unfortunately I have a conflict I cannot quite get out of this afternoon. My apologies for not being able to make it.</div><div><br></div><div>I have posted a number of issues for discussion. Note: these issues are more foundational principles that we should have consensus on before proceeding.</div><div>Issue Tracker: <a href="https://bitbucket.org/openid/risc/issues?status=new&status=open" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">https://bitbucket.org/openid/<wbr>risc/issues?status=new&status=<wbr>open</a></div><div><br></div><div>My feeling is that any RISC Profile should only deal in issues or opportunities unique to RISC. It has not been clear what those RISC specific scoping issue are. Hence, I do not see the purpose for the current RISC Profile draft. For my part, I was expecting a draft that actually defined RISC Events.</div></div></blockquote><div><br></div><div>A reminder that the draft that defines RISC events is in the same bitbucket repo, it is called risc-event-types.xml:<br></div><div><a href="https://bitbucket.org/openid/risc/src">https://bitbucket.org/openid/risc/src</a><br></div><div><br></div><div>See the original thread for PDF and ePub:</div><div><a href="http://lists.openid.net/pipermail/openid-specs-risc/Week-of-Mon-20180129/000436.html">http://lists.openid.net/pipermail/openid-specs-risc/Week-of-Mon-20180129/000436.html</a><br></div><div><br></div><div>The event definitions were split out to allow the profiling of secevent specs to take longer and to be able to stabilize the event types independently. Without splitting, if the profile spec is being updated (date and number incremented) and the event types are not affected then the definition of what events are implemented by a given transmitter or receiver becomes ambiguous.</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>Dick commented on Feb 5 that:</div><div><a href="http://lists.openid.net/pipermail/openid-specs-risc/Week-of-Mon-20180205/000439.html" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">http://lists.openid.net/<wbr>pipermail/openid-specs-risc/<wbr>Week-of-Mon-20180205/000439.<wbr>html</a></div><div><blockquote type="cite"><pre style="white-space:pre-wrap;background-color:rgb(255,255,255)">I think “need” is too strong. A single management API is desired.
Another aspect is that the management requirements of RISC, SCIM, OIDC etc. so far look quite different.
RISC has specific needs, and with a concrete API, there can more easily be a discussion on commonalities, or lack thereof with other SecEvent profiles.</pre></blockquote><div>These statements don’t really play out. The RISC group has not really identified why RISC is unique. </div><div><br></div><div>I notice some are assuming OIDC which makes it unique.</div></div></div></blockquote><div><br></div><div>The current base assumption is OAuth 2. One of the subject types makes reference to OIDC.</div><div><br></div><div>Also, keep in mind that the base use cases are based on OAuth 2:</div><div><a href="https://tools.ietf.org/html/draft-scurtescu-secevent-risc-use-cases">https://tools.ietf.org/html/draft-scurtescu-secevent-risc-use-cases</a><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><div> Yet, RISC was chartered as multi-protocol (including SAML and implicit federation). In my view, RISC has a similar diversity as SECEVENTs itself given the requirements to support implicit federation and multiple profiles.</div></div><div><br></div><div>Is it the intent to specifically narrow the scope in the RISC charter?</div><div><br></div><div>Best Regards,</div><div><br></div><div><div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div><span class="gmail-m_-1395786879412208988Apple-style-span" style="border-collapse:separate;line-height:normal"><div style="word-wrap:break-word"><div><div><div>Phil</div><div><br></div><div>Oracle Corporation, Identity Cloud Services Architect</div><div>@independentid</div><div><a href="http://www.independentid.com" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">www.independentid.com</a></div></div></div></div></span><a href="mailto:phil.hunt@oracle.com" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">phil.hunt@oracle.com</a></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div>
<div><br><blockquote type="cite"><div><div class="gmail-h5"><div>On Feb 21, 2018, at 2:29 PM, Luke Camery via Openid-specs-risc <<a href="mailto:openid-specs-risc@lists.openid.net" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">openid-specs-risc@lists.<wbr>openid.net</a>> wrote:</div><br class="gmail-m_-1395786879412208988Apple-interchange-newline"></div></div><div><div><div class="gmail-h5"><div dir="ltr">Hey All,<div><br></div><div>We are cancelling the meeting today due to our difficulty in getting the issue tracker setup. The issue tracker is <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__bitbucket.org_openid_risc_issues-3Fstatus-3Dnew-26status-3Dopen&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=xlzDRBpfeMNMAeHgEZOVY7x9Q_UQSBC9LFpdcjQ1a_0&s=9RkYS_6vwFlnAK4ufG419GfShyfHdpqZWgRvvE-42qc&e=" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">now live</a> on the <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__bitbucket.org_openid_risc_issues-3Fstatus-3Dnew-26status-3Dopen&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=xlzDRBpfeMNMAeHgEZOVY7x9Q_UQSBC9LFpdcjQ1a_0&s=9RkYS_6vwFlnAK4ufG419GfShyfHdpqZWgRvvE-42qc&e=" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">RISC WG repo</a>. Please post any issues that you would like to discuss on Monday at 15:00 PST. </div><div><br></div><div>The agenda for Monday will be to discuss issues posted to the tracker so please provide everyone with ample time to review your issue by posting as early as possible.</div><div><br></div><div>Thanks,</div><div>Luke<br><br><br><div class="gmail_quote"><div dir="ltr">On Thu, Feb 15, 2018 at 8:59 AM Luke Camery <<a href="mailto:lcamery@google.com" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">lcamery@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1mM7IuVlAJS6bTnqgDMSD7ESpnsNRMME6I79-5FmE4K5Ns_edit-3Fusp-3Dsharing&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=xlzDRBpfeMNMAeHgEZOVY7x9Q_UQSBC9LFpdcjQ1a_0&s=bTfeAlMUxp3o1kDhi84wQWP6YKo-aitQag0k4fOn7uo&e=" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">Here</a> are the notes from yesterday's weekly meeting. The working group moved to postpone this next meeting to next Wednesday due to the American holiday on Monday. The proposed time is 16:30 PST. Please respond if that time poses a conflict for you and we can reschedule.</div><div><br></div><div>Thanks,</div><div>Luke<br clear="all"><div><br></div>-- <br><div class="gmail-m_-1395786879412208988m_-1777015492063307164gmail_signature"><div dir="ltr"><table cellspacing="0" cellpadding="0" dir="ltr" border="1" style="color:rgb(136,136,136);font-size:13px;line-height:normal;margin:0px;padding:0px;border:1px solid rgb(204,204,204);border-collapse:collapse;table-layout:fixed;font-family:arial,sans,sans-serif"><tbody style="margin:0px;padding:0px;border:0px"><tr style="margin:0px;padding:0px;border:0px;height:48px"><td style="padding:2px 3px;border:1px solid rgb(255,255,255);vertical-align:middle;text-align:center"><img src="http://i.imgur.com/Ya4Rhss.gif" width="96" height="42"></td><td style="padding:2px 3px;border-width:1px 1px 1px 0px;border-top-style:solid;border-right-style:solid;border-bottom-style:solid;border-top-color:rgb(255,255,255);border-right-color:rgb(255,255,255);border-bottom-color:rgb(255,255,255);vertical-align:middle;text-align:center"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"></blockquote></td><td style="padding:2px 3px;border-width:1px 1px 1px 0px;border-top-style:solid;border-right-style:solid;border-bottom-style:solid;border-top-color:rgb(255,255,255);border-right-color:rgb(255,255,255);border-bottom-color:rgb(255,255,255);vertical-align:bottom"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><b style="font-size:small;color:rgb(61,133,198);font-family:arial"> • </b><b style="font-size:small;font-family:arial"><font color="#666666">Luke Camery</font></b><font face="arial" color="#3d85c6" style="margin:0px;padding:0px;border:0px"><b><br></b></font><b style="font-size:small;color:rgb(255,0,0);font-family:arial"> • </b><font color="#666666" style="margin:0px;padding:0px;border:0px">Associate Product Manager</font><font color="#ff0000" face="arial" style="margin:0px;padding:0px;border:0px"><b><br></b></font><b style="color:rgb(255,204,51);font-size:12.8px"> • </b><font color="#666666" style="margin:0px;padding:0px;border:0px">Federated Identity</font></blockquote></td></tr></tbody></table></div></div>
</div></div></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_-1395786879412208988gmail_signature"><div dir="ltr"><table cellspacing="0" cellpadding="0" dir="ltr" border="1" style="color:rgb(136,136,136);font-size:13px;line-height:normal;margin:0px;padding:0px;border:1px solid rgb(204,204,204);border-collapse:collapse;table-layout:fixed;font-family:arial,sans,sans-serif"><tbody style="margin:0px;padding:0px;border:0px"><tr style="margin:0px;padding:0px;border:0px;height:48px"><td style="padding:2px 3px;border:1px solid rgb(255,255,255);vertical-align:middle;text-align:center"><img src="http://i.imgur.com/Ya4Rhss.gif" width="96" height="42"></td><td style="padding:2px 3px;border-width:1px 1px 1px 0px;border-top-style:solid;border-right-style:solid;border-bottom-style:solid;border-top-color:rgb(255,255,255);border-right-color:rgb(255,255,255);border-bottom-color:rgb(255,255,255);vertical-align:middle;text-align:center"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"></blockquote></td><td style="padding:2px 3px;border-width:1px 1px 1px 0px;border-top-style:solid;border-right-style:solid;border-bottom-style:solid;border-top-color:rgb(255,255,255);border-right-color:rgb(255,255,255);border-bottom-color:rgb(255,255,255);vertical-align:bottom"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><b style="font-size:small;color:rgb(61,133,198);font-family:arial"> • </b><b style="font-size:small;font-family:arial"><font color="#666666">Luke Camery</font></b><font face="arial" color="#3d85c6" style="margin:0px;padding:0px;border:0px"><b><br></b></font><b style="font-size:small;color:rgb(255,0,0);font-family:arial"> • </b><font color="#666666" style="margin:0px;padding:0px;border:0px">Associate Product Manager</font><font color="#ff0000" face="arial" style="margin:0px;padding:0px;border:0px"><b><br></b></font><b style="color:rgb(255,204,51);font-size:12.8px"> • </b><font color="#666666" style="margin:0px;padding:0px;border:0px">Federated Identity</font></blockquote></td></tr></tbody></table></div></div></div></div></div></div>
______________________________<wbr>_________________<br>Openid-specs-risc mailing list<br><a href="mailto:Openid-specs-risc@lists.openid.net" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">Openid-specs-risc@lists.<wbr>openid.net</a><br><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openid.net_mailman_listinfo_openid-2Dspecs-2Drisc&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=xlzDRBpfeMNMAeHgEZOVY7x9Q_UQSBC9LFpdcjQ1a_0&s=qFLhSS8O5usMmqzbAk9MP05srYN4sCDktAMIJHUlmcs&e=" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">https://urldefense.proofpoint.<wbr>com/v2/url?u=http-3A__lists.<wbr>openid.net_mailman_listinfo_<wbr>openid-2Dspecs-2Drisc&d=<wbr>DwICAg&c=<wbr>RoP1YumCXCgaWHvlZYR8PZh8Bv7qIr<wbr>MUB65eapI_JnE&r=<wbr>na5FVzBTWmanqWNy4DpctyXPpuYqPk<wbr>AI1aLcLN4KZNA&m=<wbr>xlzDRBpfeMNMAeHgEZOVY7x9Q_<wbr>UQSBC9LFpdcjQ1a_0&s=<wbr>qFLhSS8O5usMmqzbAk9MP05srYN4sC<wbr>DktAMIJHUlmcs&e=</a><br></div></blockquote></div><br></div></div><br>______________________________<wbr>_________________<br>
Openid-specs-risc mailing list<br>
<a href="mailto:Openid-specs-risc@lists.openid.net" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">Openid-specs-risc@lists.<wbr>openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-risc" rel="noreferrer" target="_blank" class="gmail-cremed gmail-cremed gmail-cremed gmail-cremed cremed">http://lists.openid.net/<wbr>mailman/listinfo/openid-specs-<wbr>risc</a><br>
<br></blockquote></div><br></div></div>