<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">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. <div class=""><br class=""></div><div class="">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)</div><div class=""><br class=""></div><div class="">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. <br class=""><div class=""><br class=""></div><div class="">This draft should be a good starting place for the SEC Event WG proposed charter.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class=""> </div><div class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><span class="Apple-style-span" style="border-collapse: separate; line-height: normal; border-spacing: 0px;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><div class=""><div class="">Phil</div><div class=""><br class=""></div><div class="">@independentid</div><div class=""><a href="http://www.independentid.com" class="">www.independentid.com</a></div></div></div></div></span><a href="mailto:phil.hunt@oracle.com" class="" style="orphans: 2; widows: 2;">phil.hunt@oracle.com</a></div><div class=""><br class=""></div></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">Begin forwarded message:</div><br class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><a href="mailto:internet-drafts@ietf.org" class="">internet-drafts@ietf.org</a><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">New Version Notification for draft-hunt-idevent-token-06.txt</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">September 29, 2016 at 3:20:45 PM PDT<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">"Michael B. Jones" <<a href="mailto:mbj@microsoft.com" class="">mbj@microsoft.com</a>>, "William Denniss" <<a href="mailto:wdenniss@google.com" class="">wdenniss@google.com</a>>, "Phil Hunt" <<a href="mailto:phil.hunt@yahoo.com" class="">phil.hunt@yahoo.com</a>>, "Morteza Ansari" <<a href="mailto:morteza.ansari@cisco.com" class="">morteza.ansari@cisco.com</a>>, "Michael Jones" <<a href="mailto:mbj@microsoft.com" class="">mbj@microsoft.com</a>><br class=""></span></div><br class=""><div class=""><div class=""><br class="">A new version of I-D, draft-hunt-idevent-token-06.txt<br class="">has been successfully submitted by Phil Hunt and posted to the<br class="">IETF repository.<br class=""><br class="">Name:<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>draft-hunt-idevent-token<br class="">Revision:<span class="Apple-tab-span" style="white-space:pre"> </span>06<br class="">Title:<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>Security Event Token (SET)<br class="">Document date:<span class="Apple-tab-span" style="white-space:pre"> </span>2016-09-29<br class="">Group:<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>Individual Submission<br class="">Pages:<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>19<br class="">URL: <a href="https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-06.txt" class="">https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-06.txt</a><br class="">Status: <a href="https://datatracker.ietf.org/doc/draft-hunt-idevent-token/" class="">https://datatracker.ietf.org/doc/draft-hunt-idevent-token/</a><br class="">Htmlized: <a href="https://tools.ietf.org/html/draft-hunt-idevent-token-06" class="">https://tools.ietf.org/html/draft-hunt-idevent-token-06</a><br class="">Diff: <a href="https://www.ietf.org/rfcdiff?url2=draft-hunt-idevent-token-06" class="">https://www.ietf.org/rfcdiff?url2=draft-hunt-idevent-token-06</a><br class=""><br class="">Abstract:<br class=""> This specification defines the Security Event token, which may be<br class=""> distributed via a protocol such as HTTP. The Security Event Token<br class=""> (SET) specification profiles the JSON Web Token (JWT) and may be<br class=""> optionally signed and/or encrypted. A SET describes a statement of<br class=""> fact that may be shared by an event publisher with event subscribers.<br class=""><br class=""><br class=""><br class=""><br class="">Please note that it may take a couple of minutes from the time of submission<br class="">until the htmlized version and diff are available at <a href="http://tools.ietf.org" class="">tools.ietf.org</a>.<br class=""><br class="">The IETF Secretariat<br class=""><br class=""></div></div></blockquote></div><br class=""></div></div></body></html>