<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#002060;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">I just reviewed the changes in draft-hunt-idevent-token-06 and, for the record, I’m fine with them.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> -- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> scim [mailto:scim-bounces@ietf.org]
<b>On Behalf Of </b>Phil Hunt<br>
<b>Sent:</b> Thursday, September 29, 2016 3:39 PM<br>
<b>To:</b> id-event@ietf.org<br>
<b>Cc:</b> scim@ietf.org WG <scim@ietf.org>; openid-specs-ab@lists.openid.net Ab <openid-specs-ab@lists.openid.net>; openid-specs-risc@lists.openid.net<br>
<b>Subject:</b> [scim] Fwd: New Version Notification for draft-hunt-idevent-token-06.txt<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is a minor update to the SET Token draft. Based on the mailing list feedback, I made some revisions to the text on transactions and sequencing. I dropped the term “idempotency” as this is not really the correct usage of the word.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The issue I was trying to get at was whether SETs can be delivered in any sequence or whether there sequence is critical. For example in an Idempotent service, one cannot modify a resource that has not yet been created. So while commands
may be repeated achieving the same result, the sequence of different commands is critical. 8)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My gut feeling on sequencing (when needed) is most likely resolved by specs that profile SET Tokes by adding sequencing claim or defining “txn” for the purpose. There may be some delivery methods that can provide sequencing, but I think
that has more to do with deployment architecture rather than protocol. For example, in a distributed system, the way events are delivered to a Feed Publishing Service might enable the Feed Publisher to guarantee order. That’s not to say I haven’t overlooked
a “duh” simple solution. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">This draft should be a good starting place for the SEC Event WG proposed charter.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">Phil<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">@independentid<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><a href="http://www.independentid.com">www.independentid.com</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="color:black"><a href="mailto:phil.hunt@oracle.com">phil.hunt@oracle.com</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Begin forwarded message:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica",sans-serif">From: </span>
</b><span style="font-family:"Helvetica",sans-serif"><a href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica",sans-serif">Subject: New Version Notification for draft-hunt-idevent-token-06.txt</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica",sans-serif">Date: </span>
</b><span style="font-family:"Helvetica",sans-serif">September 29, 2016 at 3:20:45 PM PDT</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica",sans-serif">To: </span>
</b><span style="font-family:"Helvetica",sans-serif">"Michael B. Jones" <<a href="mailto:mbj@microsoft.com">mbj@microsoft.com</a>>, "William Denniss" <<a href="mailto:wdenniss@google.com">wdenniss@google.com</a>>, "Phil Hunt" <<a href="mailto:phil.hunt@yahoo.com">phil.hunt@yahoo.com</a>>,
"Morteza Ansari" <<a href="mailto:morteza.ansari@cisco.com">morteza.ansari@cisco.com</a>>, "Michael Jones" <<a href="mailto:mbj@microsoft.com">mbj@microsoft.com</a>></span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
A new version of I-D, draft-hunt-idevent-token-06.txt<br>
has been successfully submitted by Phil Hunt and posted to the<br>
IETF repository.<br>
<br>
Name:<span class="apple-tab-span"> </span>draft-hunt-idevent-token<br>
Revision:<span class="apple-tab-span"> </span>06<br>
Title:<span class="apple-tab-span"> </span>Security Event Token (SET)<br>
Document date:<span class="apple-tab-span"> </span>2016-09-29<br>
Group:<span class="apple-tab-span"> </span>Individual Submission<br>
Pages:<span class="apple-tab-span"> </span>19<br>
URL: <a href="https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-06.txt">https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-06.txt</a><br>
Status: <a href="https://datatracker.ietf.org/doc/draft-hunt-idevent-token/">https://datatracker.ietf.org/doc/draft-hunt-idevent-token/</a><br>
Htmlized: <a href="https://tools.ietf.org/html/draft-hunt-idevent-token-06">https://tools.ietf.org/html/draft-hunt-idevent-token-06</a><br>
Diff: <a href="https://www.ietf.org/rfcdiff?url2=draft-hunt-idevent-token-06">https://www.ietf.org/rfcdiff?url2=draft-hunt-idevent-token-06</a><br>
<br>
Abstract:<br>
This specification defines the Security Event token, which may be<br>
distributed via a protocol such as HTTP. The Security Event Token<br>
(SET) specification profiles the JSON Web Token (JWT) and may be<br>
optionally signed and/or encrypted. A SET describes a statement of<br>
fact that may be shared by an event publisher with event subscribers.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submission<br>
until the htmlized version and diff are available at <a href="http://tools.ietf.org">
tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>