<div dir="ltr">Here are my notes. Please let me know if I missed anything.<div><br></div><div><b>Attendees</b>: Adam Dawes, Mark Risher, Marius Scurtescu, John Bradley, Nat Sakimura, Adam Migus, George Fletcher, Phil Hunt</div><div><br></div><div><b>Google Contract for Data Sharing</b></div><div>Mark Risher gave update that Google is in final stages of redlining the contract with the first partner. Question about the best way to scale this going forward so that we don't have iterative bi-lateral negotiations. </div><div><br></div><div>Discussion about clearninghouse like Confyrm serving as way to scale contracting and also discussion about using Open Identity Exchange to create a trust framework for coming up with legal document that could be vetted by multiple legal teams and would then serve as a take-it-or-leave-it kind of offer for others. </div><div><br></div><div>AI: Adam will send out email to Amazon, Facebook, Microsoft, Confyrm and Paypal to see if they can get legal resource to work together on a standard contract that we can all agree on using the Google contract as a base. We can then decide whether we want to formalize that as a Trust Framework at OIX or just re-use it as convenient.</div><div><br></div><div><b>Data Transport Discussion</b></div><div>Google has been working on building pub/sub infrastructure to propagate changed password events which can be extended for other RISC events. In early trials on hijacking signals, it was observed that freshness of the signals is important. </div><div><br></div><div>Marius has been talking with Phil about his ID-events spec and RISC events. General agreement that ID-events spec might describe multiple modes of transport for messages, it makes sense that RISC should specifically designate a post method for transport. We can define the specifics of that within the RISC group but we will probably want to formalize it as a part of the ID-events spec. ID-events can then have additional transport mechanisms which can be used by other specs that have different use cases like SCIM.</div><div><br></div><div>Agreement that we should also start looking at the event message format. Consensus that we should NOT extend ID tokens to be used for RISC events but should more generically use JWTs and define the claims. Reusing ID Tokens poses some security risk and easy to create bugs. OpenID Connect WG is also working with ID-events for back-channel logout mechanism but we agreed that RISC should go on a separate track because semantics are probably different. </div><div><br></div><div>Because we are getting close on more scalable trials and hopefully contract will allow us to scale participants, it makes sense to now invest more effort in defining the event messages and transport issues. We will now increase RISC meetings to every two weeks to get moving on this work.</div><div><br></div><div>AI: Adam to adjust schedule of meetings</div><div><br></div><div>Please update with any errors or omissions.</div><div><br></div><div>thanks,</div><div>AD</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 8, 2016 at 5:14 PM, Hardt, Dick <span dir="ltr"><<a href="mailto:dick@amazon.com" target="_blank">dick@amazon.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="m_708333701405813935WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Sorry I was not able to make the call today. Will a summary of the call be posted soon?<u></u><u></u></span></p><div><div class="h5">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<div>
<div>
<p class="MsoNormal">On 8/8/16, 1:31 PM, someone claiming to be "Openid-specs-risc on behalf of Adam Dawes" <<a href="mailto:openid-specs-risc-bounces@lists.openid.net" target="_blank">openid-specs-risc-bounces@<wbr>lists.openid.net</a> on behalf of
<a href="mailto:adawes@google.com" target="_blank">adawes@google.com</a>> wrote:<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<blockquote style="border:none;border-left:solid #b5c4df 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="m_708333701405813935MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<p class="MsoNormal">Hi all, <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">We have our monthly RISC call scheduled for today. Agenda:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">- Progress on legal agreement for data sharing<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">- Transport design for sending RISC messages <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">- AOB<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<p class="MsoNormal">1. Please join my meeting.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="https://global.gotomeeting.com/join/576653581" target="_blank">https://global.gotomeeting.<wbr>com/join/576653581</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">United States: <a href="tel:%2B1%20%28312%29%20757-3119" value="+13127573119" target="_blank">+1 (312) 757-3119</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Australia: <a href="tel:%2B61%202%209091%207603" value="+61290917603" target="_blank">+61 2 9091 7603</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Austria: +43 (0) 7 2088 0716<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Belgium: +32 (0) 28 08 4372<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Canada: <a href="tel:%2B1%20%28647%29%20497-9380" value="+16474979380" target="_blank">+1 (647) 497-9380</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Denmark: +45 (0) 69 91 84 58<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Finland: +358 (0) 931 58 1773<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">France: +33 (0) 170 950 590<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Germany: <a href="tel:%2B49%20%280%29%20692%205736%207300" value="+4969257367300" target="_blank">+49 (0) 692 5736 7300</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Ireland: +353 (0) 15 133 006<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Italy: +39 0 699 26 68 65<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Netherlands: +31 (0) 208 080 759<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">New Zealand: <a href="tel:%2B64%209%20974%209579" value="+6499749579" target="_blank">+64 9 974 9579</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Norway: <a href="tel:%2B47%2021%2004%2030%2059" value="+4721043059" target="_blank">+47 21 04 30 59</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Spain: <a href="tel:%2B34%20931%2076%201534" value="+34931761534" target="_blank">+34 931 76 1534</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Sweden: +46 (0) 852 500 691<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Switzerland: +41 (0) 435 0026 89<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">United Kingdom: <a href="tel:%2B44%20%280%29%2020%203713%205011" value="+442037135011" target="_blank">+44 (0) 20 3713 5011</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Access Code: 576-653-581<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Audio PIN: Shown after joining the meeting<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Meeting ID: 576-653-581<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<div>
<div style="margin-top:7.5pt">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-family:Helvetica;color:#555555;border:solid #d50f25 1.5pt;padding:2.0pt">Adam Dawes |</span><span style="font-family:Helvetica;color:#555555;border:solid #3369e8 1.5pt;padding:2.0pt"> Sr. Product
Manager |</span><span style="font-family:Helvetica;color:#555555;border:solid #009939 1.5pt;padding:2.0pt"> <a href="mailto:adawes@google.com" target="_blank">adawes@google.com</a> |</span><span style="font-family:Helvetica;color:#555555;border:solid #eeb211 1.5pt;padding:2.0pt"> <wbr>+1
<a href="tel:650-214-2410" value="+16502142410" target="_blank">650-214-2410</a></span><span style="font-family:Helvetica;color:#555555"><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div style="line-height:1.5em;padding-top:10px;margin-top:10px;color:rgb(85,85,85);font-family:sans-serif;font-size:small"><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(213,15,37);padding-top:2px;margin-top:2px">Adam Dawes |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(51,105,232);padding-top:2px;margin-top:2px"> Sr. Product Manager |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(0,153,57);padding-top:2px;margin-top:2px"> <a href="mailto:adawes@google.com" target="_blank">adawes@google.com</a> |</span><span style="border-width:2px 0px 0px;border-style:solid;border-color:rgb(238,178,17);padding-top:2px;margin-top:2px"> +1 650-214-2410</span></div><br></div></div>
</div>