<div dir="ltr">Thanks for bringing this up Dick. I think you're worried about, when <a href="mailto:alice@gmail.com">alice@gmail.com</a> signs up for an account at Amazon, how would Amazon register to get events from Google. I think we can deal with this if Amazon sends a SET token to google with an "account created" event which would then create a registration at google for Amazon to receive events about alice@.<div><br></div><div>I think it is totally reasonable to think of account creation as a notifiable event. And in typical RISC fashion, it is up to the recipient to do what it will with the events. From Google's perspective, we would white list a set of partners where we have contracts to enable implicit registration. I think we should work out some response codes to make it clear to the sender whether the registration succeeded.</div><div><br></div><div>We didn't talk a lot about this in the F2F but is an idea that I had in my deck and I think it came up in Phil and my conversation last week. Phil, does the above give you any concerns? </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 28, 2017 at 9:12 AM, Phil Hunt (IDM) <span dir="ltr"><<a href="mailto:phil.hunt@oracle.com" target="_blank">phil.hunt@oracle.com</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>RISC use case is typically bi-directional so events can be used. It also works better because usually a receiver may add only or drop only depending on implicit or explicit federation. </div><div id="m_8417452791228652780AppleMailSignature"><br></div><div id="m_8417452791228652780AppleMailSignature">Adam argued for all other update items to be done OOB. </div><div id="m_8417452791228652780AppleMailSignature"><br></div><div id="m_8417452791228652780AppleMailSignature">That just left error signalling for the receiver to find out why events were not coming. </div><div id="m_8417452791228652780AppleMailSignature"><br></div><div id="m_8417452791228652780AppleMailSignature">We left it that scim can be quickly added for those that want full automated CRUD (oracle does). Buy it would not be required in core. <span class="HOEnZb"><font color="#888888"><br><br>Phil</font></span></div><div><div class="h5"><div><br>On Feb 28, 2017, at 8:32 AM, Hardt, Dick <<a href="mailto:dick@amazon.com" target="_blank">dick@amazon.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<div class="m_8417452791228652780WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Perhaps I am missing it, but I don’t see a mechanism for the receiver to add / delete which subjects the receiver is interested in. Is this not included, or am I misunderstanding what is
below? <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Or is that out of scope? If so, that seems odd as there is a control plane API in (3)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">/Dick<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">On 2/28/17, 12:53 AM, 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" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I think this is great Phil. Thanks again for the detailed conversation where we were able to arrive at this.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">On Mon, Feb 27, 2017 at 1:35 PM, Phil Hunt <<a href="mailto:phil.hunt@oracle.com" target="_blank">phil.hunt@oracle.com</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Please confirm if you agree with the following:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<p class="MsoNormal" style="margin-left:.5in">I had previously promised to break up the distribution draft into components. I ran into some difficulty as to how subscribers (receivers) of events find out if the publisher is having problems delivering events.
<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">After some discussion with the RISC WG folks and Adam Dawes, I would like to propose that I break out a SET Transmission draft that includes the following:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">1. Basic HTTPS POST profile to a specified endpoint. It is up to the receiver to provide fault tolerance and high-availability that meets its own delivery assurance requirements.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">2. A set of metadata that describes the endpoints, the encryption methods (eg. keys for signing and encrypting JWTs) etc.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">3. A simple control plane API that allows a subscriber (receiver) to perform an HTTPS GET to obtain the current configuration and subscription (stream) status. While compatible with SCIM, it will NOT require SCIM
to be implemented. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">4. Configuration of subscriptions (streams) is done through out-of-scope administrative processes offered by event publishers.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">5. In the initial profile, subscribers will not be able to “pause” streams automatically unless offered through the administrative interface of the publisher.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">If people have a need for automated management, the basic idea is that you implement the POST and PATCH methods of SCIM and you are good to go. We don’t need to spend a lot of time on it as there is nothing special
to do once the metadata for streams is defined.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Does this work for everyone?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Phil<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Oracle Corporation, Identity Cloud Services & Identity Standards<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">@independentid<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"><a href="http://www.independentid.com" target="_blank">www.independentid.com</a><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"><a href="mailto:phil.hunt@oracle.com" target="_blank">phil.hunt@oracle.com</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"><u></u> <u></u></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<u></u> <u></u></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a href="mailto:Id-event@ietf.org" target="_blank">Id-event@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/id-event" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<p class="MsoNormal" style="margin-left:.5in">-- <u></u><u></u></p>
<div>
<div>
<div style="margin-top:7.5pt">
<p class="MsoNormal" style="margin-left:.5in;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)%20214-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" style="margin-left:.5in"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</div></blockquote></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>