<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Sep 12, 2017 at 7:06 PM, Phil Hunt (IDM) <span dir="ltr"><<a href="mailto:phil.hunt@oracle.com" target="_blank" class="cremed">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>Oidf has its own publication process and template. Let me know if you need a copy. It uses the older xml2rfc converter. </div></div></blockquote><div><br></div><div>Yes, please send me the template, or point me to it. Does this mean that we should drop markdown and use only xml? I am fine with xml, just trying to understand the constraints of the tool chain.</div><div><br></div><div>What does older version of xml2rfc mean?</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div id="m_-2783604038429194AppleMailSignature"><br></div><div id="m_-2783604038429194AppleMailSignature">The life cycles are the same so i would just keep everything in one risc doc unless there is a good information or technical reason to separate (other then doc mgmt). <br></div></div></blockquote><div><br></div><div>As Annabelle mentions, by having two separate specs allows us to have a stable profile spec and a changing event type spec. I think that makes sense.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div id="m_-2783604038429194AppleMailSignature"><br>The IETF would not be a good place for the spec because most cases (at least the explicit cases) stem from OIDC use cases. </div></div></blockquote><div><br></div><div>Agreed.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div id="m_-2783604038429194AppleMailSignature"><br></div><div id="m_-2783604038429194AppleMailSignature">The only reason it might be worth discussing at IETF is the implicit cases. That could be done as a new charter in Secevents. But i think openid is fine unless this is something you feel all email providers need to consider supporting RISC. </div></div></blockquote><div><br></div><div>IMO the only thing we could consider discussing at IETF is the use case document, but not the profile or the event types.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><span class="HOEnZb"><font color="#888888"><div id="m_-2783604038429194AppleMailSignature"><br>Phil</div></font></span><div><div class="h5"><div><br>On Sep 12, 2017, at 5:26 PM, Marius Scurtescu <<a href="mailto:mscurtescu@google.com" target="_blank" class="cremed">mscurtescu@google.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">I think the RISC profile should be published as an OpenID standard, and not under IETF.<div><br></div><div>I was planning to create a separate document for the event types. The reasoning was that event types will change more frequent and a separate document makes more sense. Let me know who would like to be an author and I will create the skeleton again in a couple of days.</div></div><div class="gmail_extra"><br clear="all"><div><div class="m_-2783604038429194gmail_signature" data-smartmail="gmail_signature">Marius</div></div>
<br><div class="gmail_quote">On Tue, Sep 12, 2017 at 5:16 PM, Richard Backman, Annabelle <span dir="ltr"><<a href="mailto:richanna@amazon.com" target="_blank" class="cremed">richanna@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_-2783604038429194m_3040887295703110550WordSection1">
<p class="MsoNormal">Thanks, Marius!<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Two questions:<u></u><u></u></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="m_-2783604038429194m_3040887295703110550MsoListParagraph" style="margin-left:0in">Is the intention to publish RISC as RFCs through IETF? Or is it just a convenient organizing structure for now?<u></u><u></u></li><li class="m_-2783604038429194m_3040887295703110550MsoListParagraph" style="margin-left:0in">Will the RISC event types be defined in this document, or in a separate document? I recall us talking about this in one of our F2Fs but I cannot remember the outcome. I do recall arguing
that events defined in the future should be defined in separate documents.<u></u><u></u></li></ol>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">-- <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Annabelle Richard Backman<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Identity Services<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Marius Scurtescu <<a href="mailto:mscurtescu@google.com" target="_blank" class="cremed">mscurtescu@google.com</a>><br>
<b>Date: </b>Saturday, September 9, 2017 at 9:18 PM<br>
<b>To: </b>"<a href="mailto:openid-specs-risc@lists.openid.net" target="_blank" class="cremed">openid-specs-risc@lists.openi<wbr>d.net</a>" <<a href="mailto:openid-specs-risc@lists.openid.net" target="_blank" class="cremed">openid-specs-risc@lists.openi<wbr>d.net</a>><br>
<b>Cc: </b>Phillip Hunt <<a href="mailto:phil.hunt@oracle.com" target="_blank" class="cremed">phil.hunt@oracle.com</a>>, "Richard Backman, Annabelle" <<a href="mailto:richanna@amazon.com" target="_blank" class="cremed">richanna@amazon.com</a>>, "<a href="mailto:secevemt@ve7jtb.com" target="_blank" class="cremed">secevemt@ve7jtb.com</a>" <<a href="mailto:secevemt@ve7jtb.com" target="_blank" class="cremed">secevemt@ve7jtb.com</a>><br>
<b>Subject: </b>RISC Profile<u></u><u></u></span></p>
</div><span>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">The initial skeleton at: <u></u><u></u></p>
<div>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__bitbucket.org_openid_risc&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=JBm5biRrKugCH0FkITSeGJxPEivzjWwlNKe4C_lLIGk&m=fGVjqygzih2rKAgh_tG96wuTq4FTaObaVe4DMSRcV7k&s=2dWBwy-kCe-JQKTc53o3n76H7RYTu1YQk0YJ0whUKR8&e=" target="_blank" class="cremed">https://bitbucket.org/openid/r<wbr>isc</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">Marius<u></u><u></u></p>
</div>
</div>
</div>
</div>
</span></div>
</div>
</blockquote></div><br></div>
</div></blockquote></div></div></div></blockquote></div><br></div></div>