
From nobody Thu Sep  1 10:28:12 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F167F12D1EA; Thu,  1 Sep 2016 10:28:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q8wMo7E5-WEd; Thu,  1 Sep 2016 10:28:09 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00A1912D1E7; Thu,  1 Sep 2016 10:28:08 -0700 (PDT)
Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u81HS70j010155 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 1 Sep 2016 17:28:07 GMT
Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id u81HS61V017256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 1 Sep 2016 17:28:06 GMT
Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u81HS55n020300; Thu, 1 Sep 2016 17:28:06 GMT
Received: from [10.0.1.5] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 01 Sep 2016 10:28:05 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_3778A97A-3139-44A8-8D60-4274D23D807B"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Phil Hunt <phil.hunt@oracle.com>
Date: Thu, 1 Sep 2016 10:28:03 -0700
Message-Id: <2782FF7C-DE82-478D-97A0-F8CB29B51B60@oracle.com>
References: <147275055023.32079.13898052231663585667.idtracker@ietfa.amsl.com>
To: id-event@ietf.org
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0022.oracle.com [141.146.126.234]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/te15qKQIR6ilPZV2MhsJ2qj9U4A>
Cc: "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
Subject: [Id-event] Fwd: New Version Notification for draft-hunt-idevent-token-04.txt
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Sep 2016 17:28:11 -0000

--Apple-Mail=_3778A97A-3139-44A8-8D60-4274D23D807B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Based on input this week, I have posted draft 04.

Highlights include:
   o  Re-added the "sub" claim with clarifications that any SET type may
      use it.
   o  Added additional clarification on the use of envelope vs. paylaod
      attributes
   o  Added security consideration for event timing.
   o  Switched use of "attribute" to "claim" for consistency.
   o  Revised examples to put "sub" claim back in the top level.
   o  Added clarification that SETs typically do not use "exp".
   o  Added security consideration for distinguishing Access Tokens and
      SETs.

Thanks for the great reviews. I think we are getting close to consensus =
on this.

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>





> Begin forwarded message:
>=20
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-hunt-idevent-token-04.txt
> Date: September 1, 2016 at 10:22:30 AM PDT
> To: "William Denniss" <wdenniss@google.com>, "Phil Hunt" =
<phil.hunt@yahoo.com>, <none-chairs@ietf.org>, "Michael B. Jones" =
<mbj@microsoft.com>, "Morteza Ansari" <morteza.ansari@cisco.com>, =
"Michael Jones" <mbj@microsoft.com>
>=20
>=20
> A new version of I-D, draft-hunt-idevent-token-04.txt
> has been successfully submitted by Phil Hunt and posted to the
> IETF repository.
>=20
> Name:		draft-hunt-idevent-token
> Revision:	04
> Title:		Security Event Token (SET)
> Document date:	2016-09-01
> Group:		Individual Submission
> Pages:		17
> URL:            =
https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-04.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-hunt-idevent-token/
> Htmlized:       =
https://tools.ietf.org/html/draft-hunt-idevent-token-04
> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-token-04
>=20
> Abstract:
>   This specification defines the Security Event token, which may be
>   distributed via a protocol such as HTTP.  The Security Event Token
>   (SET) specification profiles the JSON Web Token (JWT) and may be
>   optionally signed and/or encrypted.  A SET describes a statement of
>   fact that may be shared by an event publisher with event =
subscribers.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20


--Apple-Mail=_3778A97A-3139-44A8-8D60-4274D23D807B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Based on input this week, I have posted draft 04.<div =
class=3D""><br class=3D""></div><div class=3D"">Highlights =
include:</div><div class=3D""><div style=3D"margin: 0px; font-size: =
11px; line-height: normal; font-family: Monaco;" class=3D"">&nbsp; =
&nbsp;o &nbsp;Re-added the "sub" claim with clarifications that any SET =
type may</div><div style=3D"margin: 0px; font-size: 11px; line-height: =
normal; font-family: Monaco;" class=3D"">&nbsp; &nbsp; &nbsp; use =
it.</div><div style=3D"margin: 0px; font-size: 11px; line-height: =
normal; font-family: Monaco;" class=3D"">&nbsp;&nbsp; o&nbsp; Added =
additional clarification on the use of envelope <span =
style=3D"text-decoration: underline" class=3D"">vs</span>. <span =
style=3D"text-decoration: underline" class=3D"">paylaod</span></div><div =
style=3D"margin: 0px; font-size: 11px; line-height: normal; font-family: =
Monaco;" class=3D"">&nbsp; &nbsp; &nbsp; attributes</div><div =
style=3D"margin: 0px; font-size: 11px; line-height: normal; font-family: =
Monaco;" class=3D"">&nbsp;&nbsp; o&nbsp; Added security consideration =
for event timing.</div><div style=3D"margin: 0px; font-size: 11px; =
line-height: normal; font-family: Monaco;" class=3D"">&nbsp;&nbsp; =
o&nbsp; Switched use of "attribute" to "claim" for =
consistency.</div><div style=3D"margin: 0px; font-size: 11px; =
line-height: normal; font-family: Monaco;" class=3D"">&nbsp;&nbsp; =
o&nbsp; Revised examples to put "sub" claim back in the top =
level.</div><div style=3D"margin: 0px; font-size: 11px; line-height: =
normal; font-family: Monaco;" class=3D"">&nbsp;&nbsp; o&nbsp; Added =
clarification that SETs typically do not use "<span =
style=3D"text-decoration: underline" class=3D"">exp</span>".</div><div =
style=3D"margin: 0px; font-size: 11px; line-height: normal; font-family: =
Monaco;" class=3D"">&nbsp;&nbsp; o&nbsp; Added security consideration =
for distinguishing Access Tokens and</div><div style=3D"margin: 0px; =
font-size: 11px; line-height: normal; font-family: Monaco;" =
class=3D"">&nbsp; &nbsp; &nbsp; SETs.</div></div><div class=3D""><br =
class=3D""></div><div class=3D"">Thanks for the great reviews. I think =
we are getting close to consensus on this.</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>

<div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a =
href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">New Version =
Notification for draft-hunt-idevent-token-04.txt</b><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">September 1, 2016 at 10:22:30 =
AM PDT<br class=3D""></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">"William Denniss" &lt;<a =
href=3D"mailto:wdenniss@google.com" =
class=3D"">wdenniss@google.com</a>&gt;, "Phil Hunt" &lt;<a =
href=3D"mailto:phil.hunt@yahoo.com" =
class=3D"">phil.hunt@yahoo.com</a>&gt;, &lt;<a =
href=3D"mailto:none-chairs@ietf.org" =
class=3D"">none-chairs@ietf.org</a>&gt;, "Michael B. Jones" &lt;<a =
href=3D"mailto:mbj@microsoft.com" class=3D"">mbj@microsoft.com</a>&gt;, =
"Morteza Ansari" &lt;<a href=3D"mailto:morteza.ansari@cisco.com" =
class=3D"">morteza.ansari@cisco.com</a>&gt;, "Michael Jones" &lt;<a =
href=3D"mailto:mbj@microsoft.com" class=3D"">mbj@microsoft.com</a>&gt;<br =
class=3D""></span></div><br class=3D""><div class=3D""><div class=3D""><br=
 class=3D"">A new version of I-D, draft-hunt-idevent-token-04.txt<br =
class=3D"">has been successfully submitted by Phil Hunt and posted to =
the<br class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span=
 class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-hunt-idevent-token<br class=3D"">Revision:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>04<br =
class=3D"">Title:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Security Event Token (SET)<br class=3D"">Document date:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>2016-09-01<br class=3D"">Group:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Individual Submission<br =
class=3D"">Pages:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>17<br class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-04.t=
xt" =
class=3D"">https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-0=
4.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-hunt-idevent-token/" =
class=3D"">https://datatracker.ietf.org/doc/draft-hunt-idevent-token/</a><=
br class=3D"">Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-hunt-idevent-token-04" =
class=3D"">https://tools.ietf.org/html/draft-hunt-idevent-token-04</a><br =
class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-token-04" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-token-04=
</a><br class=3D""><br class=3D"">Abstract:<br class=3D""> =
&nbsp;&nbsp;This specification defines the Security Event token, which =
may be<br class=3D""> &nbsp;&nbsp;distributed via a protocol such as =
HTTP. &nbsp;The Security Event Token<br class=3D""> &nbsp;&nbsp;(SET) =
specification profiles the JSON Web Token (JWT) and may be<br class=3D""> =
&nbsp;&nbsp;optionally signed and/or encrypted. &nbsp;A SET describes a =
statement of<br class=3D""> &nbsp;&nbsp;fact that may be shared by an =
event publisher with event subscribers.<br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D"">Please note that it may take a =
couple of minutes from the time of submission<br class=3D"">until the =
htmlized version and diff are available at <a =
href=3D"http://tools.ietf.org" class=3D"">tools.ietf.org</a>.<br =
class=3D""><br class=3D"">The IETF Secretariat<br class=3D""><br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_3778A97A-3139-44A8-8D60-4274D23D807B--


From nobody Thu Sep  1 16:47:47 2016
Return-Path: <mscurtescu@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9866E12D7A1 for <id-event@ietfa.amsl.com>; Thu,  1 Sep 2016 16:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HK1zW3XqNSKn for <id-event@ietfa.amsl.com>; Thu,  1 Sep 2016 16:47:44 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CA4F12D526 for <id-event@ietf.org>; Thu,  1 Sep 2016 16:47:44 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id v143so6329697wmv.0 for <id-event@ietf.org>; Thu, 01 Sep 2016 16:47:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vWePha66zdnQ/TK9uvPMKS+Qz7egmDYQ4AclxyBp7ps=; b=VoFdD8LLfmQcyfKiujKXlXkzNmmQuqRAnDriqgi2CXMSEPSV44gQkDogMHI8fTqXIw oU1B7lxHjlfyBqkPKG5bbbXFIfg3YhSZPyFYGr4LUJluuZ4KzIcrYzyozwZqc3lMDPxn sgq35py1AE4Ku4++pNt4ojjE496lkRLFq/ftCNnGeOfAHfrn2d55292/zR6CutZIak5y NJ3mxspUs6vldguMZf8dxqfF7B8BX/ZYI0u62rLXw7dpMSQmD5oTj81uCCClpmkUok8T febjkjt47phg+3tRIyJdWLXTbdVb1oMS3Y6MuDkZTy5lVHUK36yWrj5OGRbhLR/vdAvq he0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vWePha66zdnQ/TK9uvPMKS+Qz7egmDYQ4AclxyBp7ps=; b=ZH7okaM2QMaU8yrDkpsaN7bAGZZhmtVRt4kpHFPI3fiEG9lVzLZLvunHXNzG5BUOZy dMyhfmN9YSu0rQmDOdxlfG6jfeKEn7nUL+f9YlKY/bMILzUJmVTn5bkPcwwp8jRZoEkm n2PpshjlHWP3kIu6HJjYsd5C+M69YYxTNzIJfmhrJvS0bJIEz43nVV9O5U0hIG0dB5W5 m3t6YQCmtcUr5hxbNwzhgCFubRSvQbyPVlLhFVbQOq+gKHS4hLpNDVmg6PYs6ihhVHDR XhheIg3kZp7GrzBNA6KNTl4R+CNNfk0CvcXJ9xrvn/QjWJkUDTgsrk3+yFVv/NCMe3IA D7MA==
X-Gm-Message-State: AE9vXwMCDSfgrFwM3HrihGUufnYDVk3nODXA9YK4Ah664zaTMsMpcdT1Yvoky5aom9ak08Z95GPnbcN6x2VqiiKF
X-Received: by 10.28.27.143 with SMTP id b137mr266839wmb.12.1472773662588; Thu, 01 Sep 2016 16:47:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.197.15 with HTTP; Thu, 1 Sep 2016 16:47:21 -0700 (PDT)
In-Reply-To: <D3E095D4.444CD%moransar@cisco.com>
References: <3957B53A-D016-4C9C-A164-F90C7FB983C8@oracle.com> <CAAP42hC+uxV7vfgREC1H3zy_MV3qa3XSHY53EOk_fRrtATu+2Q@mail.gmail.com> <D3E095D4.444CD%moransar@cisco.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Thu, 1 Sep 2016 16:47:21 -0700
Message-ID: <CAGdjJpKH2+wOKJCvG7vvLQj95T51JtbPEGcWRR5KX5sS+VRaeA@mail.gmail.com>
To: "Morteza Ansari (moransar)" <moransar@cisco.com>
Content-Type: multipart/alternative; boundary=001a114b31cefe9ba2053b7ad6a9
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/8fgo3ybRo_aJYD1X6uMd8rMoc0E>
Cc: William Denniss <wdenniss@google.com>, Mike Jones <michael.jones@microsoft.com>, Leif Johansson <leifj@sunet.se>, "id-event@ietf.org" <id-event@ietf.org>, "Phil Hunt \(IDM\)" <phil.hunt@oracle.com>
Subject: Re: [Id-event] Ietf97 idevent meeting?
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Sep 2016 23:47:46 -0000

--001a114b31cefe9ba2053b7ad6a9
Content-Type: text/plain; charset=UTF-8

I will try to attend.

Marius

On Mon, Aug 22, 2016 at 11:43 AM, Morteza Ansari (moransar) <
moransar@cisco.com> wrote:

> Very unlikely I will be able to make it either, but will gladly join the
> meeting remotely.
>
> From: William Denniss <wdenniss@google.com>
> Date: Monday, August 22, 2016 at 9:28 AM
> To: Phil Hunt <phil.hunt@oracle.com>, "id-event@ietf.org" <
> id-event@ietf.org>
> Cc: Morteza <moransar@cisco.com>, Mike Jones <michael.jones@microsoft.com>,
> Marius Scurtescu <mscurtescu@google.com>, Leif Johansson <leifj@sunet.se>
> Subject: Re: Ietf97 idevent meeting?
>
> Sounds like a good idea to me. I can't attend in person this time, but
> would definitely remote in.
> On Sat, Aug 20, 2016 at 4:14 PM Phil Hunt (IDM) <phil.hunt@oracle.com>
> wrote:
>
>>
>> We have been making a lot of progress on the core id event draft. It
>> would be good to have an official meeting.
>>
>> Maybe the best thing would be to adopt the charter and get it going?
>>
>> There are a few items more to talk through like timing issues in the
>> draft to avoid unanticipated feedback concerns (discussed in issue 1000 on
>> openid connect).
>>
>> Thanks
>>
>> Phil
>>
>

--001a114b31cefe9ba2053b7ad6a9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I will try to attend.</div><div class=3D"gmail_extra"><br =
clear=3D"all"><div><div class=3D"gmail_signature" data-smartmail=3D"gmail_s=
ignature">Marius</div></div>
<br><div class=3D"gmail_quote">On Mon, Aug 22, 2016 at 11:43 AM, Morteza An=
sari (moransar) <span dir=3D"ltr">&lt;<a href=3D"mailto:moransar@cisco.com"=
 target=3D"_blank">moransar@cisco.com</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>Very unlikely I will be able to make it either, but will gladly join t=
he meeting remotely.</div>
<div><br>
</div>
<span id=3D"m_5757964732012570186OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri;font-size:11pt;text-align:left;color:blac=
k;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADD=
ING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:me=
dium none;PADDING-TOP:3pt">
<span style=3D"font-weight:bold">From: </span>William Denniss &lt;<a href=
=3D"mailto:wdenniss@google.com" target=3D"_blank">wdenniss@google.com</a>&g=
t;<br>
<span style=3D"font-weight:bold">Date: </span>Monday, August 22, 2016 at 9:=
28 AM<br>
<span style=3D"font-weight:bold">To: </span>Phil Hunt &lt;<a href=3D"mailto=
:phil.hunt@oracle.com" target=3D"_blank">phil.hunt@oracle.com</a>&gt;, &quo=
t;<a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-event@ietf.org<=
/a>&quot; &lt;<a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-eve=
nt@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>Morteza &lt;<a href=3D"mailto:m=
oransar@cisco.com" target=3D"_blank">moransar@cisco.com</a>&gt;, Mike Jones=
 &lt;<a href=3D"mailto:michael.jones@microsoft.com" target=3D"_blank">micha=
el.jones@microsoft.com</a>&gt;, Marius Scurtescu &lt;<a href=3D"mailto:mscu=
rtescu@google.com" target=3D"_blank">mscurtescu@google.com</a>&gt;,
 Leif Johansson &lt;<a href=3D"mailto:leifj@sunet.se" target=3D"_blank">lei=
fj@sunet.se</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: Ietf97 idevent meeting=
?<br>
</div><div><div class=3D"h5">
<div><br>
</div>
<div>
<div>Sounds like a good idea to me. I can&#39;t attend in person this time,=
 but would definitely remote in.
<br>
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Sat, Aug 20, 2016 at 4:14 PM Phil Hunt (IDM) &lt;<a hre=
f=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">phil.hunt@oracle.com</a=
>&gt; wrote:<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
We have been making a lot of progress on the core id event draft. It would =
be good to have an official meeting.<br>
<br>
Maybe the best thing would be to adopt the charter and get it going?<br>
<br>
There are a few items more to talk through like timing issues in the draft =
to avoid unanticipated feedback concerns (discussed in issue 1000 on openid=
 connect).<br>
<br>
Thanks<br>
<br>
Phil<br>
</blockquote>
</div>
</div>
</div>
</div></div></span>
</div>

</blockquote></div><br></div>

--001a114b31cefe9ba2053b7ad6a9--


From nobody Fri Sep  2 14:59:44 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C103F12D13F; Fri,  2 Sep 2016 14:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lSUw1P0Rkqz4; Fri,  2 Sep 2016 14:59:37 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9C3612D0F8; Fri,  2 Sep 2016 14:59:36 -0700 (PDT)
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u82LxZqc029101 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Sep 2016 21:59:35 GMT
Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by userv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u82LxZlI023989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Sep 2016 21:59:35 GMT
Received: from abhmp0014.oracle.com (abhmp0014.oracle.com [141.146.116.20]) by userv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u82LxY0p026872; Fri, 2 Sep 2016 21:59:34 GMT
Received: from [192.168.1.15] (/174.7.250.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 02 Sep 2016 14:59:33 -0700
From: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_128B70C0-73C0-4167-B3A1-09BFD11C3A16"
Message-Id: <5BFD60C3-92FE-46BA-AE90-A4546A98E786@oracle.com>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Date: Fri, 2 Sep 2016 14:59:32 -0700
References: <147285344389.24829.9566046591438611371.idtracker@ietfa.amsl.com>
To: id-event@ietf.org
X-Mailer: Apple Mail (2.3124)
X-Source-IP: userv0021.oracle.com [156.151.31.71]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/wa2pMXOQFWvFq7LjMkaSSm2-qRQ>
Cc: openid-specs-risc@lists.openid.net, "openid-specs-ab@lists.openid.net Ab" <openid-specs-ab@lists.openid.net>, "scim@ietf.org WG" <scim@ietf.org>
Subject: [Id-event] Fwd: New Version Notification for draft-hunt-idevent-token-05.txt
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Sep 2016 21:59:39 -0000

--Apple-Mail=_128B70C0-73C0-4167-B3A1-09BFD11C3A16
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

This is just a quick update. Apparently when getting rid of the term =
=E2=80=9Cattribute=E2=80=9D for =E2=80=9Cclaim=E2=80=9D, my search and =
replace had a =E2=80=9Cc=E2=80=9D tacked on the end resulting in a =
number of erroneous =E2=80=9Cclaimc=E2=80=9Ds instead of =E2=80=9Cclaim=E2=
=80=9D or =E2=80=9Cclaims=E2=80=9D throughout the document.

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>





> Begin forwarded message:
>=20
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-hunt-idevent-token-05.txt
> Date: September 2, 2016 at 2:57:23 PM PDT
> To: "William Denniss" <wdenniss@google.com>, "Phil Hunt" =
<phil.hunt@yahoo.com>, <none-chairs@ietf.org>, "Michael B. Jones" =
<mbj@microsoft.com>, "Morteza Ansari" <morteza.ansari@cisco.com>, =
"Michael Jones" <mbj@microsoft.com>
>=20
>=20
> A new version of I-D, draft-hunt-idevent-token-05.txt
> has been successfully submitted by Phil Hunt and posted to the
> IETF repository.
>=20
> Name:		draft-hunt-idevent-token
> Revision:	05
> Title:		Security Event Token (SET)
> Document date:	2016-09-02
> Group:		Individual Submission
> Pages:		17
> URL:            =
https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-05.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-hunt-idevent-token/
> Htmlized:       =
https://tools.ietf.org/html/draft-hunt-idevent-token-05
> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-token-05
>=20
> Abstract:
>   This specification defines the Security Event token, which may be
>   distributed via a protocol such as HTTP.  The Security Event Token
>   (SET) specification profiles the JSON Web Token (JWT) and may be
>   optionally signed and/or encrypted.  A SET describes a statement of
>   fact that may be shared by an event publisher with event =
subscribers.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20


--Apple-Mail=_128B70C0-73C0-4167-B3A1-09BFD11C3A16
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">This is just a quick update. Apparently when getting rid of =
the term =E2=80=9Cattribute=E2=80=9D for =E2=80=9Cclaim=E2=80=9D, my =
search and replace had a =E2=80=9Cc=E2=80=9D tacked on the end resulting =
in a number of erroneous =E2=80=9Cclaimc=E2=80=9Ds instead of =
=E2=80=9Cclaim=E2=80=9D or =E2=80=9Cclaims=E2=80=9D throughout the =
document.<div class=3D""><br class=3D""></div><div class=3D""><div =
class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>

<div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a =
href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">New Version =
Notification for draft-hunt-idevent-token-05.txt</b><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">September 2, 2016 at 2:57:23 PM =
PDT<br class=3D""></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">"William Denniss" &lt;<a =
href=3D"mailto:wdenniss@google.com" =
class=3D"">wdenniss@google.com</a>&gt;, "Phil Hunt" &lt;<a =
href=3D"mailto:phil.hunt@yahoo.com" =
class=3D"">phil.hunt@yahoo.com</a>&gt;, &lt;<a =
href=3D"mailto:none-chairs@ietf.org" =
class=3D"">none-chairs@ietf.org</a>&gt;, "Michael B. Jones" &lt;<a =
href=3D"mailto:mbj@microsoft.com" class=3D"">mbj@microsoft.com</a>&gt;, =
"Morteza Ansari" &lt;<a href=3D"mailto:morteza.ansari@cisco.com" =
class=3D"">morteza.ansari@cisco.com</a>&gt;, "Michael Jones" &lt;<a =
href=3D"mailto:mbj@microsoft.com" class=3D"">mbj@microsoft.com</a>&gt;<br =
class=3D""></span></div><br class=3D""><div class=3D""><div class=3D""><br=
 class=3D"">A new version of I-D, draft-hunt-idevent-token-05.txt<br =
class=3D"">has been successfully submitted by Phil Hunt and posted to =
the<br class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span=
 class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-hunt-idevent-token<br class=3D"">Revision:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>05<br =
class=3D"">Title:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Security Event Token (SET)<br class=3D"">Document date:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>2016-09-02<br class=3D"">Group:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Individual Submission<br =
class=3D"">Pages:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>17<br class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-05.t=
xt" =
class=3D"">https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-0=
5.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-hunt-idevent-token/" =
class=3D"">https://datatracker.ietf.org/doc/draft-hunt-idevent-token/</a><=
br class=3D"">Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-hunt-idevent-token-05" =
class=3D"">https://tools.ietf.org/html/draft-hunt-idevent-token-05</a><br =
class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-token-05" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-token-05=
</a><br class=3D""><br class=3D"">Abstract:<br class=3D""> =
&nbsp;&nbsp;This specification defines the Security Event token, which =
may be<br class=3D""> &nbsp;&nbsp;distributed via a protocol such as =
HTTP. &nbsp;The Security Event Token<br class=3D""> &nbsp;&nbsp;(SET) =
specification profiles the JSON Web Token (JWT) and may be<br class=3D""> =
&nbsp;&nbsp;optionally signed and/or encrypted. &nbsp;A SET describes a =
statement of<br class=3D""> &nbsp;&nbsp;fact that may be shared by an =
event publisher with event subscribers.<br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D"">Please note that it may take a =
couple of minutes from the time of submission<br class=3D"">until the =
htmlized version and diff are available at <a =
href=3D"http://tools.ietf.org" class=3D"">tools.ietf.org</a>.<br =
class=3D""><br class=3D"">The IETF Secretariat<br class=3D""><br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_128B70C0-73C0-4167-B3A1-09BFD11C3A16--


From nobody Fri Sep  2 16:30:18 2016
Return-Path: <wdenniss@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34DF212D5A4 for <id-event@ietfa.amsl.com>; Fri,  2 Sep 2016 16:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4tGrx_8q6ISr for <id-event@ietfa.amsl.com>; Fri,  2 Sep 2016 16:30:15 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4EAE12D5AF for <id-event@ietf.org>; Fri,  2 Sep 2016 16:30:12 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id d130so50970351ywc.3 for <id-event@ietf.org>; Fri, 02 Sep 2016 16:30:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=dfDRovEzfoCLowGOhs1MOeqGDdWrHD/gKS1/OvEiKTg=; b=Tv3zr+PTx91/tIRhac2zDmm1scq3XQWHBB4ffFyvt7yDRhPACBU1Ckc1GTHbX5/Q02 0+SSemYHezwTVwY425ZMP9zTtyPvkwKzHGb4NlqgcfvEud77w5pRC7hmovlG5fevAE9O 2glraM2A5qONs9Q9LV6ICOZBCdJPLpGVNv8C4Nndji8j9ntbOls6v2G7MPUALaAyOVrV WQg1Qgi4q3siM9ktn8QRC8P12D/wk6FBwHMrKGYN9Rm8v/7mWxgQODKWsf4Wm3nmSHS2 yO0AgH2NIpZFHVylLjiJRkbBwb0Q4iNZ+chTzyYEj9OXsEjEGDeO2a3mmtqqlYLckJp1 RIBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dfDRovEzfoCLowGOhs1MOeqGDdWrHD/gKS1/OvEiKTg=; b=mdZDDfcrGgp/913CO0fM4SuSbUnTteEPwaCj9IqQwVnWLwDmt1zpzG5a7gC0QNRs5u 05QpLXtqYAD/lZZwEMURFkf4lvcfQUPwCgznPI6xR3slc5nIYrBOfM0eH8NSYJZkX5S1 W877sgtw/T72xFk2TVg20Yat3bmVxNNJnxXbK7wXTZEXvYAHyyWzqOlngUURvI1voooV /Zl27NX5K8v4jLxKNaS+5DbaG9aa1kt0hYrBZzTc1ApjrC3dg94pupFUbbPCysVAQ1vQ u6fzw9ReZ1+3Qi45GsYeQH5nf2vgmJCCxbkyKO6B8jxsoxxNYezGVWn3c5d3+gE5Wx0z C0cA==
X-Gm-Message-State: AE9vXwOenuCDq+VEdZd1ie1Ca2+zQp51cxG7uDrqwquIPGBqcnbudRKuwBpwnoMFHbVXoYYjg9LvV8LU2pkyYeVh
X-Received: by 10.129.94.130 with SMTP id s124mr20666578ywb.172.1472859011984;  Fri, 02 Sep 2016 16:30:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.213.8 with HTTP; Fri, 2 Sep 2016 16:29:51 -0700 (PDT)
From: William Denniss <wdenniss@google.com>
Date: Fri, 2 Sep 2016 16:29:51 -0700
Message-ID: <CAAP42hC3NYsO6YcP1QbhHS=h8iqzUtyF3hrvDD6OCmnm6znbjQ@mail.gmail.com>
To: id-event@ietf.org
Content-Type: multipart/alternative; boundary=001a11491b54373bca053b8eb64e
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/_uz5geA8vkwQS8e6zB1w7o2TV1E>
Subject: [Id-event] Review of latest SET draft
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Sep 2016 23:30:17 -0000

--001a11491b54373bca053b8eb64e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The draft is looking very good, and it's great to see some consensus
building.

My only major comment is on page 5 in the section that starts "A SET has
the following structure:". I'm not a fan of the terminology "outer JSON
structure" and "SET envelope" which makes it sound more complicated than it
is, and I'm not sure reflects the recent changes where it's OK again to
have a top-level sub, etc. Can we simply refer to these as "top level JWT
claims"?  The third bullet point on the "event payload" seems fine.

I'd be happy to propose an edit of that language that refers to these
claims in typical JWT parlance.

Other minor nit:

In section 2.1, "Core SET claims" most claims start with "As defined by=E2=
=80=A6"
yet 'iss' and 'aud' do not. Let's be consistent and add "As defined by..."
to those too.

--001a11491b54373bca053b8eb64e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-size:12.8px">The draft is looking very=
 good, and it&#39;s great to see some consensus building.</span><div style=
=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px">My only maj=
or comment is on page 5 in the section that starts &quot;A SET has the foll=
owing structure:&quot;. I&#39;m not a fan of the terminology &quot;outer JS=
ON structure&quot; and &quot;SET envelope&quot; which makes it sound more c=
omplicated than it is, and I&#39;m not sure reflects the recent changes whe=
re it&#39;s OK again to have a top-level sub, etc. Can we simply refer to t=
hese as &quot;top level JWT claims&quot;?=C2=A0 The third bullet point on t=
he &quot;event payload&quot; seems fine.</div><div style=3D"font-size:12.8p=
x"><br></div><div style=3D"font-size:12.8px">I&#39;d be happy<span style=3D=
"font-size:12.8px">=C2=A0to propose an edit of that language that refers to=
 these claims in typical JWT parlance.</span></div><div style=3D"font-size:=
12.8px"><br></div><div style=3D"font-size:12.8px">Other minor nit:</div><di=
v style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px">In s=
ection 2.1, &quot;Core SET claims&quot; most claims start with &quot;As def=
ined by=E2=80=A6&quot; yet &#39;iss&#39; and &#39;aud&#39; do not. Let&#39;=
s be consistent and add &quot;As defined by...&quot; to those too.</div><di=
v style=3D"font-size:12.8px"><br></div></div>

--001a11491b54373bca053b8eb64e--


From nobody Fri Sep  2 16:54:00 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB72C12B039 for <id-event@ietfa.amsl.com>; Fri,  2 Sep 2016 16:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SjabsJGWmlzz for <id-event@ietfa.amsl.com>; Fri,  2 Sep 2016 16:53:57 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 134D912B005 for <id-event@ietf.org>; Fri,  2 Sep 2016 16:53:57 -0700 (PDT)
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u82NrtrG011026 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Sep 2016 23:53:55 GMT
Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by userv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u82NrtMh017977 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Sep 2016 23:53:55 GMT
Received: from abhmp0003.oracle.com (abhmp0003.oracle.com [141.146.116.9]) by userv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u82Nrrk4000894; Fri, 2 Sep 2016 23:53:55 GMT
Received: from [192.168.1.15] (/174.7.250.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 02 Sep 2016 16:53:51 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_C6195E9D-2047-4B8F-8265-5855BE7BCD38"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Phil Hunt <phil.hunt@oracle.com>
In-Reply-To: <CAAP42hC3NYsO6YcP1QbhHS=h8iqzUtyF3hrvDD6OCmnm6znbjQ@mail.gmail.com>
Date: Fri, 2 Sep 2016 16:53:50 -0700
Message-Id: <F8DAEBE2-7F99-4150-A561-4BD230A15016@oracle.com>
References: <CAAP42hC3NYsO6YcP1QbhHS=h8iqzUtyF3hrvDD6OCmnm6znbjQ@mail.gmail.com>
To: William Denniss <wdenniss@google.com>
X-Mailer: Apple Mail (2.3124)
X-Source-IP: userv0021.oracle.com [156.151.31.71]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/e3umvXhHd_5HlzVF1qeVgBdYRdc>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Review of latest SET draft
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Sep 2016 23:53:59 -0000

--Apple-Mail=_C6195E9D-2047-4B8F-8265-5855BE7BCD38
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

+1.  I think the text could be improved. Would welcome a proposal.

The other nits, I=E2=80=99ll pick up.

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>





> On Sep 2, 2016, at 4:29 PM, William Denniss <wdenniss@google.com> =
wrote:
>=20
> The draft is looking very good, and it's great to see some consensus =
building.
>=20
> My only major comment is on page 5 in the section that starts "A SET =
has the following structure:". I'm not a fan of the terminology "outer =
JSON structure" and "SET envelope" which makes it sound more complicated =
than it is, and I'm not sure reflects the recent changes where it's OK =
again to have a top-level sub, etc. Can we simply refer to these as "top =
level JWT claims"?  The third bullet point on the "event payload" seems =
fine.
>=20
> I'd be happy to propose an edit of that language that refers to these =
claims in typical JWT parlance.
>=20
> Other minor nit:
>=20
> In section 2.1, "Core SET claims" most claims start with "As defined =
by=E2=80=A6" yet 'iss' and 'aud' do not. Let's be consistent and add "As =
defined by..." to those too.
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event


--Apple-Mail=_C6195E9D-2047-4B8F-8265-5855BE7BCD38
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">+1. &nbsp;I think the text could be improved. Would welcome a =
proposal.<div class=3D""><br class=3D""></div><div class=3D"">The other =
nits, I=E2=80=99ll pick up.</div><div class=3D""><br class=3D""><div =
class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Sep 2, 2016, at 4:29 PM, William Denniss &lt;<a =
href=3D"mailto:wdenniss@google.com" class=3D"">wdenniss@google.com</a>&gt;=
 wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D""><span style=3D"font-size:12.8px" class=3D"">The =
draft is looking very good, and it's great to see some consensus =
building.</span><div style=3D"font-size:12.8px" class=3D""><br =
class=3D""></div><div style=3D"font-size:12.8px" class=3D"">My only =
major comment is on page 5 in the section that starts "A SET has the =
following structure:". I'm not a fan of the terminology "outer JSON =
structure" and "SET envelope" which makes it sound more complicated than =
it is, and I'm not sure reflects the recent changes where it's OK again =
to have a top-level sub, etc. Can we simply refer to these as "top level =
JWT claims"?&nbsp; The third bullet point on the "event payload" seems =
fine.</div><div style=3D"font-size:12.8px" class=3D""><br =
class=3D""></div><div style=3D"font-size:12.8px" class=3D"">I'd be =
happy<span style=3D"font-size:12.8px" class=3D"">&nbsp;to propose an =
edit of that language that refers to these claims in typical JWT =
parlance.</span></div><div style=3D"font-size:12.8px" class=3D""><br =
class=3D""></div><div style=3D"font-size:12.8px" class=3D"">Other minor =
nit:</div><div style=3D"font-size:12.8px" class=3D""><br =
class=3D""></div><div style=3D"font-size:12.8px" class=3D"">In section =
2.1, "Core SET claims" most claims start with "As defined by=E2=80=A6" =
yet 'iss' and 'aud' do not. Let's be consistent and add "As defined =
by..." to those too.</div><div style=3D"font-size:12.8px" class=3D""><br =
class=3D""></div></div>
_______________________________________________<br class=3D"">Id-event =
mailing list<br class=3D""><a href=3D"mailto:Id-event@ietf.org" =
class=3D"">Id-event@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event<br =
class=3D""></div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_C6195E9D-2047-4B8F-8265-5855BE7BCD38--


From nobody Tue Sep  6 17:01:31 2016
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CA6A12B388 for <id-event@ietfa.amsl.com>; Tue,  6 Sep 2016 17:01:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q090J786F3GL for <id-event@ietfa.amsl.com>; Tue,  6 Sep 2016 17:01:27 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0103.outbound.protection.outlook.com [104.47.37.103]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D26D712B01F for <id-event@ietf.org>; Tue,  6 Sep 2016 17:01:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=9QSuTZjPF/N2nwHn9SgMkFtvJarongouU7tOayutcpw=; b=hQTU+UmICmnnamiiAsf/RJTsF+GH8rZJ6rpmvPwm17Kj53MfFHDhVoc235M7rfU29SHMiLPk/zlKZu6cKBsGYRZLFoUqLXxNubvztC9EhCo7u9ml/TD9CpokxwmEcOL6KM5mbwFD6uQAXNRKmmFeDvaAhwm61kGu9jGTJPofte0=
Received: from DM2PR0301MB0637.namprd03.prod.outlook.com (10.160.96.11) by DM2PR0301MB0640.namprd03.prod.outlook.com (10.160.96.14) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.599.9; Wed, 7 Sep 2016 00:01:25 +0000
Received: from DM2PR0301MB0637.namprd03.prod.outlook.com ([10.160.96.11]) by DM2PR0301MB0637.namprd03.prod.outlook.com ([10.160.96.11]) with mapi id 15.01.0599.016; Wed, 7 Sep 2016 00:01:23 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "id-event@ietf.org" <id-event@ietf.org>
Thread-Topic: [Id-event] Straw man text for proposed charter
Thread-Index: AQHRpvqTgBAoFeyLHUGd148PgQ6OuZ+rVXQAgAAAWICAAmZ/AIAALRQwgAAFoYCAAAIDh4AAWcqAgGsjRwCAVHjF8A==
Date: Wed, 7 Sep 2016 00:01:22 +0000
Message-ID: <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com>
In-Reply-To: <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michael.Jones@microsoft.com; 
x-originating-ip: [2001:4898:80e8:c::57c]
x-ms-office365-filtering-correlation-id: 05e359a1-5551-45ea-03d1-08d3d6b21ae7
x-microsoft-exchange-diagnostics: 1; DM2PR0301MB0640; 6:aUxiDi/NionlrWMXiNOXTCjvqunGB83C3g6OaeWhG4Se0K+arlEERmlLZvy89lJyLsp0PzMmFYbMtLcmN5guHROIYx8NOvyO3n/OKSBTeEXvB8wWK/O6Ii238biaV0O+B+lZMFlFpSRc42tHwcKbo0CtTIK6rD7jIyzDac0GHgwhV9adGsgUNzbUFVIB8GgGe9iHMHR5De0RKFSJkzhZSKe5F1B00o3fixpXjsakTPggYBBQFTVIi7laa9+eich4GVObzTUkZjNUgzSu0ucPCWfoXI65EDOZ9OkYxvtOcGyE8phk8l4USeYZibt8LagZOsweJE9T5fF97H6ZaFdBSw==; 5:BPx0eqc0zj/t4mJo0J6cxMrAtCbi4iRE6nuyPPQLJzhZy57Phb/WN4+vC+7R1/q+sEWmTShKAAGR50ikGBNp8j8YfbHBzqQ4CX2hC31BETi+liL/kZBBAKiAkOnFF5ly6EByXNkFSkCIgtHxqMOzaQ==; 24:tFBKqce5aJyi3JTiJUffOIl36q9bwzzAd64l+wiUCfR+cviAthlfNc6dMZ4cq+JFLCsm2sy7b1H4XDrA6OjfotFDkgem9PgoF1d0nUV4y9E=; 7:69KLZ9DsnGzHc5AwPGEFFO+PV6WQAWLjkDbQbJ9lN1/InQu2Vn2J1vv/l6afPpEsFj6RiPSJ2ZB51ut3foHVCNaeMt6pv2u9m7GWZiPm0/QZnktxWkkiglnavA+WB+4tBiT0EPCRrpuD+ryY7X6SWLeZwrk0xGQ2HRjQREYcBYODFnb/dEaYn5O2yBSBHKUCuKsul65SWhPZwsIxq3bEXEGJhJEaj2Yp5GO8w/6sTsEtYi0+bDuN9x0JumKw5BFg
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB0640;
x-microsoft-antispam-prvs: <DM2PR0301MB064092E8CED6AF6D03F5E991F5F80@DM2PR0301MB0640.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278428928389397)(192374486261705)(95692535739014)(21748063052155)(146099531331640)(201166117486090);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415321)(61425038)(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(61426038)(61427038); SRVR:DM2PR0301MB0640; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0640; 
x-forefront-prvs: 0058ABBBC7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(189002)(377454003)(199003)(24454002)(87936001)(5890100001)(110136002)(106356001)(19617315012)(189998001)(2950100001)(2900100001)(122556002)(106116001)(2501003)(105586002)(19609705001)(8676002)(81156014)(81166006)(92566002)(8936002)(97736004)(16601075003)(9686002)(7906003)(54356999)(551544002)(3900700001)(19580405001)(101416001)(76176999)(586003)(86612001)(99936001)(5660300001)(50986999)(4326007)(19580395003)(2351001)(8666005)(19625215002)(7846002)(7736002)(7696003)(561944003)(16236675004)(19300405004)(99286002)(74316002)(5640700001)(5630700001)(15395725005)(5003630100001)(33656002)(10090500001)(86362001)(3280700002)(790700001)(6116002)(8990500004)(3660700001)(2906002)(15975445007)(93886004)(76576001)(68736007)(102836003)(77096005)(10400500002)(5005710100001)(10290500002)(5002640100001)(7059030)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0301MB0640; H:DM2PR0301MB0637.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/mixed; boundary="_004_DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80DM2PR0301MB0637_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Sep 2016 00:01:23.0229 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0301MB0640
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/vk_6DDOfX3MQdptl_3mwdQNi3JI>
Cc: Marius Scurtescu <mscurtescu@google.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, "Morteza Ansari \(moransar\)" <moransar@cisco.com>, William Denniss <wdenniss@google.com>, Leif Johansson <leifj@sunet.se>, "Phil Hunt \(IDM\)" <phil.hunt@oracle.com>
Subject: Re: [Id-event] Straw man text for proposed charter
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2016 00:01:30 -0000

--_004_DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80DM2PR0301MB0637_
Content-Type: multipart/alternative;
	boundary="_000_DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80DM2PR0301MB0637_"

--_000_DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80DM2PR0301MB0637_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

QW4gdXBkYXRlZCBhbmQgc2ltcGxpZmllZCBjaGFydGVyIGlzIGF0dGFjaGVkLiAgVGhpcyBkcmFm
dCBoYXMgYmVlbiByZXZpZXdlZCBieSBQaGlsIEh1bnQsIFdpbGxpYW0gRGVubmlzcywgTWFyaXVz
IFNjdXJ0ZXNjdS4NCg0KSW5wdXQgZnJvbSBBbGV4ZXkgTWVsbmlrb3YgaXMgdGhhdCB3ZSBzaG91
bGQgcHJvYmFibHkgY2hhcnRlciBhIHdvcmtpbmcgZ3JvdXAsIHJhdGhlciB0aGFuIHRyeSB0byBn
byB0aGUgQUQtc3BvbnNvcmVkIHJvdXRlLiAgVGhlcmVmb3JlLCBwbGVhc2UgcmV2aWV3IHRoaXMg
ZHJhZnQgY2hhcnRlciBhbmQgbGV0IHVzIGtub3cgaWYgeW91IHRoaW5rIGl04oCZcyByZWFkeSB0
byBnby4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIFRoYW5rcywNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAtLSBNaWtlDQoNCkZyb206IFNhcmFoIFNxdWlyZSBbbWFpbHRvOnNhcmFo
QGVuZ2FnZWlkZW50aXR5LmNvbV0NClNlbnQ6IFRodXJzZGF5LCBKdWx5IDE0LCAyMDE2IDEwOjU5
IFBNDQpUbzogUGhpbCBIdW50IChJRE0pIDxwaGlsLmh1bnRAb3JhY2xlLmNvbT4NCkNjOiBNaWtl
IEpvbmVzIDxNaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5jb20+OyBBbGFuIEthcnAgPGFsYW5oa2Fy
cEBnbWFpbC5jb20+OyBWaXZlayBCaXN3YXMgPHZpdmVrX2Jpc3dhc0B5YWhvby5jb20+OyBNb3J0
ZXphIEFuc2FyaSAobW9yYW5zYXIpIDxtb3JhbnNhckBjaXNjby5jb20+OyBpZC1ldmVudEBpZXRm
Lm9yZw0KU3ViamVjdDogUmU6IFtJZC1ldmVudF0gU3RyYXcgbWFuIHRleHQgZm9yIHByb3Bvc2Vk
IGNoYXJ0ZXINCg0KSnVzdCBzdWJtaXR0aW5nIG15IHR3byBjZW50cyBpbiB3cml0aW5nIGJlZm9y
ZSB3ZSBob3BlZnVsbHkgaGF2ZSBhIGNoYW5jZSB0byBtZWV0IGFib3V0IHRoaXMgbmV4dCB3ZWVr
Li4uDQoNCkxvb2tpbmcgYXQgdGhpcyBjaGFydGVyIGZyb20gdGhlIHBlcnNwZWN0aXZlIG9mIHRo
ZSBPSURGIEhFQVJUIHdvcmtpbmcgZ3JvdXAsIEkgdGhpbmsgaXQncyBnb2luZyBkb3duIGEgZ29v
ZCBwYXRoLiBJbiB0ZXJtcyBvZiB0aGUgZGF0YSBmb3JtYXQsIHRoaXMgaXMgbGVzcyBzdHJ1Y3R1
cmVkIHRoYW4gd2hhdCBJIHdhcyBlbnZpc2lvbmluZywgYnV0IHdlIGNvdWxkIGVhc2lseSBkbyBh
IGhlYWx0aGNhcmUtc3BlY2lmaWMgcHJvZmlsZSBvZiB3aGF0ZXZlciBkYXRhIGZvcm1hdCBjb21l
cyBvdXQgaW4gdGhlIGVuZCwgc28gaXQncyBiZXR0ZXIgdG8gYmUgdG9vIGJyb2FkIHRoYW4gdG9v
IG5hcnJvdyBhcyBmYXIgYXMgb3VyIGludGVyZXN0cyBhcmUgY29uY2VybmVkLg0KDQpUaGUgdHJh
bnNwb3J0IGxheWVyIGhvd2V2ZXIsIGhhcyBzb21lIGFkZGVkIGNvbXBsZXhpdHkuIEluIG91ciBj
b250ZXh0LCB3ZSdyZSBzaG9vdGluZyBmb3IgaW50ZXJvcGVyYWJpbGl0eSwgc28gd2UnZCBwcmVm
ZXIgc29tZXRoaW5nIGNvbnN0cmFpbmVkLiBJIGFwcHJlY2lhdGUgTWlrZSdzIGlucHV0IHRoYXQg
dGhlc2UgYXJlIGFwcGxpY2F0aW9uIGxheWVyIGRlY2lzaW9ucy4gSG93ZXZlciwgaWYgd2UncmUg
dGFsa2luZyBhYm91dCBjbG91ZCBwcm92aWRlci10by1jbG91ZCBwcm92aWRlciBjb21tdW5pY2F0
aW9uLCB0aGF0IGNlcnRhaW5seSBpcyBmYWNpbGl0YXRlZCBieSBhIHdlbGwtZGVmaW5lZCB0cmFu
c3BvcnQgbGF5ZXIuIEFnYWluLCB3ZSdyZSB3aWxsaW5nIHRvIHByb2ZpbGUgd2hhdGV2ZXIgdGhl
IGdyb3VwIGNvbWVzIHVwIHdpdGggZm9yIG91ciBvd24gZW5kcywgYnV0IEkgZG9uJ3QgcmVhbGx5
IHNlZSB0aGUgYmVuZWZpdCBvZiBoYXZpbmcgYSBsb29zZWx5IGRlZmluZWQgdHJhbnNwb3J0IGxh
eWVyIC0gaXQganVzdCBzZWVtcyBsaWtlIG1vcmUgd29yayBmb3IgYWxsIHRoZSBpbXBsZW1lbnRl
cnMgdG8gYWN0dWFsbHkgYWdyZWUgb24gZW5kcG9pbnRzIG9uIGEgY2FzZS1ieS1jYXNlIGJhc2lz
Lg0KDQpMb29raW5nIGZvcndhcmQgdG8gZGlzY3Vzc2luZyBmdXJ0aGVyIGluIEJlcmxpbiENCg0K
U2FyYWgNCg0KU2FyYWggU3F1aXJlDQpFbmdhZ2UgSWRlbnRpdHkNCmh0dHA6Ly9lbmdhZ2VpZGVu
dGl0eS5jb208aHR0cDovL2VuZ2FnZWlkZW50aXR5LmNvbS8+DQoNCk9uIFNhdCwgTWF5IDcsIDIw
MTYgYXQgNjo1MyBQTSwgUGhpbCBIdW50IChJRE0pIDxwaGlsLmh1bnRAb3JhY2xlLmNvbTxtYWls
dG86cGhpbC5odW50QG9yYWNsZS5jb20+PiB3cm90ZToNCldlIGFsc28gc2V0IHRoaW5ncyB1cCBz
byBldmVuIGEgZG9tYWluIHNwZWNpZmljIGV2ZW50IGNhbiBiZSBleHRlbmRlZC4NCg0KRWcgb24g
YSBwYXNzd29yZCByZXNldCBldmVudCwgc28gZXZlbnQgcHVibGlzaGVycyBtYXkgd2FudCB0byBh
ZGQgc2VjdXJpdHkgZG9tYWluIHNwZWNpZmljIGF0dHJpYnV0ZXMuIFRoZSBzcGVjIGxldHMgdGhl
bSBkbyB0aGF0IHdoaWxlIGF2b2lkaW5nIGludGVyb3AgaXNzdWVzLg0KDQpJIGJlbGlldmUgaW4g
dGhlIHNwZWMgd2UgaGFkIHRoZSBleGFtcGxlIG9mIGFuIGFjY291bnQgcmVzZXQgYW5kIHRoZSBw
dWJsaXNoZXIgYWRkcyByZXNldCBjb3VudCBhcyBhbiBleHRlbnNpb24uDQoNClBoaWwNCg0KT24g
TWF5IDcsIDIwMTYsIGF0IDEzOjMxLCBNaWtlIEpvbmVzIDxNaWNoYWVsLkpvbmVzQG1pY3Jvc29m
dC5jb208bWFpbHRvOk1pY2hhZWwuSm9uZXNAbWljcm9zb2Z0LmNvbT4+IHdyb3RlOg0KSW5kZWVk
LCB0aGF04oCZcyB3aHkgdGhlcmXigJlzIGEgY2xhaW1zIHJlZ2lzdHJ5IOKAkyBzbyBjb21tb24g
Y2xhaW1zIGNhbiBiZSBkZWZpbmVkIG9uY2UgYW5kIHRoZW4gcmV1c2VkLg0KDQpGcm9tOiBWaXZl
ayBCaXN3YXM8bWFpbHRvOnZpdmVrX2Jpc3dhc0B5YWhvby5jb20+DQpTZW50OiBTYXR1cmRheSwg
TWF5IDcsIDIwMTYgMToyNCBQTQ0KVG86IE1pa2UgSm9uZXM8bWFpbHRvOk1pY2hhZWwuSm9uZXNA
bWljcm9zb2Z0LmNvbT4NCkNjOiBBbGFuIEthcnA8bWFpbHRvOmFsYW5oa2FycEBnbWFpbC5jb20+
OyBNb3J0ZXphIEFuc2FyaSAobW9yYW5zYXIpPG1haWx0bzptb3JhbnNhckBjaXNjby5jb20+OyBp
ZC1ldmVudEBpZXRmLm9yZzxtYWlsdG86aWQtZXZlbnRAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTog
W0lkLWV2ZW50XSBTdHJhdyBtYW4gdGV4dCBmb3IgcHJvcG9zZWQgY2hhcnRlcg0KDQpZZXMsIEkg
YWdyZWUgdGhhdCB0aGUgY2xhaW1zIGNhbiBiZSBhcHBsaWNhdGlvbiBzcGVjaWZpYywgaG93ZXZl
ciB0aGVyZSBpcyBhIHBvc3NpYmlsaXR5IHRvIGRlZmluZSBjbGFpbXMgd2hpY2ggYXJlIGRvbWFp
biBzcGVjaWZpYy4gVGhlcmVieSBjbGFpbXMgZ2VuZXJhdGVkIGluIG9uZSBhcHBsaWNhdGlvbiBj
b3VsZCBiZSB1bmRlcnN0b29kIGJ5IGFub3RoZXIgIGFwcGxpY2F0aW9uIHdpdGhpbiB0aGUgc2Ft
ZSBkb21haW4uDQoNCldpdGggbWljcm9zZXJ2aWNlcyBiYXNlZCBhcmNoaXRlY3R1cmUgZ2V0dGlu
ZyBsb3Qgb2YgYXR0ZW50aW9uLCBpZiB0d28gZGlmZmVyZW50IG1pY3JvIHNlcnZpY2VzIGRlZmlu
aW5nIGRpZmZlcmVudCBjbGFpbXMgZm9yIHRoZSBzYW1lIGNsYWltLCBpdCBjYW4gY3JlYXRlIGNv
bmZ1c2lvbi4NCg0KTmV2ZXJ0aGVsZXNzIHRoaXMgd2VsbCBkZWZpbmVkIGNsYWltcyBmb3IgYSBw
YXJ0aWN1bGFyIGRvbWFpbiBjYW4gYmUgYW4gZXh0ZW5zaW9uIHRvIHRoZSBjb3JlIHNwZWNpZmlj
YXRpb24uDQoNCi1WaXZlayBCaXN3YXMNCiAgQ29uc3VsdGluZyBNZW1iZXIsIE9yYWNsZQ0KDQpT
ZW50IGZyb20gbXkgaVBob25lDQoNCk9uIE1heSA3LCAyMDE2LCBhdCAxOjA0IFBNLCBNaWtlIEpv
bmVzIDxNaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5jb208bWFpbHRvOk1pY2hhZWwuSm9uZXNAbWlj
cm9zb2Z0LmNvbT4+IHdyb3RlOg0KVGhhbmtzIEFsYW4sDQoNCkludGVyb3BlcmFiaWxpdHkgd2ls
bCBiZSBvbiBhIHBlci1hcHBsaWNhdGlvbiBiYXNpcywganVzdCBsaWtlIEpXVCBpbnRlcm9wZXJh
YmlsaXR5LiAgVGhlIGNsYWltcyBuZWVkZWQgaW4gYW4gaWRlbnRpdHkgZXZlbnQgYXJlIGFwcGxp
Y2F0aW9uLXNwZWNpZmljLCBqdXN0IGxpa2UgY2xhaW1zIGFyZSBmb3IgSldUcy4gIFRoaXMgaXMg
dGhlIHNhbWUgc3RhbmRhcmRzIHBvc3R1cmUgYW5kIEpXVHMgYXJlIGEgaHVnZSBzdWNjZXNzIOKA
kyBpbmNsdWRpbmcgZm9yIGludGVyb3BlcmFiaWxpdHksIGV2ZW4gaWYgSSBkbyBzYXkgc28gbXlz
ZWxmLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgQmVzdCB3aXNoZXMsDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgLS0gTWlrZQ0KDQoNCg0KDQpGcm9tOiBBbGFuIEthcnA8
bWFpbHRvOmFsYW5oa2FycEBnbWFpbC5jb20+DQpTZW50OiBTYXR1cmRheSwgTWF5IDcsIDIwMTYg
MTA6MjMgQU0NClRvOiBNaWtlIEpvbmVzPG1haWx0bzpNaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5j
b20+DQpDYzogTW9ydGV6YSBBbnNhcmkgKG1vcmFuc2FyKTxtYWlsdG86bW9yYW5zYXJAY2lzY28u
Y29tPjsgaWQtZXZlbnRAaWV0Zi5vcmc8bWFpbHRvOmlkLWV2ZW50QGlldGYub3JnPg0KU3ViamVj
dDogUmU6IFtJZC1ldmVudF0gU3RyYXcgbWFuIHRleHQgZm9yIHByb3Bvc2VkIGNoYXJ0ZXINCg0K
QXMgb25lIHdobyBwcm9wb3NlZCBkb2luZyBtb3JlLCBJIGJlbGlldmUgdGhhdCB5b3VyIHBvc2l0
aW9uIGlzIHZhbGlkLiAgTXkgb25seSBxdWVzdGlvbiBpcyB3aGV0aGVyIG9yIG5vdCB0aGF0IHdp
bGwgYmUgZW5vdWdoIGZvciBpbnRlcm9wZXJhYmlsaXR5Lg0KDQoNCi0tLS0tLS0tLS0tLS0tDQpB
bGFuIEthcnANCg0KT24gVGh1LCBNYXkgNSwgMjAxNiBhdCAxMDowMCBQTSwgTWlrZSBKb25lcyA8
TWljaGFlbC5Kb25lc0BtaWNyb3NvZnQuY29tPG1haWx0bzpNaWNoYWVsLkpvbmVzQG1pY3Jvc29m
dC5jb20+PiB3cm90ZToNClRoYW5rcyBndXlzLCBmb3Igd3JpdGluZyB0aGUgaW5pdGlhbCBjaGFy
dGVyIHRleHQuICBSZWFkaW5nIGl0IG5vdywgSSBhbSBleHRyZW1lbHkgd29ycmllZCBieSB0aGUg
c2NvcGUgY3JlZXAgZXZpZGVudCBpbiB0aGUgcHJvcG9zYWwuDQoNCkkgc3Ryb25nbHkgc3VwcG9y
dCBhIHdvcmtpbmcgZ3JvdXAgdG8gZGVmaW5lIGFuIElEIEV2ZW50cyBkYXRhIGZvcm1hdC4gIEkg
anVzdCBhcyBzdHJvbmdseSBiZWxpZXZlIHRoYXQgc3BlY2lmaWMgZXZlbnQgZGVsaXZlcnkgbWVj
aGFuaXNtcyB3aWxsIG5lY2Vzc2FyaWx5IGJlIGFwcGxpY2F0aW9uLXNwZWNpZmljIGFuZCB0aGVy
ZWZvcmUgTVVTVCBiZSBleHBsaWNpdGx5IGJlIHN0YXRlZCBhcyBiZWluZyBvdXQgb2Ygc2NvcGUg
aW4gdGhlIHdvcmtpbmcgZ3JvdXAgY2hhcnRlci4gIEF0dGVtcHRpbmcgdG8gc3BlY2lmeSBhIHBh
cnRpY3VsYXIgZXZlbnQgZGVsaXZlcnkgbWVjaGFuaXNtIHdpbGwgdGFrZSBzb21ldGhpbmcgdGhh
dCBjb3VsZCBiZSBzaW1wbGUgYW5kIHF1aWNrIHRvIGFwcHJvdmUgYW5kIGJvZyBpdCBkb3duIGlu
IG5lY2Vzc2FyaWx5IGFwcGxpY2F0aW9uLXNwZWNpZmljIGRlYmF0ZXMuDQoNClNob3VsZCBldmVu
dCBkZWxpdmVyeSBiZSByZWxpYWJsZT8gIFRoYXTigJlzIGFuIGFwcGxpY2F0aW9uLXNwZWNpZmlj
IGRlY2lzaW9uLg0KU2hvdWxkIGV2ZW50cyBiZSBpZGVtcG90ZW50PyAgVGhhdOKAmXMgYW4gYXBw
bGljYXRpb24tc3BlY2lmaWMgZGVjaXNpb24uDQpTaG91bGQgZXZlbnRzIGJlIHVuaWNhc3QsIG11
bHRpY2FzdCwgb3IgYnJvYWRjYXN0PyAgVGhhdOKAmXMgYW4gYXBwbGljYXRpb24tc3BlY2lmaWMg
ZGVjaXNpb24uDQpTaG91bGQgZXZlbnRzIGhhdmUgY2F0ZWdvcmllcyB3aXRoIGNhdGVnb3J5LXNw
ZWNpZmljIHN1YnNjcmlwdGlvbnM/ICBUaGF04oCZcyBhbiBhcHBsaWNhdGlvbi1zcGVjaWZpYyBk
ZWNpc2lvbi4NClNob3VsZCBvbmx5IG9uZSBwYXJ0eSBhdCBhIHRpbWUgYmUgYWJsZSB0byByZWdp
c3RlciBmb3IgZGVsaXZlcnkgb2YgZXZlbnRzIG9yIHNob3VsZCBtdWx0aXBsZSBwYXJ0aWVzIGJl
IGFibGUgdG8gcmVxdWVzdCBkZWxpdmVyeT8gIFRoYXTigJlzIGFuIGFwcGxpY2F0aW9uLXNwZWNp
ZmljIGRlY2lzaW9uLg0KSSBjb3VsZCBjb250aW51ZSB3aXRoIHRoaXMgbGlzdCwgYnV0IEkgdGhp
bmsgeW91IGFsbCBnZXQgdGhlIHBvaW504oCmDQoNCklmIHdlIHN0YXJ0IGRlYmF0aW5nIGFwcGxp
Y2F0aW9uLXNwZWNpZmljIGV2ZW50IGRlbGl2ZXJ5IG1lY2hhbmlzbXMsIHdl4oCZbGwgcGxlYXNl
IGFsbW9zdCBubyBvbmUsIHNpbmNlIG5lYXJseSBhbGwgYXBwbGljYXRpb25zIGhhdmUgZGlmZmVy
ZW50IGV2ZW50IGRlbGl2ZXJ5IHJlcXVpcmVtZW50cy4gIFdlIE1VU1QgZXhwbGljaXRseSBydWxl
IGFsbCBkZWxpdmVyeSBtZWNoYW5pc21zIGFzIGJlaW5nIG91dCBvZiBzY29wZS4NCg0KSWYgd2Ug
ZGVmaW5lIG9ubHkgYSBkYXRhIGZvcm1hdCwgd2UgY2FuIHF1aWNrbHkgcHJvZHVjZSBhIHZlcnkg
dXNlZnVsIHNwZWNpZmljYXRpb24uICBJZiB3ZSBkb27igJl0LCB3ZeKAmWxsIGdldCBib2dnZWQg
ZG93biBpbiB0aGUgbXVkIG9mIGRlYmF0aW5nIHdoaWNoIGFwcGxpY2F0aW9ucyB3ZeKAmXJlIGNh
dGVyaW5nIHRvIGFuZCB3aGljaCB3ZSBhcmVu4oCZdCDigJMgYW4gZXhlcmNpc2Ugb2YgcGlja2lu
ZyBmYXZvcml0ZXMgYW5kIGxpbWl0aW5nIGFwcGxpY2FiaWxpdHkgb2YgdGhlIHNwZWNpZmljYXRp
b24uICBUaGF0IHdheSBpcyBhIHNsb3csIHBhaW5mdWwgZGVzY2VudCBpbnRvIHN0YW5kYXJkcyBx
dWlja3NhbmQg4oCTIHNvbWV0aGluZyB3ZSBtdXN0IGF2b2lkLiAgSGF2aW5nIGEgc3RhbmRhcmQg
SUQgZXZlbnRzIHJlcHJlc2VudGF0aW9uIGlzIGZhciB0b28gaW1wb3J0YW50IHRvIHRpZSB0byBh
IHBhcnRpY3VsYXIgbGltaXRlZCBldmVudCBkZWxpdmVyeSBtZWNoYW5pc20uDQoNCiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBTaW5jZXJl
bHksDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgLS0gTWlrZQ0KDQpGcm9tOiBJZC1ldmVudCBbbWFpbHRvOmlkLWV2ZW50LWJvdW5jZXNA
aWV0Zi5vcmc8bWFpbHRvOmlkLWV2ZW50LWJvdW5jZXNAaWV0Zi5vcmc+XSBPbiBCZWhhbGYgT2Yg
QWxhbiBLYXJwDQpTZW50OiBUaHVyc2RheSwgTWF5IDUsIDIwMTYgOTo0MyBQTQ0KVG86IE1vcnRl
emEgQW5zYXJpIChtb3JhbnNhcikgPG1vcmFuc2FyQGNpc2NvLmNvbTxtYWlsdG86bW9yYW5zYXJA
Y2lzY28uY29tPj4NCkNjOiBpZC1ldmVudEBpZXRmLm9yZzxtYWlsdG86aWQtZXZlbnRAaWV0Zi5v
cmc+DQpTdWJqZWN0OiBSZTogW0lkLWV2ZW50XSBTdHJhdyBtYW4gdGV4dCBmb3IgcHJvcG9zZWQg
Y2hhcnRlcg0KDQpJIGRvbid0IHNlZSBhbnl0aGluZyBhYm91dCBhY2Nlc3MgY29udHJvbCBmb3Ig
cHVibGlzaGluZyBldmVudHMgYW5kIHN1YnNjcmliaW5nIHRvIHRoZW0uICBJIGFsc28gdGhpbmsg
dGhlIHNwZWMgc2hvdWxkIGFsbG93IGZpbHRlcnMgb24gc3Vic2NyaXB0aW9ucy4NCg0KDQotLS0t
LS0tLS0tLS0tLQ0KQWxhbiBLYXJwDQoNCk9uIFRodSwgTWF5IDUsIDIwMTYgYXQgMTE6MTggQU0s
IE1vcnRlemEgQW5zYXJpIChtb3JhbnNhcikgPG1vcmFuc2FyQGNpc2NvLmNvbTxtYWlsdG86bW9y
YW5zYXJAY2lzY28uY29tPj4gd3JvdGU6DQpIaSBmb2xrcywNCg0KQXQgSUlXIGEgZmV3IG9mIHVz
IChQaGlsLCBXaWxsaWFtLCBBZGFtLCBhbmQgSSkgaHVkZGxlZCBmb3IgYSBiaXQgYW5kIHB1dCB0
b2dldGhlciB0aGUgYXR0YWNoZWQgYXMgYSBzdHJhdyBtYW4gY2hhcnRlciBwcm9wb3NhbCB0byBz
dGFydCB0aGUgZGlzY3Vzc2lvbi4gUGxlYXNlIHNlbmQgeW91ciBjb21tZW50cyBhbmQgc3VnZ2Vz
dGlvbnMgZm9yIGFueSBjaGFuZ2VzIG9yIHByb3Bvc2UgYSBuZXcgb25lIGlmIHlvdSB0aGluayBp
dHMgbmVjZXNzYXJ5Lg0KDQoNCkNoZWVycywNCk1vcnRlemENCg0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCklkLWV2ZW50IG1haWxpbmcgbGlzdA0KSWQt
ZXZlbnRAaWV0Zi5vcmc8bWFpbHRvOklkLWV2ZW50QGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZC1ldmVudA0KDQoNCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQpJZC1ldmVudCBtYWlsaW5nIGxpc3QNCklkLWV2
ZW50QGlldGYub3JnPG1haWx0bzpJZC1ldmVudEBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vaWQtZXZlbnQNCl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQpJZC1ldmVudCBtYWlsaW5nIGxpc3QNCklkLWV2ZW50QGll
dGYub3JnPG1haWx0bzpJZC1ldmVudEBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vaWQtZXZlbnQNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCklkLWV2ZW50IG1haWxpbmcgbGlzdA0KSWQtZXZlbnRAaWV0Zi5v
cmc8bWFpbHRvOklkLWV2ZW50QGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9pZC1ldmVudA0KDQo=

--_000_DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80DM2PR0301MB0637_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1z
b25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCglt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnNwYW4uaG9lbnpiDQoJe21z
by1zdHlsZS1uYW1lOmhvZW56Yjt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlw
ZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCglj
b2xvcjojMDAyMDYwO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1v
bmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0
aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4w
aW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxl
PjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIg
c3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48
eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQi
IGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+
DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNs
YXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiMwMDIwNjAiPkFuIHVwZGF0ZWQgYW5kIHNpbXBsaWZpZWQgY2hhcnRlciBpcyBhdHRh
Y2hlZC4mbmJzcDsgVGhpcyBkcmFmdCBoYXMgYmVlbiByZXZpZXdlZCBieSBQaGlsIEh1bnQsIFdp
bGxpYW0gRGVubmlzcywgTWFyaXVzIFNjdXJ0ZXNjdS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzAwMjA2MCI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMwMDIwNjAiPklucHV0IGZyb20gQWxleGV5IE1lbG5pa292IGlzIHRoYXQgd2Ug
c2hvdWxkIHByb2JhYmx5IGNoYXJ0ZXIgYSB3b3JraW5nIGdyb3VwLCByYXRoZXIgdGhhbiB0cnkg
dG8gZ28gdGhlIEFELXNwb25zb3JlZCByb3V0ZS4mbmJzcDsgVGhlcmVmb3JlLCBwbGVhc2UgcmV2
aWV3IHRoaXMgZHJhZnQNCiBjaGFydGVyIGFuZCBsZXQgdXMga25vdyBpZiB5b3UgdGhpbmsgaXTi
gJlzIHJlYWR5IHRvIGdvLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMDAyMDYwIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzAwMjA2
MCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFRoYW5rcyw8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6IzAwMjA2MCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IC0tIE1p
a2U8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YSBuYW1lPSJf
TWFpbEVuZENvbXBvc2UiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMDAyMDYwIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L2E+PC9wPg0KPHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbEVu
ZENvbXBvc2UiPjwvc3Bhbj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
ZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IFNhcmFoIFNxdWlyZSBbbWFpbHRv
OnNhcmFoQGVuZ2FnZWlkZW50aXR5LmNvbV0NCjxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwg
SnVseSAxNCwgMjAxNiAxMDo1OSBQTTxicj4NCjxiPlRvOjwvYj4gUGhpbCBIdW50IChJRE0pICZs
dDtwaGlsLmh1bnRAb3JhY2xlLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IE1pa2UgSm9uZXMgJmx0
O01pY2hhZWwuSm9uZXNAbWljcm9zb2Z0LmNvbSZndDs7IEFsYW4gS2FycCAmbHQ7YWxhbmhrYXJw
QGdtYWlsLmNvbSZndDs7IFZpdmVrIEJpc3dhcyAmbHQ7dml2ZWtfYmlzd2FzQHlhaG9vLmNvbSZn
dDs7IE1vcnRlemEgQW5zYXJpIChtb3JhbnNhcikgJmx0O21vcmFuc2FyQGNpc2NvLmNvbSZndDs7
IGlkLWV2ZW50QGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbSWQtZXZlbnRdIFN0
cmF3IG1hbiB0ZXh0IGZvciBwcm9wb3NlZCBjaGFydGVyPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkp1c3Qgc3VibWl0dGluZyBteSB0d28gY2VudHMgaW4gd3Jp
dGluZyBiZWZvcmUgd2UgaG9wZWZ1bGx5IGhhdmUgYSBjaGFuY2UgdG8gbWVldCBhYm91dCB0aGlz
IG5leHQgd2Vlay4uLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPkxvb2tpbmcgYXQgdGhpcyBjaGFydGVyIGZyb20gdGhlIHBlcnNwZWN0aXZlIG9mIHRoZSBP
SURGIEhFQVJUIHdvcmtpbmcgZ3JvdXAsIEkgdGhpbmsgaXQncyBnb2luZyBkb3duIGEgZ29vZCBw
YXRoLiBJbiB0ZXJtcyBvZiB0aGUgZGF0YSBmb3JtYXQsIHRoaXMgaXMgbGVzcyBzdHJ1Y3R1cmVk
IHRoYW4gd2hhdCBJIHdhcyBlbnZpc2lvbmluZywgYnV0IHdlIGNvdWxkIGVhc2lseSBkbyBhIGhl
YWx0aGNhcmUtc3BlY2lmaWMNCiBwcm9maWxlIG9mIHdoYXRldmVyIGRhdGEgZm9ybWF0IGNvbWVz
IG91dCBpbiB0aGUgZW5kLCBzbyBpdCdzIGJldHRlciB0byBiZSB0b28gYnJvYWQgdGhhbiB0b28g
bmFycm93IGFzIGZhciBhcyBvdXIgaW50ZXJlc3RzIGFyZSBjb25jZXJuZWQuPG86cD48L286cD48
L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgdHJhbnNwb3J0IGxheWVyIGhv
d2V2ZXIsIGhhcyBzb21lIGFkZGVkIGNvbXBsZXhpdHkuIEluIG91ciBjb250ZXh0LCB3ZSdyZSBz
aG9vdGluZyBmb3IgaW50ZXJvcGVyYWJpbGl0eSwgc28gd2UnZCBwcmVmZXIgc29tZXRoaW5nIGNv
bnN0cmFpbmVkLiBJIGFwcHJlY2lhdGUgTWlrZSdzIGlucHV0IHRoYXQgdGhlc2UgYXJlIGFwcGxp
Y2F0aW9uIGxheWVyIGRlY2lzaW9ucy4gSG93ZXZlciwgaWYgd2UncmUgdGFsa2luZw0KIGFib3V0
IGNsb3VkIHByb3ZpZGVyLXRvLWNsb3VkIHByb3ZpZGVyIGNvbW11bmljYXRpb24sIHRoYXQgY2Vy
dGFpbmx5IGlzIGZhY2lsaXRhdGVkIGJ5IGEgd2VsbC1kZWZpbmVkIHRyYW5zcG9ydCBsYXllci4g
QWdhaW4sIHdlJ3JlIHdpbGxpbmcgdG8gcHJvZmlsZSB3aGF0ZXZlciB0aGUgZ3JvdXAgY29tZXMg
dXAgd2l0aCBmb3Igb3VyIG93biBlbmRzLCBidXQgSSBkb24ndCByZWFsbHkgc2VlIHRoZSBiZW5l
Zml0IG9mIGhhdmluZyBhIGxvb3NlbHkNCiBkZWZpbmVkIHRyYW5zcG9ydCBsYXllciAtIGl0IGp1
c3Qgc2VlbXMgbGlrZSBtb3JlIHdvcmsgZm9yIGFsbCB0aGUgaW1wbGVtZW50ZXJzIHRvIGFjdHVh
bGx5IGFncmVlIG9uIGVuZHBvaW50cyBvbiBhIGNhc2UtYnktY2FzZSBiYXNpcy48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TG9va2luZyBmb3J3
YXJkIHRvIGRpc2N1c3NpbmcgZnVydGhlciBpbiBCZXJsaW4hPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNhcmFoPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiciBjbGVhcj0iYWxs
Ij4NCjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojODg4ODg4Ij5TYXJhaCBTcXVpcmU8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iY29sb3I6Izg4ODg4OCI+RW5nYWdlIElkZW50aXR5PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImNvbG9yOiM4ODg4ODgiPjxhIGhyZWY9Imh0dHA6Ly9lbmdhZ2VpZGVudGl0eS5jb20vIiB0YXJn
ZXQ9Il9ibGFuayI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxMTU1Q0MiPmh0dHA6Ly9lbmdhZ2VpZGVu
dGl0eS5jb208L3NwYW4+PC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gU2F0LCBNYXkgNywgMjAxNiBhdCA2
OjUzIFBNLCBQaGlsIEh1bnQgKElETSkgJmx0OzxhIGhyZWY9Im1haWx0bzpwaGlsLmh1bnRAb3Jh
Y2xlLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnBoaWwuaHVudEBvcmFjbGUuY29tPC9hPiZndDsgd3Jv
dGU6PG86cD48L286cD48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdp
bi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5XZSBhbHNvIHNldCB0aGluZ3MgdXAgc28gZXZlbiBhIGRvbWFpbiBzcGVjaWZp
YyBldmVudCBjYW4gYmUgZXh0ZW5kZWQuJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkVnIG9uIGEgcGFzc3dvcmQgcmVzZXQgZXZlbnQs
IHNvIGV2ZW50IHB1Ymxpc2hlcnMgbWF5IHdhbnQgdG8gYWRkIHNlY3VyaXR5IGRvbWFpbiBzcGVj
aWZpYyBhdHRyaWJ1dGVzLiBUaGUgc3BlYyBsZXRzIHRoZW0gZG8gdGhhdCB3aGlsZSBhdm9pZGlu
ZyBpbnRlcm9wIGlzc3Vlcy4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBiZWxpZXZlIGluIHRoZSBzcGVjIHdlIGhhZCB0aGUgZXhh
bXBsZSBvZiBhbiBhY2NvdW50IHJlc2V0IGFuZCB0aGUgcHVibGlzaGVyIGFkZHMgcmVzZXQgY291
bnQgYXMgYW4gZXh0ZW5zaW9uLiZuYnNwOzxzcGFuIHN0eWxlPSJjb2xvcjojODg4ODg4Ij48YnI+
DQo8YnI+DQo8c3BhbiBjbGFzcz0iaG9lbnpiIj5QaGlsPC9zcGFuPjwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48YnI+DQpPbiBNYXkgNywgMjAxNiwgYXQgMTM6
MzEsIE1pa2UgSm9uZXMgJmx0OzxhIGhyZWY9Im1haWx0bzpNaWNoYWVsLkpvbmVzQG1pY3Jvc29m
dC5jb20iIHRhcmdldD0iX2JsYW5rIj5NaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5jb208L2E+Jmd0
OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdp
bi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+SW5kZWVkLCB0aGF04oCZcyB3aHkgdGhlcmXigJlzIGEgY2xhaW1zIHJl
Z2lzdHJ5IOKAkyBzbyBjb21tb24gY2xhaW1zIGNhbiBiZSBkZWZpbmVkIG9uY2UgYW5kIHRoZW4g
cmV1c2VkLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0Ux
RTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PGI+RnJvbToNCjwvYj48YSBocmVmPSJtYWlsdG86dml2ZWtfYmlzd2FzQHlhaG9vLmNv
bSIgdGFyZ2V0PSJfYmxhbmsiPlZpdmVrIEJpc3dhczwvYT48YnI+DQo8Yj5TZW50OiA8L2I+U2F0
dXJkYXksIE1heSA3LCAyMDE2IDE6MjQgUE08YnI+DQo8Yj5UbzogPC9iPjxhIGhyZWY9Im1haWx0
bzpNaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5jb20iIHRhcmdldD0iX2JsYW5rIj5NaWtlIEpvbmVz
PC9hPjxicj4NCjxiPkNjOiA8L2I+PGEgaHJlZj0ibWFpbHRvOmFsYW5oa2FycEBnbWFpbC5jb20i
IHRhcmdldD0iX2JsYW5rIj5BbGFuIEthcnA8L2E+OyA8YSBocmVmPSJtYWlsdG86bW9yYW5zYXJA
Y2lzY28uY29tIiB0YXJnZXQ9Il9ibGFuayI+DQpNb3J0ZXphIEFuc2FyaSAobW9yYW5zYXIpPC9h
PjsgPGEgaHJlZj0ibWFpbHRvOmlkLWV2ZW50QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+DQpp
ZC1ldmVudEBpZXRmLm9yZzwvYT48YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UmU6IFtJZC1ldmVudF0g
U3RyYXcgbWFuIHRleHQgZm9yIHByb3Bvc2VkIGNoYXJ0ZXI8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5ZZXMsIEkgYWdyZWUgdGhhdCB0aGUg
Y2xhaW1zIGNhbiBiZSBhcHBsaWNhdGlvbiBzcGVjaWZpYywgaG93ZXZlciB0aGVyZSBpcyBhIHBv
c3NpYmlsaXR5IHRvIGRlZmluZSBjbGFpbXMgd2hpY2ggYXJlIGRvbWFpbiBzcGVjaWZpYy4gVGhl
cmVieSBjbGFpbXMgZ2VuZXJhdGVkIGluIG9uZSBhcHBsaWNhdGlvbiBjb3VsZCBiZSB1bmRlcnN0
b29kIGJ5IGFub3RoZXIgJm5ic3A7YXBwbGljYXRpb24gd2l0aGluIHRoZSBzYW1lDQogZG9tYWlu
LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5X
aXRoIG1pY3Jvc2VydmljZXMgYmFzZWQgYXJjaGl0ZWN0dXJlIGdldHRpbmcgbG90IG9mIGF0dGVu
dGlvbiwgaWYgdHdvIGRpZmZlcmVudCBtaWNybyBzZXJ2aWNlcyBkZWZpbmluZyBkaWZmZXJlbnQg
Y2xhaW1zIGZvciB0aGUgc2FtZSBjbGFpbSwgaXQgY2FuIGNyZWF0ZSBjb25mdXNpb24uPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk5ldmVydGhl
bGVzcyB0aGlzIHdlbGwgZGVmaW5lZCBjbGFpbXMgZm9yIGEgcGFydGljdWxhciBkb21haW4gY2Fu
IGJlIGFuIGV4dGVuc2lvbiB0byB0aGUgY29yZSBzcGVjaWZpY2F0aW9uLjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tVml2ZWsgQmlzd2FzPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsg
Q29uc3VsdGluZyBNZW1iZXIsIE9yYWNsZTxicj4NCjxicj4NClNlbnQgZnJvbSBteSBpUGhvbmU8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PGJyPg0KT24gTWF5IDcsIDIwMTYsIGF0IDE6MDQgUE0s
IE1pa2UgSm9uZXMgJmx0OzxhIGhyZWY9Im1haWx0bzpNaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5j
b20iIHRhcmdldD0iX2JsYW5rIj5NaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5jb208L2E+Jmd0OyB3
cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10
b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+VGhhbmtzIEFsYW4sPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3Bh
biBzdHlsZT0iY29sb3I6IzAwMjA2MCI+SW50ZXJvcGVyYWJpbGl0eSB3aWxsIGJlIG9uIGEgcGVy
LWFwcGxpY2F0aW9uIGJhc2lzLCBqdXN0IGxpa2UgSldUIGludGVyb3BlcmFiaWxpdHkuJm5ic3A7
IFRoZSBjbGFpbXMgbmVlZGVkIGluIGFuIGlkZW50aXR5IGV2ZW50IGFyZSBhcHBsaWNhdGlvbi1z
cGVjaWZpYywNCiBqdXN0IGxpa2UgY2xhaW1zIGFyZSBmb3IgSldUcy4mbmJzcDsgVGhpcyBpcyB0
aGUgc2FtZSBzdGFuZGFyZHMgcG9zdHVyZSBhbmQgSldUcyBhcmUgYSBodWdlIHN1Y2Nlc3Mg4oCT
IGluY2x1ZGluZyBmb3IgaW50ZXJvcGVyYWJpbGl0eSwgZXZlbiBpZiBJIGRvIHNheSBzbyBteXNl
bGYuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBz
dHlsZT0iY29sb3I6IzAwMjA2MCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iY29sb3I6IzAwMjA2MCI+Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEJlc3Qgd2lzaGVz
LDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5
bGU9ImNvbG9yOiMwMDIwNjAiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyAtLSBNaWtlPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNw
OzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAx
LjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PGI+RnJvbToNCjwvYj48YSBocmVmPSJtYWlsdG86YWxhbmhrYXJwQGdtYWlsLmNvbSIgdGFyZ2V0
PSJfYmxhbmsiPkFsYW4gS2FycDwvYT48YnI+DQo8Yj5TZW50OiA8L2I+U2F0dXJkYXksIE1heSA3
LCAyMDE2IDEwOjIzIEFNPGJyPg0KPGI+VG86IDwvYj48YSBocmVmPSJtYWlsdG86TWljaGFlbC5K
b25lc0BtaWNyb3NvZnQuY29tIiB0YXJnZXQ9Il9ibGFuayI+TWlrZSBKb25lczwvYT48YnI+DQo8
Yj5DYzogPC9iPjxhIGhyZWY9Im1haWx0bzptb3JhbnNhckBjaXNjby5jb20iIHRhcmdldD0iX2Js
YW5rIj5Nb3J0ZXphIEFuc2FyaSAobW9yYW5zYXIpPC9hPjsNCjxhIGhyZWY9Im1haWx0bzppZC1l
dmVudEBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmlkLWV2ZW50QGlldGYub3JnPC9hPjxicj4N
CjxiPlN1YmplY3Q6IDwvYj5SZTogW0lkLWV2ZW50XSBTdHJhdyBtYW4gdGV4dCBmb3IgcHJvcG9z
ZWQgY2hhcnRlcjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS41cHQiPkFzIG9uZSB3aG8gcHJvcG9z
ZWQgZG9pbmcgbW9yZSwgSSBiZWxpZXZlIHRoYXQgeW91ciBwb3NpdGlvbiBpcyB2YWxpZC4mbmJz
cDsgTXkgb25seSBxdWVzdGlvbiBpcyB3aGV0aGVyIG9yIG5vdCB0aGF0IHdpbGwgYmUgZW5vdWdo
IGZvciBpbnRlcm9wZXJhYmlsaXR5Ljwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiciBjbGVhcj0iYWxsIj4NCjxvOnA+PC9vOnA+PC9w
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+DQotLS0tLS0tLS0tLS0t
LTxicj4NCkFsYW4gS2FycDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPk9uIFRodSwgTWF5IDUsIDIwMTYgYXQgMTA6MDAgUE0sIE1pa2UgSm9uZXMgJmx0Ozxh
IGhyZWY9Im1haWx0bzpNaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5jb20iIHRhcmdldD0iX2JsYW5r
Ij5NaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwv
cD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0ND
Q0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFy
Z2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMwMDIwNjAiPlRoYW5rcyBndXlzLCBmb3Igd3JpdGluZyB0aGUg
aW5pdGlhbCBjaGFydGVyIHRleHQuJm5ic3A7IFJlYWRpbmcgaXQgbm93LCBJIGFtIGV4dHJlbWVs
eSB3b3JyaWVkIGJ5IHRoZSBzY29wZQ0KIGNyZWVwIGV2aWRlbnQgaW4gdGhlIHByb3Bvc2FsLjwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMwMDIwNjAiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMwMDIwNjAiPkkgc3Ryb25nbHkg
c3VwcG9ydCBhIHdvcmtpbmcgZ3JvdXAgdG8gZGVmaW5lIGFuIElEIEV2ZW50cyBkYXRhIGZvcm1h
dC4mbmJzcDsgSSBqdXN0IGFzIHN0cm9uZ2x5IGJlbGlldmUNCiB0aGF0IHNwZWNpZmljIGV2ZW50
IGRlbGl2ZXJ5IG1lY2hhbmlzbXMgd2lsbCBuZWNlc3NhcmlseSBiZSBhcHBsaWNhdGlvbi1zcGVj
aWZpYyBhbmQgdGhlcmVmb3JlIE1VU1QgYmUgZXhwbGljaXRseSBiZSBzdGF0ZWQgYXMgYmVpbmcg
b3V0IG9mIHNjb3BlIGluIHRoZSB3b3JraW5nIGdyb3VwIGNoYXJ0ZXIuJm5ic3A7IEF0dGVtcHRp
bmcgdG8gc3BlY2lmeSBhIHBhcnRpY3VsYXIgZXZlbnQgZGVsaXZlcnkgbWVjaGFuaXNtIHdpbGwg
dGFrZSBzb21ldGhpbmcNCiB0aGF0IGNvdWxkIGJlIHNpbXBsZSBhbmQgcXVpY2sgdG8gYXBwcm92
ZSBhbmQgYm9nIGl0IGRvd24gaW4gbmVjZXNzYXJpbHkgYXBwbGljYXRpb24tc3BlY2lmaWMgZGVi
YXRlcy48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjojMDAyMDYwIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMDAyMDYwIj5TaG91
bGQgZXZlbnQgZGVsaXZlcnkgYmUgcmVsaWFibGU/Jm5ic3A7IFRoYXTigJlzIGFuIGFwcGxpY2F0
aW9uLXNwZWNpZmljIGRlY2lzaW9uLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMwMDIwNjAiPlNob3VsZCBldmVudHMg
YmUgaWRlbXBvdGVudD8mbmJzcDsgVGhhdOKAmXMgYW4gYXBwbGljYXRpb24tc3BlY2lmaWMgZGVj
aXNpb24uPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzAwMjA2MCI+U2hvdWxkIGV2ZW50cyBiZSB1bmljYXN0LCBtdWx0
aWNhc3QsIG9yIGJyb2FkY2FzdD8mbmJzcDsgVGhhdOKAmXMgYW4gYXBwbGljYXRpb24tc3BlY2lm
aWMgZGVjaXNpb24uPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzAwMjA2MCI+U2hvdWxkIGV2ZW50cyBoYXZlIGNhdGVn
b3JpZXMgd2l0aCBjYXRlZ29yeS1zcGVjaWZpYyBzdWJzY3JpcHRpb25zPyZuYnNwOyBUaGF04oCZ
cyBhbiBhcHBsaWNhdGlvbi1zcGVjaWZpYw0KIGRlY2lzaW9uLjwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMwMDIwNjAi
PlNob3VsZCBvbmx5IG9uZSBwYXJ0eSBhdCBhIHRpbWUgYmUgYWJsZSB0byByZWdpc3RlciBmb3Ig
ZGVsaXZlcnkgb2YgZXZlbnRzIG9yIHNob3VsZCBtdWx0aXBsZSBwYXJ0aWVzDQogYmUgYWJsZSB0
byByZXF1ZXN0IGRlbGl2ZXJ5PyZuYnNwOyBUaGF04oCZcyBhbiBhcHBsaWNhdGlvbi1zcGVjaWZp
YyBkZWNpc2lvbi48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMDAyMDYwIj5JIGNvdWxkIGNvbnRpbnVlIHdpdGggdGhp
cyBsaXN0LCBidXQgSSB0aGluayB5b3UgYWxsIGdldCB0aGUgcG9pbnTigKY8L3NwYW4+PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MDAyMDYwIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMDAyMDYwIj5JZiB3ZSBzdGFydCBkZWJhdGluZyBh
cHBsaWNhdGlvbi1zcGVjaWZpYyBldmVudCBkZWxpdmVyeSBtZWNoYW5pc21zLCB3ZeKAmWxsIHBs
ZWFzZSBhbG1vc3Qgbm8gb25lLCBzaW5jZQ0KIG5lYXJseSBhbGwgYXBwbGljYXRpb25zIGhhdmUg
ZGlmZmVyZW50IGV2ZW50IGRlbGl2ZXJ5IHJlcXVpcmVtZW50cy4mbmJzcDsgV2UgTVVTVCBleHBs
aWNpdGx5IHJ1bGUgYWxsIGRlbGl2ZXJ5IG1lY2hhbmlzbXMgYXMgYmVpbmcgb3V0IG9mIHNjb3Bl
Ljwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOiMwMDIwNjAiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMwMDIwNjAiPklmIHdlIGRl
ZmluZSBvbmx5IGEgZGF0YSBmb3JtYXQsIHdlIGNhbiBxdWlja2x5IHByb2R1Y2UgYSB2ZXJ5IHVz
ZWZ1bCBzcGVjaWZpY2F0aW9uLiZuYnNwOyBJZiB3ZSBkb27igJl0LA0KIHdl4oCZbGwgZ2V0IGJv
Z2dlZCBkb3duIGluIHRoZSBtdWQgb2YgZGViYXRpbmcgd2hpY2ggYXBwbGljYXRpb25zIHdl4oCZ
cmUgY2F0ZXJpbmcgdG8gYW5kIHdoaWNoIHdlIGFyZW7igJl0IOKAkyBhbiBleGVyY2lzZSBvZiBw
aWNraW5nIGZhdm9yaXRlcyBhbmQgbGltaXRpbmcgYXBwbGljYWJpbGl0eSBvZiB0aGUgc3BlY2lm
aWNhdGlvbi4mbmJzcDsgVGhhdCB3YXkgaXMgYSBzbG93LCBwYWluZnVsIGRlc2NlbnQgaW50byBz
dGFuZGFyZHMgcXVpY2tzYW5kIOKAkyBzb21ldGhpbmcNCiB3ZSBtdXN0IGF2b2lkLiZuYnNwOyBI
YXZpbmcgYSBzdGFuZGFyZCBJRCBldmVudHMgcmVwcmVzZW50YXRpb24gaXMgZmFyIHRvbyBpbXBv
cnRhbnQgdG8gdGllIHRvIGEgcGFydGljdWxhciBsaW1pdGVkIGV2ZW50IGRlbGl2ZXJ5IG1lY2hh
bmlzbS48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjojMDAyMDYwIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMDAyMDYwIj4mbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgU2lu
Y2VyZWx5LDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMwMDIwNjAiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAtLSBNaWtlPC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48YSBuYW1lPSJtXzMwMjIzNjcwNTkzMzY4OTM1NjVf
bV8xNDYxMDI0MjU0MjIyOTExIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzAwMjA2MCI+Jm5ic3A7
PC9zcGFuPjwvYT48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PGI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4gSWQtZXZlbnQg
W21haWx0bzo8YSBocmVmPSJtYWlsdG86aWQtZXZlbnQtYm91bmNlc0BpZXRmLm9yZyIgdGFyZ2V0
PSJfYmxhbmsiPmlkLWV2ZW50LWJvdW5jZXNAaWV0Zi5vcmc8L2E+XQ0KPGI+T24gQmVoYWxmIE9m
IDwvYj5BbGFuIEthcnA8YnI+DQo8Yj5TZW50OjwvYj4gVGh1cnNkYXksIE1heSA1LCAyMDE2IDk6
NDMgUE08YnI+DQo8Yj5Ubzo8L2I+IE1vcnRlemEgQW5zYXJpIChtb3JhbnNhcikgJmx0OzxhIGhy
ZWY9Im1haWx0bzptb3JhbnNhckBjaXNjby5jb20iIHRhcmdldD0iX2JsYW5rIj5tb3JhbnNhckBj
aXNjby5jb208L2E+Jmd0Ozxicj4NCjxiPkNjOjwvYj4gPGEgaHJlZj0ibWFpbHRvOmlkLWV2ZW50
QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+aWQtZXZlbnRAaWV0Zi5vcmc8L2E+PGJyPg0KPGI+
U3ViamVjdDo8L2I+IFJlOiBbSWQtZXZlbnRdIFN0cmF3IG1hbiB0ZXh0IGZvciBwcm9wb3NlZCBj
aGFydGVyPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkkgZG9uJ3Qg
c2VlIGFueXRoaW5nIGFib3V0IGFjY2VzcyBjb250cm9sIGZvciBwdWJsaXNoaW5nIGV2ZW50cyBh
bmQgc3Vic2NyaWJpbmcgdG8gdGhlbS4mbmJzcDsgSSBhbHNvIHRoaW5rIHRoZSBzcGVjIHNob3Vs
ZCBhbGxvdyBmaWx0ZXJzIG9uIHN1YnNjcmlwdGlvbnMuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxiciBjbGVhcj0iYWxsIj4NCjxvOnA+PC9v
OnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxicj4NCi0tLS0t
LS0tLS0tLS0tPGJyPg0KQWxhbiBLYXJwPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPk9uIFRodSwgTWF5IDUsIDIwMTYgYXQgMTE6MTggQU0sIE1vcnRl
emEgQW5zYXJpIChtb3JhbnNhcikgJmx0OzxhIGhyZWY9Im1haWx0bzptb3JhbnNhckBjaXNjby5j
b20iIHRhcmdldD0iX2JsYW5rIj5tb3JhbnNhckBjaXNjby5jb208L2E+Jmd0OyB3cm90ZTo8bzpw
PjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpz
b2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6
NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGluO21hcmdpbi1ib3R0b206NS4w
cHQiPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjpibGFjayI+SGkgZm9sa3MsPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2si
PiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5BdCBJSVcgYSBmZXcgb2Yg
dXMgKFBoaWwsIFdpbGxpYW0sIEFkYW0sIGFuZCBJKSBodWRkbGVkIGZvciBhIGJpdCBhbmQgcHV0
IHRvZ2V0aGVyIHRoZSBhdHRhY2hlZCBhcyBhDQogc3RyYXcgbWFuIGNoYXJ0ZXIgcHJvcG9zYWwg
dG8gc3RhcnQgdGhlIGRpc2N1c3Npb24uIFBsZWFzZSBzZW5kIHlvdXIgY29tbWVudHMgYW5kIHN1
Z2dlc3Rpb25zIGZvciBhbnkgY2hhbmdlcyBvciBwcm9wb3NlIGEgbmV3IG9uZSBpZiB5b3UgdGhp
bmsgaXRzIG5lY2Vzc2FyeS48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jm5ic3A7
PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOmJsYWNrIj5DaGVlcnMsPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2si
Pk1vcnRlemE8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1ib3R0b206
MTIuMHB0Ij48YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXzxicj4NCklkLWV2ZW50IG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzpJZC1l
dmVudEBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPklkLWV2ZW50QGlldGYub3JnPC9hPjxicj4N
CjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaWQtZXZlbnQi
IHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lk
LWV2ZW50PC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxi
bG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fPGJyPg0KSWQtZXZlbnQgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJl
Zj0ibWFpbHRvOklkLWV2ZW50QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+SWQtZXZlbnRAaWV0
Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9pZC1ldmVudCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vaWQtZXZlbnQ8L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvYmxvY2tx
dW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8YmxvY2txdW90ZSBzdHlsZT0i
bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xzxicj4NCklkLWV2ZW50IG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzpJZC1ldmVu
dEBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPklkLWV2ZW50QGlldGYub3JnPC9hPjxicj4NCjxh
IGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaWQtZXZlbnQiIHRh
cmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lkLWV2
ZW50PC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbTox
Mi4wcHQiPjxicj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fPGJyPg0KSWQtZXZlbnQgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOklkLWV2
ZW50QGlldGYub3JnIj5JZC1ldmVudEBpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lkLWV2ZW50IiB0YXJnZXQ9Il9ibGFuayI+
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZC1ldmVudDwvYT48bzpwPjwv
bzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80DM2PR0301MB0637_--

--_004_DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80DM2PR0301MB0637_
Content-Type: text/plain; name="id-event_charter_v2.txt"
Content-Description: id-event_charter_v2.txt
Content-Disposition: attachment; filename="id-event_charter_v2.txt";
	size=2164; creation-date="Tue, 06 Sep 2016 23:57:27 GMT";
	modification-date="Tue, 06 Sep 2016 23:57:27 GMT"
Content-Transfer-Encoding: base64

Q2hhcnRlcgoKIEN1cnJlbnQgU3RhdHVzOiBUQkQKCiBDaGFpcnM6CiAgICAgVEJECgogQXBwbGlj
YXRpb25zIGFuZCBSZWFsLVRpbWUgQXJlYSBEaXJlY3RvcnM6CiAgICAgVEJECgogQXBwbGljYXRp
b25zIGFuZCBSZWFsLVRpbWUgQXJlYSBBZHZpc29yOgogICAgIFRCRAoKIE1haWxpbmcgTGlzdHM6
CiAgICAgR2VuZXJhbCBEaXNjdXNzaW9uOiBpZC1ldmVudEBpZXRmLm9yZwogICAgIFRvIFN1YnNj
cmliZTogICAgICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZC1ldmVu
dAogICAgIEFyY2hpdmU6ICAgICAgICAgICAgaHR0cHM6Ly9tYWlsYXJjaGl2ZS5pZXRmLm9yZy9h
cmNoL2Jyb3dzZS9pZC1ldmVudC8KCkRlc2NyaXB0aW9uIG9mIFdvcmtpbmcgR3JvdXA6CgpNYW55
IGlkZW50aXR5IHJlbGF0ZWQgcHJvdG9jb2xzIHJlcXVpcmUgYSBtZWNoYW5pc20gdG8gY29udmV5
IG1lc3NhZ2VzIGJldHdlZW4Kc3lzdGVtcyBpbiBvcmRlciB0byBwcmV2ZW50IG9yIG1pdGlnYXRl
IHNlY3VyaXR5IHJpc2tzLCBvciB0byBwcm92aWRlCm91dC1vZi1iYW5kIGluZm9ybWF0aW9uIGFz
IG5lY2Vzc2FyeS4gRm9yIGV4YW1wbGUsIGFuIE9BdXRoIGF1dGhvcml6YXRpb24Kc2VydmVyLCBo
YXZpbmcgcmVjZWl2ZWQgYSB0b2tlbiByZXZvY2F0aW9uIHJlcXVlc3QgKFJGQzcwMDkpIG1heSBu
ZWVkIHRvCmluZm9ybSBhZmZlY3RlZCByZXNvdXJjZSBzZXJ2ZXJzOyBhIGNsb3VkIHByb3ZpZGVy
IG1heSB3aXNoIHRvIGluZm9ybSBhbm90aGVyCmNsb3VkIHByb3ZpZGVyIG9mIHN1c3BlY3RlZCBm
cmF1ZHVsZW50IHVzZSBvZiBpZGVudGl0eSBpbmZvcm1hdGlvbjsgYW4KaWRlbnRpdHkgcHJvdmlk
ZXIgbWF5IHdpc2ggdG8gc2lnbmFsIGEgc2Vzc2lvbiBsb2dvdXQgdG8gYSByZWx5aW5nIHBhcnR5
LgoKSXQgaXMgZXhwZWN0ZWQgdGhhdCBzZXZlcmFsIGlkZW50aXR5IGFuZCBzZWN1cml0eSB3b3Jr
aW5nIGdyb3VwcyBhbmQKb3JnYW5pemF0aW9ucyB3aWxsIHVzZSBJZGVudGl0eSBFdmVudCBUb2tl
bnMgdG8gZGVzY3JpYmUgYXJlYS1zcGVjaWZpYwpldmVudHMgc3VjaCBhczogU0NJTSBQcm92aXNp
b25pbmcgRXZlbnRzLCBPcGVuSUQgUklTQyBFdmVudHMsIGFuZApPcGVuSUQgQ29ubmVjdCBCYWNr
Y2hhbm5lbCBMb2dvdXQsIGFtb25nIG90aGVycy4KClRoZSBTZWN1cml0eSBFdmVudCB3b3JraW5n
IGdyb3VwIHdpbGwgcHJvZHVjZSBhIHN0YW5kYXJkcy10cmFjayBFdmVudCBUb2tlbgpzcGVjaWZp
Y2F0aW9uIHRoYXQgaW5jbHVkZXM6CiAtIEEgSldUIGV4dGVuc2lvbiBmb3IgZXhwcmVzc2luZyBz
ZWN1cml0eSBldmVudHMKIC0gQSBzeW50YXggdGhhdCBlbmFibGVzIGV2ZW50LXNwZWNpZmljIGRh
dGEgdG8gYmUgY29udmV5ZWQKVGhpcyBFdmVudCBUb2tlbiBzcGVjaWZpY2F0aW9uIHdpbGwgYmUg
ZXZlbnQgdHJhbnNwb3J0IGluZGVwZW5kZW50LgoKVGhlIHdvcmtpbmcgZ3JvdXAgd2lsbCBhbHNv
IGRldmVsb3AgYSBzaW1wbGUgc3RhbmRhcmRzLXRyYWNrIEV2ZW50IERlbGl2ZXJ5CnNwZWNpZmlj
YXRpb24gdGhhdCBpbmNsdWRlczoKIC0gQSBtZXRob2QgZm9yIGRlbGl2ZXJpbmcgZXZlbnRzIHVz
aW5nIEhUVFAgUE9TVCAocHVzaCkKIC0gTWV0YWRhdGEgZm9yIGRlc2NyaWJpbmcgZXZlbnQgZmVl
ZHMKIC0gTWV0aG9kcyBmb3Igc3Vic2NyaWJpbmcgdG8gYW5kIG1hbmFnaW5nIGV2ZW50IGZlZWRz
CiAtIE1ldGhvZHMgZm9yIHZhbGlkYXRpbmcgZXZlbnQgZmVlZCBzdWJzY3JpcHRpb25zCgpHb2Fs
cyBhbmQgTWlsZXN0b25lczoKICBPY3RvYmVyIDIwMTYgLSBJbml0aWFsIGFkb3B0aW9uIG9mIGV2
ZW50IHRva2VuIGFuZCBldmVudCBkZWxpdmVyeSBkcmFmdHMKIEZlYnJ1YXJ5IDIwMTcgLSBXRyBs
YXN0IGNhbGwgb2YgZXZlbnQgdG9rZW4gZHJhZnQKICAgIEFwcmlsIDIwMTcgLSBFdmVudCB0b2tl
biBkcmFmdCB0byBJRVNHIGFzIGEgcHJvcG9zZWQgc3RhbmRhcmQKICAgICBKdWx5IDIwMTcgLSBX
RyBsYXN0IGNhbGwgb2YgZXZlbnQgZGVsaXZlcnkgZHJhZnQKU2VwdGVtYmVyIDIwMTcgLSBFdmVu
dCBkZWxpdmVyeSBkcmFmdCB0byBJRVNHIGFzIGEgcHJvcG9zZWQgc3RhbmRhcmQKIE5vdmVtYmVy
IDIwMTcgLSBXb3JrIGNvbXBsZXRlZDsgZGlzY3VzcyByZWNoYXJ0ZXJpbmcgaWYgbmVlZGVkCg==

--_004_DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80DM2PR0301MB0637_--


From nobody Tue Sep  6 17:04:29 2016
Return-Path: <wdenniss@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54A3A12B388 for <id-event@ietfa.amsl.com>; Tue,  6 Sep 2016 17:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level: 
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kw-NylZk3lcj for <id-event@ietfa.amsl.com>; Tue,  6 Sep 2016 17:04:23 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A152912B01F for <id-event@ietf.org>; Tue,  6 Sep 2016 17:04:23 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id g192so80476725ywh.1 for <id-event@ietf.org>; Tue, 06 Sep 2016 17:04:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=EaQ+iKe52FTdui2JNaQG0ytEqi/MAvl9swleDtwp95c=; b=G8Ox2oiA+ndQ69LO/IUYJGs900B6uHBGOCdL5lDuu+ZC2eYacFLxzfLioAHlZHFbyT yCmBifH6/ZmOvXLatOCa1odVzenaN5MAA3Y2qTKT/IXzdbaxuDX5o1uBczsz763FjZj7 zXDSFqVxDpcdSF0jbJyRmVHcwNm3FhgGoMczsOdiAfgYj3+NWb5RtzebEL5rXdbMRj+l /7HOANQiOj31jhEcw24Q54HnXeR6XMW2zjFTUZN6BMIWz+wdDQqGjwSkwJniMFTLSIQV d8PIhEVHNRtTF6LTdxs7dnMZht3+O+TGbbgGevFFlD35CDlDPnYg91ob4hV5RJaVKr1q BKjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=EaQ+iKe52FTdui2JNaQG0ytEqi/MAvl9swleDtwp95c=; b=NicMBpqiAzqlDHR8uwgK1+o5g+Oas6sDcgQgEpEc/Earub0lUiaTr3s54wME5pqIze QjL4amZPwcTFeMsCH1+twqgpUmq+IXGx0bsZbDFekg0fJEhOJIipWysqj6hpbW0nub96 AN/Fiy+vSyFkmLvryOXN50bKqGarj+3nd5vHzOuB6Z976Z1d38MBXnH8u2ASjLKnJXVU ik92gm2EDlwF0IKYXhUpSgK/Xr6yqLSAhBWYC9StmNHdPkNdMI6HqpwybOfYDqE0fSaQ NRqhSTRGvm6+1sQTJICbDjHFO/lzjCqvT1Xm093EYy3U2nCuBwJuhzc9G7zT6xBv4UXe AxNQ==
X-Gm-Message-State: AE9vXwNXuBCaz1LeTRsXyNxbTmQXEnH/yfEsGza8P9007kxZePoMqmbisKYv4AtHd6endLdSLJRwY40nliMFLgQn
X-Received: by 10.13.243.196 with SMTP id c187mr34666963ywf.137.1473206662642;  Tue, 06 Sep 2016 17:04:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.108.143 with HTTP; Tue, 6 Sep 2016 17:04:02 -0700 (PDT)
In-Reply-To: <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com>
From: William Denniss <wdenniss@google.com>
Date: Tue, 6 Sep 2016 17:04:02 -0700
Message-ID: <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=94eb2c0362a4cf367e053bdfa78c
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/BYu_JhK7bANCqpWegjEOhPR-Wv8>
Cc: Marius Scurtescu <mscurtescu@google.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, "Morteza Ansari \(moransar\)" <moransar@cisco.com>, "id-event@ietf.org" <id-event@ietf.org>, Leif Johansson <leifj@sunet.se>, "Phil Hunt \(IDM\)" <phil.hunt@oracle.com>
Subject: Re: [Id-event] Straw man text for proposed charter
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2016 00:04:27 -0000

--94eb2c0362a4cf367e053bdfa78c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thank you Mike for revising the charter.

I support it, and hope we can form a WG with this charter to continue our
work.

On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <Michael.Jones@microsoft.com>
wrote:

> An updated and simplified charter is attached.  This draft has been
> reviewed by Phil Hunt, William Denniss, Marius Scurtescu.
>
>
>
> Input from Alexey Melnikov is that we should probably charter a working
> group, rather than try to go the AD-sponsored route.  Therefore, please
> review this draft charter and let us know if you think it=E2=80=99s ready=
 to go.
>
>
>
>                                                        Thanks,
>
>                                                        -- Mike
>
>
>
> *From:* Sarah Squire [mailto:sarah@engageidentity.com]
> *Sent:* Thursday, July 14, 2016 10:59 PM
> *To:* Phil Hunt (IDM) <phil.hunt@oracle.com>
> *Cc:* Mike Jones <Michael.Jones@microsoft.com>; Alan Karp <
> alanhkarp@gmail.com>; Vivek Biswas <vivek_biswas@yahoo.com>; Morteza
> Ansari (moransar) <moransar@cisco.com>; id-event@ietf.org
>
> *Subject:* Re: [Id-event] Straw man text for proposed charter
>
>
>
> Just submitting my two cents in writing before we hopefully have a chance
> to meet about this next week...
>
>
>
> Looking at this charter from the perspective of the OIDF HEART working
> group, I think it's going down a good path. In terms of the data format,
> this is less structured than what I was envisioning, but we could easily =
do
> a healthcare-specific profile of whatever data format comes out in the en=
d,
> so it's better to be too broad than too narrow as far as our interests ar=
e
> concerned.
>
>
>
> The transport layer however, has some added complexity. In our context,
> we're shooting for interoperability, so we'd prefer something constrained=
.
> I appreciate Mike's input that these are application layer decisions.
> However, if we're talking about cloud provider-to-cloud provider
> communication, that certainly is facilitated by a well-defined transport
> layer. Again, we're willing to profile whatever the group comes up with f=
or
> our own ends, but I don't really see the benefit of having a loosely
> defined transport layer - it just seems like more work for all the
> implementers to actually agree on endpoints on a case-by-case basis.
>
>
>
> Looking forward to discussing further in Berlin!
>
>
>
> Sarah
>
>
> Sarah Squire
>
> Engage Identity
>
> http://engageidentity.com
>
>
>
> On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com>
> wrote:
>
> We also set things up so even a domain specific event can be extended.
>
>
>
> Eg on a password reset event, so event publishers may want to add securit=
y
> domain specific attributes. The spec lets them do that while avoiding
> interop issues.
>
>
>
> I believe in the spec we had the example of an account reset and the
> publisher adds reset count as an extension.
>
> Phil
>
>
> On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com> wrote:
>
> Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 so=
 common claims can be
> defined once and then reused.
>
>
>
> *From: *Vivek Biswas <vivek_biswas@yahoo.com>
> *Sent: *Saturday, May 7, 2016 1:24 PM
> *To: *Mike Jones <Michael.Jones@microsoft.com>
> *Cc: *Alan Karp <alanhkarp@gmail.com>; Morteza Ansari (moransar)
> <moransar@cisco.com>; id-event@ietf.org
> *Subject: *Re: [Id-event] Straw man text for proposed charter
>
>
>
> Yes, I agree that the claims can be application specific, however there i=
s
> a possibility to define claims which are domain specific. Thereby claims
> generated in one application could be understood by another  application
> within the same domain.
>
>
>
> With microservices based architecture getting lot of attention, if two
> different micro services defining different claims for the same claim, it
> can create confusion.
>
>
>
> Nevertheless this well defined claims for a particular domain can be an
> extension to the core specification.
>
>
>
> -Vivek Biswas
>
>   Consulting Member, Oracle
>
> Sent from my iPhone
>
>
> On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:
>
> Thanks Alan,
>
>
>
> Interoperability will be on a per-application basis, just like JWT
> interoperability.  The claims needed in an identity event are
> application-specific, just like claims are for JWTs.  This is the same
> standards posture and JWTs are a huge success =E2=80=93 including for
> interoperability, even if I do say so myself.
>
>
>
>                                                           Best wishes,
>
>                                                           -- Mike
>
>
>
>
>
>
>
>
>
> *From: *Alan Karp <alanhkarp@gmail.com>
> *Sent: *Saturday, May 7, 2016 10:23 AM
> *To: *Mike Jones <Michael.Jones@microsoft.com>
> *Cc: *Morteza Ansari (moransar) <moransar@cisco.com>; id-event@ietf.org
> *Subject: *Re: [Id-event] Straw man text for proposed charter
>
>
>
> As one who proposed doing more, I believe that your position is valid.  M=
y
> only question is whether or not that will be enough for interoperability.
>
>
>
> --------------
> Alan Karp
>
>
>
> On Thu, May 5, 2016 at 10:00 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:
>
> Thanks guys, for writing the initial charter text.  Reading it now, I am
> extremely worried by the scope creep evident in the proposal.
>
>
>
> I strongly support a working group to define an ID Events data format.  I
> just as strongly believe that specific event delivery mechanisms will
> necessarily be application-specific and therefore MUST be explicitly be
> stated as being out of scope in the working group charter.  Attempting to
> specify a particular event delivery mechanism will take something that
> could be simple and quick to approve and bog it down in necessarily
> application-specific debates.
>
>
>
> Should event delivery be reliable?  That=E2=80=99s an application-specifi=
c
> decision.
>
> Should events be idempotent?  That=E2=80=99s an application-specific deci=
sion.
>
> Should events be unicast, multicast, or broadcast?  That=E2=80=99s an
> application-specific decision.
>
> Should events have categories with category-specific subscriptions?
> That=E2=80=99s an application-specific decision.
>
> Should only one party at a time be able to register for delivery of event=
s
> or should multiple parties be able to request delivery?  That=E2=80=99s a=
n
> application-specific decision.
>
> I could continue with this list, but I think you all get the point=E2=80=
=A6
>
>
>
> If we start debating application-specific event delivery mechanisms, we=
=E2=80=99ll
> please almost no one, since nearly all applications have different event
> delivery requirements.  We MUST explicitly rule all delivery mechanisms a=
s
> being out of scope.
>
>
>
> If we define only a data format, we can quickly produce a very useful
> specification.  If we don=E2=80=99t, we=E2=80=99ll get bogged down in the=
 mud of debating
> which applications we=E2=80=99re catering to and which we aren=E2=80=99t =
=E2=80=93 an exercise of
> picking favorites and limiting applicability of the specification.  That
> way is a slow, painful descent into standards quicksand =E2=80=93 somethi=
ng we must
> avoid.  Having a standard ID events representation is far too important t=
o
> tie to a particular limited event delivery mechanism.
>
>
>
>                                                           Sincerely,
>
>                                                           -- Mike
>
>
>
> *From:* Id-event [mailto:id-event-bounces@ietf.org] *On Behalf Of *Alan
> Karp
> *Sent:* Thursday, May 5, 2016 9:43 PM
> *To:* Morteza Ansari (moransar) <moransar@cisco.com>
> *Cc:* id-event@ietf.org
> *Subject:* Re: [Id-event] Straw man text for proposed charter
>
>
>
> I don't see anything about access control for publishing events and
> subscribing to them.  I also think the spec should allow filters on
> subscriptions.
>
>
>
> --------------
> Alan Karp
>
>
>
> On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar) <
> moransar@cisco.com> wrote:
>
> Hi folks,
>
>
>
> At IIW a few of us (Phil, William, Adam, and I) huddled for a bit and put
> together the attached as a straw man charter proposal to start the
> discussion. Please send your comments and suggestions for any changes or
> propose a new one if you think its necessary.
>
>
>
>
>
> Cheers,
>
> Morteza
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>
>

--94eb2c0362a4cf367e053bdfa78c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thank you Mike for revising the charter.=C2=A0<div><br></d=
iv><div>I support it, and hope we can form a WG with this charter to contin=
ue our work.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_=
quote">On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <span dir=3D"ltr">&lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_5165357944078144809WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">An updated and simplified charter is =
attached.=C2=A0 This draft has been reviewed by Phil Hunt, William Denniss,=
 Marius Scurtescu.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Input from Alexey Melnikov is that we=
 should probably charter a working group, rather than try to go the AD-spon=
sored route.=C2=A0 Therefore, please review this draft
 charter and let us know if you think it=E2=80=99s ready to go.<u></u><u></=
u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<wbr>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Thank=
s,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<wbr>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- Mi=
ke<u></u><u></u></span></p>
<p class=3D"MsoNormal"><a name=3D"m_5165357944078144809__MailEndCompose"><s=
pan style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;co=
lor:#002060"><u></u>=C2=A0<u></u></span></a></p>
<span></span>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Sarah Squire [mailto:<a href=
=3D"mailto:sarah@engageidentity.com" target=3D"_blank">sarah@engageidentity=
.<wbr>com</a>]
<br>
<b>Sent:</b> Thursday, July 14, 2016 10:59 PM<br>
<b>To:</b> Phil Hunt (IDM) &lt;<a href=3D"mailto:phil.hunt@oracle.com" targ=
et=3D"_blank">phil.hunt@oracle.com</a>&gt;<br>
<b>Cc:</b> Mike Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com" ta=
rget=3D"_blank">Michael.Jones@microsoft.com</a>&gt;; Alan Karp &lt;<a href=
=3D"mailto:alanhkarp@gmail.com" target=3D"_blank">alanhkarp@gmail.com</a>&g=
t;; Vivek Biswas &lt;<a href=3D"mailto:vivek_biswas@yahoo.com" target=3D"_b=
lank">vivek_biswas@yahoo.com</a>&gt;; Morteza Ansari (moransar) &lt;<a href=
=3D"mailto:moransar@cisco.com" target=3D"_blank">moransar@cisco.com</a>&gt;=
; <a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-event@ietf.org<=
/a></span></p><div><div class=3D"h5"><br>
<b>Subject:</b> Re: [Id-event] Straw man text for proposed charter<u></u><u=
></u></div></div><p></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">Just submitting my two cents in writing before we ho=
pefully have a chance to meet about this next week...<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">Looking at this charter from the perspective of the =
OIDF HEART working group, I think it&#39;s going down a good path. In terms=
 of the data format, this is less structured than what I was envisioning, b=
ut we could easily do a healthcare-specific
 profile of whatever data format comes out in the end, so it&#39;s better t=
o be too broad than too narrow as far as our interests are concerned.<u></u=
><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The transport layer however, has some added complexi=
ty. In our context, we&#39;re shooting for interoperability, so we&#39;d pr=
efer something constrained. I appreciate Mike&#39;s input that these are ap=
plication layer decisions. However, if we&#39;re talking
 about cloud provider-to-cloud provider communication, that certainly is fa=
cilitated by a well-defined transport layer. Again, we&#39;re willing to pr=
ofile whatever the group comes up with for our own ends, but I don&#39;t re=
ally see the benefit of having a loosely
 defined transport layer - it just seems like more work for all the impleme=
nters to actually agree on endpoints on a case-by-case basis.<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Looking forward to discussing further in Berlin!<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Sarah<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Sarah Squire<u></u><u>=
</u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Engage Identity<u></u>=
<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><a href=3D"http://enga=
geidentity.com/" target=3D"_blank"><span style=3D"color:#1155cc">http://eng=
ageidentity.com</span></a><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) &lt;=
<a href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">phil.hunt@oracle.=
com</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">We also set things up so even a domain specific even=
t can be extended.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Eg on a password reset event, so event publishers ma=
y want to add security domain specific attributes. The spec lets them do th=
at while avoiding interop issues.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I believe in the spec we had the example of an accou=
nt reset and the publisher adds reset count as an extension.=C2=A0<span sty=
le=3D"color:#888888"><br>
<br>
<span class=3D"m_5165357944078144809hoenzb">Phil</span></span><u></u><u></u=
></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On May 7, 2016, at 13:31, Mike Jones &lt;<a href=3D"mailto:Michael.Jones@mi=
crosoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; wrote:<u=
></u><u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Indeed, that=E2=80=99s why there=E2=80=99s a claims =
registry =E2=80=93 so common claims can be defined once and then reused.<u>=
</u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:
</b><a href=3D"mailto:vivek_biswas@yahoo.com" target=3D"_blank">Vivek Biswa=
s</a><br>
<b>Sent: </b>Saturday, May 7, 2016 1:24 PM<br>
<b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank"=
>Mike Jones</a><br>
<b>Cc: </b><a href=3D"mailto:alanhkarp@gmail.com" target=3D"_blank">Alan Ka=
rp</a>; <a href=3D"mailto:moransar@cisco.com" target=3D"_blank">
Morteza Ansari (moransar)</a>; <a href=3D"mailto:id-event@ietf.org" target=
=3D"_blank">
id-event@ietf.org</a><br>
<b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u></u><u=
></u></p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Yes, I agree that the claims can be application spec=
ific, however there is a possibility to define claims which are domain spec=
ific. Thereby claims generated in one application could be understood by an=
other =C2=A0application within the same
 domain.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">With microservices based architecture getting lot of=
 attention, if two different micro services defining different claims for t=
he same claim, it can create confusion.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Nevertheless this well defined claims for a particul=
ar domain can be an extension to the core specification.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-Vivek Biswas<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 Consulting Member, Oracle<br>
<br>
Sent from my iPhone<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On May 7, 2016, at 1:04 PM, Mike Jones &lt;<a href=3D"mailto:Michael.Jones@=
microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; wrote:=
<u></u><u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Thanks Alan,<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">Interoperability will =
be on a per-application basis, just like JWT interoperability.=C2=A0 The cl=
aims needed in an identity event are application-specific,
 just like claims are for JWTs.=C2=A0 This is the same standards posture an=
d JWTs are a huge success =E2=80=93 including for interoperability, even if=
 I do say so myself.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0<wbr>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Best wishes,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0<wbr>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:
</b><a href=3D"mailto:alanhkarp@gmail.com" target=3D"_blank">Alan Karp</a><=
br>
<b>Sent: </b>Saturday, May 7, 2016 10:23 AM<br>
<b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank"=
>Mike Jones</a><br>
<b>Cc: </b><a href=3D"mailto:moransar@cisco.com" target=3D"_blank">Morteza =
Ansari (moransar)</a>;
<a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-event@ietf.org</a=
><br>
<b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u></u><u=
></u></p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt">As one who proposed =
doing more, I believe that your position is valid.=C2=A0 My only question i=
s whether or not that will be enough for interoperability.</span><u></u><u>=
</u></p>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
--------------<br>
Alan Karp<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 5, 2016 at 10:00 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Thanks guys, for writing the initial =
charter text.=C2=A0 Reading it now, I am extremely worried by the scope
 creep evident in the proposal.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">I strongly support a working group to=
 define an ID Events data format.=C2=A0 I just as strongly believe
 that specific event delivery mechanisms will necessarily be application-sp=
ecific and therefore MUST be explicitly be stated as being out of scope in =
the working group charter.=C2=A0 Attempting to specify a particular event d=
elivery mechanism will take something
 that could be simple and quick to approve and bog it down in necessarily a=
pplication-specific debates.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Should event delivery be reliable?=C2=
=A0 That=E2=80=99s an application-specific decision.</span><u></u><u></u></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Should events be idempotent?=C2=A0 Th=
at=E2=80=99s an application-specific decision.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Should events be unicast, multicast, =
or broadcast?=C2=A0 That=E2=80=99s an application-specific decision.</span>=
<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Should events have categories with ca=
tegory-specific subscriptions?=C2=A0 That=E2=80=99s an application-specific
 decision.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Should only one party at a time be ab=
le to register for delivery of events or should multiple parties
 be able to request delivery?=C2=A0 That=E2=80=99s an application-specific =
decision.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">I could continue with this list, but =
I think you all get the point=E2=80=A6</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">If we start debating application-spec=
ific event delivery mechanisms, we=E2=80=99ll please almost no one, since
 nearly all applications have different event delivery requirements.=C2=A0 =
We MUST explicitly rule all delivery mechanisms as being out of scope.</spa=
n><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">If we define only a data format, we c=
an quickly produce a very useful specification.=C2=A0 If we don=E2=80=99t,
 we=E2=80=99ll get bogged down in the mud of debating which applications we=
=E2=80=99re catering to and which we aren=E2=80=99t =E2=80=93 an exercise o=
f picking favorites and limiting applicability of the specification.=C2=A0 =
That way is a slow, painful descent into standards quicksand =E2=80=93 some=
thing
 we must avoid.=C2=A0 Having a standard ID events representation is far too=
 important to tie to a particular limited event delivery mechanism.</span><=
u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<wbr>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 Sincerely,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<wbr>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><a name=3D"m_5165357944078144809_m_30223670593368935=
65_m_1461024254222911"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0</span></a><u></u><u></u></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Id-event [mailto:<a href=3D"ma=
ilto:id-event-bounces@ietf.org" target=3D"_blank">id-event-bounces@ietf.<wb=
r>org</a>]
<b>On Behalf Of </b>Alan Karp<br>
<b>Sent:</b> Thursday, May 5, 2016 9:43 PM<br>
<b>To:</b> Morteza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.c=
om" target=3D"_blank">moransar@cisco.com</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-event@=
ietf.org</a><br>
<b>Subject:</b> Re: [Id-event] Straw man text for proposed charter</span><u=
></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I don&#39;t see anything about access control for pu=
blishing events and subscribing to them.=C2=A0 I also think the spec should=
 allow filters on subscriptions.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
--------------<br>
Alan Karp<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (mor=
ansar) &lt;<a href=3D"mailto:moransar@cisco.com" target=3D"_blank">moransar=
@cisco.com</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Hi folks,</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">At IIW a few of us (Phil, William, Adam=
, and I) huddled for a bit and put together the attached as a
 straw man charter proposal to start the discussion. Please send your comme=
nts and suggestions for any changes or propose a new one if you think its n=
ecessary.</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Cheers,</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Morteza</span><u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank=
">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">______________________________<wbr>_________________=
<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank=
">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">______________________________<wbr>_________________=
<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank=
">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank=
">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--94eb2c0362a4cf367e053bdfa78c--


From nobody Tue Sep  6 17:11:32 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B73C912B01F for <id-event@ietfa.amsl.com>; Tue,  6 Sep 2016 17:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.708
X-Spam-Level: 
X-Spam-Status: No, score=-5.708 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HnB6GoWqpKH8 for <id-event@ietfa.amsl.com>; Tue,  6 Sep 2016 17:11:28 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 301D512B428 for <id-event@ietf.org>; Tue,  6 Sep 2016 17:11:28 -0700 (PDT)
Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u870BLlT016068 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 7 Sep 2016 00:11:22 GMT
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id u870BLoE026776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 7 Sep 2016 00:11:21 GMT
Received: from abhmp0018.oracle.com (abhmp0018.oracle.com [141.146.116.24]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u870BKqR009228; Wed, 7 Sep 2016 00:11:20 GMT
Received: from [25.89.117.74] (/72.143.228.114) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 06 Sep 2016 17:11:18 -0700
Content-Type: multipart/alternative; boundary=Apple-Mail-3FCF1AE3-C538-48DB-ACEC-57729DD14205
Mime-Version: 1.0 (1.0)
From: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
X-Mailer: iPhone Mail (13G36)
In-Reply-To: <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com>
Date: Tue, 6 Sep 2016 17:11:11 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <8FEB7131-1DFE-4156-9002-D56D1E34B138@oracle.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com>
To: William Denniss <wdenniss@google.com>
X-Source-IP: aserv0022.oracle.com [141.146.126.234]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/6dMDePDeh-opFjQuobASAS-R30k>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, Marius Scurtescu <mscurtescu@google.com>, "Morteza Ansari \(moransar\)" <moransar@cisco.com>, Mike Jones <Michael.Jones@microsoft.com>, "id-event@ietf.org" <id-event@ietf.org>, Leif Johansson <leifj@sunet.se>
Subject: Re: [Id-event] Straw man text for proposed charter
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2016 00:11:31 -0000

--Apple-Mail-3FCF1AE3-C538-48DB-ACEC-57729DD14205
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

+1=20

Thanks Mike.=20


Phil

> On Sep 6, 2016, at 5:04 PM, William Denniss <wdenniss@google.com> wrote:
>=20
> Thank you Mike for revising the charter.=20
>=20
> I support it, and hope we can form a WG with this charter to continue our w=
ork.
>=20
>> On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <Michael.Jones@microsoft.com> w=
rote:
>> An updated and simplified charter is attached.  This draft has been revie=
wed by Phil Hunt, William Denniss, Marius Scurtescu.
>>=20
>> =20
>>=20
>> Input from Alexey Melnikov is that we should probably charter a working g=
roup, rather than try to go the AD-sponsored route.  Therefore, please revie=
w this draft charter and let us know if you think it=E2=80=99s ready to go.
>>=20
>> =20
>>=20
>>                                                        Thanks,
>>=20
>>                                                        -- Mike
>>=20
>> =20
>>=20
>> From: Sarah Squire [mailto:sarah@engageidentity.com]=20
>> Sent: Thursday, July 14, 2016 10:59 PM
>> To: Phil Hunt (IDM) <phil.hunt@oracle.com>
>> Cc: Mike Jones <Michael.Jones@microsoft.com>; Alan Karp <alanhkarp@gmail.=
com>; Vivek Biswas <vivek_biswas@yahoo.com>; Morteza Ansari (moransar) <mora=
nsar@cisco.com>; id-event@ietf.org
>>=20
>>=20
>> Subject: Re: [Id-event] Straw man text for proposed charter
>> =20
>>=20
>> Just submitting my two cents in writing before we hopefully have a chance=
 to meet about this next week...
>>=20
>> =20
>>=20
>> Looking at this charter from the perspective of the OIDF HEART working gr=
oup, I think it's going down a good path. In terms of the data format, this i=
s less structured than what I was envisioning, but we could easily do a heal=
thcare-specific profile of whatever data format comes out in the end, so it'=
s better to be too broad than too narrow as far as our interests are concern=
ed.
>>=20
>> =20
>>=20
>> The transport layer however, has some added complexity. In our context, w=
e're shooting for interoperability, so we'd prefer something constrained. I a=
ppreciate Mike's input that these are application layer decisions. However, i=
f we're talking about cloud provider-to-cloud provider communication, that c=
ertainly is facilitated by a well-defined transport layer. Again, we're will=
ing to profile whatever the group comes up with for our own ends, but I don'=
t really see the benefit of having a loosely defined transport layer - it ju=
st seems like more work for all the implementers to actually agree on endpoi=
nts on a case-by-case basis.
>>=20
>> =20
>>=20
>> Looking forward to discussing further in Berlin!
>>=20
>> =20
>>=20
>> Sarah
>>=20
>>=20
>>=20
>> Sarah Squire
>>=20
>> Engage Identity
>>=20
>> http://engageidentity.com
>>=20
>> =20
>>=20
>> On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com> wr=
ote:
>>=20
>> We also set things up so even a domain specific event can be extended.=20=

>>=20
>> =20
>>=20
>> Eg on a password reset event, so event publishers may want to add securit=
y domain specific attributes. The spec lets them do that while avoiding inte=
rop issues.=20
>>=20
>> =20
>>=20
>> I believe in the spec we had the example of an account reset and the publ=
isher adds reset count as an extension.=20
>>=20
>> Phil
>>=20
>>=20
>> On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com> wrote:=

>>=20
>> Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 so=
 common claims can be defined once and then reused.
>>=20
>> =20
>>=20
>> From: Vivek Biswas
>> Sent: Saturday, May 7, 2016 1:24 PM
>> To: Mike Jones
>> Cc: Alan Karp; Morteza Ansari (moransar); id-event@ietf.org
>> Subject: Re: [Id-event] Straw man text for proposed charter
>>=20
>> =20
>>=20
>> Yes, I agree that the claims can be application specific, however there i=
s a possibility to define claims which are domain specific. Thereby claims g=
enerated in one application could be understood by another  application with=
in the same domain.
>>=20
>> =20
>>=20
>> With microservices based architecture getting lot of attention, if two di=
fferent micro services defining different claims for the same claim, it can c=
reate confusion.
>>=20
>> =20
>>=20
>> Nevertheless this well defined claims for a particular domain can be an e=
xtension to the core specification.
>>=20
>> =20
>>=20
>> -Vivek Biswas
>>=20
>>   Consulting Member, Oracle
>>=20
>> Sent from my iPhone
>>=20
>>=20
>> On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com> wrot=
e:
>>=20
>> Thanks Alan,
>>=20
>> =20
>>=20
>> Interoperability will be on a per-application basis, just like JWT intero=
perability.  The claims needed in an identity event are application-specific=
,  just like claims are for JWTs.  This is the same standards posture and JW=
Ts are a huge success =E2=80=93 including for interoperability, even if I do=
 say so myself.
>>=20
>> =20
>>=20
>>                                                           Best wishes,
>>=20
>>                                                           -- Mike
>>=20
>> =20
>>=20
>> =20
>>=20
>> =20
>>=20
>> =20
>>=20
>> From: Alan Karp
>> Sent: Saturday, May 7, 2016 10:23 AM
>> To: Mike Jones
>> Cc: Morteza Ansari (moransar); id-event@ietf.org
>> Subject: Re: [Id-event] Straw man text for proposed charter
>>=20
>> =20
>>=20
>> As one who proposed doing more, I believe that your position is valid.  M=
y only question is whether or not that will be enough for interoperability.
>>=20
>>=20
>>=20
>>=20
>> --------------
>> Alan Karp
>>=20
>> =20
>>=20
>> On Thu, May 5, 2016 at 10:00 PM, Mike Jones <Michael.Jones@microsoft.com>=
 wrote:
>>=20
>> Thanks guys, for writing the initial charter text.  Reading it now, I am e=
xtremely worried by the scope creep evident in the proposal.
>>=20
>> =20
>>=20
>> I strongly support a working group to define an ID Events data format.  I=
 just as strongly believe that specific event delivery mechanisms will neces=
sarily be application-specific and therefore MUST be explicitly be stated as=
 being out of scope in the working group charter.  Attempting to specify a p=
articular event delivery mechanism will take something that could be simple a=
nd quick to approve and bog it down in necessarily application-specific deba=
tes.
>>=20
>> =20
>>=20
>> Should event delivery be reliable?  That=E2=80=99s an application-specifi=
c decision.
>>=20
>> Should events be idempotent?  That=E2=80=99s an application-specific deci=
sion.
>>=20
>> Should events be unicast, multicast, or broadcast?  That=E2=80=99s an app=
lication-specific decision.
>>=20
>> Should events have categories with category-specific subscriptions?  That=
=E2=80=99s an application-specific decision.
>>=20
>> Should only one party at a time be able to register for delivery of event=
s or should multiple parties be able to request delivery?  That=E2=80=99s an=
 application-specific decision.
>>=20
>> I could continue with this list, but I think you all get the point=E2=80=A6=

>>=20
>> =20
>>=20
>> If we start debating application-specific event delivery mechanisms, we=E2=
=80=99ll please almost no one, since nearly all applications have different e=
vent delivery requirements.  We MUST explicitly rule all delivery mechanisms=
 as being out of scope.
>>=20
>> =20
>>=20
>> If we define only a data format, we can quickly produce a very useful spe=
cification.  If we don=E2=80=99t, we=E2=80=99ll get bogged down in the mud o=
f debating which applications we=E2=80=99re catering to and which we aren=E2=
=80=99t =E2=80=93 an exercise of picking favorites and limiting applicabilit=
y of the specification.  That way is a slow, painful descent into standards q=
uicksand =E2=80=93 something we must avoid.  Having a standard ID events rep=
resentation is far too important to tie to a particular limited event delive=
ry mechanism.
>>=20
>> =20
>>=20
>>                                                           Sincerely,
>>=20
>>                                                           -- Mike
>>=20
>> =20
>>=20
>> From: Id-event [mailto:id-event-bounces@ietf.org] On Behalf Of Alan Karp
>> Sent: Thursday, May 5, 2016 9:43 PM
>> To: Morteza Ansari (moransar) <moransar@cisco.com>
>> Cc: id-event@ietf.org
>> Subject: Re: [Id-event] Straw man text for proposed charter
>>=20
>> =20
>>=20
>> I don't see anything about access control for publishing events and subsc=
ribing to them.  I also think the spec should allow filters on subscriptions=
.
>>=20
>>=20
>>=20
>>=20
>> --------------
>> Alan Karp
>>=20
>> =20
>>=20
>> On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar) <moransar@cisc=
o.com> wrote:
>>=20
>> Hi folks,
>>=20
>> =20
>>=20
>> At IIW a few of us (Phil, William, Adam, and I) huddled for a bit and put=
 together the attached as a straw man charter proposal to start the discussi=
on. Please send your comments and suggestions for any changes or propose a n=
ew one if you think its necessary.
>>=20
>> =20
>>=20
>> =20
>>=20
>> Cheers,
>>=20
>> Morteza
>>=20
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>=20
>> =20
>>=20
>> =20
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>=20
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>=20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event

--Apple-Mail-3FCF1AE3-C538-48DB-ACEC-57729DD14205
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>+1&nbsp;</div><div id=3D"AppleMailSign=
ature"><br></div><div id=3D"AppleMailSignature">Thanks Mike.&nbsp;</div><div=
 id=3D"AppleMailSignature"><br><br>Phil</div><div><br>On Sep 6, 2016, at 5:0=
4 PM, William Denniss &lt;<a href=3D"mailto:wdenniss@google.com">wdenniss@go=
ogle.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><div dir=
=3D"ltr">Thank you Mike for revising the charter.&nbsp;<div><br></div><div>I=
 support it, and hope we can form a WG with this charter to continue our wor=
k.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On T=
ue, Sep 6, 2016 at 5:01 PM, Mike Jones <span dir=3D"ltr">&lt;<a href=3D"mail=
to:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.co=
m</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_5165357944078144809WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">An updated and simplified charter is at=
tached.&nbsp; This draft has been reviewed by Phil Hunt, William Denniss, Ma=
rius Scurtescu.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">Input from Alexey Melnikov is that we s=
hould probably charter a working group, rather than try to go the AD-sponsor=
ed route.&nbsp; Therefore, please review this draft
 charter and let us know if you think it=E2=80=99s ready to go.<u></u><u></u=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<u></u=
><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<u></u=
><u></u></span></p>
<p class=3D"MsoNormal"><a name=3D"m_5165357944078144809__MailEndCompose"><sp=
an style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;colo=
r:#002060"><u></u>&nbsp;<u></u></span></a></p>
<span></span>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif"> Sarah Squire [mailto:<a href=3D"m=
ailto:sarah@engageidentity.com" target=3D"_blank">sarah@engageidentity.<wbr>=
com</a>]
<br>
<b>Sent:</b> Thursday, July 14, 2016 10:59 PM<br>
<b>To:</b> Phil Hunt (IDM) &lt;<a href=3D"mailto:phil.hunt@oracle.com" targe=
t=3D"_blank">phil.hunt@oracle.com</a>&gt;<br>
<b>Cc:</b> Mike Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com" tar=
get=3D"_blank">Michael.Jones@microsoft.com</a>&gt;; Alan Karp &lt;<a href=3D=
"mailto:alanhkarp@gmail.com" target=3D"_blank">alanhkarp@gmail.com</a>&gt;; V=
ivek Biswas &lt;<a href=3D"mailto:vivek_biswas@yahoo.com" target=3D"_blank">=
vivek_biswas@yahoo.com</a>&gt;; Morteza Ansari (moransar) &lt;<a href=3D"mai=
lto:moransar@cisco.com" target=3D"_blank">moransar@cisco.com</a>&gt;; <a hre=
f=3D"mailto:id-event@ietf.org" target=3D"_blank">id-event@ietf.org</a></span=
></p><div><div class=3D"h5"><br>
<b>Subject:</b> Re: [Id-event] Straw man text for proposed charter<u></u><u>=
</u></div></div><p></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">Just submitting my two cents in writing before we hop=
efully have a chance to meet about this next week...<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<p class=3D"MsoNormal">Looking at this charter from the perspective of the O=
IDF HEART working group, I think it's going down a good path. In terms of th=
e data format, this is less structured than what I was envisioning, but we c=
ould easily do a healthcare-specific
 profile of whatever data format comes out in the end, so it's better to be t=
oo broad than too narrow as far as our interests are concerned.<u></u><u></u=
></p>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The transport layer however, has some added complexit=
y. In our context, we're shooting for interoperability, so we'd prefer somet=
hing constrained. I appreciate Mike's input that these are application layer=
 decisions. However, if we're talking
 about cloud provider-to-cloud provider communication, that certainly is fac=
ilitated by a well-defined transport layer. Again, we're willing to profile w=
hatever the group comes up with for our own ends, but I don't really see the=
 benefit of having a loosely
 defined transport layer - it just seems like more work for all the implemen=
ters to actually agree on endpoints on a case-by-case basis.<u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Looking forward to discussing further in Berlin!<u></=
u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Sarah<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Sarah Squire<u></u><u><=
/u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Engage Identity<u></u><=
u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><a href=3D"http://engag=
eidentity.com/" target=3D"_blank"><span style=3D"color:#1155cc">http://engag=
eidentity.com</span></a><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<p class=3D"MsoNormal">On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) &lt;<=
a href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">phil.hunt@oracle.co=
m</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"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=3D"MsoNormal">We also set things up so even a domain specific event=
 can be extended.&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Eg on a password reset event, so event publishers may=
 want to add security domain specific attributes. The spec lets them do that=
 while avoiding interop issues.&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I believe in the spec we had the example of an accoun=
t reset and the publisher adds reset count as an extension.&nbsp;<span style=
=3D"color:#888888"><br>
<br>
<span class=3D"m_5165357944078144809hoenzb">Phil</span></span><u></u><u></u>=
</p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On May 7, 2016, at 13:31, Mike Jones &lt;<a href=3D"mailto:Michael.Jones@mic=
rosoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; wrote:<u><=
/u><u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Indeed, that=E2=80=99s why there=E2=80=99s a claims r=
egistry =E2=80=93 so common claims can be defined once and then reused.<u></=
u><u></u></p>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0=
in 0in">
<p class=3D"MsoNormal"><b>From:
</b><a href=3D"mailto:vivek_biswas@yahoo.com" target=3D"_blank">Vivek Biswas=
</a><br>
<b>Sent: </b>Saturday, May 7, 2016 1:24 PM<br>
<b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">=
Mike Jones</a><br>
<b>Cc: </b><a href=3D"mailto:alanhkarp@gmail.com" target=3D"_blank">Alan Kar=
p</a>; <a href=3D"mailto:moransar@cisco.com" target=3D"_blank">
Morteza Ansari (moransar)</a>; <a href=3D"mailto:id-event@ietf.org" target=3D=
"_blank">
id-event@ietf.org</a><br>
<b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u></u><u>=
</u></p>
</div>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Yes, I agree that the claims can be application speci=
fic, however there is a possibility to define claims which are domain specif=
ic. Thereby claims generated in one application could be understood by anoth=
er &nbsp;application within the same
 domain.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">With microservices based architecture getting lot of a=
ttention, if two different micro services defining different claims for the s=
ame claim, it can create confusion.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Nevertheless this well defined claims for a particula=
r domain can be an extension to the core specification.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-Vivek Biswas<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; Consulting Member, Oracle<br>
<br>
Sent from my iPhone<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On May 7, 2016, at 1:04 PM, Mike Jones &lt;<a href=3D"mailto:Michael.Jones@m=
icrosoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; wrote:<u=
></u><u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Thanks Alan,<u></u><u></u></p>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">Interoperability will b=
e on a per-application basis, just like JWT interoperability.&nbsp; The clai=
ms needed in an identity event are application-specific,
 just like claims are for JWTs.&nbsp; This is the same standards posture and=
 JWTs are a huge success =E2=80=93 including for interoperability, even if I=
 do say so myself.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">&nbsp;</span><u></u><u>=
</u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Best wishes,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0=
in 0in">
<p class=3D"MsoNormal"><b>From:
</b><a href=3D"mailto:alanhkarp@gmail.com" target=3D"_blank">Alan Karp</a><b=
r>
<b>Sent: </b>Saturday, May 7, 2016 10:23 AM<br>
<b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">=
Mike Jones</a><br>
<b>Cc: </b><a href=3D"mailto:moransar@cisco.com" target=3D"_blank">Morteza A=
nsari (moransar)</a>;
<a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-event@ietf.org</a>=
<br>
<b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u></u><u>=
</u></p>
</div>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt">As one who proposed d=
oing more, I believe that your position is valid.&nbsp; My only question is w=
hether or not that will be enough for interoperability.</span><u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
--------------<br>
Alan Karp<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 5, 2016 at 10:00 PM, Mike Jones &lt;<a hr=
ef=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@mi=
crosoft.com</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"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=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">Thanks guys, for writing the initial ch=
arter text.&nbsp; Reading it now, I am extremely worried by the scope
 creep evident in the proposal.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">I strongly support a working group to d=
efine an ID Events data format.&nbsp; I just as strongly believe
 that specific event delivery mechanisms will necessarily be application-spe=
cific and therefore MUST be explicitly be stated as being out of scope in th=
e working group charter.&nbsp; Attempting to specify a particular event deli=
very mechanism will take something
 that could be simple and quick to approve and bog it down in necessarily ap=
plication-specific debates.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">Should event delivery be reliable?&nbsp=
; That=E2=80=99s an application-specific decision.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">Should events be idempotent?&nbsp; That=
=E2=80=99s an application-specific decision.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">Should events be unicast, multicast, or=
 broadcast?&nbsp; That=E2=80=99s an application-specific decision.</span><u>=
</u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">Should events have categories with cate=
gory-specific subscriptions?&nbsp; That=E2=80=99s an application-specific
 decision.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">Should only one party at a time be able=
 to register for delivery of events or should multiple parties
 be able to request delivery?&nbsp; That=E2=80=99s an application-specific d=
ecision.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">I could continue with this list, but I t=
hink you all get the point=E2=80=A6</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">If we start debating application-specif=
ic event delivery mechanisms, we=E2=80=99ll please almost no one, since
 nearly all applications have different event delivery requirements.&nbsp; W=
e MUST explicitly rule all delivery mechanisms as being out of scope.</span>=
<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">If we define only a data format, we can=
 quickly produce a very useful specification.&nbsp; If we don=E2=80=99t,
 we=E2=80=99ll get bogged down in the mud of debating which applications we=E2=
=80=99re catering to and which we aren=E2=80=99t =E2=80=93 an exercise of pi=
cking favorites and limiting applicability of the specification.&nbsp; That w=
ay is a slow, painful descent into standards quicksand =E2=80=93 something
 we must avoid.&nbsp; Having a standard ID events representation is far too i=
mportant to tie to a particular limited event delivery mechanism.</span><u><=
/u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Sincerely,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><a name=3D"m_5165357944078144809_m_302236705933689356=
5_m_1461024254222911"><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,sans-serif;color:#002060">&nbsp;</span></a><u></u><u></u></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif"> Id-event [mailto:<a href=3D"mailt=
o:id-event-bounces@ietf.org" target=3D"_blank">id-event-bounces@ietf.<wbr>or=
g</a>]
<b>On Behalf Of </b>Alan Karp<br>
<b>Sent:</b> Thursday, May 5, 2016 9:43 PM<br>
<b>To:</b> Morteza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.co=
m" target=3D"_blank">moransar@cisco.com</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-event@i=
etf.org</a><br>
<b>Subject:</b> Re: [Id-event] Straw man text for proposed charter</span><u>=
</u><u></u></p>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I don't see anything about access control for publish=
ing events and subscribing to them.&nbsp; I also think the spec should allow=
 filters on subscriptions.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
--------------<br>
Alan Karp<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (mora=
nsar) &lt;<a href=3D"mailto:moransar@cisco.com" target=3D"_blank">moransar@c=
isco.com</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0in=
 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bo=
ttom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:black">Hi folks,</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:black">&nbsp;</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:black">At IIW a few of us (Phil, William, Adam, a=
nd I) huddled for a bit and put together the attached as a
 straw man charter proposal to start the discussion. Please send your commen=
ts and suggestions for any changes or propose a new one if you think its nec=
essary.</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:black">&nbsp;</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:black">&nbsp;</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:black">Cheers,</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:black">Morteza</span><u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a>=
<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank"=
>https://www.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">______________________________<wbr>_________________<=
br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a>=
<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank"=
>https://www.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">______________________________<wbr>_________________<=
br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a>=
<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank"=
>https://www.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a>=
<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank"=
>https://www.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>Id-event mailing list</span><br>=
<span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></span><br><=
span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www.=
ietf.org/mailman/listinfo/id-event</a></span><br></div></blockquote></body><=
/html>=

--Apple-Mail-3FCF1AE3-C538-48DB-ACEC-57729DD14205--


From nobody Tue Sep  6 17:41:26 2016
Return-Path: <mscurtescu@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27FB412B47F for <id-event@ietfa.amsl.com>; Tue,  6 Sep 2016 17:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level: 
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mWj4cKBuELjf for <id-event@ietfa.amsl.com>; Tue,  6 Sep 2016 17:41:21 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 598F212B47A for <id-event@ietf.org>; Tue,  6 Sep 2016 17:41:20 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id 1so3980181wmz.1 for <id-event@ietf.org>; Tue, 06 Sep 2016 17:41:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=veleakkzBhl2Gh0IS/lfFZp0vmm3iDLK+fac+oTfq7s=; b=bnOnF2FsoWNE4cEpdFjERp0Eb32BVXwumw8EjKTwj6oejQZsrJBnH8C+nBi36lDdR7 AUpOx4qdMT2EAjELjXqz4xmWhk488dW823FdC3HaGIkEo3hO/LZoz9EbvSm4o3TCxLdY B/sIjlmzU7AyL5LYW71T+NcBuOcjKRQlp5k9ssshBof3i/sE+aVYoUARqNlDANq+Ua4p b0Pl9larmTP/CuLfyl7XCfn17kTubXprW8CiOzVJBF7giNvnbvDAV/X3nQlya1R4H2YX ur4DW6Bq5fVYv5ouA4ykL76YZBiG919bWglPnD4QyZICAJBxLFrRDcP7TJloi+kSQaF6 Et+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=veleakkzBhl2Gh0IS/lfFZp0vmm3iDLK+fac+oTfq7s=; b=Yd5JsxicPnf0QH8vUFD5tWxSzl8RsNlz0ExgGQMQ9g0ar6Ar+p0XG0zeUsnXE3pNLb D43LbE1fjYwlqpoxJRdM6NILc6xzvR9zeyj95e34dxL5TtgjsF5/+YLgv/Hdy5O7AASB Ym8atXukiOKbzy81Rp75jqD5Vu1pTzZtQE8zMlpii4iX3f/FVhSq6hcY4hyGFiNTQvr2 VxTrMiKNsVksXO20rCmMQkNdcrJeuYc+vogy3QRXcrwzMGjU75qwYurXM1rtWpE/kIQY 7DqDHPEUT3xqMl5JQVtat8VPfzEsHBClQPwrO4LRjxklnZq6zLTLz9D0/5YvwBlHxXtn 7w2A==
X-Gm-Message-State: AE9vXwNoR+unI6QIrUva1Q1fz75kUjJU9StEMhd8zu07dygwbcG/3CKdn2ifV6lDTih9SW3os5jRK4X0wUMroQ4O
X-Received: by 10.28.191.14 with SMTP id p14mr1145479wmf.39.1473208878606; Tue, 06 Sep 2016 17:41:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.35.86 with HTTP; Tue, 6 Sep 2016 17:40:57 -0700 (PDT)
In-Reply-To: <8FEB7131-1DFE-4156-9002-D56D1E34B138@oracle.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com> <8FEB7131-1DFE-4156-9002-D56D1E34B138@oracle.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Tue, 6 Sep 2016 17:40:57 -0700
Message-ID: <CAGdjJpLu-CwuYQt9f-UZsZYmjOnwhgGnA2MZ38nZUgfC2Q5REw@mail.gmail.com>
To: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary=001a114cef06e42205053be02b3f
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/aJgeN844bJc9Uk9-cLX9UyFhqyw>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, "Morteza Ansari \(moransar\)" <moransar@cisco.com>, Mike Jones <Michael.Jones@microsoft.com>, "id-event@ietf.org" <id-event@ietf.org>, William Denniss <wdenniss@google.com>, Leif Johansson <leifj@sunet.se>
Subject: Re: [Id-event] Straw man text for proposed charter
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2016 00:41:24 -0000

--001a114cef06e42205053be02b3f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks Mike, it looks good.

Marius

On Tue, Sep 6, 2016 at 5:11 PM, Phil Hunt (IDM) <phil.hunt@oracle.com>
wrote:

> +1
>
> Thanks Mike.
>
>
> Phil
>
> On Sep 6, 2016, at 5:04 PM, William Denniss <wdenniss@google.com> wrote:
>
> Thank you Mike for revising the charter.
>
> I support it, and hope we can form a WG with this charter to continue our
> work.
>
> On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:
>
>> An updated and simplified charter is attached.  This draft has been
>> reviewed by Phil Hunt, William Denniss, Marius Scurtescu.
>>
>>
>>
>> Input from Alexey Melnikov is that we should probably charter a working
>> group, rather than try to go the AD-sponsored route.  Therefore, please
>> review this draft charter and let us know if you think it=E2=80=99s read=
y to go.
>>
>>
>>
>>                                                        Thanks,
>>
>>                                                        -- Mike
>>
>>
>>
>> *From:* Sarah Squire [mailto:sarah@engageidentity.com]
>> *Sent:* Thursday, July 14, 2016 10:59 PM
>> *To:* Phil Hunt (IDM) <phil.hunt@oracle.com>
>> *Cc:* Mike Jones <Michael.Jones@microsoft.com>; Alan Karp <
>> alanhkarp@gmail.com>; Vivek Biswas <vivek_biswas@yahoo.com>; Morteza
>> Ansari (moransar) <moransar@cisco.com>; id-event@ietf.org
>>
>> *Subject:* Re: [Id-event] Straw man text for proposed charter
>>
>>
>>
>> Just submitting my two cents in writing before we hopefully have a chanc=
e
>> to meet about this next week...
>>
>>
>>
>> Looking at this charter from the perspective of the OIDF HEART working
>> group, I think it's going down a good path. In terms of the data format,
>> this is less structured than what I was envisioning, but we could easily=
 do
>> a healthcare-specific profile of whatever data format comes out in the e=
nd,
>> so it's better to be too broad than too narrow as far as our interests a=
re
>> concerned.
>>
>>
>>
>> The transport layer however, has some added complexity. In our context,
>> we're shooting for interoperability, so we'd prefer something constraine=
d.
>> I appreciate Mike's input that these are application layer decisions.
>> However, if we're talking about cloud provider-to-cloud provider
>> communication, that certainly is facilitated by a well-defined transport
>> layer. Again, we're willing to profile whatever the group comes up with =
for
>> our own ends, but I don't really see the benefit of having a loosely
>> defined transport layer - it just seems like more work for all the
>> implementers to actually agree on endpoints on a case-by-case basis.
>>
>>
>>
>> Looking forward to discussing further in Berlin!
>>
>>
>>
>> Sarah
>>
>>
>> Sarah Squire
>>
>> Engage Identity
>>
>> http://engageidentity.com
>>
>>
>>
>> On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com>
>> wrote:
>>
>> We also set things up so even a domain specific event can be extended.
>>
>>
>>
>> Eg on a password reset event, so event publishers may want to add
>> security domain specific attributes. The spec lets them do that while
>> avoiding interop issues.
>>
>>
>>
>> I believe in the spec we had the example of an account reset and the
>> publisher adds reset count as an extension.
>>
>> Phil
>>
>>
>> On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com> wrote=
:
>>
>> Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 s=
o common claims can be
>> defined once and then reused.
>>
>>
>>
>> *From: *Vivek Biswas <vivek_biswas@yahoo.com>
>> *Sent: *Saturday, May 7, 2016 1:24 PM
>> *To: *Mike Jones <Michael.Jones@microsoft.com>
>> *Cc: *Alan Karp <alanhkarp@gmail.com>; Morteza Ansari (moransar)
>> <moransar@cisco.com>; id-event@ietf.org
>> *Subject: *Re: [Id-event] Straw man text for proposed charter
>>
>>
>>
>> Yes, I agree that the claims can be application specific, however there
>> is a possibility to define claims which are domain specific. Thereby cla=
ims
>> generated in one application could be understood by another  application
>> within the same domain.
>>
>>
>>
>> With microservices based architecture getting lot of attention, if two
>> different micro services defining different claims for the same claim, i=
t
>> can create confusion.
>>
>>
>>
>> Nevertheless this well defined claims for a particular domain can be an
>> extension to the core specification.
>>
>>
>>
>> -Vivek Biswas
>>
>>   Consulting Member, Oracle
>>
>> Sent from my iPhone
>>
>>
>> On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com>
>> wrote:
>>
>> Thanks Alan,
>>
>>
>>
>> Interoperability will be on a per-application basis, just like JWT
>> interoperability.  The claims needed in an identity event are
>> application-specific, just like claims are for JWTs.  This is the same
>> standards posture and JWTs are a huge success =E2=80=93 including for
>> interoperability, even if I do say so myself.
>>
>>
>>
>>                                                           Best wishes,
>>
>>                                                           -- Mike
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *Alan Karp <alanhkarp@gmail.com>
>> *Sent: *Saturday, May 7, 2016 10:23 AM
>> *To: *Mike Jones <Michael.Jones@microsoft.com>
>> *Cc: *Morteza Ansari (moransar) <moransar@cisco.com>; id-event@ietf.org
>> *Subject: *Re: [Id-event] Straw man text for proposed charter
>>
>>
>>
>> As one who proposed doing more, I believe that your position is valid.
>> My only question is whether or not that will be enough for interoperabil=
ity.
>>
>>
>>
>> --------------
>> Alan Karp
>>
>>
>>
>> On Thu, May 5, 2016 at 10:00 PM, Mike Jones <Michael.Jones@microsoft.com=
>
>> wrote:
>>
>> Thanks guys, for writing the initial charter text.  Reading it now, I am
>> extremely worried by the scope creep evident in the proposal.
>>
>>
>>
>> I strongly support a working group to define an ID Events data format.  =
I
>> just as strongly believe that specific event delivery mechanisms will
>> necessarily be application-specific and therefore MUST be explicitly be
>> stated as being out of scope in the working group charter.  Attempting t=
o
>> specify a particular event delivery mechanism will take something that
>> could be simple and quick to approve and bog it down in necessarily
>> application-specific debates.
>>
>>
>>
>> Should event delivery be reliable?  That=E2=80=99s an application-specif=
ic
>> decision.
>>
>> Should events be idempotent?  That=E2=80=99s an application-specific dec=
ision.
>>
>> Should events be unicast, multicast, or broadcast?  That=E2=80=99s an
>> application-specific decision.
>>
>> Should events have categories with category-specific subscriptions?
>> That=E2=80=99s an application-specific decision.
>>
>> Should only one party at a time be able to register for delivery of
>> events or should multiple parties be able to request delivery?  That=E2=
=80=99s an
>> application-specific decision.
>>
>> I could continue with this list, but I think you all get the point=E2=80=
=A6
>>
>>
>>
>> If we start debating application-specific event delivery mechanisms,
>> we=E2=80=99ll please almost no one, since nearly all applications have d=
ifferent
>> event delivery requirements.  We MUST explicitly rule all delivery
>> mechanisms as being out of scope.
>>
>>
>>
>> If we define only a data format, we can quickly produce a very useful
>> specification.  If we don=E2=80=99t, we=E2=80=99ll get bogged down in th=
e mud of debating
>> which applications we=E2=80=99re catering to and which we aren=E2=80=99t=
 =E2=80=93 an exercise of
>> picking favorites and limiting applicability of the specification.  That
>> way is a slow, painful descent into standards quicksand =E2=80=93 someth=
ing we must
>> avoid.  Having a standard ID events representation is far too important =
to
>> tie to a particular limited event delivery mechanism.
>>
>>
>>
>>                                                           Sincerely,
>>
>>                                                           -- Mike
>>
>>
>>
>> *From:* Id-event [mailto:id-event-bounces@ietf.org] *On Behalf Of *Alan
>> Karp
>> *Sent:* Thursday, May 5, 2016 9:43 PM
>> *To:* Morteza Ansari (moransar) <moransar@cisco.com>
>> *Cc:* id-event@ietf.org
>> *Subject:* Re: [Id-event] Straw man text for proposed charter
>>
>>
>>
>> I don't see anything about access control for publishing events and
>> subscribing to them.  I also think the spec should allow filters on
>> subscriptions.
>>
>>
>>
>> --------------
>> Alan Karp
>>
>>
>>
>> On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar) <
>> moransar@cisco.com> wrote:
>>
>> Hi folks,
>>
>>
>>
>> At IIW a few of us (Phil, William, Adam, and I) huddled for a bit and pu=
t
>> together the attached as a straw man charter proposal to start the
>> discussion. Please send your comments and suggestions for any changes or
>> propose a new one if you think its necessary.
>>
>>
>>
>>
>>
>> Cheers,
>>
>> Morteza
>>
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>>
>>
>>
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>>
>>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>

--001a114cef06e42205053be02b3f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Mike, it looks good.</div><div class=3D"gmail_extra=
"><br clear=3D"all"><div><div class=3D"gmail_signature" data-smartmail=3D"g=
mail_signature">Marius</div></div>
<br><div class=3D"gmail_quote">On Tue, Sep 6, 2016 at 5:11 PM, Phil Hunt (I=
DM) <span dir=3D"ltr">&lt;<a href=3D"mailto:phil.hunt@oracle.com" target=3D=
"_blank">phil.hunt@oracle.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><div dir=3D"auto"><div>+1=C2=A0</div><div id=3D"m_-1072212518660=
021386AppleMailSignature"><br></div><div id=3D"m_-1072212518660021386AppleM=
ailSignature">Thanks Mike.=C2=A0</div><span class=3D"HOEnZb"><font color=3D=
"#888888"><div id=3D"m_-1072212518660021386AppleMailSignature"><br><br>Phil=
</div></font></span><div><div class=3D"h5"><div><br>On Sep 6, 2016, at 5:04=
 PM, William Denniss &lt;<a href=3D"mailto:wdenniss@google.com" target=3D"_=
blank">wdenniss@google.com</a>&gt; wrote:<br><br></div><blockquote type=3D"=
cite"><div><div dir=3D"ltr">Thank you Mike for revising the charter.=C2=A0<=
div><br></div><div>I support it, and hope we can form a WG with this charte=
r to continue our work.</div></div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <span dir=3D"l=
tr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Mi=
chael.Jones@microsoft.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-1072212518660021386m_5165357944078144809WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">An updated and simplified charter is =
attached.=C2=A0 This draft has been reviewed by Phil Hunt, William Denniss,=
 Marius Scurtescu.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Input from Alexey Melnikov is that we=
 should probably charter a working group, rather than try to go the AD-spon=
sored route.=C2=A0 Therefore, please review this draft
 charter and let us know if you think it=E2=80=99s ready to go.<u></u><u></=
u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<wbr>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Thank=
s,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<wbr>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- Mi=
ke<u></u><u></u></span></p>
<p class=3D"MsoNormal"><a name=3D"m_-1072212518660021386_m_5165357944078144=
809__MailEndCompose"><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,sans-serif;color:#002060"><u></u>=C2=A0<u></u></span></a></p>
<span></span>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Sarah Squire [mailto:<a href=
=3D"mailto:sarah@engageidentity.com" target=3D"_blank">sarah@engageidentity=
.c<wbr>om</a>]
<br>
<b>Sent:</b> Thursday, July 14, 2016 10:59 PM<br>
<b>To:</b> Phil Hunt (IDM) &lt;<a href=3D"mailto:phil.hunt@oracle.com" targ=
et=3D"_blank">phil.hunt@oracle.com</a>&gt;<br>
<b>Cc:</b> Mike Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com" ta=
rget=3D"_blank">Michael.Jones@microsoft.com</a>&gt;; Alan Karp &lt;<a href=
=3D"mailto:alanhkarp@gmail.com" target=3D"_blank">alanhkarp@gmail.com</a>&g=
t;; Vivek Biswas &lt;<a href=3D"mailto:vivek_biswas@yahoo.com" target=3D"_b=
lank">vivek_biswas@yahoo.com</a>&gt;; Morteza Ansari (moransar) &lt;<a href=
=3D"mailto:moransar@cisco.com" target=3D"_blank">moransar@cisco.com</a>&gt;=
; <a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-event@ietf.org<=
/a></span></p><div><div class=3D"m_-1072212518660021386h5"><br>
<b>Subject:</b> Re: [Id-event] Straw man text for proposed charter<u></u><u=
></u></div></div><p></p><div><div class=3D"m_-1072212518660021386h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">Just submitting my two cents in writing before we ho=
pefully have a chance to meet about this next week...<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">Looking at this charter from the perspective of the =
OIDF HEART working group, I think it&#39;s going down a good path. In terms=
 of the data format, this is less structured than what I was envisioning, b=
ut we could easily do a healthcare-specific
 profile of whatever data format comes out in the end, so it&#39;s better t=
o be too broad than too narrow as far as our interests are concerned.<u></u=
><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The transport layer however, has some added complexi=
ty. In our context, we&#39;re shooting for interoperability, so we&#39;d pr=
efer something constrained. I appreciate Mike&#39;s input that these are ap=
plication layer decisions. However, if we&#39;re talking
 about cloud provider-to-cloud provider communication, that certainly is fa=
cilitated by a well-defined transport layer. Again, we&#39;re willing to pr=
ofile whatever the group comes up with for our own ends, but I don&#39;t re=
ally see the benefit of having a loosely
 defined transport layer - it just seems like more work for all the impleme=
nters to actually agree on endpoints on a case-by-case basis.<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Looking forward to discussing further in Berlin!<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Sarah<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Sarah Squire<u></u><u>=
</u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Engage Identity<u></u>=
<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><a href=3D"http://enga=
geidentity.com/" target=3D"_blank"><span style=3D"color:#1155cc">http://eng=
ageidentity.com</span></a><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) &lt;=
<a href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">phil.hunt@oracle.=
com</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">We also set things up so even a domain specific even=
t can be extended.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Eg on a password reset event, so event publishers ma=
y want to add security domain specific attributes. The spec lets them do th=
at while avoiding interop issues.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I believe in the spec we had the example of an accou=
nt reset and the publisher adds reset count as an extension.=C2=A0<span sty=
le=3D"color:#888888"><br>
<br>
<span class=3D"m_-1072212518660021386m_5165357944078144809hoenzb">Phil</spa=
n></span><u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On May 7, 2016, at 13:31, Mike Jones &lt;<a href=3D"mailto:Michael.Jones@mi=
crosoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; wrote:<u=
></u><u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Indeed, that=E2=80=99s why there=E2=80=99s a claims =
registry =E2=80=93 so common claims can be defined once and then reused.<u>=
</u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:
</b><a href=3D"mailto:vivek_biswas@yahoo.com" target=3D"_blank">Vivek Biswa=
s</a><br>
<b>Sent: </b>Saturday, May 7, 2016 1:24 PM<br>
<b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank"=
>Mike Jones</a><br>
<b>Cc: </b><a href=3D"mailto:alanhkarp@gmail.com" target=3D"_blank">Alan Ka=
rp</a>; <a href=3D"mailto:moransar@cisco.com" target=3D"_blank">
Morteza Ansari (moransar)</a>; <a href=3D"mailto:id-event@ietf.org" target=
=3D"_blank">
id-event@ietf.org</a><br>
<b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u></u><u=
></u></p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Yes, I agree that the claims can be application spec=
ific, however there is a possibility to define claims which are domain spec=
ific. Thereby claims generated in one application could be understood by an=
other =C2=A0application within the same
 domain.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">With microservices based architecture getting lot of=
 attention, if two different micro services defining different claims for t=
he same claim, it can create confusion.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Nevertheless this well defined claims for a particul=
ar domain can be an extension to the core specification.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-Vivek Biswas<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 Consulting Member, Oracle<br>
<br>
Sent from my iPhone<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On May 7, 2016, at 1:04 PM, Mike Jones &lt;<a href=3D"mailto:Michael.Jones@=
microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; wrote:=
<u></u><u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Thanks Alan,<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">Interoperability will =
be on a per-application basis, just like JWT interoperability.=C2=A0 The cl=
aims needed in an identity event are application-specific,
 just like claims are for JWTs.=C2=A0 This is the same standards posture an=
d JWTs are a huge success =E2=80=93 including for interoperability, even if=
 I do say so myself.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">=C2=A0</span><u></u><u=
></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0<wbr>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Best wishes,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#002060">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0<wbr>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:
</b><a href=3D"mailto:alanhkarp@gmail.com" target=3D"_blank">Alan Karp</a><=
br>
<b>Sent: </b>Saturday, May 7, 2016 10:23 AM<br>
<b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank"=
>Mike Jones</a><br>
<b>Cc: </b><a href=3D"mailto:moransar@cisco.com" target=3D"_blank">Morteza =
Ansari (moransar)</a>;
<a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-event@ietf.org</a=
><br>
<b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u></u><u=
></u></p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt">As one who proposed =
doing more, I believe that your position is valid.=C2=A0 My only question i=
s whether or not that will be enough for interoperability.</span><u></u><u>=
</u></p>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
--------------<br>
Alan Karp<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 5, 2016 at 10:00 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Thanks guys, for writing the initial =
charter text.=C2=A0 Reading it now, I am extremely worried by the scope
 creep evident in the proposal.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">I strongly support a working group to=
 define an ID Events data format.=C2=A0 I just as strongly believe
 that specific event delivery mechanisms will necessarily be application-sp=
ecific and therefore MUST be explicitly be stated as being out of scope in =
the working group charter.=C2=A0 Attempting to specify a particular event d=
elivery mechanism will take something
 that could be simple and quick to approve and bog it down in necessarily a=
pplication-specific debates.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Should event delivery be reliable?=C2=
=A0 That=E2=80=99s an application-specific decision.</span><u></u><u></u></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Should events be idempotent?=C2=A0 Th=
at=E2=80=99s an application-specific decision.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Should events be unicast, multicast, =
or broadcast?=C2=A0 That=E2=80=99s an application-specific decision.</span>=
<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Should events have categories with ca=
tegory-specific subscriptions?=C2=A0 That=E2=80=99s an application-specific
 decision.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">Should only one party at a time be ab=
le to register for delivery of events or should multiple parties
 be able to request delivery?=C2=A0 That=E2=80=99s an application-specific =
decision.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">I could continue with this list, but =
I think you all get the point=E2=80=A6</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">If we start debating application-spec=
ific event delivery mechanisms, we=E2=80=99ll please almost no one, since
 nearly all applications have different event delivery requirements.=C2=A0 =
We MUST explicitly rule all delivery mechanisms as being out of scope.</spa=
n><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">If we define only a data format, we c=
an quickly produce a very useful specification.=C2=A0 If we don=E2=80=99t,
 we=E2=80=99ll get bogged down in the mud of debating which applications we=
=E2=80=99re catering to and which we aren=E2=80=99t =E2=80=93 an exercise o=
f picking favorites and limiting applicability of the specification.=C2=A0 =
That way is a slow, painful descent into standards quicksand =E2=80=93 some=
thing
 we must avoid.=C2=A0 Having a standard ID events representation is far too=
 important to tie to a particular limited event delivery mechanism.</span><=
u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<wbr>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 Sincerely,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#002060">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<wbr>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><a name=3D"m_-1072212518660021386_m_5165357944078144=
809_m_3022367059336893565_m_1461024254222911"><span style=3D"font-size:11.0=
pt;font-family:&quot;Calibri&quot;,sans-serif;color:#002060">=C2=A0</span><=
/a><u></u><u></u></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Id-event [mailto:<a href=3D"ma=
ilto:id-event-bounces@ietf.org" target=3D"_blank">id-event-bounces@ietf.<wb=
r>org</a>]
<b>On Behalf Of </b>Alan Karp<br>
<b>Sent:</b> Thursday, May 5, 2016 9:43 PM<br>
<b>To:</b> Morteza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.c=
om" target=3D"_blank">moransar@cisco.com</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-event@=
ietf.org</a><br>
<b>Subject:</b> Re: [Id-event] Straw man text for proposed charter</span><u=
></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I don&#39;t see anything about access control for pu=
blishing events and subscribing to them.=C2=A0 I also think the spec should=
 allow filters on subscriptions.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
--------------<br>
Alan Karp<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (mor=
ansar) &lt;<a href=3D"mailto:moransar@cisco.com" target=3D"_blank">moransar=
@cisco.com</a>&gt; wrote:<u></u><u></u></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Hi folks,</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">At IIW a few of us (Phil, William, Adam=
, and I) huddled for a bit and put together the attached as a
 straw man charter proposal to start the discussion. Please send your comme=
nts and suggestions for any changes or propose a new one if you think its n=
ecessary.</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Cheers,</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Morteza</span><u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank=
">https://www.ietf.org/mailman/l<wbr>istinfo/id-event</a><u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">______________________________<wbr>_________________=
<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank=
">https://www.ietf.org/mailman/l<wbr>istinfo/id-event</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">______________________________<wbr>_________________=
<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank=
">https://www.ietf.org/mailman/l<wbr>istinfo/id-event</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank=
">https://www.ietf.org/mailman/l<wbr>istinfo/id-event</a><u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>
</div></blockquote><blockquote type=3D"cite"><div><span>___________________=
___________<wbr>_________________</span><br><span>Id-event mailing list</sp=
an><br><span><a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-even=
t@ietf.org</a></span><br><span><a href=3D"https://www.ietf.org/mailman/list=
info/id-event" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo=
/id-event</a></span><br></div></blockquote></div></div></div></blockquote><=
/div><br></div>

--001a114cef06e42205053be02b3f--


From nobody Wed Sep  7 09:35:47 2016
Return-Path: <vivek_biswas@yahoo.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE59C12B3B7 for <id-event@ietfa.amsl.com>; Wed,  7 Sep 2016 09:35:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.227
X-Spam-Level: 
X-Spam-Status: No, score=-4.227 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UVVV23PThx-E for <id-event@ietfa.amsl.com>; Wed,  7 Sep 2016 09:35:40 -0700 (PDT)
Received: from nm40-vm2.bullet.mail.ne1.yahoo.com (nm40-vm2.bullet.mail.ne1.yahoo.com [98.138.229.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E34A312B23B for <id-event@ietf.org>; Wed,  7 Sep 2016 09:35:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1473266139; bh=2Trl6S67gj6OuKsdIAwjUYr9rXPqhU02giWb49QMjqs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=OGqrT14IOlHssoI56vDZCaBSPKXzfR7nV73R/4LP9s32XCi6D1B7wvOFTDRiH/dyj/mH7UQkJtrDCst62Qo0y7rdVto0Cm8g0tO+R3Ho2pR1FoN8QERQWGsJDK/puuQMcvEuEpuR6Yu6sqp/pUnhDZh5ImST/GzQiAbTE2q/S8aKhGnHJj1r13JcaUJgSlYAmuuodT695KrcWgOYJw5nJxcDWKlVpp9S4szXT+vOEYEXBOp960iuqHC2wZW6b9gniSf08iaE6ItTivR4EaE0el8BJ8pdUtP8mgTfLpg4vOU0dwpqiMRTxdWB1s7AvVdN58T9GFML2KMGScOuHaKMkg==
Received: from [127.0.0.1] by nm40.bullet.mail.ne1.yahoo.com with NNFMP; 07 Sep 2016 16:35:39 -0000
Received: from [98.138.100.112] by nm40.bullet.mail.ne1.yahoo.com with NNFMP;  07 Sep 2016 16:32:58 -0000
Received: from [98.138.89.234] by tm103.bullet.mail.ne1.yahoo.com with NNFMP;  07 Sep 2016 16:32:57 -0000
Received: from [127.0.0.1] by omp1049.mail.ne1.yahoo.com with NNFMP; 07 Sep 2016 16:32:57 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 900425.29843.bm@omp1049.mail.ne1.yahoo.com
X-YMail-OSG: AMvfrrIVM1moxjUo6iTEtOvOxK9HBS5FTSFe82lRAvuUyRyYf0J2OiCZ1y4846M Cf.t8MQxHhLHDJSANhwDV8CvgBozUc6WcLgGuUpuVr8ge8fhWVWQYXXsXrE7Z2rpHYnnfRJ5lfkN T4v8H1X7pyFaAx363pvLql4H9VzOZtvSTidctnhNEwJ95iGQbBZrjIguVOkdu6IjvxoBMlvDy_Cw x0pgMCvwtBhs6zQcEGKwKGu1anZ_aPdsyVliuEoeeSNg3I1zLkTbYrhhICGm1imS5ayTVvr9rYEz ELFpS1Y_aetL6.llfl3k4QAOu_Hjm8WRzbuTsoUrswt0fKvOH4kmHU085Sf2wpuxIQYw3XAiUoTY kLC3pbwJx9pzQiGt4Vnzt.y1fkAMCS6Nble_aflUAchfFEHXsIqCNSj0yTRf23notDLWK7G3e7.b EJSHx6PK_8AfPJP0M4DS8dp_0LY6BOfrN93d5Ly8VZKDNAk9kUxHlt0QzwEQsPDOCVlsmN76Wt7E md1CqAa9JTI.EO7rp5MxYRJMBQmMzs_GIviJ4
Received: from jws10053.mail.ne1.yahoo.com by sendmailws124.mail.ne1.yahoo.com;  Wed, 07 Sep 2016 16:32:57 +0000; 1473265977.414
Date: Wed, 7 Sep 2016 16:32:56 +0000 (UTC)
From: Vivek Biswas <vivek_biswas@yahoo.com>
To: Mike Jones <Michael.Jones@microsoft.com>,  "id-event@ietf.org" <id-event@ietf.org>
Message-ID: <595998295.367982.1473265977000@mail.yahoo.com>
In-Reply-To: <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_367981_1369448070.1473265976971"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/qwhD9ah6xO6UPiv4LYI6L21Yurw>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, Marius Scurtescu <mscurtescu@google.com>, "Morteza Ansari \(moransar\)" <moransar@cisco.com>, William Denniss <wdenniss@google.com>, Leif Johansson <leifj@sunet.se>, "Phil Hunt \(IDM\)" <phil.hunt@oracle.com>
Subject: Re: [Id-event] Straw man text for proposed charter
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Vivek Biswas <vivek_biswas@yahoo.com>
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2016 16:35:44 -0000

------=_Part_367981_1369448070.1473265976971
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Mike,
I believe there is one more item that MAY be added.
After the line "Methods for validating event feed subscriptions""Obligation=
 that may be needed to be fulfilled upon validating an event feed".
RegardsVivek BiswasConsulting Member @SecurityOracle.



      From: Mike Jones <Michael.Jones@microsoft.com>
 To: "id-event@ietf.org" <id-event@ietf.org>=20
Cc: Marius Scurtescu <mscurtescu@google.com>; Alexey Melnikov <aamelnikov@f=
astmail.fm>; Morteza Ansari (moransar) <moransar@cisco.com>; William Dennis=
s <wdenniss@google.com>; Leif Johansson <leifj@sunet.se>; Phil Hunt (IDM) <=
phil.hunt@oracle.com>
 Sent: Tuesday, September 6, 2016 5:01 PM
 Subject: Re: [Id-event] Straw man text for proposed charter
  =20
#yiv8143991987 #yiv8143991987 -- _filtered #yiv8143991987 {panose-1:2 4 5 3=
 5 4 6 3 2 4;} _filtered #yiv8143991987 {font-family:Calibri;panose-1:2 15 =
5 2 2 2 4 3 2 4;}#yiv8143991987 #yiv8143991987 p.yiv8143991987MsoNormal, #y=
iv8143991987 li.yiv8143991987MsoNormal, #yiv8143991987 div.yiv8143991987Mso=
Normal {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv8143991987 a=
:link, #yiv8143991987 span.yiv8143991987MsoHyperlink {color:blue;text-decor=
ation:underline;}#yiv8143991987 a:visited, #yiv8143991987 span.yiv814399198=
7MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv81439919=
87 p.yiv8143991987msonormal0, #yiv8143991987 li.yiv8143991987msonormal0, #y=
iv8143991987 div.yiv8143991987msonormal0 {margin-right:0in;margin-left:0in;=
font-size:12.0pt;}#yiv8143991987 span.yiv8143991987hoenzb {}#yiv8143991987 =
span.yiv8143991987EmailStyle19 {color:#002060;}#yiv8143991987 .yiv814399198=
7MsoChpDefault {} _filtered #yiv8143991987 {margin:1.0in 1.0in 1.0in 1.0in;=
}#yiv8143991987 div.yiv8143991987WordSection1 {}#yiv8143991987 An updated a=
nd simplified charter is attached.=C2=A0 This draft has been reviewed by Ph=
il Hunt, William Denniss, Marius Scurtescu.  =C2=A0 Input from Alexey Melni=
kov is that we should probably charter a working group, rather than try to =
go the AD-sponsored route.=C2=A0 Therefore, please review this draft charte=
r and let us know if you think it=E2=80=99s ready to go.  =C2=A0 =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 Thanks, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- Mike  =C2=A0 From: Sara=
h Squire [mailto:sarah@engageidentity.com]
Sent: Thursday, July 14, 2016 10:59 PM
To: Phil Hunt (IDM) <phil.hunt@oracle.com>
Cc: Mike Jones <Michael.Jones@microsoft.com>; Alan Karp <alanhkarp@gmail.co=
m>; Vivek Biswas <vivek_biswas@yahoo.com>; Morteza Ansari (moransar) <moran=
sar@cisco.com>; id-event@ietf.org
Subject: Re: [Id-event] Straw man text for proposed charter  =C2=A0 Just su=
bmitting my two cents in writing before we hopefully have a chance to meet =
about this next week...  =C2=A0 Looking at this charter from the perspectiv=
e of the OIDF HEART working group, I think it's going down a good path. In =
terms of the data format, this is less structured than what I was envisioni=
ng, but we could easily do a healthcare-specific profile of whatever data f=
ormat comes out in the end, so it's better to be too broad than too narrow =
as far as our interests are concerned.  =C2=A0 The transport layer however,=
 has some added complexity. In our context, we're shooting for interoperabi=
lity, so we'd prefer something constrained. I appreciate Mike's input that =
these are application layer decisions. However, if we're talking about clou=
d provider-to-cloud provider communication, that certainly is facilitated b=
y a well-defined transport layer. Again, we're willing to profile whatever =
the group comes up with for our own ends, but I don't really see the benefi=
t of having a loosely defined transport layer - it just seems like more wor=
k for all the implementers to actually agree on endpoints on a case-by-case=
 basis.  =C2=A0 Looking forward to discussing further in Berlin!  =C2=A0 Sa=
rah=20
 Sarah Squire Engage Identity http://engageidentity.com  =C2=A0 On Sat, May=
 7, 2016 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com> wrote:=20
We also set things up so even a domain specific event can be extended.=C2=
=A0  =C2=A0 Eg on a password reset event, so event publishers may want to a=
dd security domain specific attributes. The spec lets them do that while av=
oiding interop issues.=C2=A0  =C2=A0 I believe in the spec we had the examp=
le of an account reset and the publisher adds reset count as an extension.=
=C2=A0

Phil=20
On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com> wrote:=
=20
Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 so c=
ommon claims can be defined once and then reused. =C2=A0 From:Vivek Biswas
Sent: Saturday, May 7, 2016 1:24 PM
To: Mike Jones
Cc: Alan Karp; Morteza Ansari (moransar); id-event@ietf.org
Subject: Re: [Id-event] Straw man text for proposed charter =C2=A0 Yes, I a=
gree that the claims can be application specific, however there is a possib=
ility to define claims which are domain specific. Thereby claims generated =
in one application could be understood by another =C2=A0application within =
the same domain.  =C2=A0 With microservices based architecture getting lot =
of attention, if two different micro services defining different claims for=
 the same claim, it can create confusion.  =C2=A0 Nevertheless this well de=
fined claims for a particular domain can be an extension to the core specif=
ication.  =C2=A0 -Vivek Biswas =C2=A0 Consulting Member, Oracle

Sent from my iPhone=20
On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com> wrote:=
=20
Thanks Alan, =C2=A0 Interoperability will be on a per-application basis, ju=
st like JWT interoperability.=C2=A0 The claims needed in an identity event =
are application-specific, just like claims are for JWTs.=C2=A0 This is the =
same standards posture and JWTs are a huge success =E2=80=93 including for =
interoperability, even if I do say so myself. =C2=A0 =C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Best wishes, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 -- Mike =C2=A0 =C2=A0 =C2=A0 =C2=A0 From:Alan Karp
Sent: Saturday, May 7, 2016 10:23 AM
To: Mike Jones
Cc: Morteza Ansari (moransar);id-event@ietf.org
Subject: Re: [Id-event] Straw man text for proposed charter =C2=A0 As one w=
ho proposed doing more, I believe that your position is valid.=C2=A0 My onl=
y question is whether or not that will be enough for interoperability.=20
=20
--------------
Alan Karp  =C2=A0 On Thu, May 5, 2016 at 10:00 PM, Mike Jones <Michael.Jone=
s@microsoft.com> wrote:=20
Thanks guys, for writing the initial charter text.=C2=A0 Reading it now, I =
am extremely worried by the scope creep evident in the proposal. =C2=A0 I s=
trongly support a working group to define an ID Events data format.=C2=A0 I=
 just as strongly believe that specific event delivery mechanisms will nece=
ssarily be application-specific and therefore MUST be explicitly be stated =
as being out of scope in the working group charter.=C2=A0 Attempting to spe=
cify a particular event delivery mechanism will take something that could b=
e simple and quick to approve and bog it down in necessarily application-sp=
ecific debates. =C2=A0 Should event delivery be reliable?=C2=A0 That=E2=80=
=99s an application-specific decision. Should events be idempotent?=C2=A0 T=
hat=E2=80=99s an application-specific decision. Should events be unicast, m=
ulticast, or broadcast?=C2=A0 That=E2=80=99s an application-specific decisi=
on. Should events have categories with category-specific subscriptions?=C2=
=A0 That=E2=80=99s an application-specific decision. Should only one party =
at a time be able to register for delivery of events or should multiple par=
ties be able to request delivery?=C2=A0 That=E2=80=99s an application-speci=
fic decision. I could continue with this list, but I think you all get the =
point=E2=80=A6 =C2=A0 If we start debating application-specific event deliv=
ery mechanisms, we=E2=80=99ll please almost no one, since nearly all applic=
ations have different event delivery requirements.=C2=A0 We MUST explicitly=
 rule all delivery mechanisms as being out of scope. =C2=A0 If we define on=
ly a data format, we can quickly produce a very useful specification.=C2=A0=
 If we don=E2=80=99t, we=E2=80=99ll get bogged down in the mud of debating =
which applications we=E2=80=99re catering to and which we aren=E2=80=99t =
=E2=80=93 an exercise of picking favorites and limiting applicability of th=
e specification.=C2=A0 That way is a slow, painful descent into standards q=
uicksand =E2=80=93 something we must avoid.=C2=A0 Having a standard ID even=
ts representation is far too important to tie to a particular limited event=
 delivery mechanism. =C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Si=
ncerely, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- Mike =C2=A0 From: Id=
-event [mailto:id-event-bounces@ietf.org]On Behalf Of Alan Karp
Sent: Thursday, May 5, 2016 9:43 PM
To: Morteza Ansari (moransar) <moransar@cisco.com>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Straw man text for proposed charter =C2=A0 I don't =
see anything about access control for publishing events and subscribing to =
them.=C2=A0 I also think the spec should allow filters on subscriptions.=20
=20
--------------
Alan Karp =C2=A0 On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar)=
 <moransar@cisco.com> wrote:=20
Hi folks, =C2=A0 At IIW a few of us (Phil, William, Adam, and I) huddled fo=
r a bit and put together the attached as a straw man charter proposal to st=
art the discussion. Please send your comments and suggestions for any chang=
es or propose a new one if you think its necessary. =C2=A0 =C2=A0 Cheers, M=
orteza=20
_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event=20
=C2=A0=20
 =C2=A0=20

_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event=20


_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event=20

_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event=20
 =C2=A0=20
_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event


  =20
------=_Part_367981_1369448070.1473265976971
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:verdana, helvetica, sans-serif;font-size:16px"><div id=3D"yui_3_=
16_0_ym19_1_1473265247048_12746">Hi Mike,</div><div id=3D"yui_3_16_0_ym19_1=
_1473265247048_12746"><br></div><div id=3D"yui_3_16_0_ym19_1_1473265247048_=
12746">I believe there is one more item that MAY be added.</div><div id=3D"=
yui_3_16_0_ym19_1_1473265247048_12746"><br></div><div id=3D"yui_3_16_0_ym19=
_1_1473265247048_12746" dir=3D"ltr">After the line "<span style=3D"font-fam=
ily: pg-1ff9; line-height: 37.2852px; white-space: pre-wrap; -webkit-text-s=
troke: 0.6px rgba(0, 0, 0, 0);" id=3D"yui_3_16_0_ym19_1_1473265247048_12804=
"><font size=3D"3" id=3D"yui_3_16_0_ym19_1_1473265247048_13077">Methods for=
 validating event feed subscriptions"</font></span></div><div id=3D"yui_3_1=
6_0_ym19_1_1473265247048_12746" dir=3D"ltr"><span style=3D"font-family: pg-=
1ff9; line-height: 37.2852px; white-space: pre-wrap; -webkit-text-stroke: 0=
.6px rgba(0, 0, 0, 0);" id=3D"yui_3_16_0_ym19_1_1473265247048_13175"><font =
size=3D"3" id=3D"yui_3_16_0_ym19_1_1473265247048_13174">"Obligation that ma=
y be needed to be fulfilled upon validating an event feed".</font></span></=
div><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746" dir=3D"ltr"><br></div=
><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746" dir=3D"ltr">Regards</div=
><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746" dir=3D"ltr">Vivek Biswas=
</div><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746" dir=3D"ltr">Consult=
ing Member @Security</div><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746"=
 dir=3D"ltr">Oracle.</div><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746"=
 dir=3D"ltr"><br></div><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746" di=
r=3D"ltr"><br></div><div class=3D"qtdSeparateBR"><br><br></div><div class=
=3D"yahoo_quoted" id=3D"yui_3_16_0_ym19_1_1473265247048_12800" style=3D"dis=
play: block;">  <div style=3D"font-family: verdana, helvetica, sans-serif; =
font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1473265247048_12799"> <div style=
=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Gr=
ande, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1473265247048_1=
2798"> <div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1473265247048_12797"> <font=
 size=3D"2" face=3D"Arial" id=3D"yui_3_16_0_ym19_1_1473265247048_12796"> <h=
r size=3D"1" id=3D"yui_3_16_0_ym19_1_1473265247048_12795"> <b><span style=
=3D"font-weight:bold;">From:</span></b> Mike Jones &lt;Michael.Jones@micros=
oft.com&gt;<br> <b><span style=3D"font-weight: bold;">To:</span></b> "id-ev=
ent@ietf.org" &lt;id-event@ietf.org&gt; <br><b><span style=3D"font-weight: =
bold;">Cc:</span></b> Marius Scurtescu &lt;mscurtescu@google.com&gt;; Alexe=
y Melnikov &lt;aamelnikov@fastmail.fm&gt;; Morteza Ansari (moransar) &lt;mo=
ransar@cisco.com&gt;; William Denniss &lt;wdenniss@google.com&gt;; Leif Joh=
ansson &lt;leifj@sunet.se&gt;; Phil Hunt (IDM) &lt;phil.hunt@oracle.com&gt;=
<br> <b><span style=3D"font-weight: bold;">Sent:</span></b> Tuesday, Septem=
ber 6, 2016 5:01 PM<br> <b><span style=3D"font-weight: bold;">Subject:</spa=
n></b> Re: [Id-event] Straw man text for proposed charter<br> </font> </div=
> <div class=3D"y_msg_container"><br><div id=3D"yiv8143991987"><style>#yiv8=
143991987 #yiv8143991987 --
=20
 _filtered #yiv8143991987 {panose-1:2 4 5 3 5 4 6 3 2 4;}
 _filtered #yiv8143991987 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 =
4;}
#yiv8143991987 =20
#yiv8143991987 p.yiv8143991987MsoNormal, #yiv8143991987 li.yiv8143991987Mso=
Normal, #yiv8143991987 div.yiv8143991987MsoNormal
=09{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}
#yiv8143991987 a:link, #yiv8143991987 span.yiv8143991987MsoHyperlink
=09{color:blue;text-decoration:underline;}
#yiv8143991987 a:visited, #yiv8143991987 span.yiv8143991987MsoHyperlinkFoll=
owed
=09{color:purple;text-decoration:underline;}
#yiv8143991987 p.yiv8143991987msonormal0, #yiv8143991987 li.yiv8143991987ms=
onormal0, #yiv8143991987 div.yiv8143991987msonormal0
=09{margin-right:0in;margin-left:0in;font-size:12.0pt;}
#yiv8143991987 span.yiv8143991987hoenzb
=09{}
#yiv8143991987 span.yiv8143991987EmailStyle19
=09{color:#002060;}
#yiv8143991987 .yiv8143991987MsoChpDefault
=09{}
 _filtered #yiv8143991987 {margin:1.0in 1.0in 1.0in 1.0in;}
#yiv8143991987 div.yiv8143991987WordSection1
=09{}
#yiv8143991987 </style><div>
<div class=3D"yiv8143991987WordSection1">
<div class=3D"yiv8143991987MsoNormal"><span style=3D"font-size:11.0pt;">An =
updated and simplified charter is attached.&nbsp; This draft has been revie=
wed by Phil Hunt, William Denniss, Marius Scurtescu.</span></div>=20
<div class=3D"yiv8143991987MsoNormal"><span style=3D"font-size:11.0pt;"> &n=
bsp;</span></div>=20
<div class=3D"yiv8143991987MsoNormal"><span style=3D"font-size:11.0pt;">Inp=
ut from Alexey Melnikov is that we should probably charter a working group,=
 rather than try to go the AD-sponsored route.&nbsp; Therefore, please revi=
ew this draft
 charter and let us know if you think it=E2=80=99s ready to go.</span></div=
>=20
<div class=3D"yiv8143991987MsoNormal"><span style=3D"font-size:11.0pt;"> &n=
bsp;</span></div>=20
<div class=3D"yiv8143991987MsoNormal"><span style=3D"font-size:11.0pt;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; Thanks,</span></div>=20
<div class=3D"yiv8143991987MsoNormal"><span style=3D"font-size:11.0pt;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; -- Mike</span></div>=20
<div class=3D"yiv8143991987MsoNormal"><a rel=3D"nofollow" shape=3D"rect" na=
me=3D"_MailEndCompose" href=3D""><span style=3D"font-size:11.0pt;"> &nbsp;<=
/span></a></div>=20
<span style=3D""></span>
<div class=3D"yiv8143991987yqt5176189511" id=3D"yiv8143991987yqt64133"><div=
 class=3D"yiv8143991987MsoNormal"><b><span style=3D"font-size:11.0pt;">From=
:</span></b><span style=3D"font-size:11.0pt;"> Sarah Squire [mailto:sarah@e=
ngageidentity.com]
<br clear=3D"none">
<b>Sent:</b> Thursday, July 14, 2016 10:59 PM<br clear=3D"none">
<b>To:</b> Phil Hunt (IDM) &lt;phil.hunt@oracle.com&gt;<br clear=3D"none">
<b>Cc:</b> Mike Jones &lt;Michael.Jones@microsoft.com&gt;; Alan Karp &lt;al=
anhkarp@gmail.com&gt;; Vivek Biswas &lt;vivek_biswas@yahoo.com&gt;; Morteza=
 Ansari (moransar) &lt;moransar@cisco.com&gt;; id-event@ietf.org<br clear=
=3D"none">
<b>Subject:</b> Re: [Id-event] Straw man text for proposed charter</span></=
div>=20
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
<div>
<div>
<div class=3D"yiv8143991987MsoNormal">Just submitting my two cents in writi=
ng before we hopefully have a chance to meet about this next week...</div>=
=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
</div>
<div class=3D"yiv8143991987MsoNormal">Looking at this charter from the pers=
pective of the OIDF HEART working group, I think it's going down a good pat=
h. In terms of the data format, this is less structured than what I was env=
isioning, but we could easily do a healthcare-specific
 profile of whatever data format comes out in the end, so it's better to be=
 too broad than too narrow as far as our interests are concerned.</div>=20
<div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal">The transport layer however, has some=
 added complexity. In our context, we're shooting for interoperability, so =
we'd prefer something constrained. I appreciate Mike's input that these are=
 application layer decisions. However, if we're talking
 about cloud provider-to-cloud provider communication, that certainly is fa=
cilitated by a well-defined transport layer. Again, we're willing to profil=
e whatever the group comes up with for our own ends, but I don't really see=
 the benefit of having a loosely
 defined transport layer - it just seems like more work for all the impleme=
nters to actually agree on endpoints on a case-by-case basis.</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal">Looking forward to discussing further=
 in Berlin!</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal">Sarah</div>=20
</div>
</div></div>
<div>
<div class=3D"yiv8143991987yqt5176189511" id=3D"yiv8143991987yqt99533"><div=
 class=3D"yiv8143991987MsoNormal"><br clear=3D"all">
</div>=20
<div>
<div>
<div>
<div>
<div class=3D"yiv8143991987MsoNormal"><span style=3D"color:#888888;">Sarah =
Squire</span></div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal"><span style=3D"color:#888888;">Engage=
 Identity</span></div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal"><span style=3D"color:#888888;"><a rel=
=3D"nofollow" shape=3D"rect" target=3D"_blank" href=3D"http://engageidentit=
y.com/"><span style=3D"color:#1155CC;">http://engageidentity.com</span></a>=
</span></div>=20
</div>
</div>
</div>
</div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
<div>
<div class=3D"yiv8143991987MsoNormal">On Sat, May 7, 2016 at 6:53 PM, Phil =
Hunt (IDM) &lt;<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:phil.hu=
nt@oracle.com" target=3D"_blank" href=3D"mailto:phil.hunt@oracle.com">phil.=
hunt@oracle.com</a>&gt; wrote:</div>=20
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in;">
<div>
<div>
<div class=3D"yiv8143991987MsoNormal">We also set things up so even a domai=
n specific event can be extended.&nbsp;</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal">Eg on a password reset event, so even=
t publishers may want to add security domain specific attributes. The spec =
lets them do that while avoiding interop issues.&nbsp;</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal">I believe in the spec we had the exam=
ple of an account reset and the publisher adds reset count as an extension.=
&nbsp;<span style=3D"color:#888888;"><br clear=3D"none">
<br clear=3D"none">
<span class=3D"yiv8143991987hoenzb">Phil</span></span></div>=20
</div>
<div>
<div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D"margin-bottom:12.0pt;"><br c=
lear=3D"none">
On May 7, 2016, at 13:31, Mike Jones &lt;<a rel=3D"nofollow" shape=3D"rect"=
 ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" href=3D"m=
ailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrot=
e:</div>=20
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt;">
<div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D"">Indeed, that=E2=80=99s why=
 there=E2=80=99s a claims registry =E2=80=93 so common claims can be define=
d once and then reused.</div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D"">&nbsp;</div>=20
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in;">
<div class=3D"yiv8143991987MsoNormal" style=3D""><b>From:
</b><a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:vivek_biswas@yahoo=
.com" target=3D"_blank" href=3D"mailto:vivek_biswas@yahoo.com">Vivek Biswas=
</a><br clear=3D"none">
<b>Sent: </b>Saturday, May 7, 2016 1:24 PM<br clear=3D"none">
<b>To: </b><a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Michael.Jon=
es@microsoft.com" target=3D"_blank" href=3D"mailto:Michael.Jones@microsoft.=
com">Mike Jones</a><br clear=3D"none">
<b>Cc: </b><a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:alanhkarp@g=
mail.com" target=3D"_blank" href=3D"mailto:alanhkarp@gmail.com">Alan Karp</=
a>; <a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:moransar@cisco.com=
" target=3D"_blank" href=3D"mailto:moransar@cisco.com">
Morteza Ansari (moransar)</a>; <a rel=3D"nofollow" shape=3D"rect" ymailto=
=3D"mailto:id-event@ietf.org" target=3D"_blank" href=3D"mailto:id-event@iet=
f.org">
id-event@ietf.org</a><br clear=3D"none">
<b>Subject: </b>Re: [Id-event] Straw man text for proposed charter</div>=20
</div>
<div class=3D"yiv8143991987MsoNormal" style=3D"">&nbsp;</div>=20
</div>
<div>
<div>
<div class=3D"yiv8143991987MsoNormal">Yes, I agree that the claims can be a=
pplication specific, however there is a possibility to define claims which =
are domain specific. Thereby claims generated in one application could be u=
nderstood by another &nbsp;application within the same
 domain.</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal">With microservices based architecture=
 getting lot of attention, if two different micro services defining differe=
nt claims for the same claim, it can create confusion.</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal">Nevertheless this well defined claims=
 for a particular domain can be an extension to the core specification.</di=
v>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal">-Vivek Biswas</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal">&nbsp; Consulting Member, Oracle<br c=
lear=3D"none">
<br clear=3D"none">
Sent from my iPhone</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D"margin-bottom:12.0pt;"><br c=
lear=3D"none">
On May 7, 2016, at 1:04 PM, Mike Jones &lt;<a rel=3D"nofollow" shape=3D"rec=
t" ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" href=3D=
"mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wr=
ote:</div>=20
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt;">
<div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D"">Thanks Alan,</div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D"">&nbsp;</div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"color:#0020=
60;">Interoperability will be on a per-application basis, just like JWT int=
eroperability.&nbsp; The claims needed in an identity event are application=
-specific,
 just like claims are for JWTs.&nbsp; This is the same standards posture an=
d JWTs are a huge success =E2=80=93 including for interoperability, even if=
 I do say so myself.</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"color:#0020=
60;">&nbsp;</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"color:#0020=
60;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Best wishes,</span></div>=
=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"color:#0020=
60;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D"">&nbsp;</div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D"">&nbsp;</div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D"">&nbsp;</div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D"">&nbsp;</div>=20
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in;">
<div class=3D"yiv8143991987MsoNormal" style=3D""><b>From:
</b><a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:alanhkarp@gmail.co=
m" target=3D"_blank" href=3D"mailto:alanhkarp@gmail.com">Alan Karp</a><br c=
lear=3D"none">
<b>Sent: </b>Saturday, May 7, 2016 10:23 AM<br clear=3D"none">
<b>To: </b><a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Michael.Jon=
es@microsoft.com" target=3D"_blank" href=3D"mailto:Michael.Jones@microsoft.=
com">Mike Jones</a><br clear=3D"none">
<b>Cc: </b><a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:moransar@ci=
sco.com" target=3D"_blank" href=3D"mailto:moransar@cisco.com">Morteza Ansar=
i (moransar)</a>;
<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:id-event@ietf.org" tar=
get=3D"_blank" href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a><br c=
lear=3D"none">
<b>Subject: </b>Re: [Id-event] Straw man text for proposed charter</div>=20
</div>
<div class=3D"yiv8143991987MsoNormal" style=3D"">&nbsp;</div>=20
</div>
<div>
<div>
<div class=3D"yiv8143991987MsoNormal"><span style=3D"font-size:9.5pt;">As o=
ne who proposed doing more, I believe that your position is valid.&nbsp; My=
 only question is whether or not that will be enough for interoperability.<=
/span></div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal"><br clear=3D"all">
</div>=20
<div>
<div>
<div class=3D"yiv8143991987MsoNormal"><br clear=3D"none">
--------------<br clear=3D"none">
Alan Karp</div>=20
</div>
</div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
<div>
<div class=3D"yiv8143991987MsoNormal">On Thu, May 5, 2016 at 10:00 PM, Mike=
 Jones &lt;<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Michael.Jon=
es@microsoft.com" target=3D"_blank" href=3D"mailto:Michael.Jones@microsoft.=
com">Michael.Jones@microsoft.com</a>&gt; wrote:</div>=20
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in;">
<div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">Thanks guys, for writing the initial charter text.&nbsp; Reading it=
 now, I am extremely worried by the scope
 creep evident in the proposal.</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">&nbsp;</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">I strongly support a working group to define an ID Events data form=
at.&nbsp; I just as strongly believe
 that specific event delivery mechanisms will necessarily be application-sp=
ecific and therefore MUST be explicitly be stated as being out of scope in =
the working group charter.&nbsp; Attempting to specify a particular event d=
elivery mechanism will take something
 that could be simple and quick to approve and bog it down in necessarily a=
pplication-specific debates.</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">&nbsp;</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">Should event delivery be reliable?&nbsp; That=E2=80=99s an applicat=
ion-specific decision.</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">Should events be idempotent?&nbsp; That=E2=80=99s an application-sp=
ecific decision.</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">Should events be unicast, multicast, or broadcast?&nbsp; That=E2=80=
=99s an application-specific decision.</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">Should events have categories with category-specific subscriptions?=
&nbsp; That=E2=80=99s an application-specific
 decision.</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">Should only one party at a time be able to register for delivery of=
 events or should multiple parties
 be able to request delivery?&nbsp; That=E2=80=99s an application-specific =
decision.</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">I could continue with this list, but I think you all get the point=
=E2=80=A6</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">&nbsp;</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">If we start debating application-specific event delivery mechanisms=
, we=E2=80=99ll please almost no one, since
 nearly all applications have different event delivery requirements.&nbsp; =
We MUST explicitly rule all delivery mechanisms as being out of scope.</spa=
n></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">&nbsp;</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">If we define only a data format, we can quickly produce a very usef=
ul specification.&nbsp; If we don=E2=80=99t,
 we=E2=80=99ll get bogged down in the mud of debating which applications we=
=E2=80=99re catering to and which we aren=E2=80=99t =E2=80=93 an exercise o=
f picking favorites and limiting applicability of the specification.&nbsp; =
That way is a slow, painful descent into standards quicksand =E2=80=93 some=
thing
 we must avoid.&nbsp; Having a standard ID events representation is far too=
 important to tie to a particular limited event delivery mechanism.</span><=
/div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">&nbsp;</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sincerely,</span></div>=
=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
1.0pt;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><a rel=3D"nofollow" shape=
=3D"rect" name=3D"m_3022367059336893565_m_1461024254222911" href=3D""><span=
 style=3D"font-size:11.0pt;">&nbsp;</span></a></div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D""><b><span style=3D"font-siz=
e:11.0pt;">From:</span></b><span style=3D"font-size:11.0pt;"> Id-event [mai=
lto:<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:id-event-bounces@i=
etf.org" target=3D"_blank" href=3D"mailto:id-event-bounces@ietf.org">id-eve=
nt-bounces@ietf.org</a>]
<b>On Behalf Of </b>Alan Karp<br clear=3D"none">
<b>Sent:</b> Thursday, May 5, 2016 9:43 PM<br clear=3D"none">
<b>To:</b> Morteza Ansari (moransar) &lt;<a rel=3D"nofollow" shape=3D"rect"=
 ymailto=3D"mailto:moransar@cisco.com" target=3D"_blank" href=3D"mailto:mor=
ansar@cisco.com">moransar@cisco.com</a>&gt;<br clear=3D"none">
<b>Cc:</b> <a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:id-event@ie=
tf.org" target=3D"_blank" href=3D"mailto:id-event@ietf.org">id-event@ietf.o=
rg</a><br clear=3D"none">
<b>Subject:</b> Re: [Id-event] Straw man text for proposed charter</span></=
div>=20
<div class=3D"yiv8143991987MsoNormal" style=3D"">&nbsp;</div>=20
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D"">I don't see anything about=
 access control for publishing events and subscribing to them.&nbsp; I also=
 think the spec should allow filters on subscriptions.</div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D""><br clear=3D"all">
</div>=20
<div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D""><br clear=3D"none">
--------------<br clear=3D"none">
Alan Karp</div>=20
</div>
</div>
<div class=3D"yiv8143991987MsoNormal" style=3D"">&nbsp;</div>=20
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D"">On Thu, May 5, 2016 at 11:=
18 AM, Morteza Ansari (moransar) &lt;<a rel=3D"nofollow" shape=3D"rect" yma=
ilto=3D"mailto:moransar@cisco.com" target=3D"_blank" href=3D"mailto:moransa=
r@cisco.com">moransar@cisco.com</a>&gt; wrote:</div>=20
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt;">
<div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
0.5pt;">Hi folks,</span></div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
0.5pt;">&nbsp;</span></div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
0.5pt;">At IIW a few of us (Phil, William, Adam, and I) huddled for a bit a=
nd put together the attached as a
 straw man charter proposal to start the discussion. Please send your comme=
nts and suggestions for any changes or propose a new one if you think its n=
ecessary.</span></div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
0.5pt;">&nbsp;</span></div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
0.5pt;">&nbsp;</span></div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
0.5pt;">Cheers,</span></div>=20
</div>
<div>
<div class=3D"yiv8143991987MsoNormal" style=3D""><span style=3D"font-size:1=
0.5pt;">Morteza</span></div>=20
</div>
</div>
<div class=3D"yiv8143991987MsoNormal" style=3D"margin-bottom:12.0pt;"><br c=
lear=3D"none">
_______________________________________________<br clear=3D"none">
Id-event mailing list<br clear=3D"none">
<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Id-event@ietf.org" tar=
get=3D"_blank" href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br c=
lear=3D"none">
<a rel=3D"nofollow" shape=3D"rect" target=3D"_blank" href=3D"https://www.ie=
tf.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/listinfo/id-=
event</a></div>=20
</blockquote>
</div>
<div class=3D"yiv8143991987MsoNormal" style=3D"">&nbsp;</div>=20
</div>
</div>
</div>
</blockquote>
</div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
</div>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt;">
<div>
<div class=3D"yiv8143991987MsoNormal">_____________________________________=
__________<br clear=3D"none">
Id-event mailing list<br clear=3D"none">
<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Id-event@ietf.org" tar=
get=3D"_blank" href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br c=
lear=3D"none">
<a rel=3D"nofollow" shape=3D"rect" target=3D"_blank" href=3D"https://www.ie=
tf.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/listinfo/id-=
event</a></div>=20
</div>
</blockquote>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt;">
<div>
<div class=3D"yiv8143991987MsoNormal">_____________________________________=
__________<br clear=3D"none">
Id-event mailing list<br clear=3D"none">
<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Id-event@ietf.org" tar=
get=3D"_blank" href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br c=
lear=3D"none">
<a rel=3D"nofollow" shape=3D"rect" target=3D"_blank" href=3D"https://www.ie=
tf.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/listinfo/id-=
event</a></div>=20
</div>
</blockquote>
</div>
</div>
</div>
<div class=3D"yiv8143991987MsoNormal" style=3D"margin-bottom:12.0pt;"><br c=
lear=3D"none">
_______________________________________________<br clear=3D"none">
Id-event mailing list<br clear=3D"none">
<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Id-event@ietf.org" tar=
get=3D"_blank" href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br c=
lear=3D"none">
<a rel=3D"nofollow" shape=3D"rect" target=3D"_blank" href=3D"https://www.ie=
tf.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/listinfo/id-=
event</a></div>=20
</blockquote>
</div></div>
<div class=3D"yiv8143991987MsoNormal"> &nbsp;</div>=20
</div>
</div>
</div></div><br><div class=3D"yqt5176189511" id=3D"yqt18602">______________=
_________________________________<br clear=3D"none">Id-event mailing list<b=
r clear=3D"none"><a shape=3D"rect" ymailto=3D"mailto:Id-event@ietf.org" hre=
f=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br clear=3D"none"><a s=
hape=3D"rect" href=3D"https://www.ietf.org/mailman/listinfo/id-event" targe=
t=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br clear=3D=
"none"></div><br><br></div> </div> </div>  </div></div></body></html>
------=_Part_367981_1369448070.1473265976971--


From nobody Wed Sep  7 09:47:53 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD5912B3B7 for <id-event@ietfa.amsl.com>; Wed,  7 Sep 2016 09:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.709
X-Spam-Level: 
X-Spam-Status: No, score=-5.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T_ViAxg_WbCB for <id-event@ietfa.amsl.com>; Wed,  7 Sep 2016 09:47:51 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E85D412B2BD for <id-event@ietf.org>; Wed,  7 Sep 2016 09:47:50 -0700 (PDT)
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u87GlnxR004045 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <id-event@ietf.org>; Wed, 7 Sep 2016 16:47:50 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u87GlnuF006493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <id-event@ietf.org>; Wed, 7 Sep 2016 16:47:49 GMT
Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u87Glm1O021366 for <id-event@ietf.org>; Wed, 7 Sep 2016 16:47:49 GMT
Received: from [10.0.1.5] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 07 Sep 2016 09:47:48 -0700
From: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_706F7FED-E3EC-4570-BECC-F6E02E114DC3"
Message-Id: <7139447F-8A52-4A10-8373-AE4AADBAD031@oracle.com>
Date: Wed, 7 Sep 2016 09:47:47 -0700
To: id-event@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0021.oracle.com [141.146.126.233]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/1PgQojLhW02hO0B5Gn0QW-qvSO4>
Subject: [Id-event] Distribution draft - charter aligned revision coming
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2016 16:47:52 -0000

--Apple-Mail=_706F7FED-E3EC-4570-BECC-F6E02E114DC3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

FYI.  I am currently working to revise the current distribution draft to =
be in line with the proposed charter that went out yesterday.

For those that wish to follow along, the github repository for the =
drafts in progress is here:
https://github.com/independentid/Identity-Events/

As proposed in the charter, the distribution draft will only define HTTP =
POST based delivery (aka web callback).  A lot of this has been driven =
from operational experience from SCIM, and from the early work that has =
been done on RISC.  For example, sending an HTTP POST per SET appears =
pretty efficient and =E2=80=9Cbatch=E2=80=9D modes where multiple SETs =
are sent or retrieved at once end up creating complexity that doesn=E2=80=99=
t actually pay off.   HTTP POST has the advantage over GET that the =
receiver of the POST can validate the JWT and signal correct reception =
in the HTTP Response.

I hope to get the new charter aligned version of distribution published =
in time for consideration at the Seoul meeting.

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>






--Apple-Mail=_706F7FED-E3EC-4570-BECC-F6E02E114DC3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">FYI. &nbsp;I am currently working to revise the current =
distribution draft to be in line with the proposed charter that went out =
yesterday.<div class=3D""><br class=3D""></div><div class=3D"">For those =
that wish to follow along, the github repository for the drafts in =
progress is here:</div><div class=3D""><a =
href=3D"https://github.com/independentid/Identity-Events/" =
class=3D"">https://github.com/independentid/Identity-Events/</a></div><div=
 class=3D""><br class=3D""></div><div class=3D"">As proposed in the =
charter, the distribution draft will only define HTTP POST based =
delivery (aka web callback). &nbsp;A lot of this has been driven from =
operational experience from SCIM, and from the early work that has been =
done on RISC. &nbsp;For example, sending an HTTP POST per SET appears =
pretty efficient and =E2=80=9Cbatch=E2=80=9D modes where multiple SETs =
are sent or retrieved at once end up creating complexity that doesn=E2=80=99=
t actually pay off. &nbsp; HTTP POST has the advantage over GET that the =
receiver of the POST can validate the JWT and signal correct reception =
in the HTTP Response.</div><div class=3D""><br class=3D""></div><div =
class=3D"">I hope to get the new charter aligned version of distribution =
published in time for consideration at the Seoul meeting.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Phil</div><div =
class=3D""><div class=3D""><div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
line-height: normal; border-spacing: 0px;"><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D""><br class=3D""></div><div =
class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_706F7FED-E3EC-4570-BECC-F6E02E114DC3--


From nobody Wed Sep  7 09:50:17 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E22AC12B3B7 for <id-event@ietfa.amsl.com>; Wed,  7 Sep 2016 09:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.728
X-Spam-Level: 
X-Spam-Status: No, score=-5.728 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQ0zWq_4f3RL for <id-event@ietfa.amsl.com>; Wed,  7 Sep 2016 09:50:13 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 438DD12B20C for <id-event@ietf.org>; Wed,  7 Sep 2016 09:50:13 -0700 (PDT)
Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u87Go7cR029177 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 7 Sep 2016 16:50:07 GMT
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id u87Go68q003893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 7 Sep 2016 16:50:07 GMT
Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u87Go6VS010039; Wed, 7 Sep 2016 16:50:06 GMT
Received: from [10.0.1.5] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 07 Sep 2016 09:50:05 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_9BD8A94A-32D8-46A1-A2D3-A9698EB034F2"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Phil Hunt <phil.hunt@oracle.com>
In-Reply-To: <595998295.367982.1473265977000@mail.yahoo.com>
Date: Wed, 7 Sep 2016 09:50:04 -0700
Message-Id: <785F772B-5546-4389-BB7F-1D6738BA383A@oracle.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <595998295.367982.1473265977000@mail.yahoo.com>
To: Vivek Biswas <vivek_biswas@yahoo.com>
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0022.oracle.com [141.146.126.234]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/og_e3rYBlmKYqJtDAn16hF1foxg>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, Marius Scurtescu <mscurtescu@google.com>, "id-event@ietf.org" <id-event@ietf.org>, Mike Jones <Michael.Jones@microsoft.com>, William Denniss <wdenniss@google.com>, Leif Johansson <leifj@sunet.se>, Morteza Ansari <moransar@cisco.com>
Subject: Re: [Id-event] Straw man text for proposed charter
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2016 16:50:16 -0000

--Apple-Mail=_9BD8A94A-32D8-46A1-A2D3-A9698EB034F2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Vivek,

Can you elaborate?

The validation just ensures that the endpoints actually work.  It also =
serves to block DoS issues where someone accidentally or intentionally =
tries to send SETs to an unwilling subscriber.

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>





> On Sep 7, 2016, at 9:32 AM, Vivek Biswas <vivek_biswas@yahoo.com> =
wrote:
>=20
> Hi Mike,
>=20
> I believe there is one more item that MAY be added.
>=20
> After the line "Methods for validating event feed subscriptions"
> "Obligation that may be needed to be fulfilled upon validating an =
event feed".
>=20
> Regards
> Vivek Biswas
> Consulting Member @Security
> Oracle.
>=20
>=20
>=20
>=20
> From: Mike Jones <Michael.Jones@microsoft.com>
> To: "id-event@ietf.org" <id-event@ietf.org>=20
> Cc: Marius Scurtescu <mscurtescu@google.com>; Alexey Melnikov =
<aamelnikov@fastmail.fm>; Morteza Ansari (moransar) =
<moransar@cisco.com>; William Denniss <wdenniss@google.com>; Leif =
Johansson <leifj@sunet.se>; Phil Hunt (IDM) <phil.hunt@oracle.com>
> Sent: Tuesday, September 6, 2016 5:01 PM
> Subject: Re: [Id-event] Straw man text for proposed charter
>=20
> An updated and simplified charter is attached.  This draft has been =
reviewed by Phil Hunt, William Denniss, Marius Scurtescu.
> =20
> Input from Alexey Melnikov is that we should probably charter a =
working group, rather than try to go the AD-sponsored route.  Therefore, =
please review this draft charter and let us know if you think it=E2=80=99s=
 ready to go.
> =20
>                                                        Thanks,
>                                                        -- Mike
> =C2=A0 <applewebdata://F9C8DFD9-CBDA-4D7F-8D01-83EC3A9A6D5A>
> From: Sarah Squire [mailto:sarah@engageidentity.com]=20
> Sent: Thursday, July 14, 2016 10:59 PM
> To: Phil Hunt (IDM) <phil.hunt@oracle.com>
> Cc: Mike Jones <Michael.Jones@microsoft.com>; Alan Karp =
<alanhkarp@gmail.com>; Vivek Biswas <vivek_biswas@yahoo.com>; Morteza =
Ansari (moransar) <moransar@cisco.com>; id-event@ietf.org
> Subject: Re: [Id-event] Straw man text for proposed charter
> =20
> Just submitting my two cents in writing before we hopefully have a =
chance to meet about this next week...
> =20
> Looking at this charter from the perspective of the OIDF HEART working =
group, I think it's going down a good path. In terms of the data format, =
this is less structured than what I was envisioning, but we could easily =
do a healthcare-specific profile of whatever data format comes out in =
the end, so it's better to be too broad than too narrow as far as our =
interests are concerned.
> =20
> The transport layer however, has some added complexity. In our =
context, we're shooting for interoperability, so we'd prefer something =
constrained. I appreciate Mike's input that these are application layer =
decisions. However, if we're talking about cloud provider-to-cloud =
provider communication, that certainly is facilitated by a well-defined =
transport layer. Again, we're willing to profile whatever the group =
comes up with for our own ends, but I don't really see the benefit of =
having a loosely defined transport layer - it just seems like more work =
for all the implementers to actually agree on endpoints on a =
case-by-case basis.
> =20
> Looking forward to discussing further in Berlin!
> =20
> Sarah
>=20
> Sarah Squire
> Engage Identity
> http://engageidentity.com <http://engageidentity.com/>
> =20
> On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>> wrote:
> We also set things up so even a domain specific event can be extended.=20=

> =20
> Eg on a password reset event, so event publishers may want to add =
security domain specific attributes. The spec lets them do that while =
avoiding interop issues.=20
> =20
> I believe in the spec we had the example of an account reset and the =
publisher adds reset count as an extension.=20
>=20
> Phil
>=20
> On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com =
<mailto:Michael.Jones@microsoft.com>> wrote:
> Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 =
so common claims can be defined once and then reused.
> =20
> From: Vivek Biswas <mailto:vivek_biswas@yahoo.com>
> Sent: Saturday, May 7, 2016 1:24 PM
> To: Mike Jones <mailto:Michael.Jones@microsoft.com>
> Cc: Alan Karp <mailto:alanhkarp@gmail.com>; Morteza Ansari (moransar) =
<mailto:moransar@cisco.com>; id-event@ietf.org =
<mailto:id-event@ietf.org>
> Subject: Re: [Id-event] Straw man text for proposed charter
> =20
> Yes, I agree that the claims can be application specific, however =
there is a possibility to define claims which are domain specific. =
Thereby claims generated in one application could be understood by =
another  application within the same domain.
> =20
> With microservices based architecture getting lot of attention, if two =
different micro services defining different claims for the same claim, =
it can create confusion.
> =20
> Nevertheless this well defined claims for a particular domain can be =
an extension to the core specification.
> =20
> -Vivek Biswas
>   Consulting Member, Oracle
>=20
> Sent from my iPhone
>=20
> On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com =
<mailto:Michael.Jones@microsoft.com>> wrote:
> Thanks Alan,
> =20
> Interoperability will be on a per-application basis, just like JWT =
interoperability.  The claims needed in an identity event are =
application-specific, just like claims are for JWTs.  This is the same =
standards posture and JWTs are a huge success =E2=80=93 including for =
interoperability, even if I do say so myself.
> =20
>                                                           Best wishes,
>                                                           -- Mike
> =20
> =20
> =20
> =20
> From: Alan Karp <mailto:alanhkarp@gmail.com>
> Sent: Saturday, May 7, 2016 10:23 AM
> To: Mike Jones <mailto:Michael.Jones@microsoft.com>
> Cc: Morteza Ansari (moransar) <mailto:moransar@cisco.com>; =
id-event@ietf.org <mailto:id-event@ietf.org>
> Subject: Re: [Id-event] Straw man text for proposed charter
> =20
> As one who proposed doing more, I believe that your position is valid. =
 My only question is whether or not that will be enough for =
interoperability.
>=20
>=20
> --------------
> Alan Karp
> =20
> On Thu, May 5, 2016 at 10:00 PM, Mike Jones =
<Michael.Jones@microsoft.com <mailto:Michael.Jones@microsoft.com>> =
wrote:
> Thanks guys, for writing the initial charter text.  Reading it now, I =
am extremely worried by the scope creep evident in the proposal.
> =20
> I strongly support a working group to define an ID Events data format. =
 I just as strongly believe that specific event delivery mechanisms will =
necessarily be application-specific and therefore MUST be explicitly be =
stated as being out of scope in the working group charter.  Attempting =
to specify a particular event delivery mechanism will take something =
that could be simple and quick to approve and bog it down in necessarily =
application-specific debates.
> =20
> Should event delivery be reliable?  That=E2=80=99s an =
application-specific decision.
> Should events be idempotent?  That=E2=80=99s an application-specific =
decision.
> Should events be unicast, multicast, or broadcast?  That=E2=80=99s an =
application-specific decision.
> Should events have categories with category-specific subscriptions?  =
That=E2=80=99s an application-specific decision.
> Should only one party at a time be able to register for delivery of =
events or should multiple parties be able to request delivery?  That=E2=80=
=99s an application-specific decision.
> I could continue with this list, but I think you all get the point=E2=80=
=A6
> =20
> If we start debating application-specific event delivery mechanisms, =
we=E2=80=99ll please almost no one, since nearly all applications have =
different event delivery requirements.  We MUST explicitly rule all =
delivery mechanisms as being out of scope.
> =20
> If we define only a data format, we can quickly produce a very useful =
specification.  If we don=E2=80=99t, we=E2=80=99ll get bogged down in =
the mud of debating which applications we=E2=80=99re catering to and =
which we aren=E2=80=99t =E2=80=93 an exercise of picking favorites and =
limiting applicability of the specification.  That way is a slow, =
painful descent into standards quicksand =E2=80=93 something we must =
avoid.  Having a standard ID events representation is far too important =
to tie to a particular limited event delivery mechanism.
> =20
>                                                           Sincerely,
>                                                           -- Mike
> =C2=A0 <applewebdata://F9C8DFD9-CBDA-4D7F-8D01-83EC3A9A6D5A>
> From: Id-event [mailto:id-event-bounces@ietf.org =
<mailto:id-event-bounces@ietf.org>] On Behalf Of Alan Karp
> Sent: Thursday, May 5, 2016 9:43 PM
> To: Morteza Ansari (moransar) <moransar@cisco.com =
<mailto:moransar@cisco.com>>
> Cc: id-event@ietf.org <mailto:id-event@ietf.org>
> Subject: Re: [Id-event] Straw man text for proposed charter
> =20
> I don't see anything about access control for publishing events and =
subscribing to them.  I also think the spec should allow filters on =
subscriptions.
>=20
>=20
> --------------
> Alan Karp
> =20
> On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar) =
<moransar@cisco.com <mailto:moransar@cisco.com>> wrote:
> Hi folks,
> =20
> At IIW a few of us (Phil, William, Adam, and I) huddled for a bit and =
put together the attached as a straw man charter proposal to start the =
discussion. Please send your comments and suggestions for any changes or =
propose a new one if you think its necessary.
> =20
> =20
> Cheers,
> Morteza
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org <mailto:Id-event@ietf.org>
> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
> =20
> =20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org <mailto:Id-event@ietf.org>
> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org <mailto:Id-event@ietf.org>
> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org <mailto:Id-event@ietf.org>
> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
> =20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org <mailto:Id-event@ietf.org>
> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>

--Apple-Mail=_9BD8A94A-32D8-46A1-A2D3-A9698EB034F2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Vivek,</div><div class=3D""><br =
class=3D""></div>Can you elaborate?<div class=3D""><br =
class=3D""></div><div class=3D"">The validation just ensures that the =
endpoints actually work. &nbsp;It also serves to block DoS issues where =
someone accidentally or intentionally tries to send SETs to an unwilling =
subscriber.</div><div class=3D""><br class=3D""><div class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Sep 7, 2016, at 9:32 AM, Vivek Biswas &lt;<a =
href=3D"mailto:vivek_biswas@yahoo.com" =
class=3D"">vivek_biswas@yahoo.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
style=3D"font-style: normal; font-variant-caps: normal; font-weight: =
normal; 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; =
background-color: rgb(255, 255, 255); font-family: verdana, helvetica, =
sans-serif; font-size: 16px;" class=3D""><div =
id=3D"yui_3_16_0_ym19_1_1473265247048_12746" class=3D"">Hi =
Mike,</div><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746" =
class=3D""><br class=3D""></div><div =
id=3D"yui_3_16_0_ym19_1_1473265247048_12746" class=3D"">I believe there =
is one more item that MAY be added.</div><div =
id=3D"yui_3_16_0_ym19_1_1473265247048_12746" class=3D""><br =
class=3D""></div><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746" =
dir=3D"ltr" class=3D"">After the line "<span =
id=3D"yui_3_16_0_ym19_1_1473265247048_12804" style=3D"font-family: =
pg-1ff9; line-height: 37.2852px; white-space: pre-wrap; =
-webkit-text-stroke-width: 0.6px; -webkit-text-stroke-color: rgba(0, 0, =
0, 0);" class=3D""><font size=3D"3" =
id=3D"yui_3_16_0_ym19_1_1473265247048_13077" class=3D"">Methods for =
validating event feed subscriptions"</font></span></div><div =
id=3D"yui_3_16_0_ym19_1_1473265247048_12746" dir=3D"ltr" class=3D""><span =
id=3D"yui_3_16_0_ym19_1_1473265247048_13175" style=3D"font-family: =
pg-1ff9; line-height: 37.2852px; white-space: pre-wrap; =
-webkit-text-stroke-width: 0.6px; -webkit-text-stroke-color: rgba(0, 0, =
0, 0);" class=3D""><font size=3D"3" =
id=3D"yui_3_16_0_ym19_1_1473265247048_13174" class=3D"">"Obligation that =
may be needed to be fulfilled upon validating an event =
feed".</font></span></div><div =
id=3D"yui_3_16_0_ym19_1_1473265247048_12746" dir=3D"ltr" class=3D""><br =
class=3D""></div><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746" =
dir=3D"ltr" class=3D"">Regards</div><div =
id=3D"yui_3_16_0_ym19_1_1473265247048_12746" dir=3D"ltr" class=3D"">Vivek =
Biswas</div><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746" dir=3D"ltr" =
class=3D"">Consulting Member @Security</div><div =
id=3D"yui_3_16_0_ym19_1_1473265247048_12746" dir=3D"ltr" =
class=3D"">Oracle.</div><div id=3D"yui_3_16_0_ym19_1_1473265247048_12746" =
dir=3D"ltr" class=3D""><br class=3D""></div><div =
id=3D"yui_3_16_0_ym19_1_1473265247048_12746" dir=3D"ltr" class=3D""><br =
class=3D""></div><div class=3D"qtdSeparateBR"><br class=3D""><br =
class=3D""></div><div class=3D"yahoo_quoted" =
id=3D"yui_3_16_0_ym19_1_1473265247048_12800" style=3D"display: =
block;"><div id=3D"yui_3_16_0_ym19_1_1473265247048_12799" =
style=3D"font-family: verdana, helvetica, sans-serif; font-size: 16px;" =
class=3D""><div id=3D"yui_3_16_0_ym19_1_1473265247048_12798" =
style=3D"font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, =
'Lucida Grande', sans-serif; font-size: 16px;" class=3D""><div dir=3D"ltr"=
 id=3D"yui_3_16_0_ym19_1_1473265247048_12797" class=3D""><font size=3D"2" =
face=3D"Arial" id=3D"yui_3_16_0_ym19_1_1473265247048_12796" class=3D""><hr=
 size=3D"1" id=3D"yui_3_16_0_ym19_1_1473265247048_12795" class=3D""><b =
class=3D""><span style=3D"font-weight: bold;" =
class=3D"">From:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" =
class=3D"">Michael.Jones@microsoft.com</a>&gt;<br class=3D""><b =
class=3D""><span style=3D"font-weight: bold;" =
class=3D"">To:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>"<a =
href=3D"mailto:id-event@ietf.org" class=3D"">id-event@ietf.org</a>" =
&lt;<a href=3D"mailto:id-event@ietf.org" =
class=3D"">id-event@ietf.org</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D""><b =
class=3D""><span style=3D"font-weight: bold;" =
class=3D"">Cc:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Marius Scurtescu &lt;<a =
href=3D"mailto:mscurtescu@google.com" =
class=3D"">mscurtescu@google.com</a>&gt;; Alexey Melnikov &lt;<a =
href=3D"mailto:aamelnikov@fastmail.fm" =
class=3D"">aamelnikov@fastmail.fm</a>&gt;; Morteza Ansari (moransar) =
&lt;<a href=3D"mailto:moransar@cisco.com" =
class=3D"">moransar@cisco.com</a>&gt;; William Denniss &lt;<a =
href=3D"mailto:wdenniss@google.com" =
class=3D"">wdenniss@google.com</a>&gt;; Leif Johansson &lt;<a =
href=3D"mailto:leifj@sunet.se" class=3D"">leifj@sunet.se</a>&gt;; Phil =
Hunt (IDM) &lt;<a href=3D"mailto:phil.hunt@oracle.com" =
class=3D"">phil.hunt@oracle.com</a>&gt;<br class=3D""><b class=3D""><span =
style=3D"font-weight: bold;" class=3D"">Sent:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Tuesday, September 6, 2016 =
5:01 PM<br class=3D""><b class=3D""><span style=3D"font-weight: bold;" =
class=3D"">Subject:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [Id-event] Straw man =
text for proposed charter<br class=3D""></font></div><div =
class=3D"y_msg_container"><br class=3D""><div id=3D"yiv8143991987" =
class=3D""><div class=3D""><div class=3D"yiv8143991987WordSection1"><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" class=3D"">An updated =
and simplified charter is attached.&nbsp; This draft has been reviewed =
by Phil Hunt, William Denniss, Marius Scurtescu.</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" =
class=3D"">&nbsp;</span></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><span =
style=3D"font-size: 11pt;" class=3D"">Input from Alexey Melnikov is that =
we should probably charter a working group, rather than try to go the =
AD-sponsored route.&nbsp; Therefore, please review this draft charter =
and let us know if you think it=E2=80=99s ready to go.</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" =
class=3D"">&nbsp;</span></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><span =
style=3D"font-size: 11pt;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><a rel=3D"nofollow" shape=3D"rect" =
name=3D"_MailEndCompose" href=3D"" style=3D"color: purple; =
text-decoration: underline;" class=3D""><span style=3D"font-size: 11pt;" =
class=3D"">&nbsp;</span></a></div><span class=3D""></span><div =
class=3D"yiv8143991987yqt5176189511" id=3D"yiv8143991987yqt64133"><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><b class=3D""><span style=3D"font-size: 11pt;" =
class=3D"">From:</span></b><span style=3D"font-size: 11pt;" =
class=3D""><span class=3D"Apple-converted-space">&nbsp;</span>Sarah =
Squire [<a href=3D"mailto:sarah@engageidentity.com" =
class=3D"">mailto:sarah@engageidentity.com</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><br clear=3D"none" =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Thursday, July 14, 2016 =
10:59 PM<br clear=3D"none" class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Phil Hunt (IDM) &lt;<a =
href=3D"mailto:phil.hunt@oracle.com" =
class=3D"">phil.hunt@oracle.com</a>&gt;<br clear=3D"none" class=3D""><b =
class=3D"">Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span>Mike =
Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com" =
class=3D"">Michael.Jones@microsoft.com</a>&gt;; Alan Karp &lt;<a =
href=3D"mailto:alanhkarp@gmail.com" =
class=3D"">alanhkarp@gmail.com</a>&gt;; Vivek Biswas &lt;<a =
href=3D"mailto:vivek_biswas@yahoo.com" =
class=3D"">vivek_biswas@yahoo.com</a>&gt;; Morteza Ansari (moransar) =
&lt;<a href=3D"mailto:moransar@cisco.com" =
class=3D"">moransar@cisco.com</a>&gt;; <a =
href=3D"mailto:id-event@ietf.org" class=3D"">id-event@ietf.org</a><br =
clear=3D"none" class=3D""><b class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [Id-event] Straw man =
text for proposed charter</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div><div class=3D""><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">Just submitting my two cents in writing before we =
hopefully have a chance to meet about this next week...</div></div><div =
class=3D""><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt;">&nbsp;</div></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">Looking at this charter from the perspective of the =
OIDF HEART working group, I think it's going down a good path. In terms =
of the data format, this is less structured than what I was envisioning, =
but we could easily do a healthcare-specific profile of whatever data =
format comes out in the end, so it's better to be too broad than too =
narrow as far as our interests are concerned.</div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">The transport layer however, has some added =
complexity. In our context, we're shooting for interoperability, so we'd =
prefer something constrained. I appreciate Mike's input that these are =
application layer decisions. However, if we're talking about cloud =
provider-to-cloud provider communication, that certainly is facilitated =
by a well-defined transport layer. Again, we're willing to profile =
whatever the group comes up with for our own ends, but I don't really =
see the benefit of having a loosely defined transport layer - it just =
seems like more work for all the implementers to actually agree on =
endpoints on a case-by-case basis.</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">Looking forward to discussing further in =
Berlin!</div></div><div class=3D""><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: =
12pt;">&nbsp;</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">Sarah</div></div></div></div><div class=3D""><div =
class=3D"yiv8143991987yqt5176189511" id=3D"yiv8143991987yqt99533"><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><br clear=3D"all" class=3D""></div><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"color: rgb(136, 136, 136);" =
class=3D"">Sarah Squire</span></div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"color: rgb(136, 136, 136);" =
class=3D"">Engage Identity</span></div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"color: rgb(136, 136, 136);" class=3D""><a=
 rel=3D"nofollow" shape=3D"rect" target=3D"_blank" =
href=3D"http://engageidentity.com/" style=3D"color: purple; =
text-decoration: underline;" class=3D""><span style=3D"color: rgb(17, =
85, 204);" =
class=3D"">http://engageidentity.com</span></a></span></div></div></div></=
div></div><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt;">&nbsp;</div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) &lt;<a =
rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:phil.hunt@oracle.com" =
target=3D"_blank" href=3D"mailto:phil.hunt@oracle.com" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">phil.hunt@oracle.com</a>&gt; wrote:</div><blockquote =
style=3D"border-style: none none none solid; border-left-color: rgb(204, =
204, 204); border-left-width: 1pt; padding: 0in 0in 0in 6pt; =
margin-left: 4.8pt; margin-right: 0in;" class=3D""><div class=3D""><div =
class=3D""><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt;">We also set things up so even a domain =
specific event can be extended.&nbsp;</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">Eg on a password reset event, so event publishers may =
want to add security domain specific attributes. The spec lets them do =
that while avoiding interop issues.&nbsp;</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">I believe in the spec we had the example of an account =
reset and the publisher adds reset count as an extension.&nbsp;<span =
style=3D"color: rgb(136, 136, 136);" class=3D""><br clear=3D"none" =
class=3D""><br clear=3D"none" class=3D""><span =
class=3D"yiv8143991987hoenzb">Phil</span></span></div></div><div =
class=3D""><div class=3D""><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 12pt; =
font-size: 12pt;"><br clear=3D"none" class=3D"">On May 7, 2016, at =
13:31, Mike Jones &lt;<a rel=3D"nofollow" shape=3D"rect" =
ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" =
href=3D"mailto:Michael.Jones@microsoft.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">Michael.Jones@microsoft.com</a>&gt; =
wrote:</div></div><blockquote style=3D"margin-top: 5pt; margin-bottom: =
5pt;" class=3D""><div class=3D""><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">Indeed, that=E2=80=99s why there=E2=80=99s a claims =
registry =E2=80=93 so common claims can be defined once and then =
reused.</div><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt;">&nbsp;</div><div style=3D"border-style: =
solid none none; border-top-color: rgb(225, 225, 225); border-top-width: =
1pt; padding: 3pt 0in 0in;" class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><b class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></b><a rel=3D"nofollow" =
shape=3D"rect" ymailto=3D"mailto:vivek_biswas@yahoo.com" target=3D"_blank"=
 href=3D"mailto:vivek_biswas@yahoo.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">Vivek Biswas</a><br clear=3D"none"=
 class=3D""><b class=3D"">Sent:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Saturday, May 7, 2016 =
1:24 PM<br clear=3D"none" class=3D""><b class=3D"">To:<span =
class=3D"Apple-converted-space">&nbsp;</span></b><a rel=3D"nofollow" =
shape=3D"rect" ymailto=3D"mailto:Michael.Jones@microsoft.com" =
target=3D"_blank" href=3D"mailto:Michael.Jones@microsoft.com" =
style=3D"color: purple; text-decoration: underline;" class=3D"">Mike =
Jones</a><br clear=3D"none" class=3D""><b class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></b><a rel=3D"nofollow" =
shape=3D"rect" ymailto=3D"mailto:alanhkarp@gmail.com" target=3D"_blank" =
href=3D"mailto:alanhkarp@gmail.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">Alan Karp</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a rel=3D"nofollow" =
shape=3D"rect" ymailto=3D"mailto:moransar@cisco.com" target=3D"_blank" =
href=3D"mailto:moransar@cisco.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">Morteza Ansari =
(moransar)</a>;<span class=3D"Apple-converted-space">&nbsp;</span><a =
rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:id-event@ietf.org" =
target=3D"_blank" href=3D"mailto:id-event@ietf.org" style=3D"color: =
purple; text-decoration: underline;" class=3D"">id-event@ietf.org</a><br =
clear=3D"none" class=3D""><b class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Re: [Id-event] Straw =
man text for proposed charter</div></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div></div><div class=3D""><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">Yes, I agree that the claims can be application =
specific, however there is a possibility to define claims which are =
domain specific. Thereby claims generated in one application could be =
understood by another &nbsp;application within the same =
domain.</div></div><div class=3D""><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: =
12pt;">&nbsp;</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">With microservices based architecture getting lot of =
attention, if two different micro services defining different claims for =
the same claim, it can create confusion.</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">Nevertheless this well defined claims for a particular =
domain can be an extension to the core specification.</div></div><div =
class=3D""><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt;">&nbsp;</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">-Vivek Biswas</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp; Consulting Member, Oracle<br clear=3D"none" =
class=3D""><br clear=3D"none" class=3D"">Sent from my =
iPhone</div></div><div class=3D""><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 12pt; font-size: 12pt;"><br clear=3D"none" =
class=3D"">On May 7, 2016, at 1:04 PM, Mike Jones &lt;<a rel=3D"nofollow" =
shape=3D"rect" ymailto=3D"mailto:Michael.Jones@microsoft.com" =
target=3D"_blank" href=3D"mailto:Michael.Jones@microsoft.com" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">Michael.Jones@microsoft.com</a>&gt; =
wrote:</div></div><blockquote style=3D"margin-top: 5pt; margin-bottom: =
5pt;" class=3D""><div class=3D""><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">Thanks Alan,</div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;">&nbsp;</div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"color: rgb(0, 32, 96);" =
class=3D"">Interoperability will be on a per-application basis, just =
like JWT interoperability.&nbsp; The claims needed in an identity event =
are application-specific, just like claims are for JWTs.&nbsp; This is =
the same standards posture and JWTs are a huge success =E2=80=93 =
including for interoperability, even if I do say so =
myself.</span></div><div class=3D"yiv8143991987MsoNormal" style=3D"margin:=
 0in 0in 0.0001pt; font-size: 12pt;"><span style=3D"color: rgb(0, 32, =
96);" class=3D"">&nbsp;</span></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><span style=3D"color:=
 rgb(0, 32, 96);" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Best =
wishes,</span></div><div class=3D"yiv8143991987MsoNormal" style=3D"margin:=
 0in 0in 0.0001pt; font-size: 12pt;"><span style=3D"color: rgb(0, 32, =
96);" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike</span></div><div class=3D"yiv8143991987MsoNormal" style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt;">&nbsp;</div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;">&nbsp;</div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div><div style=3D"border-style: solid none =
none; border-top-color: rgb(225, 225, 225); border-top-width: 1pt; =
padding: 3pt 0in 0in;" class=3D""><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><b =
class=3D"">From:<span class=3D"Apple-converted-space">&nbsp;</span></b><a =
rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:alanhkarp@gmail.com" =
target=3D"_blank" href=3D"mailto:alanhkarp@gmail.com" style=3D"color: =
purple; text-decoration: underline;" class=3D"">Alan Karp</a><br =
clear=3D"none" class=3D""><b class=3D"">Sent:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Saturday, May 7, 2016 =
10:23 AM<br clear=3D"none" class=3D""><b class=3D"">To:<span =
class=3D"Apple-converted-space">&nbsp;</span></b><a rel=3D"nofollow" =
shape=3D"rect" ymailto=3D"mailto:Michael.Jones@microsoft.com" =
target=3D"_blank" href=3D"mailto:Michael.Jones@microsoft.com" =
style=3D"color: purple; text-decoration: underline;" class=3D"">Mike =
Jones</a><br clear=3D"none" class=3D""><b class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></b><a rel=3D"nofollow" =
shape=3D"rect" ymailto=3D"mailto:moransar@cisco.com" target=3D"_blank" =
href=3D"mailto:moransar@cisco.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">Morteza Ansari =
(moransar)</a>;<span class=3D"Apple-converted-space">&nbsp;</span><a =
rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:id-event@ietf.org" =
target=3D"_blank" href=3D"mailto:id-event@ietf.org" style=3D"color: =
purple; text-decoration: underline;" class=3D"">id-event@ietf.org</a><br =
clear=3D"none" class=3D""><b class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Re: [Id-event] Straw =
man text for proposed charter</div></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div></div><div class=3D""><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 9.5pt;" class=3D"">As one =
who proposed doing more, I believe that your position is valid.&nbsp; My =
only question is whether or not that will be enough for =
interoperability.</span></div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><br clear=3D"all" class=3D""></div><div class=3D""><div =
class=3D""><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt;"><br clear=3D"none" =
class=3D"">--------------<br clear=3D"none" class=3D"">Alan =
Karp</div></div></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;">&nbsp;</div><div =
class=3D""><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt;">On Thu, May 5, 2016 at 10:00 PM, Mike =
Jones &lt;<a rel=3D"nofollow" shape=3D"rect" =
ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" =
href=3D"mailto:Michael.Jones@microsoft.com" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">Michael.Jones@microsoft.com</a>&gt; wrote:</div><blockquote =
style=3D"border-style: none none none solid; border-left-color: rgb(204, =
204, 204); border-left-width: 1pt; padding: 0in 0in 0in 6pt; =
margin-left: 4.8pt; margin-right: 0in;" class=3D""><div class=3D""><div =
class=3D""><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt;"><span style=3D"font-size: 11pt;" =
class=3D"">Thanks guys, for writing the initial charter text.&nbsp; =
Reading it now, I am extremely worried by the scope creep evident in the =
proposal.</span></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><span =
style=3D"font-size: 11pt;" class=3D"">&nbsp;</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" class=3D"">I strongly =
support a working group to define an ID Events data format.&nbsp; I just =
as strongly believe that specific event delivery mechanisms will =
necessarily be application-specific and therefore MUST be explicitly be =
stated as being out of scope in the working group charter.&nbsp; =
Attempting to specify a particular event delivery mechanism will take =
something that could be simple and quick to approve and bog it down in =
necessarily application-specific debates.</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" =
class=3D"">&nbsp;</span></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><span =
style=3D"font-size: 11pt;" class=3D"">Should event delivery be =
reliable?&nbsp; That=E2=80=99s an application-specific =
decision.</span></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><span =
style=3D"font-size: 11pt;" class=3D"">Should events be idempotent?&nbsp; =
That=E2=80=99s an application-specific decision.</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" class=3D"">Should =
events be unicast, multicast, or broadcast?&nbsp; That=E2=80=99s an =
application-specific decision.</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" class=3D"">Should =
events have categories with category-specific subscriptions?&nbsp; =
That=E2=80=99s an application-specific decision.</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" class=3D"">Should =
only one party at a time be able to register for delivery of events or =
should multiple parties be able to request delivery?&nbsp; That=E2=80=99s =
an application-specific decision.</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" class=3D"">I could =
continue with this list, but I think you all get the =
point=E2=80=A6</span></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><span =
style=3D"font-size: 11pt;" class=3D"">&nbsp;</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" class=3D"">If we =
start debating application-specific event delivery mechanisms, we=E2=80=99=
ll please almost no one, since nearly all applications have different =
event delivery requirements.&nbsp; We MUST explicitly rule all delivery =
mechanisms as being out of scope.</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" =
class=3D"">&nbsp;</span></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><span =
style=3D"font-size: 11pt;" class=3D"">If we define only a data format, =
we can quickly produce a very useful specification.&nbsp; If we don=E2=80=99=
t, we=E2=80=99ll get bogged down in the mud of debating which =
applications we=E2=80=99re catering to and which we aren=E2=80=99t =E2=80=93=
 an exercise of picking favorites and limiting applicability of the =
specification.&nbsp; That way is a slow, painful descent into standards =
quicksand =E2=80=93 something we must avoid.&nbsp; Having a standard ID =
events representation is far too important to tie to a particular =
limited event delivery mechanism.</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 11pt;" =
class=3D"">&nbsp;</span></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><span =
style=3D"font-size: 11pt;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Sincerely,</span></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><span =
style=3D"font-size: 11pt;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike</span></div><div class=3D"yiv8143991987MsoNormal" style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt;"><a rel=3D"nofollow" shape=3D"rect" =
name=3D"m_3022367059336893565_m_1461024254222911" href=3D"" =
style=3D"color: purple; text-decoration: underline;" class=3D""><span =
style=3D"font-size: 11pt;" class=3D"">&nbsp;</span></a></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><b class=3D""><span style=3D"font-size: 11pt;" =
class=3D"">From:</span></b><span style=3D"font-size: 11pt;" =
class=3D""><span class=3D"Apple-converted-space">&nbsp;</span>Id-event =
[mailto:<a rel=3D"nofollow" shape=3D"rect" =
ymailto=3D"mailto:id-event-bounces@ietf.org" target=3D"_blank" =
href=3D"mailto:id-event-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">id-event-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Alan Karp<br =
clear=3D"none" class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Thursday, May 5, 2016 9:43 =
PM<br clear=3D"none" class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Morteza Ansari (moransar) =
&lt;<a rel=3D"nofollow" shape=3D"rect" =
ymailto=3D"mailto:moransar@cisco.com" target=3D"_blank" =
href=3D"mailto:moransar@cisco.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">moransar@cisco.com</a>&gt;<br =
clear=3D"none" class=3D""><b class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span><a rel=3D"nofollow" =
shape=3D"rect" ymailto=3D"mailto:id-event@ietf.org" target=3D"_blank" =
href=3D"mailto:id-event@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">id-event@ietf.org</a><br =
clear=3D"none" class=3D""><b class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [Id-event] Straw man =
text for proposed charter</span></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">I don't see anything about access control for =
publishing events and subscribing to them.&nbsp; I also think the spec =
should allow filters on subscriptions.</div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><br clear=3D"all" class=3D""></div><div class=3D""><div =
class=3D""><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt;"><br clear=3D"none" =
class=3D"">--------------<br clear=3D"none" class=3D"">Alan =
Karp</div></div></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;">&nbsp;</div><div =
class=3D""><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt;">On Thu, May 5, 2016 at 11:18 AM, Morteza =
Ansari (moransar) &lt;<a rel=3D"nofollow" shape=3D"rect" =
ymailto=3D"mailto:moransar@cisco.com" target=3D"_blank" =
href=3D"mailto:moransar@cisco.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">moransar@cisco.com</a>&gt; =
wrote:</div><blockquote style=3D"border-style: none none none solid; =
border-left-color: rgb(204, 204, 204); border-left-width: 1pt; padding: =
0in 0in 0in 6pt; margin: 5pt 0in 5pt 4.8pt;" class=3D""><div =
class=3D""><div class=3D""><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt;"><span =
style=3D"font-size: 10.5pt;" class=3D"">Hi folks,</span></div></div><div =
class=3D""><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt;"><span style=3D"font-size: 10.5pt;" =
class=3D"">&nbsp;</span></div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 10.5pt;" class=3D"">At IIW a =
few of us (Phil, William, Adam, and I) huddled for a bit and put =
together the attached as a straw man charter proposal to start the =
discussion. Please send your comments and suggestions for any changes or =
propose a new one if you think its necessary.</span></div></div><div =
class=3D""><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt;"><span style=3D"font-size: 10.5pt;" =
class=3D"">&nbsp;</span></div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 10.5pt;" =
class=3D"">&nbsp;</span></div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 10.5pt;" =
class=3D"">Cheers,</span></div></div><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;"><span style=3D"font-size: 10.5pt;" =
class=3D"">Morteza</span></div></div></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 12pt; =
font-size: 12pt;"><br clear=3D"none" =
class=3D"">_______________________________________________<br =
clear=3D"none" class=3D"">Id-event mailing list<br clear=3D"none" =
class=3D""><a rel=3D"nofollow" shape=3D"rect" =
ymailto=3D"mailto:Id-event@ietf.org" target=3D"_blank" =
href=3D"mailto:Id-event@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">Id-event@ietf.org</a><br =
clear=3D"none" class=3D""><a rel=3D"nofollow" shape=3D"rect" =
target=3D"_blank" href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event</a></div></block=
quote></div><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: =
12pt;">&nbsp;</div></div></div></div></blockquote></div><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">&nbsp;</div></div></div></div></blockquote><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div =
class=3D""><div class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in =
0in 0.0001pt; font-size: =
12pt;">_______________________________________________<br clear=3D"none" =
class=3D"">Id-event mailing list<br clear=3D"none" class=3D""><a =
rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Id-event@ietf.org" =
target=3D"_blank" href=3D"mailto:Id-event@ietf.org" style=3D"color: =
purple; text-decoration: underline;" class=3D"">Id-event@ietf.org</a><br =
clear=3D"none" class=3D""><a rel=3D"nofollow" shape=3D"rect" =
target=3D"_blank" href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event</a></div></div><=
/blockquote></div></div></blockquote><blockquote style=3D"margin-top: =
5pt; margin-bottom: 5pt;" class=3D""><div class=3D""><div =
class=3D"yiv8143991987MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt;">_______________________________________________<br =
clear=3D"none" class=3D"">Id-event mailing list<br clear=3D"none" =
class=3D""><a rel=3D"nofollow" shape=3D"rect" =
ymailto=3D"mailto:Id-event@ietf.org" target=3D"_blank" =
href=3D"mailto:Id-event@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">Id-event@ietf.org</a><br =
clear=3D"none" class=3D""><a rel=3D"nofollow" shape=3D"rect" =
target=3D"_blank" href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event</a></div></div><=
/blockquote></div></div></div><div class=3D"yiv8143991987MsoNormal" =
style=3D"margin: 0in 0in 12pt; font-size: 12pt;"><br clear=3D"none" =
class=3D"">_______________________________________________<br =
clear=3D"none" class=3D"">Id-event mailing list<br clear=3D"none" =
class=3D""><a rel=3D"nofollow" shape=3D"rect" =
ymailto=3D"mailto:Id-event@ietf.org" target=3D"_blank" =
href=3D"mailto:Id-event@ietf.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">Id-event@ietf.org</a><br =
clear=3D"none" class=3D""><a rel=3D"nofollow" shape=3D"rect" =
target=3D"_blank" href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event</a></div></block=
quote></div></div><div class=3D"yiv8143991987MsoNormal" style=3D"margin: =
0in 0in 0.0001pt; font-size: =
12pt;">&nbsp;</div></div></div></div></div><br class=3D""><div =
class=3D"yqt5176189511" =
id=3D"yqt18602">_______________________________________________<br =
clear=3D"none" class=3D"">Id-event mailing list<br clear=3D"none" =
class=3D""><a shape=3D"rect" ymailto=3D"mailto:Id-event@ietf.org" =
href=3D"mailto:Id-event@ietf.org" class=3D"">Id-event@ietf.org</a><br =
clear=3D"none" class=3D""><a shape=3D"rect" =
href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event</a></div></div><=
/div></div></div></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_9BD8A94A-32D8-46A1-A2D3-A9698EB034F2--


From nobody Wed Sep  7 10:06:58 2016
Return-Path: <vivek_biswas@yahoo.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B346A12B222 for <id-event@ietfa.amsl.com>; Wed,  7 Sep 2016 10:06:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.207
X-Spam-Level: 
X-Spam-Status: No, score=-4.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.001, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wzmVS9H71I3T for <id-event@ietfa.amsl.com>; Wed,  7 Sep 2016 10:06:54 -0700 (PDT)
Received: from nm43-vm1.bullet.mail.ne1.yahoo.com (nm43-vm1.bullet.mail.ne1.yahoo.com [98.138.120.225]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB62312B3CF for <id-event@ietf.org>; Wed,  7 Sep 2016 10:06:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1473268013; bh=fkeOiyCn9RJha6m2b3q2/NMtPs93y5wudyVdYwzR0Qg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=X8y8721Jz0Po/RHWsrcN9TcvkCgVJDe/TfGCnxa52C3JzIFWrf3PUI9+uAIh2JgrXQrAXFK5Ha8SCOYeRXMSShrF/AXal7IylYjxuShwB2VxXSJ5PWL7RwGxRYjCQNs+9ENlH4SuZQHIMmU3vaR9nxc23q+bO6FcJZb3juxPsUW+RscxdavnNo9AEf9maYKhczTXg4gsPUzOcIqvaHYPTEtIOD44HWzJHn/uX9qELdslwl5PU7ibe9NnGkaHTGx2E5R3Y7cQMNRgwZtYBRIUewngfU7fhYMXzopeu7S00kkkHDenrD9ZW5yBaFTb1RsI+yb51Npzb4jQyvwi7r6gOg==
Received: from [127.0.0.1] by nm43.bullet.mail.ne1.yahoo.com with NNFMP; 07 Sep 2016 17:06:53 -0000
Received: from [98.138.100.114] by nm43.bullet.mail.ne1.yahoo.com with NNFMP;  07 Sep 2016 17:04:09 -0000
Received: from [98.138.89.170] by tm105.bullet.mail.ne1.yahoo.com with NNFMP;  07 Sep 2016 17:04:09 -0000
Received: from [127.0.0.1] by omp1026.mail.ne1.yahoo.com with NNFMP; 07 Sep 2016 17:04:09 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 714782.67874.bm@omp1026.mail.ne1.yahoo.com
X-YMail-OSG: Z1n.aBcVM1lDtT_T5KjH6EP.6H_pBmc4wVkAGdfYNOm_aMdf6uSCiKlUR2ZGzef pGtLG317sonoe2ByEpdxehmiSOw0lXHTB2XmAraNCmlueEezuE5pkyboEd15VY3oxTf2Nqo0ojOq AlWNEX7x7j.XOJcSQJznM_3rm3DO.hOIlbzoW4rLRmJWvWTrVLvPwMdFmuHVnDhbJGqwpgQ4F9cD 5UT6T9Zj3Z3r.48i2FhRlbHHXlzWVpUkr656IN9GjCgDUqBYjyLsOdQwt6X1Hx8YqxG.A_QdlUro 6LSlDNb40PijXBgJPWr2ML72nlMizLhywy947AWFLW4_yVbar0hjEkUVzQYtCHixjTFy3cEouo45 8JCBJqil49q77uIZ4PgK8xsmPhWwf6rJAqUkrESfQIwhQG4nAZ2Fpat44IWyDGO_YYRnmJRFwKAT ccl9PGm3Q40TiuCi8gMIW4kmekkJizOT1eQkQ59rXWsq5C9k12tXue.ueDrUwtWpuHegFdpqYjBn 3Wyu.0KYHk5ZC6k0RWfdGUSvQUUjF8r2mgwrJ
Received: from jws100206.mail.ne1.yahoo.com by sendmailws134.mail.ne1.yahoo.com; Wed, 07 Sep 2016 17:04:09 +0000; 1473267849.257
Date: Wed, 7 Sep 2016 17:03:56 +0000 (UTC)
From: Vivek Biswas <vivek_biswas@yahoo.com>
To: Phil Hunt <phil.hunt@oracle.com>
Message-ID: <858410497.419243.1473267836614@mail.yahoo.com>
In-Reply-To: <785F772B-5546-4389-BB7F-1D6738BA383A@oracle.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <595998295.367982.1473265977000@mail.yahoo.com> <785F772B-5546-4389-BB7F-1D6738BA383A@oracle.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_419242_284661789.1473267836585"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/kuzkOXHGZvxdmAPBLIPy2o4l84g>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, Marius Scurtescu <mscurtescu@google.com>, "id-event@ietf.org" <id-event@ietf.org>, Mike Jones <Michael.Jones@microsoft.com>, William Denniss <wdenniss@google.com>, Leif Johansson <leifj@sunet.se>, Morteza Ansari <moransar@cisco.com>
Subject: Re: [Id-event] Straw man text for proposed charter
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Vivek Biswas <vivek_biswas@yahoo.com>
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2016 17:06:57 -0000

------=_Part_419242_284661789.1473267836585
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Phil,
=C2=A0Thanks for asking the question and also adding more description to th=
e "validation" task.
The Obligation here means "Do we need to take any actions if the endpoints =
don't work"
Do we need to send any alert in case of someone is trying to do DoS attacks=
"
This obligation is an optional feature which can/may be fulfilled upon the =
validation task.
RegardsVivek BiswasConsulting Member @SecurityOracle

      From: Phil Hunt <phil.hunt@oracle.com>
 To: Vivek Biswas <vivek_biswas@yahoo.com>=20
Cc: Mike Jones <Michael.Jones@microsoft.com>; "id-event@ietf.org" <id-event=
@ietf.org>; Marius Scurtescu <mscurtescu@google.com>; Alexey Melnikov <aame=
lnikov@fastmail.fm>; Morteza Ansari <moransar@cisco.com>; William Denniss <=
wdenniss@google.com>; Leif Johansson <leifj@sunet.se>
 Sent: Wednesday, September 7, 2016 9:50 AM
 Subject: Re: [Id-event] Straw man text for proposed charter
  =20
Vivek,
Can you elaborate?
The validation just ensures that the endpoints actually work. =C2=A0It also=
 serves to block DoS issues where someone accidentally or intentionally tri=
es to send SETs to an unwilling subscriber.
Phil
@independentidwww.independentid.comphil.hunt@oracle.com





On Sep 7, 2016, at 9:32 AM, Vivek Biswas <vivek_biswas@yahoo.com> wrote:
Hi Mike,
I believe there is one more item that MAY be added.
After the line "Methods for validating event feed subscriptions""Obligation=
 that may be needed to be fulfilled upon validating an event feed".
RegardsVivek BiswasConsulting Member @SecurityOracle.



From:=C2=A0Mike Jones <Michael.Jones@microsoft.com>
To:=C2=A0"id-event@ietf.org" <id-event@ietf.org>=C2=A0
Cc:=C2=A0Marius Scurtescu <mscurtescu@google.com>; Alexey Melnikov <aamelni=
kov@fastmail.fm>; Morteza Ansari (moransar) <moransar@cisco.com>; William D=
enniss <wdenniss@google.com>; Leif Johansson <leifj@sunet.se>; Phil Hunt (I=
DM) <phil.hunt@oracle.com>
Sent:=C2=A0Tuesday, September 6, 2016 5:01 PM
Subject:=C2=A0Re: [Id-event] Straw man text for proposed charter

An updated and simplified charter is attached.=C2=A0 This draft has been re=
viewed by Phil Hunt, William Denniss, Marius Scurtescu.=C2=A0Input from Ale=
xey Melnikov is that we should probably charter a working group, rather tha=
n try to go the AD-sponsored route.=C2=A0 Therefore, please review this dra=
ft charter and let us know if you think it=E2=80=99s ready to go.=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Thanks,=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- Mike=C2=A0From:=
=C2=A0Sarah Squire [mailto:sarah@engageidentity.com]=C2=A0
Sent:=C2=A0Thursday, July 14, 2016 10:59 PM
To:=C2=A0Phil Hunt (IDM) <phil.hunt@oracle.com>
Cc:=C2=A0Mike Jones <Michael.Jones@microsoft.com>; Alan Karp <alanhkarp@gma=
il.com>; Vivek Biswas <vivek_biswas@yahoo.com>; Morteza Ansari (moransar) <=
moransar@cisco.com>; id-event@ietf.org
Subject:=C2=A0Re: [Id-event] Straw man text for proposed charter=C2=A0Just =
submitting my two cents in writing before we hopefully have a chance to mee=
t about this next week...=C2=A0Looking at this charter from the perspective=
 of the OIDF HEART working group, I think it's going down a good path. In t=
erms of the data format, this is less structured than what I was envisionin=
g, but we could easily do a healthcare-specific profile of whatever data fo=
rmat comes out in the end, so it's better to be too broad than too narrow a=
s far as our interests are concerned.=C2=A0The transport layer however, has=
 some added complexity. In our context, we're shooting for interoperability=
, so we'd prefer something constrained. I appreciate Mike's input that thes=
e are application layer decisions. However, if we're talking about cloud pr=
ovider-to-cloud provider communication, that certainly is facilitated by a =
well-defined transport layer. Again, we're willing to profile whatever the =
group comes up with for our own ends, but I don't really see the benefit of=
 having a loosely defined transport layer - it just seems like more work fo=
r all the implementers to actually agree on endpoints on a case-by-case bas=
is.=C2=A0Looking forward to discussing further in Berlin!=C2=A0Sarah
Sarah SquireEngage Identityhttp://engageidentity.com=C2=A0On Sat, May 7, 20=
16 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com> wrote:
We also set things up so even a domain specific event can be extended.=C2=
=A0=C2=A0Eg on a password reset event, so event publishers may want to add =
security domain specific attributes. The spec lets them do that while avoid=
ing interop issues.=C2=A0=C2=A0I believe in the spec we had the example of =
an account reset and the publisher adds reset count as an extension.=C2=A0

Phil
On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com> wrote:
Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 so c=
ommon claims can be defined once and then reused.=C2=A0From:=C2=A0Vivek Bis=
was
Sent:=C2=A0Saturday, May 7, 2016 1:24 PM
To:=C2=A0Mike Jones
Cc:=C2=A0Alan Karp;=C2=A0Morteza Ansari (moransar);=C2=A0id-event@ietf.org
Subject:=C2=A0Re: [Id-event] Straw man text for proposed charter=C2=A0Yes, =
I agree that the claims can be application specific, however there is a pos=
sibility to define claims which are domain specific. Thereby claims generat=
ed in one application could be understood by another =C2=A0application with=
in the same domain.=C2=A0With microservices based architecture getting lot =
of attention, if two different micro services defining different claims for=
 the same claim, it can create confusion.=C2=A0Nevertheless this well defin=
ed claims for a particular domain can be an extension to the core specifica=
tion.=C2=A0-Vivek Biswas=C2=A0 Consulting Member, Oracle

Sent from my iPhone
On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com> wrote:
Thanks Alan,=C2=A0Interoperability will be on a per-application basis, just=
 like JWT interoperability.=C2=A0 The claims needed in an identity event ar=
e application-specific, just like claims are for JWTs.=C2=A0 This is the sa=
me standards posture and JWTs are a huge success =E2=80=93 including for in=
teroperability, even if I do say so myself.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 Best wishes,=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 -- Mike=C2=A0=C2=A0=C2=A0=C2=A0From:=C2=A0Alan Karp
Sent:=C2=A0Saturday, May 7, 2016 10:23 AM
To:=C2=A0Mike Jones
Cc:=C2=A0Morteza Ansari (moransar);=C2=A0id-event@ietf.org
Subject:=C2=A0Re: [Id-event] Straw man text for proposed charter=C2=A0As on=
e who proposed doing more, I believe that your position is valid.=C2=A0 My =
only question is whether or not that will be enough for interoperability.

--------------
Alan Karp=C2=A0On Thu, May 5, 2016 at 10:00 PM, Mike Jones <Michael.Jones@m=
icrosoft.com> wrote:
Thanks guys, for writing the initial charter text.=C2=A0 Reading it now, I =
am extremely worried by the scope creep evident in the proposal.=C2=A0I str=
ongly support a working group to define an ID Events data format.=C2=A0 I j=
ust as strongly believe that specific event delivery mechanisms will necess=
arily be application-specific and therefore MUST be explicitly be stated as=
 being out of scope in the working group charter.=C2=A0 Attempting to speci=
fy a particular event delivery mechanism will take something that could be =
simple and quick to approve and bog it down in necessarily application-spec=
ific debates.=C2=A0Should event delivery be reliable?=C2=A0 That=E2=80=99s =
an application-specific decision.Should events be idempotent?=C2=A0 That=E2=
=80=99s an application-specific decision.Should events be unicast, multicas=
t, or broadcast?=C2=A0 That=E2=80=99s an application-specific decision.Shou=
ld events have categories with category-specific subscriptions?=C2=A0 That=
=E2=80=99s an application-specific decision.Should only one party at a time=
 be able to register for delivery of events or should multiple parties be a=
ble to request delivery?=C2=A0 That=E2=80=99s an application-specific decis=
ion.I could continue with this list, but I think you all get the point=E2=
=80=A6=C2=A0If we start debating application-specific event delivery mechan=
isms, we=E2=80=99ll please almost no one, since nearly all applications hav=
e different event delivery requirements.=C2=A0 We MUST explicitly rule all =
delivery mechanisms as being out of scope.=C2=A0If we define only a data fo=
rmat, we can quickly produce a very useful specification.=C2=A0 If we don=
=E2=80=99t, we=E2=80=99ll get bogged down in the mud of debating which appl=
ications we=E2=80=99re catering to and which we aren=E2=80=99t =E2=80=93 an=
 exercise of picking favorites and limiting applicability of the specificat=
ion.=C2=A0 That way is a slow, painful descent into standards quicksand =E2=
=80=93 something we must avoid.=C2=A0 Having a standard ID events represent=
ation is far too important to tie to a particular limited event delivery me=
chanism.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Sincerely,=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- Mike=C2=A0From:=C2=A0Id-event [mail=
to:id-event-bounces@ietf.org]=C2=A0On Behalf Of=C2=A0Alan Karp
Sent:=C2=A0Thursday, May 5, 2016 9:43 PM
To:=C2=A0Morteza Ansari (moransar) <moransar@cisco.com>
Cc:=C2=A0id-event@ietf.org
Subject:=C2=A0Re: [Id-event] Straw man text for proposed charter=C2=A0I don=
't see anything about access control for publishing events and subscribing =
to them.=C2=A0 I also think the spec should allow filters on subscriptions.

--------------
Alan Karp=C2=A0On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar) <=
moransar@cisco.com> wrote:
Hi folks,=C2=A0At IIW a few of us (Phil, William, Adam, and I) huddled for =
a bit and put together the attached as a straw man charter proposal to star=
t the discussion. Please send your comments and suggestions for any changes=
 or propose a new one if you think its necessary.=C2=A0=C2=A0Cheers,Morteza
_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event
=C2=A0
=C2=A0

_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event


_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event

_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event
=C2=A0
_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event



  =20
------=_Part_419242_284661789.1473267836585
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:verdana, helvetica, sans-serif;font-size:16px"><div><span>Hi Phi=
l,</span></div><div><span><br></span></div><div>&nbsp;Thanks for asking the=
 question and also adding more description to the "validation" task.</div><=
div><br></div><div>The Obligation here means "Do we need to take any action=
s if the endpoints don't work"</div><div id=3D"yui_3_16_0_ym19_1_1473266322=
087_7842"><br></div><div id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D=
"ltr">Do we need to send any alert in case of someone is trying to do DoS a=
ttacks"</div><div id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"ltr"><=
br></div><div id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"ltr">This =
obligation is an optional feature which can/may be fulfilled upon the valid=
ation task.</div><div id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"lt=
r"><br></div><div id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"ltr">R=
egards</div><div id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"ltr">Vi=
vek Biswas</div><div id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"ltr=
">Consulting Member @Security</div><div id=3D"yui_3_16_0_ym19_1_14732663220=
87_7841" dir=3D"ltr">Oracle</div><div class=3D"qtdSeparateBR" id=3D"yui_3_1=
6_0_ym19_1_1473266322087_7508"><br><br></div><div class=3D"yahoo_quoted" id=
=3D"yui_3_16_0_ym19_1_1473266322087_7516" style=3D"display: block;">  <div =
style=3D"font-family: verdana, helvetica, sans-serif; font-size: 16px;" id=
=3D"yui_3_16_0_ym19_1_1473266322087_7515"> <div style=3D"font-family: Helve=
ticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font=
-size: 16px;" id=3D"yui_3_16_0_ym19_1_1473266322087_7514"> <div dir=3D"ltr"=
 id=3D"yui_3_16_0_ym19_1_1473266322087_7513"> <font size=3D"2" face=3D"Aria=
l" id=3D"yui_3_16_0_ym19_1_1473266322087_7512"> <hr size=3D"1" id=3D"yui_3_=
16_0_ym19_1_1473266322087_7511"> <b><span style=3D"font-weight:bold;">From:=
</span></b> Phil Hunt &lt;phil.hunt@oracle.com&gt;<br> <b><span style=3D"fo=
nt-weight: bold;">To:</span></b> Vivek Biswas &lt;vivek_biswas@yahoo.com&gt=
; <br><b><span style=3D"font-weight: bold;">Cc:</span></b> Mike Jones &lt;M=
ichael.Jones@microsoft.com&gt;; "id-event@ietf.org" &lt;id-event@ietf.org&g=
t;; Marius Scurtescu &lt;mscurtescu@google.com&gt;; Alexey Melnikov &lt;aam=
elnikov@fastmail.fm&gt;; Morteza Ansari &lt;moransar@cisco.com&gt;; William=
 Denniss &lt;wdenniss@google.com&gt;; Leif Johansson &lt;leifj@sunet.se&gt;=
<br> <b><span style=3D"font-weight: bold;">Sent:</span></b> Wednesday, Sept=
ember 7, 2016 9:50 AM<br> <b><span style=3D"font-weight: bold;">Subject:</s=
pan></b> Re: [Id-event] Straw man text for proposed charter<br> </font> </d=
iv> <div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1473266322087_76=
52"><br><div id=3D"yiv6965053192"><div id=3D"yui_3_16_0_ym19_1_147326632208=
7_7651"><div class=3D"yiv6965053192" id=3D"yui_3_16_0_ym19_1_1473266322087_=
7844">Vivek,</div><div class=3D"yiv6965053192"><br clear=3D"none" class=3D"=
yiv6965053192"></div>Can you elaborate?<div class=3D"yiv6965053192" id=3D"y=
ui_3_16_0_ym19_1_1473266322087_7719"><br clear=3D"none" class=3D"yiv6965053=
192"></div><div class=3D"yiv6965053192" id=3D"yui_3_16_0_ym19_1_14732663220=
87_7781">The validation just ensures that the endpoints actually work. &nbs=
p;It also serves to block DoS issues where someone accidentally or intentio=
nally tries to send SETs to an unwilling subscriber.</div><div class=3D"yiv=
6965053192" id=3D"yui_3_16_0_ym19_1_1473266322087_7650"><br clear=3D"none" =
class=3D"yiv6965053192"><div class=3D"yiv6965053192" id=3D"yui_3_16_0_ym19_=
1_1473266322087_7649">
<div class=3D"yiv6965053192" style=3D"color:rgb(0, 0, 0);letter-spacing:nor=
mal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px=
;word-wrap:break-word;" id=3D"yui_3_16_0_ym19_1_1473266322087_7648"><div cl=
ass=3D"yiv6965053192" style=3D"color:rgb(0, 0, 0);letter-spacing:normal;tex=
t-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-w=
rap:break-word;" id=3D"yui_3_16_0_ym19_1_1473266322087_7647"><div class=3D"=
yiv6965053192" id=3D"yui_3_16_0_ym19_1_1473266322087_7646"><span class=3D"y=
iv6965053192Apple-style-span" style=3D"border-collapse:separate;line-height=
:normal;border-spacing:0px;"></span><div class=3D"yiv6965053192" style=3D"w=
ord-wrap:break-word;" id=3D"yui_3_16_0_ym19_1_1473266322087_7645"><div clas=
s=3D"yiv6965053192" id=3D"yui_3_16_0_ym19_1_1473266322087_7644"><div class=
=3D"yiv6965053192" id=3D"yui_3_16_0_ym19_1_1473266322087_7643"><div class=
=3D"yiv6965053192" id=3D"yui_3_16_0_ym19_1_1473266322087_7642">Phil</div><d=
iv class=3D"yiv6965053192"><br clear=3D"none" class=3D"yiv6965053192"></div=
><div class=3D"yiv6965053192">@independentid</div><div class=3D"yiv69650531=
92"><a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" target=3D"_b=
lank" href=3D"http://www.independentid.com/">www.independentid.com</a></div=
></div></div></div><a rel=3D"nofollow" shape=3D"rect" class=3D"yiv696505319=
2" ymailto=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" href=3D"mailto=
:phil.hunt@oracle.com" style=3D"orphans:2;widows:2;">phil.hunt@oracle.com</=
a></div><div class=3D"yiv6965053192"><br clear=3D"none" class=3D"yiv6965053=
192"></div></div><br clear=3D"none" class=3D"yiv6965053192Apple-interchange=
-newline"></div><br clear=3D"none" class=3D"yiv6965053192Apple-interchange-=
newline"><br clear=3D"none" class=3D"yiv6965053192Apple-interchange-newline=
">
</div>
<br clear=3D"none" class=3D"yiv6965053192"><div class=3D"yiv6965053192yqt47=
80177444" id=3D"yiv6965053192yqt95605"><div><blockquote class=3D"yiv6965053=
192" type=3D"cite"><div class=3D"yiv6965053192">On Sep 7, 2016, at 9:32 AM,=
 Vivek Biswas &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192=
" ymailto=3D"mailto:vivek_biswas@yahoo.com" target=3D"_blank" href=3D"mailt=
o:vivek_biswas@yahoo.com">vivek_biswas@yahoo.com</a>&gt; wrote:</div><br cl=
ear=3D"none" class=3D"yiv6965053192Apple-interchange-newline"><div class=3D=
"yiv6965053192"><div class=3D"yiv6965053192" style=3D"font-style:normal;fon=
t-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;w=
hite-space:normal;word-spacing:0px;background-color:rgb(255, 255, 255);font=
-family:verdana, helvetica, sans-serif;font-size:16px;"><div class=3D"yiv69=
65053192" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">Hi Mike=
,</div><div class=3D"yiv6965053192" id=3D"yiv6965053192yui_3_16_0_ym19_1_14=
73265247048_12746"><br clear=3D"none" class=3D"yiv6965053192"></div><div cl=
ass=3D"yiv6965053192" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12=
746">I believe there is one more item that MAY be added.</div><div class=3D=
"yiv6965053192" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746"><=
br clear=3D"none" class=3D"yiv6965053192"></div><div class=3D"yiv6965053192=
" dir=3D"ltr" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">Aft=
er the line "<span class=3D"yiv6965053192" id=3D"yiv6965053192yui_3_16_0_ym=
19_1_1473265247048_12804" style=3D"font-family:pg-1ff9;line-height:37.2852p=
x;white-space:pre-wrap;"><font class=3D"yiv6965053192" id=3D"yiv6965053192y=
ui_3_16_0_ym19_1_1473265247048_13077" size=3D"3">Methods for validating eve=
nt feed subscriptions"</font></span></div><div class=3D"yiv6965053192" dir=
=3D"ltr" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746"><span cl=
ass=3D"yiv6965053192" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_13=
175" style=3D"font-family:pg-1ff9;line-height:37.2852px;white-space:pre-wra=
p;"><font class=3D"yiv6965053192" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473=
265247048_13174" size=3D"3">"Obligation that may be needed to be fulfilled =
upon validating an event feed".</font></span></div><div class=3D"yiv6965053=
192" dir=3D"ltr" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">=
<br clear=3D"none" class=3D"yiv6965053192"></div><div class=3D"yiv696505319=
2" dir=3D"ltr" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">Re=
gards</div><div class=3D"yiv6965053192" dir=3D"ltr" id=3D"yiv6965053192yui_=
3_16_0_ym19_1_1473265247048_12746">Vivek Biswas</div><div class=3D"yiv69650=
53192" dir=3D"ltr" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746=
">Consulting Member @Security</div><div class=3D"yiv6965053192" dir=3D"ltr"=
 id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">Oracle.</div><di=
v class=3D"yiv6965053192" dir=3D"ltr" id=3D"yiv6965053192yui_3_16_0_ym19_1_=
1473265247048_12746"><br clear=3D"none" class=3D"yiv6965053192"></div><div =
class=3D"yiv6965053192" dir=3D"ltr" id=3D"yiv6965053192yui_3_16_0_ym19_1_14=
73265247048_12746"><br clear=3D"none" class=3D"yiv6965053192"></div><div cl=
ass=3D"yiv6965053192qtdSeparateBR"><br clear=3D"none" class=3D"yiv696505319=
2"><br clear=3D"none" class=3D"yiv6965053192"></div><div class=3D"yiv696505=
3192yahoo_quoted" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12800"=
 style=3D"display:block;"><div class=3D"yiv6965053192" id=3D"yiv6965053192y=
ui_3_16_0_ym19_1_1473265247048_12799" style=3D"font-family:verdana, helveti=
ca, sans-serif;font-size:16px;"><div class=3D"yiv6965053192" id=3D"yiv69650=
53192yui_3_16_0_ym19_1_1473265247048_12798" style=3D"font-family:HelveticaN=
eue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;font-s=
ize:16px;"><div class=3D"yiv6965053192" dir=3D"ltr" id=3D"yiv6965053192yui_=
3_16_0_ym19_1_1473265247048_12797"><font class=3D"yiv6965053192" id=3D"yiv6=
965053192yui_3_16_0_ym19_1_1473265247048_12796" size=3D"2" face=3D"Arial"><=
/font><hr class=3D"yiv6965053192" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473=
265247048_12795" size=3D"1"><b class=3D"yiv6965053192"><span class=3D"yiv69=
65053192" style=3D"font-weight:bold;">From:</span></b><span class=3D"yiv696=
5053192Apple-converted-space">&nbsp;</span>Mike Jones &lt;<a rel=3D"nofollo=
w" shape=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:Michael.Jones@m=
icrosoft.com" target=3D"_blank" href=3D"mailto:Michael.Jones@microsoft.com"=
>Michael.Jones@microsoft.com</a>&gt;<br clear=3D"none" class=3D"yiv69650531=
92"><b class=3D"yiv6965053192"><span class=3D"yiv6965053192" style=3D"font-=
weight:bold;">To:</span></b><span class=3D"yiv6965053192Apple-converted-spa=
ce">&nbsp;</span>"<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192=
" ymailto=3D"mailto:id-event@ietf.org" target=3D"_blank" href=3D"mailto:id-=
event@ietf.org">id-event@ietf.org</a>" &lt;<a rel=3D"nofollow" shape=3D"rec=
t" class=3D"yiv6965053192" ymailto=3D"mailto:id-event@ietf.org" target=3D"_=
blank" href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a>&gt;<span cla=
ss=3D"yiv6965053192Apple-converted-space">&nbsp;</span><br clear=3D"none" c=
lass=3D"yiv6965053192"><b class=3D"yiv6965053192"><span class=3D"yiv6965053=
192" style=3D"font-weight:bold;">Cc:</span></b><span class=3D"yiv6965053192=
Apple-converted-space">&nbsp;</span>Marius Scurtescu &lt;<a rel=3D"nofollow=
" shape=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:mscurtescu@googl=
e.com" target=3D"_blank" href=3D"mailto:mscurtescu@google.com">mscurtescu@g=
oogle.com</a>&gt;; Alexey Melnikov &lt;<a rel=3D"nofollow" shape=3D"rect" c=
lass=3D"yiv6965053192" ymailto=3D"mailto:aamelnikov@fastmail.fm" target=3D"=
_blank" href=3D"mailto:aamelnikov@fastmail.fm">aamelnikov@fastmail.fm</a>&g=
t;; Morteza Ansari (moransar) &lt;<a rel=3D"nofollow" shape=3D"rect" class=
=3D"yiv6965053192" ymailto=3D"mailto:moransar@cisco.com" target=3D"_blank" =
href=3D"mailto:moransar@cisco.com">moransar@cisco.com</a>&gt;; William Denn=
iss &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" ymailto=
=3D"mailto:wdenniss@google.com" target=3D"_blank" href=3D"mailto:wdenniss@g=
oogle.com">wdenniss@google.com</a>&gt;; Leif Johansson &lt;<a rel=3D"nofoll=
ow" shape=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:leifj@sunet.se=
" target=3D"_blank" href=3D"mailto:leifj@sunet.se">leifj@sunet.se</a>&gt;; =
Phil Hunt (IDM) &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv69650531=
92" ymailto=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" href=3D"mailt=
o:phil.hunt@oracle.com">phil.hunt@oracle.com</a>&gt;<br clear=3D"none" clas=
s=3D"yiv6965053192"><b class=3D"yiv6965053192"><span class=3D"yiv6965053192=
" style=3D"font-weight:bold;">Sent:</span></b><span class=3D"yiv6965053192A=
pple-converted-space">&nbsp;</span>Tuesday, September 6, 2016 5:01 PM<br cl=
ear=3D"none" class=3D"yiv6965053192"><b class=3D"yiv6965053192"><span class=
=3D"yiv6965053192" style=3D"font-weight:bold;">Subject:</span></b><span cla=
ss=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Re: [Id-event] Straw=
 man text for proposed charter<br clear=3D"none" class=3D"yiv6965053192"></=
div><div class=3D"yiv6965053192y_msg_container"><br clear=3D"none" class=3D=
"yiv6965053192"><div class=3D"yiv6965053192" id=3D"yiv6965053192"><div clas=
s=3D"yiv6965053192"><div class=3D"yiv6965053192WordSection1"><div class=3D"=
yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><=
span class=3D"yiv6965053192" style=3D"font-size:11pt;">An updated and simpl=
ified charter is attached.&nbsp; This draft has been reviewed by Phil Hunt,=
 William Denniss, Marius Scurtescu.</span></div><div class=3D"yiv6965053192=
MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=3D=
"yiv6965053192" style=3D"font-size:11pt;">&nbsp;</span></div><div class=3D"=
yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><=
span class=3D"yiv6965053192" style=3D"font-size:11pt;">Input from Alexey Me=
lnikov is that we should probably charter a working group, rather than try =
to go the AD-sponsored route.&nbsp; Therefore, please review this draft cha=
rter and let us know if you think it=E2=80=99s ready to go.</span></div><di=
v class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-si=
ze:12pt;"><span class=3D"yiv6965053192" style=3D"font-size:11pt;">&nbsp;</s=
pan></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0=
001pt;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"font-size:11p=
t;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,</span></div><div class=3D"yiv696505319=
2MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=
=3D"yiv6965053192" style=3D"font-size:11pt;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mi=
ke</span></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0i=
n 0.0001pt;font-size:12pt;"><a rel=3D"nofollow" shape=3D"rect" class=3D"yiv=
6965053192" name=3D"_MailEndCompose" style=3D"color:purple;text-decoration:=
underline;" href=3D""><span class=3D"yiv6965053192" style=3D"font-size:11pt=
;">&nbsp;</span></a></div><span class=3D"yiv6965053192"></span><div class=
=3D"yiv6965053192yqt5176189511" id=3D"yiv6965053192yqt64133"><div class=3D"=
yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><=
b class=3D"yiv6965053192"><span class=3D"yiv6965053192" style=3D"font-size:=
11pt;">From:</span></b><span class=3D"yiv6965053192" style=3D"font-size:11p=
t;"><span class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Sarah S=
quire [<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" ymailto=
=3D"mailto:sarah@engageidentity.com" target=3D"_blank" href=3D"mailto:sarah=
@engageidentity.com">mailto:sarah@engageidentity.com</a>]<span class=3D"yiv=
6965053192Apple-converted-space">&nbsp;</span><br clear=3D"none" class=3D"y=
iv6965053192"><b class=3D"yiv6965053192">Sent:</b><span class=3D"yiv6965053=
192Apple-converted-space">&nbsp;</span>Thursday, July 14, 2016 10:59 PM<br =
clear=3D"none" class=3D"yiv6965053192"><b class=3D"yiv6965053192">To:</b><s=
pan class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Phil Hunt (ID=
M) &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" ymailto=
=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" href=3D"mailto:phil.hunt=
@oracle.com">phil.hunt@oracle.com</a>&gt;<br clear=3D"none" class=3D"yiv696=
5053192"><b class=3D"yiv6965053192">Cc:</b><span class=3D"yiv6965053192Appl=
e-converted-space">&nbsp;</span>Mike Jones &lt;<a rel=3D"nofollow" shape=3D=
"rect" class=3D"yiv6965053192" ymailto=3D"mailto:Michael.Jones@microsoft.co=
m" target=3D"_blank" href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jo=
nes@microsoft.com</a>&gt;; Alan Karp &lt;<a rel=3D"nofollow" shape=3D"rect"=
 class=3D"yiv6965053192" ymailto=3D"mailto:alanhkarp@gmail.com" target=3D"_=
blank" href=3D"mailto:alanhkarp@gmail.com">alanhkarp@gmail.com</a>&gt;; Viv=
ek Biswas &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" ym=
ailto=3D"mailto:vivek_biswas@yahoo.com" target=3D"_blank" href=3D"mailto:vi=
vek_biswas@yahoo.com">vivek_biswas@yahoo.com</a>&gt;; Morteza Ansari (moran=
sar) &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" ymailto=
=3D"mailto:moransar@cisco.com" target=3D"_blank" href=3D"mailto:moransar@ci=
sco.com">moransar@cisco.com</a>&gt;; <a rel=3D"nofollow" shape=3D"rect" cla=
ss=3D"yiv6965053192" ymailto=3D"mailto:id-event@ietf.org" target=3D"_blank"=
 href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a><br clear=3D"none" =
class=3D"yiv6965053192"><b class=3D"yiv6965053192">Subject:</b><span class=
=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Re: [Id-event] Straw m=
an text for proposed charter</span></div><div class=3D"yiv6965053192MsoNorm=
al" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div><div clas=
s=3D"yiv6965053192"><div class=3D"yiv6965053192"><div class=3D"yiv696505319=
2MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">Just submitti=
ng my two cents in writing before we hopefully have a chance to meet about =
this next week...</div></div><div class=3D"yiv6965053192"><div class=3D"yiv=
6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbs=
p;</div></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in=
 0.0001pt;font-size:12pt;">Looking at this charter from the perspective of =
the OIDF HEART working group, I think it's going down a good path. In terms=
 of the data format, this is less structured than what I was envisioning, b=
ut we could easily do a healthcare-specific profile of whatever data format=
 comes out in the end, so it's better to be too broad than too narrow as fa=
r as our interests are concerned.</div><div class=3D"yiv6965053192"><div cl=
ass=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:1=
2pt;">&nbsp;</div></div><div class=3D"yiv6965053192"><div class=3D"yiv69650=
53192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">The trans=
port layer however, has some added complexity. In our context, we're shooti=
ng for interoperability, so we'd prefer something constrained. I appreciate=
 Mike's input that these are application layer decisions. However, if we're=
 talking about cloud provider-to-cloud provider communication, that certain=
ly is facilitated by a well-defined transport layer. Again, we're willing t=
o profile whatever the group comes up with for our own ends, but I don't re=
ally see the benefit of having a loosely defined transport layer - it just =
seems like more work for all the implementers to actually agree on endpoint=
s on a case-by-case basis.</div></div><div class=3D"yiv6965053192"><div cla=
ss=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12=
pt;">&nbsp;</div></div><div class=3D"yiv6965053192"><div class=3D"yiv696505=
3192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">Looking fo=
rward to discussing further in Berlin!</div></div><div class=3D"yiv69650531=
92"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;=
font-size:12pt;">&nbsp;</div></div><div class=3D"yiv6965053192"><div class=
=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt=
;">Sarah</div></div></div></div><div class=3D"yiv6965053192"><div class=3D"=
yiv6965053192yqt5176189511" id=3D"yiv6965053192yqt99533"><div class=3D"yiv6=
965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><br c=
lear=3D"all" class=3D"yiv6965053192"></div><div class=3D"yiv6965053192"><di=
v class=3D"yiv6965053192"><div class=3D"yiv6965053192"><div class=3D"yiv696=
5053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.00=
01pt;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"color:rgb(136,=
 136, 136);">Sarah Squire</span></div></div><div class=3D"yiv6965053192"><d=
iv class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-s=
ize:12pt;"><span class=3D"yiv6965053192" style=3D"color:rgb(136, 136, 136);=
">Engage Identity</span></div></div><div class=3D"yiv6965053192"><div class=
=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt=
;"><span class=3D"yiv6965053192" style=3D"color:rgb(136, 136, 136);"><a rel=
=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" target=3D"_blank" href=
=3D"http://engageidentity.com/" style=3D"color:purple;text-decoration:under=
line;"><span class=3D"yiv6965053192" style=3D"color:rgb(17, 85, 204);">http=
://engageidentity.com</span></a></span></div></div></div></div></div><div c=
lass=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:=
12pt;">&nbsp;</div><div class=3D"yiv6965053192"><div class=3D"yiv6965053192=
MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">On Sat, May 7,=
 2016 at 6:53 PM, Phil Hunt (IDM) &lt;<a rel=3D"nofollow" shape=3D"rect" cl=
ass=3D"yiv6965053192" ymailto=3D"mailto:phil.hunt@oracle.com" target=3D"_bl=
ank" href=3D"mailto:phil.hunt@oracle.com" style=3D"color:purple;text-decora=
tion:underline;">phil.hunt@oracle.com</a>&gt; wrote:</div><blockquote class=
=3D"yiv6965053192" style=3D"border-style:none none none solid;border-left-c=
olor:rgb(204, 204, 204);border-left-width:1pt;padding:0in 0in 0in 6pt;margi=
n-left:4.8pt;margin-right:0in;"><div class=3D"yiv6965053192"><div class=3D"=
yiv6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0i=
n 0.0001pt;font-size:12pt;">We also set things up so even a domain specific=
 event can be extended.&nbsp;</div></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size=
:12pt;">&nbsp;</div></div><div class=3D"yiv6965053192"><div class=3D"yiv696=
5053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">Eg on a=
 password reset event, so event publishers may want to add security domain =
specific attributes. The spec lets them do that while avoiding interop issu=
es.&nbsp;</div></div><div class=3D"yiv6965053192"><div class=3D"yiv69650531=
92MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div>=
</div><div class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" st=
yle=3D"margin:0in 0in 0.0001pt;font-size:12pt;">I believe in the spec we ha=
d the example of an account reset and the publisher adds reset count as an =
extension.&nbsp;<span class=3D"yiv6965053192" style=3D"color:rgb(136, 136, =
136);"><br clear=3D"none" class=3D"yiv6965053192"><br clear=3D"none" class=
=3D"yiv6965053192"><span class=3D"yiv6965053192hoenzb">Phil</span></span></=
div></div><div class=3D"yiv6965053192"><div class=3D"yiv6965053192"><div cl=
ass=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin=
:0in 0in 12pt;font-size:12pt;"><br clear=3D"none" class=3D"yiv6965053192">O=
n May 7, 2016, at 13:31, Mike Jones &lt;<a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" ymailto=3D"mailto:Michael.Jones@microsoft.com" targ=
et=3D"_blank" href=3D"mailto:Michael.Jones@microsoft.com" style=3D"color:pu=
rple;text-decoration:underline;">Michael.Jones@microsoft.com</a>&gt; wrote:=
</div></div><blockquote class=3D"yiv6965053192" style=3D"margin-top:5pt;mar=
gin-bottom:5pt;"><div class=3D"yiv6965053192"><div class=3D"yiv6965053192">=
<div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font=
-size:12pt;">Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =
=E2=80=93 so common claims can be defined once and then reused.</div><div c=
lass=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:=
12pt;">&nbsp;</div><div class=3D"yiv6965053192" style=3D"border-style:solid=
 none none;border-top-color:rgb(225, 225, 225);border-top-width:1pt;padding=
:3pt 0in 0in;"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0i=
n 0.0001pt;font-size:12pt;"><b class=3D"yiv6965053192">From:<span class=3D"=
yiv6965053192Apple-converted-space">&nbsp;</span></b><a rel=3D"nofollow" sh=
ape=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:vivek_biswas@yahoo.c=
om" target=3D"_blank" href=3D"mailto:vivek_biswas@yahoo.com" style=3D"color=
:purple;text-decoration:underline;">Vivek Biswas</a><br clear=3D"none" clas=
s=3D"yiv6965053192"><b class=3D"yiv6965053192">Sent:<span class=3D"yiv69650=
53192Apple-converted-space">&nbsp;</span></b>Saturday, May 7, 2016 1:24 PM<=
br clear=3D"none" class=3D"yiv6965053192"><b class=3D"yiv6965053192">To:<sp=
an class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b><a rel=3D"=
nofollow" shape=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:Michael.=
Jones@microsoft.com" target=3D"_blank" href=3D"mailto:Michael.Jones@microso=
ft.com" style=3D"color:purple;text-decoration:underline;">Mike Jones</a><br=
 clear=3D"none" class=3D"yiv6965053192"><b class=3D"yiv6965053192">Cc:<span=
 class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b><a rel=3D"no=
follow" shape=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:alanhkarp@=
gmail.com" target=3D"_blank" href=3D"mailto:alanhkarp@gmail.com" style=3D"c=
olor:purple;text-decoration:underline;">Alan Karp</a>;<span class=3D"yiv696=
5053192Apple-converted-space">&nbsp;</span><a rel=3D"nofollow" shape=3D"rec=
t" class=3D"yiv6965053192" ymailto=3D"mailto:moransar@cisco.com" target=3D"=
_blank" href=3D"mailto:moransar@cisco.com" style=3D"color:purple;text-decor=
ation:underline;">Morteza Ansari (moransar)</a>;<span class=3D"yiv696505319=
2Apple-converted-space">&nbsp;</span><a rel=3D"nofollow" shape=3D"rect" cla=
ss=3D"yiv6965053192" ymailto=3D"mailto:id-event@ietf.org" target=3D"_blank"=
 href=3D"mailto:id-event@ietf.org" style=3D"color:purple;text-decoration:un=
derline;">id-event@ietf.org</a><br clear=3D"none" class=3D"yiv6965053192"><=
b class=3D"yiv6965053192">Subject:<span class=3D"yiv6965053192Apple-convert=
ed-space">&nbsp;</span></b>Re: [Id-event] Straw man text for proposed chart=
er</div></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in=
 0.0001pt;font-size:12pt;">&nbsp;</div></div><div class=3D"yiv6965053192"><=
div class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"=
margin:0in 0in 0.0001pt;font-size:12pt;">Yes, I agree that the claims can b=
e application specific, however there is a possibility to define claims whi=
ch are domain specific. Thereby claims generated in one application could b=
e understood by another &nbsp;application within the same domain.</div></di=
v><div class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" style=
=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div></div><div class=
=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0i=
n 0in 0.0001pt;font-size:12pt;">With microservices based architecture getti=
ng lot of attention, if two different micro services defining different cla=
ims for the same claim, it can create confusion.</div></div><div class=3D"y=
iv6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in=
 0.0001pt;font-size:12pt;">&nbsp;</div></div><div class=3D"yiv6965053192"><=
div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-=
size:12pt;">Nevertheless this well defined claims for a particular domain c=
an be an extension to the core specification.</div></div><div class=3D"yiv6=
965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.=
0001pt;font-size:12pt;">&nbsp;</div></div><div class=3D"yiv6965053192"><div=
 class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-siz=
e:12pt;">-Vivek Biswas</div></div><div class=3D"yiv6965053192"><div class=
=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt=
;">&nbsp; Consulting Member, Oracle<br clear=3D"none" class=3D"yiv696505319=
2"><br clear=3D"none" class=3D"yiv6965053192">Sent from my iPhone</div></di=
v><div class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" style=
=3D"margin:0in 0in 12pt;font-size:12pt;"><br clear=3D"none" class=3D"yiv696=
5053192">On May 7, 2016, at 1:04 PM, Mike Jones &lt;<a rel=3D"nofollow" sha=
pe=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:Michael.Jones@microso=
ft.com" target=3D"_blank" href=3D"mailto:Michael.Jones@microsoft.com" style=
=3D"color:purple;text-decoration:underline;">Michael.Jones@microsoft.com</a=
>&gt; wrote:</div></div><blockquote class=3D"yiv6965053192" style=3D"margin=
-top:5pt;margin-bottom:5pt;"><div class=3D"yiv6965053192"><div class=3D"yiv=
6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0=
.0001pt;font-size:12pt;">Thanks Alan,</div><div class=3D"yiv6965053192MsoNo=
rmal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div><div cl=
ass=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:1=
2pt;"><span class=3D"yiv6965053192" style=3D"color:rgb(0, 32, 96);">Interop=
erability will be on a per-application basis, just like JWT interoperabilit=
y.&nbsp; The claims needed in an identity event are application-specific, j=
ust like claims are for JWTs.&nbsp; This is the same standards posture and =
JWTs are a huge success =E2=80=93 including for interoperability, even if I=
 do say so myself.</span></div><div class=3D"yiv6965053192MsoNormal" style=
=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"color:rgb(0, 32, 96);">&nbsp;</span></div><div class=3D"yiv6965053=
192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=
=3D"yiv6965053192" style=3D"color:rgb(0, 32, 96);">&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; Best wishes,</span></div><div class=3D"yiv6965053192MsoN=
ormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=3D"yiv=
6965053192" style=3D"color:rgb(0, 32, 96);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; -- Mike</span></div><div class=3D"yiv6965053192MsoNormal" style=
=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div><div class=3D"yiv6=
965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp=
;</div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001=
pt;font-size:12pt;">&nbsp;</div><div class=3D"yiv6965053192MsoNormal" style=
=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div><div class=3D"yiv6=
965053192" style=3D"border-style:solid none none;border-top-color:rgb(225, =
225, 225);border-top-width:1pt;padding:3pt 0in 0in;"><div class=3D"yiv69650=
53192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><b class=
=3D"yiv6965053192">From:<span class=3D"yiv6965053192Apple-converted-space">=
&nbsp;</span></b><a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192"=
 ymailto=3D"mailto:alanhkarp@gmail.com" target=3D"_blank" href=3D"mailto:al=
anhkarp@gmail.com" style=3D"color:purple;text-decoration:underline;">Alan K=
arp</a><br clear=3D"none" class=3D"yiv6965053192"><b class=3D"yiv6965053192=
">Sent:<span class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b>=
Saturday, May 7, 2016 10:23 AM<br clear=3D"none" class=3D"yiv6965053192"><b=
 class=3D"yiv6965053192">To:<span class=3D"yiv6965053192Apple-converted-spa=
ce">&nbsp;</span></b><a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053=
192" ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" href=
=3D"mailto:Michael.Jones@microsoft.com" style=3D"color:purple;text-decorati=
on:underline;">Mike Jones</a><br clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">Cc:<span class=3D"yiv6965053192Apple-converted-spac=
e">&nbsp;</span></b><a rel=3D"nofollow" shape=3D"rect" class=3D"yiv69650531=
92" ymailto=3D"mailto:moransar@cisco.com" target=3D"_blank" href=3D"mailto:=
moransar@cisco.com" style=3D"color:purple;text-decoration:underline;">Morte=
za Ansari (moransar)</a>;<span class=3D"yiv6965053192Apple-converted-space"=
>&nbsp;</span><a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" ym=
ailto=3D"mailto:id-event@ietf.org" target=3D"_blank" href=3D"mailto:id-even=
t@ietf.org" style=3D"color:purple;text-decoration:underline;">id-event@ietf=
.org</a><br clear=3D"none" class=3D"yiv6965053192"><b class=3D"yiv696505319=
2">Subject:<span class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>=
</b>Re: [Id-event] Straw man text for proposed charter</div></div><div clas=
s=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12p=
t;">&nbsp;</div></div><div class=3D"yiv6965053192"><div class=3D"yiv6965053=
192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt=
;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"font-size:9.5pt;">=
As one who proposed doing more, I believe that your position is valid.&nbsp=
; My only question is whether or not that will be enough for interoperabili=
ty.</span></div></div><div class=3D"yiv6965053192"><div class=3D"yiv6965053=
192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><br clear=
=3D"all" class=3D"yiv6965053192"></div><div class=3D"yiv6965053192"><div cl=
ass=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin=
:0in 0in 0.0001pt;font-size:12pt;"><br clear=3D"none" class=3D"yiv696505319=
2">--------------<br clear=3D"none" class=3D"yiv6965053192">Alan Karp</div>=
</div></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0=
.0001pt;font-size:12pt;">&nbsp;</div><div class=3D"yiv6965053192"><div clas=
s=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12p=
t;">On Thu, May 5, 2016 at 10:00 PM, Mike Jones &lt;<a rel=3D"nofollow" sha=
pe=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:Michael.Jones@microso=
ft.com" target=3D"_blank" href=3D"mailto:Michael.Jones@microsoft.com" style=
=3D"color:purple;text-decoration:underline;">Michael.Jones@microsoft.com</a=
>&gt; wrote:</div><blockquote class=3D"yiv6965053192" style=3D"border-style=
:none none none solid;border-left-color:rgb(204, 204, 204);border-left-widt=
h:1pt;padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in;"><div cla=
ss=3D"yiv6965053192"><div class=3D"yiv6965053192"><div class=3D"yiv69650531=
92MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=
=3D"yiv6965053192" style=3D"font-size:11pt;">Thanks guys, for writing the i=
nitial charter text.&nbsp; Reading it now, I am extremely worried by the sc=
ope creep evident in the proposal.</span></div><div class=3D"yiv6965053192M=
soNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=3D"=
yiv6965053192" style=3D"font-size:11pt;">&nbsp;</span></div><div class=3D"y=
iv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><s=
pan class=3D"yiv6965053192" style=3D"font-size:11pt;">I strongly support a =
working group to define an ID Events data format.&nbsp; I just as strongly =
believe that specific event delivery mechanisms will necessarily be applica=
tion-specific and therefore MUST be explicitly be stated as being out of sc=
ope in the working group charter.&nbsp; Attempting to specify a particular =
event delivery mechanism will take something that could be simple and quick=
 to approve and bog it down in necessarily application-specific debates.</s=
pan></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0=
001pt;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"font-size:11p=
t;">&nbsp;</span></div><div class=3D"yiv6965053192MsoNormal" style=3D"margi=
n:0in 0in 0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"=
font-size:11pt;">Should event delivery be reliable?&nbsp; That=E2=80=99s an=
 application-specific decision.</span></div><div class=3D"yiv6965053192MsoN=
ormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=3D"yiv=
6965053192" style=3D"font-size:11pt;">Should events be idempotent?&nbsp; Th=
at=E2=80=99s an application-specific decision.</span></div><div class=3D"yi=
v6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><sp=
an class=3D"yiv6965053192" style=3D"font-size:11pt;">Should events be unica=
st, multicast, or broadcast?&nbsp; That=E2=80=99s an application-specific d=
ecision.</span></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:=
0in 0in 0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"fo=
nt-size:11pt;">Should events have categories with category-specific subscri=
ptions?&nbsp; That=E2=80=99s an application-specific decision.</span></div>=
<div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font=
-size:12pt;"><span class=3D"yiv6965053192" style=3D"font-size:11pt;">Should=
 only one party at a time be able to register for delivery of events or sho=
uld multiple parties be able to request delivery?&nbsp; That=E2=80=99s an a=
pplication-specific decision.</span></div><div class=3D"yiv6965053192MsoNor=
mal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=3D"yiv69=
65053192" style=3D"font-size:11pt;">I could continue with this list, but I =
think you all get the point=E2=80=A6</span></div><div class=3D"yiv696505319=
2MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=
=3D"yiv6965053192" style=3D"font-size:11pt;">&nbsp;</span></div><div class=
=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt=
;"><span class=3D"yiv6965053192" style=3D"font-size:11pt;">If we start deba=
ting application-specific event delivery mechanisms, we=E2=80=99ll please a=
lmost no one, since nearly all applications have different event delivery r=
equirements.&nbsp; We MUST explicitly rule all delivery mechanisms as being=
 out of scope.</span></div><div class=3D"yiv6965053192MsoNormal" style=3D"m=
argin:0in 0in 0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" style=
=3D"font-size:11pt;">&nbsp;</span></div><div class=3D"yiv6965053192MsoNorma=
l" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=3D"yiv6965=
053192" style=3D"font-size:11pt;">If we define only a data format, we can q=
uickly produce a very useful specification.&nbsp; If we don=E2=80=99t, we=
=E2=80=99ll get bogged down in the mud of debating which applications we=E2=
=80=99re catering to and which we aren=E2=80=99t =E2=80=93 an exercise of p=
icking favorites and limiting applicability of the specification.&nbsp; Tha=
t way is a slow, painful descent into standards quicksand =E2=80=93 somethi=
ng we must avoid.&nbsp; Having a standard ID events representation is far t=
oo important to tie to a particular limited event delivery mechanism.</span=
></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001=
pt;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"font-size:11pt;"=
>&nbsp;</span></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0=
in 0in 0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"fon=
t-size:11pt;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sincerely,</span><=
/div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt=
;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"font-size:11pt;">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span></div><div class=3D=
"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">=
<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" name=3D"m_302236=
7059336893565_m_1461024254222911" style=3D"color:purple;text-decoration:und=
erline;" href=3D""><span class=3D"yiv6965053192" style=3D"font-size:11pt;">=
&nbsp;</span></a></div><div class=3D"yiv6965053192MsoNormal" style=3D"margi=
n:0in 0in 0.0001pt;font-size:12pt;"><b class=3D"yiv6965053192"><span class=
=3D"yiv6965053192" style=3D"font-size:11pt;">From:</span></b><span class=3D=
"yiv6965053192" style=3D"font-size:11pt;"><span class=3D"yiv6965053192Apple=
-converted-space">&nbsp;</span>Id-event [mailto:<a rel=3D"nofollow" shape=
=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:id-event-bounces@ietf.o=
rg" target=3D"_blank" href=3D"mailto:id-event-bounces@ietf.org" style=3D"co=
lor:purple;text-decoration:underline;">id-event-bounces@ietf.org</a>]<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span><b class=3D"yiv69=
65053192">On Behalf Of<span class=3D"yiv6965053192Apple-converted-space">&n=
bsp;</span></b>Alan Karp<br clear=3D"none" class=3D"yiv6965053192"><b class=
=3D"yiv6965053192">Sent:</b><span class=3D"yiv6965053192Apple-converted-spa=
ce">&nbsp;</span>Thursday, May 5, 2016 9:43 PM<br clear=3D"none" class=3D"y=
iv6965053192"><b class=3D"yiv6965053192">To:</b><span class=3D"yiv696505319=
2Apple-converted-space">&nbsp;</span>Morteza Ansari (moransar) &lt;<a rel=
=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:mora=
nsar@cisco.com" target=3D"_blank" href=3D"mailto:moransar@cisco.com" style=
=3D"color:purple;text-decoration:underline;">moransar@cisco.com</a>&gt;<br =
clear=3D"none" class=3D"yiv6965053192"><b class=3D"yiv6965053192">Cc:</b><s=
pan class=3D"yiv6965053192Apple-converted-space">&nbsp;</span><a rel=3D"nof=
ollow" shape=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:id-event@ie=
tf.org" target=3D"_blank" href=3D"mailto:id-event@ietf.org" style=3D"color:=
purple;text-decoration:underline;">id-event@ietf.org</a><br clear=3D"none" =
class=3D"yiv6965053192"><b class=3D"yiv6965053192">Subject:</b><span class=
=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Re: [Id-event] Straw m=
an text for proposed charter</span></div><div class=3D"yiv6965053192MsoNorm=
al" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div><div clas=
s=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0=
in 0in 0.0001pt;font-size:12pt;">I don't see anything about access control =
for publishing events and subscribing to them.&nbsp; I also think the spec =
should allow filters on subscriptions.</div></div><div class=3D"yiv69650531=
92"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;=
font-size:12pt;"><br clear=3D"all" class=3D"yiv6965053192"></div><div class=
=3D"yiv6965053192"><div class=3D"yiv6965053192"><div class=3D"yiv6965053192=
MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><br clear=3D"n=
one" class=3D"yiv6965053192">--------------<br clear=3D"none" class=3D"yiv6=
965053192">Alan Karp</div></div></div><div class=3D"yiv6965053192MsoNormal"=
 style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div><div class=
=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0i=
n 0in 0.0001pt;font-size:12pt;">On Thu, May 5, 2016 at 11:18 AM, Morteza An=
sari (moransar) &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv69650531=
92" ymailto=3D"mailto:moransar@cisco.com" target=3D"_blank" href=3D"mailto:=
moransar@cisco.com" style=3D"color:purple;text-decoration:underline;">moran=
sar@cisco.com</a>&gt; wrote:</div><blockquote class=3D"yiv6965053192" style=
=3D"border-style:none none none solid;border-left-color:rgb(204, 204, 204);=
border-left-width:1pt;padding:0in 0in 0in 6pt;margin:5pt 0in 5pt 4.8pt;"><d=
iv class=3D"yiv6965053192"><div class=3D"yiv6965053192"><div class=3D"yiv69=
65053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"font-size:10.5pt;">Hi folks,</span></div><=
/div><div class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" sty=
le=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192=
" style=3D"font-size:10.5pt;">&nbsp;</span></div></div><div class=3D"yiv696=
5053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.00=
01pt;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"font-size:10.5=
pt;">At IIW a few of us (Phil, William, Adam, and I) huddled for a bit and =
put together the attached as a straw man charter proposal to start the disc=
ussion. Please send your comments and suggestions for any changes or propos=
e a new one if you think its necessary.</span></div></div><div class=3D"yiv=
6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0=
.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"font-size:1=
0.5pt;">&nbsp;</span></div></div><div class=3D"yiv6965053192"><div class=3D=
"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">=
<span class=3D"yiv6965053192" style=3D"font-size:10.5pt;">&nbsp;</span></di=
v></div><div class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span class=3D"yiv6965053=
192" style=3D"font-size:10.5pt;">Cheers,</span></div></div><div class=3D"yi=
v6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" style=3D"font-size:=
10.5pt;">Morteza</span></div></div></div><div class=3D"yiv6965053192MsoNorm=
al" style=3D"margin:0in 0in 12pt;font-size:12pt;"><br clear=3D"none" class=
=3D"yiv6965053192">_______________________________________________<br clear=
=3D"none" class=3D"yiv6965053192">Id-event mailing list<br clear=3D"none" c=
lass=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" class=3D"yiv69650=
53192" ymailto=3D"mailto:Id-event@ietf.org" target=3D"_blank" href=3D"mailt=
o:Id-event@ietf.org" style=3D"color:purple;text-decoration:underline;">Id-e=
vent@ietf.org</a><br clear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofol=
low" shape=3D"rect" class=3D"yiv6965053192" target=3D"_blank" href=3D"https=
://www.ietf.org/mailman/listinfo/id-event" style=3D"color:purple;text-decor=
ation:underline;">https://www.ietf.org/mailman/listinfo/id-event</a></div><=
/blockquote></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in=
 0in 0.0001pt;font-size:12pt;">&nbsp;</div></div></div></div></blockquote><=
/div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in 0.0001pt=
;font-size:12pt;">&nbsp;</div></div></div></div></blockquote><blockquote cl=
ass=3D"yiv6965053192" style=3D"margin-top:5pt;margin-bottom:5pt;"><div clas=
s=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0=
in 0in 0.0001pt;font-size:12pt;">__________________________________________=
_____<br clear=3D"none" class=3D"yiv6965053192">Id-event mailing list<br cl=
ear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" cla=
ss=3D"yiv6965053192" ymailto=3D"mailto:Id-event@ietf.org" target=3D"_blank"=
 href=3D"mailto:Id-event@ietf.org" style=3D"color:purple;text-decoration:un=
derline;">Id-event@ietf.org</a><br clear=3D"none" class=3D"yiv6965053192"><=
a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" target=3D"_blank"=
 href=3D"https://www.ietf.org/mailman/listinfo/id-event" style=3D"color:pur=
ple;text-decoration:underline;">https://www.ietf.org/mailman/listinfo/id-ev=
ent</a></div></div></blockquote></div></div></blockquote><blockquote class=
=3D"yiv6965053192" style=3D"margin-top:5pt;margin-bottom:5pt;"><div class=
=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0i=
n 0in 0.0001pt;font-size:12pt;">___________________________________________=
____<br clear=3D"none" class=3D"yiv6965053192">Id-event mailing list<br cle=
ar=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" clas=
s=3D"yiv6965053192" ymailto=3D"mailto:Id-event@ietf.org" target=3D"_blank" =
href=3D"mailto:Id-event@ietf.org" style=3D"color:purple;text-decoration:und=
erline;">Id-event@ietf.org</a><br clear=3D"none" class=3D"yiv6965053192"><a=
 rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" target=3D"_blank" =
href=3D"https://www.ietf.org/mailman/listinfo/id-event" style=3D"color:purp=
le;text-decoration:underline;">https://www.ietf.org/mailman/listinfo/id-eve=
nt</a></div></div></blockquote></div></div></div><div class=3D"yiv696505319=
2MsoNormal" style=3D"margin:0in 0in 12pt;font-size:12pt;"><br clear=3D"none=
" class=3D"yiv6965053192">_______________________________________________<b=
r clear=3D"none" class=3D"yiv6965053192">Id-event mailing list<br clear=3D"=
none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" class=3D"y=
iv6965053192" ymailto=3D"mailto:Id-event@ietf.org" target=3D"_blank" href=
=3D"mailto:Id-event@ietf.org" style=3D"color:purple;text-decoration:underli=
ne;">Id-event@ietf.org</a><br clear=3D"none" class=3D"yiv6965053192"><a rel=
=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" target=3D"_blank" href=
=3D"https://www.ietf.org/mailman/listinfo/id-event" style=3D"color:purple;t=
ext-decoration:underline;">https://www.ietf.org/mailman/listinfo/id-event</=
a></div></blockquote></div></div><div class=3D"yiv6965053192MsoNormal" styl=
e=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div></div></div></div=
></div><br clear=3D"none" class=3D"yiv6965053192"><div class=3D"yiv69650531=
92yqt5176189511" id=3D"yiv6965053192yqt18602">_____________________________=
__________________<br clear=3D"none" class=3D"yiv6965053192">Id-event maili=
ng list<br clear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=
=3D"rect" class=3D"yiv6965053192" ymailto=3D"mailto:Id-event@ietf.org" targ=
et=3D"_blank" href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br cl=
ear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" cla=
ss=3D"yiv6965053192" target=3D"_blank" href=3D"https://www.ietf.org/mailman=
/listinfo/id-event">https://www.ietf.org/mailman/listinfo/id-event</a></div=
></div></div></div></div></div></div></blockquote></div></div><br clear=3D"=
none" class=3D"yiv6965053192"></div></div></div><br><br></div> </div> </div=
>  </div></div></body></html>
------=_Part_419242_284661789.1473267836585--


From nobody Wed Sep  7 10:13:58 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2963D12B4D4 for <id-event@ietfa.amsl.com>; Wed,  7 Sep 2016 10:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.709
X-Spam-Level: 
X-Spam-Status: No, score=-5.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85C4CmWwnoh2 for <id-event@ietfa.amsl.com>; Wed,  7 Sep 2016 10:13:54 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7E9F12B21E for <id-event@ietf.org>; Wed,  7 Sep 2016 10:13:54 -0700 (PDT)
Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u87HDrQN006199 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 7 Sep 2016 17:13:53 GMT
Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id u87HDrYZ017415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 7 Sep 2016 17:13:53 GMT
Received: from abhmp0009.oracle.com (abhmp0009.oracle.com [141.146.116.15]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u87HDq4x010984; Wed, 7 Sep 2016 17:13:52 GMT
Received: from [10.0.1.5] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 07 Sep 2016 10:13:51 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_A323B470-AD0A-4CB1-B602-D4C8A687A60D"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Phil Hunt <phil.hunt@oracle.com>
In-Reply-To: <858410497.419243.1473267836614@mail.yahoo.com>
Date: Wed, 7 Sep 2016 10:13:49 -0700
Message-Id: <78DAD4A9-982B-4362-AD9D-F3911578296A@oracle.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <595998295.367982.1473265977000@mail.yahoo.com> <785F772B-5546-4389-BB7F-1D6738BA383A@oracle.com> <858410497.419243.1473267836614@mail.yahoo.com>
To: Vivek Biswas <vivek_biswas@yahoo.com>
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0022.oracle.com [141.146.126.234]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/3wf1MXSULrXoH0jQvXBbxYz32pg>
Cc: "id-event@ietf.org" <id-event@ietf.org>
Subject: Re: [Id-event] Straw man text for proposed charter
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Sep 2016 17:13:57 -0000

--Apple-Mail=_A323B470-AD0A-4CB1-B602-D4C8A687A60D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Agreed. Though I don=E2=80=99t think we need to call it out specifically =
in the charter as the kind of detail required in almost every aspect.  =
For example, what should a receiver of a SET do before signalling an =
HTTP response should be assumed to be part of the draft.

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>





> On Sep 7, 2016, at 10:03 AM, Vivek Biswas <vivek_biswas@yahoo.com> =
wrote:
>=20
> Hi Phil,
>=20
>  Thanks for asking the question and also adding more description to =
the "validation" task.
>=20
> The Obligation here means "Do we need to take any actions if the =
endpoints don't work"
>=20
> Do we need to send any alert in case of someone is trying to do DoS =
attacks"
>=20
> This obligation is an optional feature which can/may be fulfilled upon =
the validation task.
>=20
> Regards
> Vivek Biswas
> Consulting Member @Security
> Oracle
>=20
>=20
> From: Phil Hunt <phil.hunt@oracle.com>
> To: Vivek Biswas <vivek_biswas@yahoo.com>=20
> Cc: Mike Jones <Michael.Jones@microsoft.com>; "id-event@ietf.org" =
<id-event@ietf.org>; Marius Scurtescu <mscurtescu@google.com>; Alexey =
Melnikov <aamelnikov@fastmail.fm>; Morteza Ansari <moransar@cisco.com>; =
William Denniss <wdenniss@google.com>; Leif Johansson <leifj@sunet.se>
> Sent: Wednesday, September 7, 2016 9:50 AM
> Subject: Re: [Id-event] Straw man text for proposed charter
>=20
> Vivek,
>=20
> Can you elaborate?
>=20
> The validation just ensures that the endpoints actually work.  It also =
serves to block DoS issues where someone accidentally or intentionally =
tries to send SETs to an unwilling subscriber.
>=20
> Phil
>=20
> @independentid
> www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>
>=20
>=20
>=20
>=20
>=20
>> On Sep 7, 2016, at 9:32 AM, Vivek Biswas <vivek_biswas@yahoo.com =
<mailto:vivek_biswas@yahoo.com>> wrote:
>>=20
>> Hi Mike,
>>=20
>> I believe there is one more item that MAY be added.
>>=20
>> After the line "Methods for validating event feed subscriptions"
>> "Obligation that may be needed to be fulfilled upon validating an =
event feed".
>>=20
>> Regards
>> Vivek Biswas
>> Consulting Member @Security
>> Oracle.
>>=20
>>=20
>>=20
>>=20
>> From: Mike Jones <Michael.Jones@microsoft.com =
<mailto:Michael.Jones@microsoft.com>>
>> To: "id-event@ietf.org <mailto:id-event@ietf.org>" <id-event@ietf.org =
<mailto:id-event@ietf.org>>=20
>> Cc: Marius Scurtescu <mscurtescu@google.com =
<mailto:mscurtescu@google.com>>; Alexey Melnikov <aamelnikov@fastmail.fm =
<mailto:aamelnikov@fastmail.fm>>; Morteza Ansari (moransar) =
<moransar@cisco.com <mailto:moransar@cisco.com>>; William Denniss =
<wdenniss@google.com <mailto:wdenniss@google.com>>; Leif Johansson =
<leifj@sunet.se <mailto:leifj@sunet.se>>; Phil Hunt (IDM) =
<phil.hunt@oracle.com <mailto:phil.hunt@oracle.com>>
>> Sent: Tuesday, September 6, 2016 5:01 PM
>> Subject: Re: [Id-event] Straw man text for proposed charter
>>=20
>> An updated and simplified charter is attached.  This draft has been =
reviewed by Phil Hunt, William Denniss, Marius Scurtescu.
>> =20
>> Input from Alexey Melnikov is that we should probably charter a =
working group, rather than try to go the AD-sponsored route.  Therefore, =
please review this draft charter and let us know if you think it=E2=80=99s=
 ready to go.
>> =20
>>                                                        Thanks,
>>                                                        -- Mike
>> =C2=A0 <applewebdata://BEADDEE2-A293-4672-9C12-B7BE68FB55FE>
>> From: Sarah Squire [mailto:sarah@engageidentity.com =
<mailto:sarah@engageidentity.com>]=20
>> Sent: Thursday, July 14, 2016 10:59 PM
>> To: Phil Hunt (IDM) <phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>>
>> Cc: Mike Jones <Michael.Jones@microsoft.com =
<mailto:Michael.Jones@microsoft.com>>; Alan Karp <alanhkarp@gmail.com =
<mailto:alanhkarp@gmail.com>>; Vivek Biswas <vivek_biswas@yahoo.com =
<mailto:vivek_biswas@yahoo.com>>; Morteza Ansari (moransar) =
<moransar@cisco.com <mailto:moransar@cisco.com>>; id-event@ietf.org =
<mailto:id-event@ietf.org>
>> Subject: Re: [Id-event] Straw man text for proposed charter
>> =20
>> Just submitting my two cents in writing before we hopefully have a =
chance to meet about this next week...
>> =20
>> Looking at this charter from the perspective of the OIDF HEART =
working group, I think it's going down a good path. In terms of the data =
format, this is less structured than what I was envisioning, but we =
could easily do a healthcare-specific profile of whatever data format =
comes out in the end, so it's better to be too broad than too narrow as =
far as our interests are concerned.
>> =20
>> The transport layer however, has some added complexity. In our =
context, we're shooting for interoperability, so we'd prefer something =
constrained. I appreciate Mike's input that these are application layer =
decisions. However, if we're talking about cloud provider-to-cloud =
provider communication, that certainly is facilitated by a well-defined =
transport layer. Again, we're willing to profile whatever the group =
comes up with for our own ends, but I don't really see the benefit of =
having a loosely defined transport layer - it just seems like more work =
for all the implementers to actually agree on endpoints on a =
case-by-case basis.
>> =20
>> Looking forward to discussing further in Berlin!
>> =20
>> Sarah
>>=20
>> Sarah Squire
>> Engage Identity
>> http://engageidentity.com <http://engageidentity.com/>
>> =20
>> On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>> wrote:
>> We also set things up so even a domain specific event can be =
extended.=20
>> =20
>> Eg on a password reset event, so event publishers may want to add =
security domain specific attributes. The spec lets them do that while =
avoiding interop issues.=20
>> =20
>> I believe in the spec we had the example of an account reset and the =
publisher adds reset count as an extension.=20
>>=20
>> Phil
>>=20
>> On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com =
<mailto:Michael.Jones@microsoft.com>> wrote:
>> Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 =
so common claims can be defined once and then reused.
>> =20
>> From: Vivek Biswas <mailto:vivek_biswas@yahoo.com>
>> Sent: Saturday, May 7, 2016 1:24 PM
>> To: Mike Jones <mailto:Michael.Jones@microsoft.com>
>> Cc: Alan Karp <mailto:alanhkarp@gmail.com>; Morteza Ansari (moransar) =
<mailto:moransar@cisco.com>; id-event@ietf.org =
<mailto:id-event@ietf.org>
>> Subject: Re: [Id-event] Straw man text for proposed charter
>> =20
>> Yes, I agree that the claims can be application specific, however =
there is a possibility to define claims which are domain specific. =
Thereby claims generated in one application could be understood by =
another  application within the same domain.
>> =20
>> With microservices based architecture getting lot of attention, if =
two different micro services defining different claims for the same =
claim, it can create confusion.
>> =20
>> Nevertheless this well defined claims for a particular domain can be =
an extension to the core specification.
>> =20
>> -Vivek Biswas
>>   Consulting Member, Oracle
>>=20
>> Sent from my iPhone
>>=20
>> On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com =
<mailto:Michael.Jones@microsoft.com>> wrote:
>> Thanks Alan,
>> =20
>> Interoperability will be on a per-application basis, just like JWT =
interoperability.  The claims needed in an identity event are =
application-specific, just like claims are for JWTs.  This is the same =
standards posture and JWTs are a huge success =E2=80=93 including for =
interoperability, even if I do say so myself.
>> =20
>>                                                           Best =
wishes,
>>                                                           -- Mike
>> =20
>> =20
>> =20
>> =20
>> From: Alan Karp <mailto:alanhkarp@gmail.com>
>> Sent: Saturday, May 7, 2016 10:23 AM
>> To: Mike Jones <mailto:Michael.Jones@microsoft.com>
>> Cc: Morteza Ansari (moransar) <mailto:moransar@cisco.com>; =
id-event@ietf.org <mailto:id-event@ietf.org>
>> Subject: Re: [Id-event] Straw man text for proposed charter
>> =20
>> As one who proposed doing more, I believe that your position is =
valid.  My only question is whether or not that will be enough for =
interoperability.
>>=20
>>=20
>> --------------
>> Alan Karp
>> =20
>> On Thu, May 5, 2016 at 10:00 PM, Mike Jones =
<Michael.Jones@microsoft.com <mailto:Michael.Jones@microsoft.com>> =
wrote:
>> Thanks guys, for writing the initial charter text.  Reading it now, I =
am extremely worried by the scope creep evident in the proposal.
>> =20
>> I strongly support a working group to define an ID Events data =
format.  I just as strongly believe that specific event delivery =
mechanisms will necessarily be application-specific and therefore MUST =
be explicitly be stated as being out of scope in the working group =
charter.  Attempting to specify a particular event delivery mechanism =
will take something that could be simple and quick to approve and bog it =
down in necessarily application-specific debates.
>> =20
>> Should event delivery be reliable?  That=E2=80=99s an =
application-specific decision.
>> Should events be idempotent?  That=E2=80=99s an application-specific =
decision.
>> Should events be unicast, multicast, or broadcast?  That=E2=80=99s an =
application-specific decision.
>> Should events have categories with category-specific subscriptions?  =
That=E2=80=99s an application-specific decision.
>> Should only one party at a time be able to register for delivery of =
events or should multiple parties be able to request delivery?  That=E2=80=
=99s an application-specific decision.
>> I could continue with this list, but I think you all get the point=E2=80=
=A6
>> =20
>> If we start debating application-specific event delivery mechanisms, =
we=E2=80=99ll please almost no one, since nearly all applications have =
different event delivery requirements.  We MUST explicitly rule all =
delivery mechanisms as being out of scope.
>> =20
>> If we define only a data format, we can quickly produce a very useful =
specification.  If we don=E2=80=99t, we=E2=80=99ll get bogged down in =
the mud of debating which applications we=E2=80=99re catering to and =
which we aren=E2=80=99t =E2=80=93 an exercise of picking favorites and =
limiting applicability of the specification.  That way is a slow, =
painful descent into standards quicksand =E2=80=93 something we must =
avoid.  Having a standard ID events representation is far too important =
to tie to a particular limited event delivery mechanism.
>> =20
>>                                                           Sincerely,
>>                                                           -- Mike
>> =C2=A0 <applewebdata://BEADDEE2-A293-4672-9C12-B7BE68FB55FE>
>> From: Id-event [mailto:id-event-bounces@ietf.org =
<mailto:id-event-bounces@ietf.org>] On Behalf Of Alan Karp
>> Sent: Thursday, May 5, 2016 9:43 PM
>> To: Morteza Ansari (moransar) <moransar@cisco.com =
<mailto:moransar@cisco.com>>
>> Cc: id-event@ietf.org <mailto:id-event@ietf.org>
>> Subject: Re: [Id-event] Straw man text for proposed charter
>> =20
>> I don't see anything about access control for publishing events and =
subscribing to them.  I also think the spec should allow filters on =
subscriptions.
>>=20
>>=20
>> --------------
>> Alan Karp
>> =20
>> On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar) =
<moransar@cisco.com <mailto:moransar@cisco.com>> wrote:
>> Hi folks,
>> =20
>> At IIW a few of us (Phil, William, Adam, and I) huddled for a bit and =
put together the attached as a straw man charter proposal to start the =
discussion. Please send your comments and suggestions for any changes or =
propose a new one if you think its necessary.
>> =20
>> =20
>> Cheers,
>> Morteza
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org <mailto:Id-event@ietf.org>
>> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
>> =20
>> =20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org <mailto:Id-event@ietf.org>
>> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org <mailto:Id-event@ietf.org>
>> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org <mailto:Id-event@ietf.org>
>> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
>> =20
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org <mailto:Id-event@ietf.org>
>> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
>=20
>=20


--Apple-Mail=_A323B470-AD0A-4CB1-B602-D4C8A687A60D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Agreed. Though I don=E2=80=99t think we need =
to call it out specifically in the charter as the kind of detail =
required in almost every aspect. &nbsp;For example, what should a =
receiver of a SET do before signalling an HTTP response should be =
assumed to be part of the draft.<br class=3D""><div class=3D""><br =
class=3D""><div class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Sep 7, 2016, at 10:03 AM, Vivek Biswas &lt;<a =
href=3D"mailto:vivek_biswas@yahoo.com" =
class=3D"">vivek_biswas@yahoo.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D""><div =
style=3D"background-color: rgb(255, 255, 255); font-family: verdana, =
helvetica, sans-serif; font-size: 16px;" class=3D""><div class=3D""><span =
class=3D"">Hi Phil,</span></div><div class=3D""><span class=3D""><br =
class=3D""></span></div><div class=3D"">&nbsp;Thanks for asking the =
question and also adding more description to the "validation" =
task.</div><div class=3D""><br class=3D""></div><div class=3D"">The =
Obligation here means "Do we need to take any actions if the endpoints =
don't work"</div><div id=3D"yui_3_16_0_ym19_1_1473266322087_7842" =
class=3D""><br class=3D""></div><div =
id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"ltr" class=3D"">Do we =
need to send any alert in case of someone is trying to do DoS =
attacks"</div><div id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"ltr"=
 class=3D""><br class=3D""></div><div =
id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"ltr" class=3D"">This =
obligation is an optional feature which can/may be fulfilled upon the =
validation task.</div><div id=3D"yui_3_16_0_ym19_1_1473266322087_7841" =
dir=3D"ltr" class=3D""><br class=3D""></div><div =
id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"ltr" =
class=3D"">Regards</div><div id=3D"yui_3_16_0_ym19_1_1473266322087_7841" =
dir=3D"ltr" class=3D"">Vivek Biswas</div><div =
id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"ltr" =
class=3D"">Consulting Member @Security</div><div =
id=3D"yui_3_16_0_ym19_1_1473266322087_7841" dir=3D"ltr" =
class=3D"">Oracle</div><div class=3D"qtdSeparateBR" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7508"><br class=3D""><br =
class=3D""></div><div class=3D"yahoo_quoted" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7516" style=3D"display: block;">  =
<div style=3D"font-family: verdana, helvetica, sans-serif; font-size: =
16px;" id=3D"yui_3_16_0_ym19_1_1473266322087_7515" class=3D""> <div =
style=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, =
Lucida Grande, sans-serif; font-size: 16px;" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7514" class=3D""> <div dir=3D"ltr" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7513" class=3D""> <font size=3D"2" =
face=3D"Arial" id=3D"yui_3_16_0_ym19_1_1473266322087_7512" class=3D""> =
<hr size=3D"1" id=3D"yui_3_16_0_ym19_1_1473266322087_7511" class=3D""> =
<b class=3D""><span style=3D"font-weight:bold;" =
class=3D"">From:</span></b> Phil Hunt &lt;<a =
href=3D"mailto:phil.hunt@oracle.com" =
class=3D"">phil.hunt@oracle.com</a>&gt;<br class=3D""> <b class=3D""><span=
 style=3D"font-weight: bold;" class=3D"">To:</span></b> Vivek Biswas =
&lt;<a href=3D"mailto:vivek_biswas@yahoo.com" =
class=3D"">vivek_biswas@yahoo.com</a>&gt; <br class=3D""><b =
class=3D""><span style=3D"font-weight: bold;" class=3D"">Cc:</span></b> =
Mike Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com" =
class=3D"">Michael.Jones@microsoft.com</a>&gt;; "<a =
href=3D"mailto:id-event@ietf.org" class=3D"">id-event@ietf.org</a>" =
&lt;<a href=3D"mailto:id-event@ietf.org" =
class=3D"">id-event@ietf.org</a>&gt;; Marius Scurtescu &lt;<a =
href=3D"mailto:mscurtescu@google.com" =
class=3D"">mscurtescu@google.com</a>&gt;; Alexey Melnikov &lt;<a =
href=3D"mailto:aamelnikov@fastmail.fm" =
class=3D"">aamelnikov@fastmail.fm</a>&gt;; Morteza Ansari &lt;<a =
href=3D"mailto:moransar@cisco.com" class=3D"">moransar@cisco.com</a>&gt;; =
William Denniss &lt;<a href=3D"mailto:wdenniss@google.com" =
class=3D"">wdenniss@google.com</a>&gt;; Leif Johansson &lt;<a =
href=3D"mailto:leifj@sunet.se" class=3D"">leifj@sunet.se</a>&gt;<br =
class=3D""> <b class=3D""><span style=3D"font-weight: bold;" =
class=3D"">Sent:</span></b> Wednesday, September 7, 2016 9:50 AM<br =
class=3D""> <b class=3D""><span style=3D"font-weight: bold;" =
class=3D"">Subject:</span></b> Re: [Id-event] Straw man text for =
proposed charter<br class=3D""> </font> </div> <div =
class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1473266322087_7652"><br =
class=3D""><div id=3D"yiv6965053192" class=3D""><div =
id=3D"yui_3_16_0_ym19_1_1473266322087_7651" class=3D""><div =
class=3D"yiv6965053192" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7844">Vivek,</div><div =
class=3D"yiv6965053192"><br clear=3D"none" =
class=3D"yiv6965053192"></div>Can you elaborate?<div =
class=3D"yiv6965053192" id=3D"yui_3_16_0_ym19_1_1473266322087_7719"><br =
clear=3D"none" class=3D"yiv6965053192"></div><div class=3D"yiv6965053192" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7781">The validation just ensures =
that the endpoints actually work. &nbsp;It also serves to block DoS =
issues where someone accidentally or intentionally tries to send SETs to =
an unwilling subscriber.</div><div class=3D"yiv6965053192" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7650"><br clear=3D"none" =
class=3D"yiv6965053192"><div class=3D"yiv6965053192" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7649">
<div class=3D"yiv6965053192" style=3D"letter-spacing: normal; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; word-wrap: break-word;" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7648"><div class=3D"yiv6965053192" =
style=3D"letter-spacing: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; word-wrap: break-word;" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7647"><div class=3D"yiv6965053192" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7646"><span =
class=3D"yiv6965053192Apple-style-span" =
style=3D"border-collapse:separate;line-height:normal;border-spacing:0px;">=
</span><div class=3D"yiv6965053192" style=3D"word-wrap:break-word;" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7645"><div class=3D"yiv6965053192" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7644"><div class=3D"yiv6965053192" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7643"><div class=3D"yiv6965053192" =
id=3D"yui_3_16_0_ym19_1_1473266322087_7642">Phil</div><div =
class=3D"yiv6965053192"><br clear=3D"none" =
class=3D"yiv6965053192"></div><div =
class=3D"yiv6965053192">@independentid</div><div =
class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" target=3D"_blank" =
href=3D"http://www.independentid.com/">www.independentid.com</a></div></di=
v></div></div><a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" =
href=3D"mailto:phil.hunt@oracle.com" =
style=3D"orphans:2;widows:2;">phil.hunt@oracle.com</a></div><div =
class=3D"yiv6965053192"><br clear=3D"none" =
class=3D"yiv6965053192"></div></div><br clear=3D"none" =
class=3D"yiv6965053192Apple-interchange-newline"></div><br clear=3D"none" =
class=3D"yiv6965053192Apple-interchange-newline"><br clear=3D"none" =
class=3D"yiv6965053192Apple-interchange-newline">
</div>
<br clear=3D"none" class=3D"yiv6965053192"><div =
class=3D"yiv6965053192yqt4780177444" id=3D"yiv6965053192yqt95605"><div =
class=3D""><blockquote class=3D"yiv6965053192" type=3D"cite"><div =
class=3D"yiv6965053192">On Sep 7, 2016, at 9:32 AM, Vivek Biswas &lt;<a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:vivek_biswas@yahoo.com" target=3D"_blank" =
href=3D"mailto:vivek_biswas@yahoo.com">vivek_biswas@yahoo.com</a>&gt; =
wrote:</div><br clear=3D"none" =
class=3D"yiv6965053192Apple-interchange-newline"><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192" =
style=3D"font-style:normal;font-weight:normal;letter-spacing:normal;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;backgrou=
nd-color:rgb(255, 255, 255);font-family:verdana, helvetica, =
sans-serif;font-size:16px;"><div class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">Hi =
Mike,</div><div class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746"><br =
clear=3D"none" class=3D"yiv6965053192"></div><div class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">I believe =
there is one more item that MAY be added.</div><div =
class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746"><br =
clear=3D"none" class=3D"yiv6965053192"></div><div class=3D"yiv6965053192" =
dir=3D"ltr" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">After the line =
"<span class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12804" =
style=3D"font-family:pg-1ff9;line-height:37.2852px;white-space:pre-wrap;">=
<font class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_13077" =
size=3D"3">Methods for validating event feed =
subscriptions"</font></span></div><div class=3D"yiv6965053192" dir=3D"ltr"=
 id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746"><span =
class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_13175" =
style=3D"font-family:pg-1ff9;line-height:37.2852px;white-space:pre-wrap;">=
<font class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_13174" =
size=3D"3">"Obligation that may be needed to be fulfilled upon =
validating an event feed".</font></span></div><div class=3D"yiv6965053192"=
 dir=3D"ltr" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746"><br=
 clear=3D"none" class=3D"yiv6965053192"></div><div class=3D"yiv6965053192"=
 dir=3D"ltr" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">Regards</div><di=
v class=3D"yiv6965053192" dir=3D"ltr" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">Vivek =
Biswas</div><div class=3D"yiv6965053192" dir=3D"ltr" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">Consulting =
Member @Security</div><div class=3D"yiv6965053192" dir=3D"ltr" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746">Oracle.</div><di=
v class=3D"yiv6965053192" dir=3D"ltr" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746"><br =
clear=3D"none" class=3D"yiv6965053192"></div><div class=3D"yiv6965053192" =
dir=3D"ltr" id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12746"><br =
clear=3D"none" class=3D"yiv6965053192"></div><div =
class=3D"yiv6965053192qtdSeparateBR"><br clear=3D"none" =
class=3D"yiv6965053192"><br clear=3D"none" =
class=3D"yiv6965053192"></div><div class=3D"yiv6965053192yahoo_quoted" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12800" =
style=3D"display:block;"><div class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12799" =
style=3D"font-family:verdana, helvetica, =
sans-serif;font-size:16px;"><div class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12798" =
style=3D"font-family:HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, =
'Lucida Grande', sans-serif;font-size:16px;"><div class=3D"yiv6965053192" =
dir=3D"ltr" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12797"><font =
class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12796" size=3D"2" =
face=3D"Arial"></font><hr class=3D"yiv6965053192" =
id=3D"yiv6965053192yui_3_16_0_ym19_1_1473265247048_12795" size=3D"1"><b =
class=3D"yiv6965053192"><span class=3D"yiv6965053192" =
style=3D"font-weight:bold;">From:</span></b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Mike Jones =
&lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" =
href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a=
>&gt;<br clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192"><span class=3D"yiv6965053192" =
style=3D"font-weight:bold;">To:</span></b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>"<a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:id-event@ietf.org" target=3D"_blank" =
href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a>" &lt;<a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:id-event@ietf.org" target=3D"_blank" =
href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a>&gt;<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span><br =
clear=3D"none" class=3D"yiv6965053192"><b class=3D"yiv6965053192"><span =
class=3D"yiv6965053192" style=3D"font-weight:bold;">Cc:</span></b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Marius =
Scurtescu &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:mscurtescu@google.com" target=3D"_blank" =
href=3D"mailto:mscurtescu@google.com">mscurtescu@google.com</a>&gt;; =
Alexey Melnikov &lt;<a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" ymailto=3D"mailto:aamelnikov@fastmail.fm" =
target=3D"_blank" =
href=3D"mailto:aamelnikov@fastmail.fm">aamelnikov@fastmail.fm</a>&gt;; =
Morteza Ansari (moransar) &lt;<a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" ymailto=3D"mailto:moransar@cisco.com" =
target=3D"_blank" =
href=3D"mailto:moransar@cisco.com">moransar@cisco.com</a>&gt;; William =
Denniss &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:wdenniss@google.com" target=3D"_blank" =
href=3D"mailto:wdenniss@google.com">wdenniss@google.com</a>&gt;; Leif =
Johansson &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:leifj@sunet.se" target=3D"_blank" =
href=3D"mailto:leifj@sunet.se">leifj@sunet.se</a>&gt;; Phil Hunt (IDM) =
&lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" =
href=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.com</a>&gt;<br =
clear=3D"none" class=3D"yiv6965053192"><b class=3D"yiv6965053192"><span =
class=3D"yiv6965053192" style=3D"font-weight:bold;">Sent:</span></b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Tuesday, =
September 6, 2016 5:01 PM<br clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192"><span class=3D"yiv6965053192" =
style=3D"font-weight:bold;">Subject:</span></b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Re: [Id-event] =
Straw man text for proposed charter<br clear=3D"none" =
class=3D"yiv6965053192"></div><div =
class=3D"yiv6965053192y_msg_container"><br clear=3D"none" =
class=3D"yiv6965053192"><div class=3D"yiv6965053192" =
id=3D"yiv6965053192"><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192WordSection1"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"font-size:11pt;">An updated and =
simplified charter is attached.&nbsp; This draft has been reviewed by =
Phil Hunt, William Denniss, Marius Scurtescu.</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">&nbsp;</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">Input from Alexey Melnikov is that we should =
probably charter a working group, rather than try to go the AD-sponsored =
route.&nbsp; Therefore, please review this draft charter and let us know =
if you think it=E2=80=99s ready to go.</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">&nbsp;</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Thanks,</span></div><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" =
style=3D"font-size:11pt;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike</span></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in=
 0in 0.0001pt;font-size:12pt;"><a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" name=3D"_MailEndCompose" =
style=3D"color:purple;text-decoration:underline;" href=3D""><span =
class=3D"yiv6965053192" =
style=3D"font-size:11pt;">&nbsp;</span></a></div><span =
class=3D"yiv6965053192"></span><div class=3D"yiv6965053192yqt5176189511" =
id=3D"yiv6965053192yqt64133"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><b =
class=3D"yiv6965053192"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">From:</span></b><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;"><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Sarah Squire =
[<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:sarah@engageidentity.com" target=3D"_blank" =
href=3D"mailto:sarah@engageidentity.com">mailto:sarah@engageidentity.com</=
a>]<span class=3D"yiv6965053192Apple-converted-space">&nbsp;</span><br =
clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">Sent:</b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Thursday, July =
14, 2016 10:59 PM<br clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">To:</b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Phil Hunt =
(IDM) &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" =
href=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.com</a>&gt;<br =
clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">Cc:</b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Mike Jones =
&lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" =
href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a=
>&gt;; Alan Karp &lt;<a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" ymailto=3D"mailto:alanhkarp@gmail.com" =
target=3D"_blank" =
href=3D"mailto:alanhkarp@gmail.com">alanhkarp@gmail.com</a>&gt;; Vivek =
Biswas &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:vivek_biswas@yahoo.com" target=3D"_blank" =
href=3D"mailto:vivek_biswas@yahoo.com">vivek_biswas@yahoo.com</a>&gt;; =
Morteza Ansari (moransar) &lt;<a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" ymailto=3D"mailto:moransar@cisco.com" =
target=3D"_blank" =
href=3D"mailto:moransar@cisco.com">moransar@cisco.com</a>&gt;; <a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:id-event@ietf.org" target=3D"_blank" =
href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a><br clear=3D"none" =
class=3D"yiv6965053192"><b class=3D"yiv6965053192">Subject:</b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Re: [Id-event] =
Straw man text for proposed charter</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">Just submitting my two =
cents in writing before we hopefully have a chance to meet about this =
next week...</div></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">Looking at this charter from the perspective =
of the OIDF HEART working group, I think it's going down a good path. In =
terms of the data format, this is less structured than what I was =
envisioning, but we could easily do a healthcare-specific profile of =
whatever data format comes out in the end, so it's better to be too =
broad than too narrow as far as our interests are concerned.</div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">The transport layer =
however, has some added complexity. In our context, we're shooting for =
interoperability, so we'd prefer something constrained. I appreciate =
Mike's input that these are application layer decisions. However, if =
we're talking about cloud provider-to-cloud provider communication, that =
certainly is facilitated by a well-defined transport layer. Again, we're =
willing to profile whatever the group comes up with for our own ends, =
but I don't really see the benefit of having a loosely defined transport =
layer - it just seems like more work for all the implementers to =
actually agree on endpoints on a case-by-case basis.</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">Looking forward to =
discussing further in Berlin!</div></div><div class=3D"yiv6965053192"><div=
 class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">Sarah</div></div></div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192yqt5176189511" =
id=3D"yiv6965053192yqt99533"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><br clear=3D"all" =
class=3D"yiv6965053192"></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"color:rgb(136, 136, 136);">Sarah =
Squire</span></div></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"color:rgb(136, 136, 136);">Engage =
Identity</span></div></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"color:rgb(136, 136, 136);"><a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" target=3D"_blank" =
href=3D"http://engageidentity.com/" =
style=3D"color:purple;text-decoration:underline;"><span =
class=3D"yiv6965053192" style=3D"color:rgb(17, 85, =
204);">http://engageidentity.com</span></a></span></div></div></div></div>=
</div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">On Sat, May 7, 2016 at 6:53 PM, Phil Hunt =
(IDM) &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" =
href=3D"mailto:phil.hunt@oracle.com" =
style=3D"color:purple;text-decoration:underline;">phil.hunt@oracle.com</a>=
&gt; wrote:</div><blockquote class=3D"yiv6965053192" =
style=3D"border-style:none none none solid;border-left-color:rgb(204, =
204, 204);border-left-width:1pt;padding:0in 0in 0in =
6pt;margin-left:4.8pt;margin-right:0in;"><div class=3D"yiv6965053192"><div=
 class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">We also set things up =
so even a domain specific event can be extended.&nbsp;</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">&nbsp;</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">Eg on a password reset =
event, so event publishers may want to add security domain specific =
attributes. The spec lets them do that while avoiding interop =
issues.&nbsp;</div></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">I believe in the spec =
we had the example of an account reset and the publisher adds reset =
count as an extension.&nbsp;<span class=3D"yiv6965053192" =
style=3D"color:rgb(136, 136, 136);"><br clear=3D"none" =
class=3D"yiv6965053192"><br clear=3D"none" class=3D"yiv6965053192"><span =
class=3D"yiv6965053192hoenzb">Phil</span></span></div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 12pt;font-size:12pt;"><br clear=3D"none" =
class=3D"yiv6965053192">On May 7, 2016, at 13:31, Mike Jones &lt;<a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" =
href=3D"mailto:Michael.Jones@microsoft.com" =
style=3D"color:purple;text-decoration:underline;">Michael.Jones@microsoft.=
com</a>&gt; wrote:</div></div><blockquote class=3D"yiv6965053192" =
style=3D"margin-top:5pt;margin-bottom:5pt;"><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">Indeed, that=E2=80=99s why there=E2=80=99s a =
claims registry =E2=80=93 so common claims can be defined once and then =
reused.</div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in =
0in 0.0001pt;font-size:12pt;">&nbsp;</div><div class=3D"yiv6965053192" =
style=3D"border-style:solid none none;border-top-color:rgb(225, 225, =
225);border-top-width:1pt;padding:3pt 0in 0in;"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><b class=3D"yiv6965053192">From:<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b><a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:vivek_biswas@yahoo.com" target=3D"_blank" =
href=3D"mailto:vivek_biswas@yahoo.com" =
style=3D"color:purple;text-decoration:underline;">Vivek Biswas</a><br =
clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">Sent:<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b>Saturday, =
May 7, 2016 1:24 PM<br clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">To:<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b><a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" =
href=3D"mailto:Michael.Jones@microsoft.com" =
style=3D"color:purple;text-decoration:underline;">Mike Jones</a><br =
clear=3D"none" class=3D"yiv6965053192"><b class=3D"yiv6965053192">Cc:<span=
 class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b><a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:alanhkarp@gmail.com" target=3D"_blank" =
href=3D"mailto:alanhkarp@gmail.com" =
style=3D"color:purple;text-decoration:underline;">Alan Karp</a>;<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span><a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:moransar@cisco.com" target=3D"_blank" =
href=3D"mailto:moransar@cisco.com" =
style=3D"color:purple;text-decoration:underline;">Morteza Ansari =
(moransar)</a>;<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span><a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:id-event@ietf.org" target=3D"_blank" =
href=3D"mailto:id-event@ietf.org" =
style=3D"color:purple;text-decoration:underline;">id-event@ietf.org</a><br=
 clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">Subject:<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b>Re: =
[Id-event] Straw man text for proposed charter</div></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">Yes, I agree that the claims can be =
application specific, however there is a possibility to define claims =
which are domain specific. Thereby claims generated in one application =
could be understood by another &nbsp;application within the same =
domain.</div></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">With microservices =
based architecture getting lot of attention, if two different micro =
services defining different claims for the same claim, it can create =
confusion.</div></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">Nevertheless this well =
defined claims for a particular domain can be an extension to the core =
specification.</div></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;">-Vivek =
Biswas</div></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp; Consulting Member, Oracle<br =
clear=3D"none" class=3D"yiv6965053192"><br clear=3D"none" =
class=3D"yiv6965053192">Sent from my iPhone</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 12pt;font-size:12pt;"><br clear=3D"none" =
class=3D"yiv6965053192">On May 7, 2016, at 1:04 PM, Mike Jones &lt;<a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" =
href=3D"mailto:Michael.Jones@microsoft.com" =
style=3D"color:purple;text-decoration:underline;">Michael.Jones@microsoft.=
com</a>&gt; wrote:</div></div><blockquote class=3D"yiv6965053192" =
style=3D"margin-top:5pt;margin-bottom:5pt;"><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">Thanks Alan,</div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"color:rgb(0, 32, 96);">Interoperability will be on a =
per-application basis, just like JWT interoperability.&nbsp; The claims =
needed in an identity event are application-specific, just like claims =
are for JWTs.&nbsp; This is the same standards posture and JWTs are a =
huge success =E2=80=93 including for interoperability, even if I do say =
so myself.</span></div><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"color:rgb(0, 32, =
96);">&nbsp;</span></div><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"color:rgb(0, 32, =
96);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Best =
wishes,</span></div><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"color:rgb(0, 32, =
96);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike</span></div><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in=
 0in 0.0001pt;font-size:12pt;">&nbsp;</div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div><div class=3D"yiv6965053192" =
style=3D"border-style:solid none none;border-top-color:rgb(225, 225, =
225);border-top-width:1pt;padding:3pt 0in 0in;"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><b class=3D"yiv6965053192">From:<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b><a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:alanhkarp@gmail.com" target=3D"_blank" =
href=3D"mailto:alanhkarp@gmail.com" =
style=3D"color:purple;text-decoration:underline;">Alan Karp</a><br =
clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">Sent:<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b>Saturday, =
May 7, 2016 10:23 AM<br clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">To:<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b><a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" =
href=3D"mailto:Michael.Jones@microsoft.com" =
style=3D"color:purple;text-decoration:underline;">Mike Jones</a><br =
clear=3D"none" class=3D"yiv6965053192"><b class=3D"yiv6965053192">Cc:<span=
 class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b><a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:moransar@cisco.com" target=3D"_blank" =
href=3D"mailto:moransar@cisco.com" =
style=3D"color:purple;text-decoration:underline;">Morteza Ansari =
(moransar)</a>;<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span><a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:id-event@ietf.org" target=3D"_blank" =
href=3D"mailto:id-event@ietf.org" =
style=3D"color:purple;text-decoration:underline;">id-event@ietf.org</a><br=
 clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">Subject:<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b>Re: =
[Id-event] Straw man text for proposed charter</div></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:9.5pt;">As one who proposed doing more, I believe =
that your position is valid.&nbsp; My only question is whether or not =
that will be enough for interoperability.</span></div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><br clear=3D"all" =
class=3D"yiv6965053192"></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><br clear=3D"none" =
class=3D"yiv6965053192">--------------<br clear=3D"none" =
class=3D"yiv6965053192">Alan Karp</div></div></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">On Thu, May 5, 2016 at 10:00 PM, Mike Jones =
&lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" =
href=3D"mailto:Michael.Jones@microsoft.com" =
style=3D"color:purple;text-decoration:underline;">Michael.Jones@microsoft.=
com</a>&gt; wrote:</div><blockquote class=3D"yiv6965053192" =
style=3D"border-style:none none none solid;border-left-color:rgb(204, =
204, 204);border-left-width:1pt;padding:0in 0in 0in =
6pt;margin-left:4.8pt;margin-right:0in;"><div class=3D"yiv6965053192"><div=
 class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"font-size:11pt;">Thanks guys, for =
writing the initial charter text.&nbsp; Reading it now, I am extremely =
worried by the scope creep evident in the proposal.</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">&nbsp;</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">I strongly support a working group to define =
an ID Events data format.&nbsp; I just as strongly believe that specific =
event delivery mechanisms will necessarily be application-specific and =
therefore MUST be explicitly be stated as being out of scope in the =
working group charter.&nbsp; Attempting to specify a particular event =
delivery mechanism will take something that could be simple and quick to =
approve and bog it down in necessarily application-specific =
debates.</span></div><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"font-size:11pt;">&nbsp;</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">Should event delivery be reliable?&nbsp; =
That=E2=80=99s an application-specific decision.</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">Should events be idempotent?&nbsp; That=E2=80=99=
s an application-specific decision.</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">Should events be unicast, multicast, or =
broadcast?&nbsp; That=E2=80=99s an application-specific =
decision.</span></div><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"font-size:11pt;">Should events have =
categories with category-specific subscriptions?&nbsp; That=E2=80=99s an =
application-specific decision.</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">Should only one party at a time be able to =
register for delivery of events or should multiple parties be able to =
request delivery?&nbsp; That=E2=80=99s an application-specific =
decision.</span></div><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"font-size:11pt;">I could continue with =
this list, but I think you all get the point=E2=80=A6</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">&nbsp;</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">If we start debating application-specific =
event delivery mechanisms, we=E2=80=99ll please almost no one, since =
nearly all applications have different event delivery =
requirements.&nbsp; We MUST explicitly rule all delivery mechanisms as =
being out of scope.</span></div><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"font-size:11pt;">&nbsp;</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">If we define only a data format, we can =
quickly produce a very useful specification.&nbsp; If we don=E2=80=99t, =
we=E2=80=99ll get bogged down in the mud of debating which applications =
we=E2=80=99re catering to and which we aren=E2=80=99t =E2=80=93 an =
exercise of picking favorites and limiting applicability of the =
specification.&nbsp; That way is a slow, painful descent into standards =
quicksand =E2=80=93 something we must avoid.&nbsp; Having a standard ID =
events representation is far too important to tie to a particular =
limited event delivery mechanism.</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">&nbsp;</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:11pt;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Sincerely,</span></div><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" =
style=3D"font-size:11pt;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-- Mike</span></div><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><a rel=3D"nofollow" =
shape=3D"rect" class=3D"yiv6965053192" =
name=3D"m_3022367059336893565_m_1461024254222911" =
style=3D"color:purple;text-decoration:underline;" href=3D""><span =
class=3D"yiv6965053192" =
style=3D"font-size:11pt;">&nbsp;</span></a></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><b class=3D"yiv6965053192"><span =
class=3D"yiv6965053192" style=3D"font-size:11pt;">From:</span></b><span =
class=3D"yiv6965053192" style=3D"font-size:11pt;"><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Id-event =
[mailto:<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:id-event-bounces@ietf.org" target=3D"_blank" =
href=3D"mailto:id-event-bounces@ietf.org" =
style=3D"color:purple;text-decoration:underline;">id-event-bounces@ietf.or=
g</a>]<span class=3D"yiv6965053192Apple-converted-space">&nbsp;</span><b =
class=3D"yiv6965053192">On Behalf Of<span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span></b>Alan =
Karp<br clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">Sent:</b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Thursday, May =
5, 2016 9:43 PM<br clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">To:</b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Morteza Ansari =
(moransar) &lt;<a rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:moransar@cisco.com" target=3D"_blank" =
href=3D"mailto:moransar@cisco.com" =
style=3D"color:purple;text-decoration:underline;">moransar@cisco.com</a>&g=
t;<br clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">Cc:</b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span><a =
rel=3D"nofollow" shape=3D"rect" class=3D"yiv6965053192" =
ymailto=3D"mailto:id-event@ietf.org" target=3D"_blank" =
href=3D"mailto:id-event@ietf.org" =
style=3D"color:purple;text-decoration:underline;">id-event@ietf.org</a><br=
 clear=3D"none" class=3D"yiv6965053192"><b =
class=3D"yiv6965053192">Subject:</b><span =
class=3D"yiv6965053192Apple-converted-space">&nbsp;</span>Re: [Id-event] =
Straw man text for proposed charter</span></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">I don't see anything about access control for =
publishing events and subscribing to them.&nbsp; I also think the spec =
should allow filters on subscriptions.</div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><br clear=3D"all" =
class=3D"yiv6965053192"></div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><br clear=3D"none" =
class=3D"yiv6965053192">--------------<br clear=3D"none" =
class=3D"yiv6965053192">Alan Karp</div></div></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div><div class=3D"yiv6965053192"><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">On Thu, May 5, 2016 at 11:18 AM, Morteza =
Ansari (moransar) &lt;<a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" ymailto=3D"mailto:moransar@cisco.com" =
target=3D"_blank" href=3D"mailto:moransar@cisco.com" =
style=3D"color:purple;text-decoration:underline;">moransar@cisco.com</a>&g=
t; wrote:</div><blockquote class=3D"yiv6965053192" =
style=3D"border-style:none none none solid;border-left-color:rgb(204, =
204, 204);border-left-width:1pt;padding:0in 0in 0in 6pt;margin:5pt 0in =
5pt 4.8pt;"><div class=3D"yiv6965053192"><div class=3D"yiv6965053192"><div=
 class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;"><span class=3D"yiv6965053192" =
style=3D"font-size:10.5pt;">Hi folks,</span></div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" =
style=3D"font-size:10.5pt;">&nbsp;</span></div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" style=3D"font-size:10.5pt;">At IIW a few of us =
(Phil, William, Adam, and I) huddled for a bit and put together the =
attached as a straw man charter proposal to start the discussion. Please =
send your comments and suggestions for any changes or propose a new one =
if you think its necessary.</span></div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" =
style=3D"font-size:10.5pt;">&nbsp;</span></div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" =
style=3D"font-size:10.5pt;">&nbsp;</span></div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" =
style=3D"font-size:10.5pt;">Cheers,</span></div></div><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in 0.0001pt;font-size:12pt;"><span =
class=3D"yiv6965053192" =
style=3D"font-size:10.5pt;">Morteza</span></div></div></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
12pt;font-size:12pt;"><br clear=3D"none" =
class=3D"yiv6965053192">_______________________________________________<br=
 clear=3D"none" class=3D"yiv6965053192">Id-event mailing list<br =
clear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" ymailto=3D"mailto:Id-event@ietf.org" =
target=3D"_blank" href=3D"mailto:Id-event@ietf.org" =
style=3D"color:purple;text-decoration:underline;">Id-event@ietf.org</a><br=
 clear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect"=
 class=3D"yiv6965053192" target=3D"_blank" =
href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
style=3D"color:purple;text-decoration:underline;">https://www.ietf.org/mai=
lman/listinfo/id-event</a></div></blockquote></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div></div></div></div></blockquote></div=
><div class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div></div></div></div></blockquote><bloc=
kquote class=3D"yiv6965053192" =
style=3D"margin-top:5pt;margin-bottom:5pt;"><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">_______________________________________________<=
br clear=3D"none" class=3D"yiv6965053192">Id-event mailing list<br =
clear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" ymailto=3D"mailto:Id-event@ietf.org" =
target=3D"_blank" href=3D"mailto:Id-event@ietf.org" =
style=3D"color:purple;text-decoration:underline;">Id-event@ietf.org</a><br=
 clear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect"=
 class=3D"yiv6965053192" target=3D"_blank" =
href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
style=3D"color:purple;text-decoration:underline;">https://www.ietf.org/mai=
lman/listinfo/id-event</a></div></div></blockquote></div></div></blockquot=
e><blockquote class=3D"yiv6965053192" =
style=3D"margin-top:5pt;margin-bottom:5pt;"><div =
class=3D"yiv6965053192"><div class=3D"yiv6965053192MsoNormal" =
style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">_______________________________________________<=
br clear=3D"none" class=3D"yiv6965053192">Id-event mailing list<br =
clear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" ymailto=3D"mailto:Id-event@ietf.org" =
target=3D"_blank" href=3D"mailto:Id-event@ietf.org" =
style=3D"color:purple;text-decoration:underline;">Id-event@ietf.org</a><br=
 clear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect"=
 class=3D"yiv6965053192" target=3D"_blank" =
href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
style=3D"color:purple;text-decoration:underline;">https://www.ietf.org/mai=
lman/listinfo/id-event</a></div></div></blockquote></div></div></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
12pt;font-size:12pt;"><br clear=3D"none" =
class=3D"yiv6965053192">_______________________________________________<br=
 clear=3D"none" class=3D"yiv6965053192">Id-event mailing list<br =
clear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" ymailto=3D"mailto:Id-event@ietf.org" =
target=3D"_blank" href=3D"mailto:Id-event@ietf.org" =
style=3D"color:purple;text-decoration:underline;">Id-event@ietf.org</a><br=
 clear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect"=
 class=3D"yiv6965053192" target=3D"_blank" =
href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
style=3D"color:purple;text-decoration:underline;">https://www.ietf.org/mai=
lman/listinfo/id-event</a></div></blockquote></div></div><div =
class=3D"yiv6965053192MsoNormal" style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;">&nbsp;</div></div></div></div></div><br =
clear=3D"none" class=3D"yiv6965053192"><div =
class=3D"yiv6965053192yqt5176189511" =
id=3D"yiv6965053192yqt18602">_____________________________________________=
__<br clear=3D"none" class=3D"yiv6965053192">Id-event mailing list<br =
clear=3D"none" class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" ymailto=3D"mailto:Id-event@ietf.org" =
target=3D"_blank" =
href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br clear=3D"none" =
class=3D"yiv6965053192"><a rel=3D"nofollow" shape=3D"rect" =
class=3D"yiv6965053192" target=3D"_blank" =
href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www.ietf.o=
rg/mailman/listinfo/id-event</a></div></div></div></div></div></div></div>=
</blockquote></div></div><br clear=3D"none" =
class=3D"yiv6965053192"></div></div></div><br class=3D""><br =
class=3D""></div> </div> </div>  =
</div></div></div></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_A323B470-AD0A-4CB1-B602-D4C8A687A60D--


From nobody Tue Sep 13 14:52:08 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C4FD12B0BE for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 14:52:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.728
X-Spam-Level: 
X-Spam-Status: No, score=-5.728 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UetMidacgcQy for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 14:52:05 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8568712B0A8 for <id-event@ietf.org>; Tue, 13 Sep 2016 14:52:05 -0700 (PDT)
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8DLq4kH005870 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <id-event@ietf.org>; Tue, 13 Sep 2016 21:52:05 GMT
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u8DLq4oK019492 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <id-event@ietf.org>; Tue, 13 Sep 2016 21:52:04 GMT
Received: from abhmp0010.oracle.com (abhmp0010.oracle.com [141.146.116.16]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u8DLq4Rb012222 for <id-event@ietf.org>; Tue, 13 Sep 2016 21:52:04 GMT
Received: from [10.151.111.46] (/148.87.13.10) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 13 Sep 2016 14:52:04 -0700
From: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_37EDF20F-7095-4635-BB17-197F7EC2C996"
Message-Id: <56279609-CC17-465B-B7C4-AFCB696D68D8@oracle.com>
Date: Tue, 13 Sep 2016 14:52:03 -0700
To: id-event@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0021.oracle.com [141.146.126.233]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/PKCuncv5Axkm6mQL8w_Wo6YItLg>
Subject: [Id-event] Transaction identifier for SETs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Sep 2016 21:52:07 -0000

--Apple-Mail=_37EDF20F-7095-4635-BB17-197F7EC2C996
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

In discussing SET schema with a bunch of people, it is becoming clear =
that in many cases, a simple state change in a system could trigger many =
different types of SET feeds generating 4 or 5 SETs for the same =
transaction.

For example, a user=E2=80=99s profile is changed in SCIM.  This could =
trigger:

*  A SCIM modify event
*  A RISC event (account reset)
*  Access log event=20
*  OAuth /Connect events (e.g. reset session)

Normally each of these events would each have their own JTI.  There =
would be a separate subscriber for each.  But I can envision some =
systems operationally that will want to look at these events together =
(e.g. devOps).

It seems useful to have a common attribute =E2=80=9Ctxn=E2=80=9D which =
would be a unique identifier for the source transaction.  Thus if a =
system receives more than one event type (directly or indirectly) it can =
detect whether the 2 or more events are about the same transaction.

I propose to add this to the core spec as an optional value.

Any objections?

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>






--Apple-Mail=_37EDF20F-7095-4635-BB17-197F7EC2C996
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">In discussing SET schema with a bunch of people, it is =
becoming clear that in many cases, a simple state change in a system =
could trigger many different types of SET feeds generating 4 or 5 SETs =
for the same transaction.<div class=3D""><br class=3D""></div><div =
class=3D"">For example, a user=E2=80=99s profile is changed in SCIM. =
&nbsp;This could trigger:</div><div class=3D""><br class=3D""></div><div =
class=3D"">* &nbsp;A SCIM modify event</div><div class=3D"">* &nbsp;A =
RISC event (account reset)</div><div class=3D"">* &nbsp;Access log =
event&nbsp;</div><div class=3D"">* &nbsp;OAuth /Connect events (e.g. =
reset session)</div><div class=3D""><br class=3D""></div><div =
class=3D"">Normally each of these events would each have their own JTI. =
&nbsp;There would be a separate subscriber for each. &nbsp;But I can =
envision some systems operationally that will want to look at these =
events together (e.g. devOps).</div><div class=3D""><br =
class=3D""></div><div class=3D"">It seems useful to have a common =
attribute =E2=80=9Ctxn=E2=80=9D which would be a unique identifier for =
the source transaction. &nbsp;Thus if a system receives more than one =
event type (directly or indirectly) it can detect whether the 2 or more =
events are about the same transaction.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I propose to add this to the core spec =
as an optional value.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Any objections?</div><div class=3D""><br class=3D""><div =
class=3D""><div class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></div></body></html>=

--Apple-Mail=_37EDF20F-7095-4635-BB17-197F7EC2C996--


From nobody Tue Sep 13 14:57:40 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E459612B0C2 for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 14:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.728
X-Spam-Level: 
X-Spam-Status: No, score=-5.728 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AnmTM7sSPq8O for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 14:57:37 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 921D412B0EC for <id-event@ietf.org>; Tue, 13 Sep 2016 14:57:06 -0700 (PDT)
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8DLv5AH011137 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <id-event@ietf.org>; Tue, 13 Sep 2016 21:57:05 GMT
Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u8DLv45F004531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <id-event@ietf.org>; Tue, 13 Sep 2016 21:57:04 GMT
Received: from abhmp0006.oracle.com (abhmp0006.oracle.com [141.146.116.12]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u8DLv42q031830 for <id-event@ietf.org>; Tue, 13 Sep 2016 21:57:04 GMT
Received: from [10.151.111.46] (/148.87.13.10) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 13 Sep 2016 14:57:04 -0700
From: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F62993DA-EF48-486A-9D2E-D489B3B78902"
Message-Id: <2EC6A66C-1219-4B40-9B95-FD557794C069@oracle.com>
Date: Tue, 13 Sep 2016 14:56:54 -0700
To: id-event@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-Source-IP: userv0021.oracle.com [156.151.31.71]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/jdx0bvDelpWzuJWywHVvOzxtnwA>
Subject: [Id-event] Ordering of SET events
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Sep 2016 21:57:39 -0000

--Apple-Mail=_F62993DA-EF48-486A-9D2E-D489B3B78902
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I think we may need to ensure we have the correct language on how =
subscribers can order events. Can they strictly depend on the order by =
which they are received, or can they use =E2=80=9Ciat=E2=80=9D?

The issue is that when SETs are published they may be published by =
highly distributed systems were it is unreasonable to co-ordinate a =
sequence number in many cases.  This basically leads us to using =
timestamps.

Would it be reasonable to use =E2=80=9Ciat=E2=80=9D for this purpose?  =
Keep in mind, we have discussed that =E2=80=9Ciat=E2=80=9D corresponds =
to the time of the SET being generated (and optionally signed) and might =
not be the transaction time.

Do we need some sort of clarifying language on this?

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>






--Apple-Mail=_F62993DA-EF48-486A-9D2E-D489B3B78902
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">I think we may need to ensure we have the correct language on =
how subscribers can order events. Can they strictly depend on the order =
by which they are received, or can they use =E2=80=9Ciat=E2=80=9D?<div =
class=3D""><br class=3D""></div><div class=3D"">The issue is that when =
SETs are published they may be published by highly distributed systems =
were it is unreasonable to co-ordinate a sequence number in many cases. =
&nbsp;This basically leads us to using timestamps.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Would it be reasonable =
to use =E2=80=9Ciat=E2=80=9D for this purpose? &nbsp;Keep in mind, we =
have discussed that =E2=80=9Ciat=E2=80=9D corresponds to the time of the =
SET being generated (and optionally signed) and might not be the =
transaction time.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Do we need some sort of clarifying language on =
this?</div><div class=3D""><br class=3D""><div class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_F62993DA-EF48-486A-9D2E-D489B3B78902--


From nobody Tue Sep 13 17:30:22 2016
Return-Path: <mscurtescu@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5D712B512 for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 17:30:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level: 
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BlpHiEhTqiRB for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 17:30:18 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D185312B4F9 for <id-event@ietf.org>; Tue, 13 Sep 2016 17:30:13 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id b187so21303664wme.1 for <id-event@ietf.org>; Tue, 13 Sep 2016 17:30:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KdIdGq1Zb38lV5+c/7/EutK90lBMaXm1+77ri/T7hXY=; b=nzXU9IlbQVEOjqq+8aX5PRmCWInymAbUr7wrky1PMpLsoFmw9STBiGHkR/z0o4+/d4 mM5VV29wuYyvHHqR3Z20m6bwSH6W7PFGkTNv7rX3M9Nb91vu5GWswgsOd3w+ddU1meM8 +a22qGO3I4DRX8C2BUSEbnczDtVa9De0C5DElYtmQdeBXchE4VLHgg+T1f4U75Pc/m76 qDdjPHhTZVJUOEhA1agzZPkdCyOmoLuPCdh7JLog9KKFMqPOzYUDnAWGdKPLYk4Pyb9K TqSxfZIy6MxbEAImD1EAvqbPb3OyVC61EPHcnjl3W+m1k+J1UO0ClgpDI1nAZo7uvw/M 5IjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KdIdGq1Zb38lV5+c/7/EutK90lBMaXm1+77ri/T7hXY=; b=f01LODIAKacRTf6J/+8cn0W0m93BsajCF+J2IBEy7T3ZJbvQs7usJ3Tii1OytTlYG9 D4XIjV5qPpkh4zqiHnGrAaZ/ywj+l3i8cVlfLncJxJ/id4TqIg7okT0DIYHxGh4UUiA2 MZttO7Z/NBbLIK7/ZS+7g6XCwDUI1XM5O8l7W/eRcu1/rbzMK2xq+D9qRLsIDC72ts5V JEJ2BjikDerm8s8T2O8G88+JuabMXm/GSjVKSutokkQbigfD7N/lwO6fcWleYKXETphG j8wboqaHXnNT+waFEmfJ8s8jkbd6ycb5xYktL4xOklsO9dhEQBxVkeF9nFzO3rvV6bEH 5jSg==
X-Gm-Message-State: AE9vXwNvHFCDMQwABqgfNPIpbNXL4mrkAjX1yeGkAnvK/xRK61WudLSGs8k53+UNQKw/c2FUt/d3tRJLNHwrp8XS
X-Received: by 10.28.87.16 with SMTP id l16mr162123wmb.75.1473813012269; Tue, 13 Sep 2016 17:30:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.187.136 with HTTP; Tue, 13 Sep 2016 17:29:51 -0700 (PDT)
In-Reply-To: <56279609-CC17-465B-B7C4-AFCB696D68D8@oracle.com>
References: <56279609-CC17-465B-B7C4-AFCB696D68D8@oracle.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Tue, 13 Sep 2016 17:29:51 -0700
Message-ID: <CAGdjJpJo6Wc2F6p+0bOMavZy3PJGGhiRBhzSFcUrEaj2eYzChg@mail.gmail.com>
To: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary=001a1144375a10070d053c6cd524
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/ujd8VFnuKhbuW37itJ7S6Vy0enQ>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Transaction identifier for SETs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2016 00:30:21 -0000

--001a1144375a10070d053c6cd524
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

It might be extremely difficult or impossible for a publisher to
consistently set a correct txn. Would txn be useful at all if a publisher
is setting it as "best effort"?

Not objecting to adding as optional, just wondering if it is realistic to
set an expectation here.


Marius

On Tue, Sep 13, 2016 at 2:52 PM, Phil Hunt <phil.hunt@oracle.com> wrote:

> In discussing SET schema with a bunch of people, it is becoming clear tha=
t
> in many cases, a simple state change in a system could trigger many
> different types of SET feeds generating 4 or 5 SETs for the same
> transaction.
>
> For example, a user=E2=80=99s profile is changed in SCIM.  This could tri=
gger:
>
> *  A SCIM modify event
> *  A RISC event (account reset)
> *  Access log event
> *  OAuth /Connect events (e.g. reset session)
>
> Normally each of these events would each have their own JTI.  There would
> be a separate subscriber for each.  But I can envision some systems
> operationally that will want to look at these events together (e.g. devOp=
s).
>
> It seems useful to have a common attribute =E2=80=9Ctxn=E2=80=9D which wo=
uld be a unique
> identifier for the source transaction.  Thus if a system receives more th=
an
> one event type (directly or indirectly) it can detect whether the 2 or mo=
re
> events are about the same transaction.
>
> I propose to add this to the core spec as an optional value.
>
> Any objections?
>
> Phil
>
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
>
>
>
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>

--001a1144375a10070d053c6cd524
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">It might be extremely difficult or impossible for a publis=
her to consistently set a correct txn. Would txn be useful at all if a publ=
isher is setting it as &quot;best effort&quot;?<div><br></div><div>Not obje=
cting to adding as optional, just wondering if it is realistic to set an ex=
pectation here.</div><div><br></div></div><div class=3D"gmail_extra"><br cl=
ear=3D"all"><div><div class=3D"gmail_signature" data-smartmail=3D"gmail_sig=
nature">Marius</div></div>
<br><div class=3D"gmail_quote">On Tue, Sep 13, 2016 at 2:52 PM, Phil Hunt <=
span dir=3D"ltr">&lt;<a href=3D"mailto:phil.hunt@oracle.com" target=3D"_bla=
nk">phil.hunt@oracle.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div style=3D"word-wrap:break-word">In discussing SET schema with a b=
unch of people, it is becoming clear that in many cases, a simple state cha=
nge in a system could trigger many different types of SET feeds generating =
4 or 5 SETs for the same transaction.<div><br></div><div>For example, a use=
r=E2=80=99s profile is changed in SCIM.=C2=A0 This could trigger:</div><div=
><br></div><div>* =C2=A0A SCIM modify event</div><div>* =C2=A0A RISC event =
(account reset)</div><div>* =C2=A0Access log event=C2=A0</div><div>* =C2=A0=
OAuth /Connect events (e.g. reset session)</div><div><br></div><div>Normall=
y each of these events would each have their own JTI.=C2=A0 There would be =
a separate subscriber for each.=C2=A0 But I can envision some systems opera=
tionally that will want to look at these events together (e.g. devOps).</di=
v><div><br></div><div>It seems useful to have a common attribute =E2=80=9Ct=
xn=E2=80=9D which would be a unique identifier for the source transaction.=
=C2=A0 Thus if a system receives more than one event type (directly or indi=
rectly) it can detect whether the 2 or more events are about the same trans=
action.</div><div><br></div><div>I propose to add this to the core spec as =
an optional value.</div><div><br></div><div>Any objections?</div><div><br><=
div><div>
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wra=
p:break-word"><div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-ali=
gn:start;text-indent:0px;text-transform:none;white-space:normal;word-spacin=
g:0px;word-wrap:break-word"><div><span class=3D"m_-6717957258555541342Apple=
-style-span" style=3D"border-collapse:separate;line-height:normal;border-sp=
acing:0px"><div style=3D"word-wrap:break-word"><div><div><div>Phil</div><di=
v><br></div><div>@independentid</div><div><a href=3D"http://www.independent=
id.com" target=3D"_blank">www.independentid.com</a></div></div></div></div>=
</span><a href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">phil.hunt@=
oracle.com</a></div><div><br></div></div><br class=3D"m_-671795725855554134=
2Apple-interchange-newline"></div><br class=3D"m_-6717957258555541342Apple-=
interchange-newline"><br class=3D"m_-6717957258555541342Apple-interchange-n=
ewline">
</div>
<br></div></div></div><br>______________________________<wbr>______________=
___<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a=
><br>
<br></blockquote></div><br></div>

--001a1144375a10070d053c6cd524--


From nobody Tue Sep 13 17:32:42 2016
Return-Path: <mscurtescu@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E540A12B109 for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 17:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level: 
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ozcQ9xtypEgR for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 17:32:38 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0005512B156 for <id-event@ietf.org>; Tue, 13 Sep 2016 17:32:37 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id b187so21354441wme.1 for <id-event@ietf.org>; Tue, 13 Sep 2016 17:32:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ja+npzQjU+eK477e9pZiU/n8ECCKCyv2m0tKXIdobPM=; b=K8CAz0i9P8GWT/FJBM64q8tDqVYdeOjV3lXNdqOfhVMXxgV/RXbXBC5x6B67ZCAefB e20T1f3cMYSrMrO897VUIVuyBKFpO9XV9TSWCQdmgQgxKSIGqh4PonNoKjsEi0XOzlsr A+7Lw92DFP/IzWn15AnVnUll9GA85ufJz9Wc3i1Uii4arR9eWEStBqODn+xu1ZPkBy7G LG4WtgbE+jl6AsoRykQD98wwbpch5ULtiCWO3sIlYYXa2nL+HlMhmrUzF0loGRRcpR3T paVHA95Vo/hi4fsDzw0ZHkkTVPjh8oGIGnJYXwtTqBy7kb/WypPPiE6YrjxXc5ERwWRk jYvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ja+npzQjU+eK477e9pZiU/n8ECCKCyv2m0tKXIdobPM=; b=hQVnuUW4xCwSs8uaA/8UtZxy3zAQGJjr7IBAkLKl+Y+lX6wqPUVak7M3eUCk3bMuUC IU5E2/3Dfgg/QHwowhYKWQcTtV0kDVZ3P2lDlDxBAiIsIHjkxfUbxBErK6eeHE57tpXK vNFJfHYZD96dCiwgrcq2o5a/cITEW0UvltMjnESRRPeQySsWoJGgSuNZ4PJEVLXiNHun C1CHKoDR4FlUfq4pOV+U8f7gCKj2d/nTvI4nThScAl9lV306JaL/zlslE5LGxPPoA2r8 0rZa5SixWWuZbitoYzVEy4OixW98LyXaOBt+vNMK10dFcIN/DojpZTzc1jin5EU96jac U6ag==
X-Gm-Message-State: AE9vXwMOuiM65dJBWFuWyUo7fovmTnsZXPd5mb7RC9CoxNhFLNTBXmKclerBG3O/9fiDdBCt4BO0q27TerD3qCPY
X-Received: by 10.194.116.197 with SMTP id jy5mr3012332wjb.11.1473813156346; Tue, 13 Sep 2016 17:32:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.187.136 with HTTP; Tue, 13 Sep 2016 17:32:15 -0700 (PDT)
In-Reply-To: <2EC6A66C-1219-4B40-9B95-FD557794C069@oracle.com>
References: <2EC6A66C-1219-4B40-9B95-FD557794C069@oracle.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Tue, 13 Sep 2016 17:32:15 -0700
Message-ID: <CAGdjJpJyxxupeWN0M9=d6KNb8MjMu5pkGb6-1Jqd4hFr1HVOxw@mail.gmail.com>
To: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary=001a1130cf26a6a19f053c6cdd20
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/59E89j5Jjio3cbDbxxxl7d5n2Bg>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Ordering of SET events
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2016 00:32:41 -0000

--001a1130cf26a6a19f053c6cdd20
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I think the only reasonable statement is that subscribers should not assume
any kind of ordering.

Is there a use case where subscribers care about ordering?

Marius

On Tue, Sep 13, 2016 at 2:56 PM, Phil Hunt <phil.hunt@oracle.com> wrote:

> I think we may need to ensure we have the correct language on how
> subscribers can order events. Can they strictly depend on the order by
> which they are received, or can they use =E2=80=9Ciat=E2=80=9D?
>
> The issue is that when SETs are published they may be published by highly
> distributed systems were it is unreasonable to co-ordinate a sequence
> number in many cases.  This basically leads us to using timestamps.
>
> Would it be reasonable to use =E2=80=9Ciat=E2=80=9D for this purpose?  Ke=
ep in mind, we
> have discussed that =E2=80=9Ciat=E2=80=9D corresponds to the time of the =
SET being
> generated (and optionally signed) and might not be the transaction time.
>
> Do we need some sort of clarifying language on this?
>
> Phil
>
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
>
>
>
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>

--001a1130cf26a6a19f053c6cdd20
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think the only reasonable statement is that subscribers =
should not assume any kind of ordering.<div><br></div><div>Is there a use c=
ase where subscribers care about ordering?</div></div><div class=3D"gmail_e=
xtra"><br clear=3D"all"><div><div class=3D"gmail_signature" data-smartmail=
=3D"gmail_signature">Marius</div></div>
<br><div class=3D"gmail_quote">On Tue, Sep 13, 2016 at 2:56 PM, Phil Hunt <=
span dir=3D"ltr">&lt;<a href=3D"mailto:phil.hunt@oracle.com" target=3D"_bla=
nk">phil.hunt@oracle.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div style=3D"word-wrap:break-word">I think we may need to ensure we =
have the correct language on how subscribers can order events. Can they str=
ictly depend on the order by which they are received, or can they use =E2=
=80=9Ciat=E2=80=9D?<div><br></div><div>The issue is that when SETs are publ=
ished they may be published by highly distributed systems were it is unreas=
onable to co-ordinate a sequence number in many cases.=C2=A0 This basically=
 leads us to using timestamps.</div><div><br></div><div>Would it be reasona=
ble to use =E2=80=9Ciat=E2=80=9D for this purpose?=C2=A0 Keep in mind, we h=
ave discussed that =E2=80=9Ciat=E2=80=9D corresponds to the time of the SET=
 being generated (and optionally signed) and might not be the transaction t=
ime.</div><div><br></div><div>Do we need some sort of clarifying language o=
n this?</div><div><br><div>
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wra=
p:break-word"><div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-ali=
gn:start;text-indent:0px;text-transform:none;white-space:normal;word-spacin=
g:0px;word-wrap:break-word"><div><span class=3D"m_-6927950503172065459Apple=
-style-span" style=3D"border-collapse:separate;line-height:normal;border-sp=
acing:0px"><div style=3D"word-wrap:break-word"><div><div><div>Phil</div><di=
v><br></div><div>@independentid</div><div><a href=3D"http://www.independent=
id.com" target=3D"_blank">www.independentid.com</a></div></div></div></div>=
</span><a href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">phil.hunt@=
oracle.com</a></div><div><br></div></div><br class=3D"m_-692795050317206545=
9Apple-interchange-newline"></div><br class=3D"m_-6927950503172065459Apple-=
interchange-newline"><br class=3D"m_-6927950503172065459Apple-interchange-n=
ewline">
</div>
<br></div></div><br>______________________________<wbr>_________________<br=
>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a=
><br>
<br></blockquote></div><br></div>

--001a1130cf26a6a19f053c6cdd20--


From nobody Tue Sep 13 19:24:02 2016
Return-Path: <cmortimore@salesforce.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB21C12B47E for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 19:24:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=salesforce.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dk480prrUHPP for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 19:23:58 -0700 (PDT)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1F7712B4B9 for <id-event@ietf.org>; Tue, 13 Sep 2016 19:23:58 -0700 (PDT)
Received: by mail-it0-x230.google.com with SMTP id 186so4343030itf.0 for <id-event@ietf.org>; Tue, 13 Sep 2016 19:23:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salesforce.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=p/2adWAfjbQ9joiUuoiQRTT6LE6vECdYai54peOpFdk=; b=GSEMTSkRtwHVZTgv4qFUjSZ/MdzYg4HFc2WGgwDfWTVoqCAQqE7mua1Ja+3awsyhTq 0tjYLYUGtbvS5sBlmfYeREE3wT7XH6NG2mewZgdrMJaX0OPR68uzVwyy6yNAIfd9pnrj X71tJVnYwqufZrb6qwJYexj+/2kzp/yZ0+YuU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=p/2adWAfjbQ9joiUuoiQRTT6LE6vECdYai54peOpFdk=; b=TbErLyH+VwORgKfk5Kn/fjeCkQHLuczCNpovPTH/itnMIii+NOd0clYxOrjGD96ovL I4aQH6+bwm7+xgcWlQBu7dKHO1rMdtzKFunfgxjyt4wm9XfpivjGHzla31OPpMviu8k+ KPq3c5Sqr6TnY50A8vt6p9AQ7K6YMiBp0qPYjCijcjhGAohZFN6nF9/FPLYnGvWbnFzr tmyi8CJvo9vqAi4qSvRginEfqspTmXzZ1ymR0tp3Pq/sdvwIZWN7RQn8u8ZcYrEY4W1j ayPpkxDuFGzjQj90cAUMa2CFULOzxUurR9z2NsZsW2kHnYZNYgCEmEP/wbmTBs+jsP1n oO5g==
X-Gm-Message-State: AE9vXwPJCrRa4z6FRwr3OhX8/V63H/bI/WdUerSdMgEd/NchBdRLz8+DScHDs5J5KfA9rg2SBGR/cTTt7ekPWFtj
X-Received: by 10.107.19.37 with SMTP id b37mr1349904ioj.162.1473819837948; Tue, 13 Sep 2016 19:23:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.238.37 with HTTP; Tue, 13 Sep 2016 19:23:57 -0700 (PDT)
In-Reply-To: <2EC6A66C-1219-4B40-9B95-FD557794C069@oracle.com>
References: <2EC6A66C-1219-4B40-9B95-FD557794C069@oracle.com>
From: Chuck Mortimore <cmortimore@salesforce.com>
Date: Tue, 13 Sep 2016 19:23:57 -0700
Message-ID: <CA+wnMn-_TdC9GcCPYyd98Qhd8cwSAOSpxgU93KdKathEk7pzGA@mail.gmail.com>
To: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary=001a113dea0ee7e426053c6e6bec
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/ezi9z1RCtBg9nZQ3oW1x5rNwo-I>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Ordering of SET events
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2016 02:24:02 -0000

--001a113dea0ee7e426053c6e6bec
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

>From a protocol perspective, I don't believe it's reasonable to use iat for
ordering purposes.  Either the use-cases demand ordered deliver, in which
case you account for it in protocol and architecture, or they don't.
Trying to approximate it via timestamps isn't the right solution.

On Tue, Sep 13, 2016 at 2:56 PM, Phil Hunt <phil.hunt@oracle.com> wrote:

> I think we may need to ensure we have the correct language on how
> subscribers can order events. Can they strictly depend on the order by
> which they are received, or can they use =E2=80=9Ciat=E2=80=9D?
>
> The issue is that when SETs are published they may be published by highly
> distributed systems were it is unreasonable to co-ordinate a sequence
> number in many cases.  This basically leads us to using timestamps.
>
> Would it be reasonable to use =E2=80=9Ciat=E2=80=9D for this purpose?  Ke=
ep in mind, we
> have discussed that =E2=80=9Ciat=E2=80=9D corresponds to the time of the =
SET being
> generated (and optionally signed) and might not be the transaction time.
>
> Do we need some sort of clarifying language on this?
>
> Phil
>
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
>
>
>
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>

--001a113dea0ee7e426053c6e6bec
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">From a protocol perspective, I don&#39;t believe it&#39;s =
reasonable to use iat for ordering purposes.=C2=A0 Either the use-cases dem=
and ordered deliver, in which case you account for it in protocol and archi=
tecture, or they don&#39;t. =C2=A0 Trying to approximate it via timestamps =
isn&#39;t the right solution.</div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Tue, Sep 13, 2016 at 2:56 PM, Phil Hunt <span dir=3D"l=
tr">&lt;<a href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">phil.hunt=
@oracle.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div st=
yle=3D"word-wrap:break-word">I think we may need to ensure we have the corr=
ect language on how subscribers can order events. Can they strictly depend =
on the order by which they are received, or can they use =E2=80=9Ciat=E2=80=
=9D?<div><br></div><div>The issue is that when SETs are published they may =
be published by highly distributed systems were it is unreasonable to co-or=
dinate a sequence number in many cases.=C2=A0 This basically leads us to us=
ing timestamps.</div><div><br></div><div>Would it be reasonable to use =E2=
=80=9Ciat=E2=80=9D for this purpose?=C2=A0 Keep in mind, we have discussed =
that =E2=80=9Ciat=E2=80=9D corresponds to the time of the SET being generat=
ed (and optionally signed) and might not be the transaction time.</div><div=
><br></div><div>Do we need some sort of clarifying language on this?</div><=
div><br><div>
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wra=
p:break-word"><div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-ali=
gn:start;text-indent:0px;text-transform:none;white-space:normal;word-spacin=
g:0px;word-wrap:break-word"><div><span style=3D"border-collapse:separate;li=
ne-height:normal;border-spacing:0px"><div style=3D"word-wrap:break-word"><d=
iv><div><div>Phil</div><div><br></div><div>@independentid</div><div><a href=
=3D"http://www.independentid.com" target=3D"_blank">www.independentid.com</=
a></div></div></div></div></span><a href=3D"mailto:phil.hunt@oracle.com" ta=
rget=3D"_blank">phil.hunt@oracle.com</a></div><div><br></div></div><br></di=
v><br><br>
</div>
<br></div></div><br>______________________________<wbr>_________________<br=
>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a=
><br>
<br></blockquote></div><br></div>

--001a113dea0ee7e426053c6e6bec--


From nobody Tue Sep 13 19:25:27 2016
Return-Path: <cmortimore@salesforce.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9464112B50F for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 19:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=salesforce.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OgyovawZfIIz for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 19:25:23 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4484A12B4B9 for <id-event@ietf.org>; Tue, 13 Sep 2016 19:25:23 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id n143so4328070ita.1 for <id-event@ietf.org>; Tue, 13 Sep 2016 19:25:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salesforce.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=j71MKZJZm0Qgjbn1fUGD3cuYCejJmj060R7n3L6+RaI=; b=WQhVkenB4ew1zWURjrbM6bpE9j9OlkWYxGst55lGXpMAfeVO8CnTz80J8lp/CYr6fL Tkdl2qCMTWjzy6h/IoNzq84kfxMOF4L0/dVXxQevDzfwLHUvhozqxI1zHeVB2RuAlJIX in+13nxcGpA7WEb0187H97zEgvy6qafVZgMhU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=j71MKZJZm0Qgjbn1fUGD3cuYCejJmj060R7n3L6+RaI=; b=hHClIuoI90YGMQKfDHlgPoO5kEU+M4eEYjQO41TVVexG8zSGBqgrj/Lrpn8vPi8yR6 +yT84mrH4+RIfSVb3dFVEO867sYr5KfT1kSyc/A7/0Z8FE5daPGv8ya5pGap4G0yDTbg Rns4vktTqHKBUzSj+UNFTe3BuKis9QJx6LqhRCpuybA+NOEw20jWV8AcddGdi3cY3RZQ L2i8EhvQCrlFS9BXLqK1x4MHKMGODeYVKaXqMS8k4Nv1/yuMiwqa8lvmZnX6Do8rr0Jh RK6O2C1cOS7Gh67FfB2pgiify9t28IL3c5dM5lzdEDFBXW3RSrFA0dt7A+C0eOyjPiVJ 2rnA==
X-Gm-Message-State: AE9vXwMw+cg/gx8zmi4jNXjLCpzR+gnofKMDnTyz8e+3RK2z+Gbk+YlsYOaRYACG0bAHfZbY0MJslNPkqxXgBFTm
X-Received: by 10.107.135.22 with SMTP id j22mr1444590iod.2.1473819922572; Tue, 13 Sep 2016 19:25:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.238.37 with HTTP; Tue, 13 Sep 2016 19:25:22 -0700 (PDT)
In-Reply-To: <56279609-CC17-465B-B7C4-AFCB696D68D8@oracle.com>
References: <56279609-CC17-465B-B7C4-AFCB696D68D8@oracle.com>
From: Chuck Mortimore <cmortimore@salesforce.com>
Date: Tue, 13 Sep 2016 19:25:22 -0700
Message-ID: <CA+wnMn_qSvH=pjxMUDrbyTtJ2SvM_f9EiMAvFLr439NoG655cA@mail.gmail.com>
To: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary=001a113f993ef2ec00053c6e7094
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/uHU4gIqc1V_pd6Fi_tbxpmdsV_k>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Transaction identifier for SETs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2016 02:25:25 -0000

--001a113f993ef2ec00053c6e7094
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

If it's added, I'd make sure the txn identifier is clearly relative/unique
by issuer.

On Tue, Sep 13, 2016 at 2:52 PM, Phil Hunt <phil.hunt@oracle.com> wrote:

> In discussing SET schema with a bunch of people, it is becoming clear tha=
t
> in many cases, a simple state change in a system could trigger many
> different types of SET feeds generating 4 or 5 SETs for the same
> transaction.
>
> For example, a user=E2=80=99s profile is changed in SCIM.  This could tri=
gger:
>
> *  A SCIM modify event
> *  A RISC event (account reset)
> *  Access log event
> *  OAuth /Connect events (e.g. reset session)
>
> Normally each of these events would each have their own JTI.  There would
> be a separate subscriber for each.  But I can envision some systems
> operationally that will want to look at these events together (e.g. devOp=
s).
>
> It seems useful to have a common attribute =E2=80=9Ctxn=E2=80=9D which wo=
uld be a unique
> identifier for the source transaction.  Thus if a system receives more th=
an
> one event type (directly or indirectly) it can detect whether the 2 or mo=
re
> events are about the same transaction.
>
> I propose to add this to the core spec as an optional value.
>
> Any objections?
>
> Phil
>
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
>
>
>
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>

--001a113f993ef2ec00053c6e7094
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">If it&#39;s added, I&#39;d make sure the txn identifier is=
 clearly relative/unique by issuer.</div><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Tue, Sep 13, 2016 at 2:52 PM, Phil Hunt <span di=
r=3D"ltr">&lt;<a href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">phi=
l.hunt@oracle.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
div style=3D"word-wrap:break-word">In discussing SET schema with a bunch of=
 people, it is becoming clear that in many cases, a simple state change in =
a system could trigger many different types of SET feeds generating 4 or 5 =
SETs for the same transaction.<div><br></div><div>For example, a user=E2=80=
=99s profile is changed in SCIM.=C2=A0 This could trigger:</div><div><br></=
div><div>* =C2=A0A SCIM modify event</div><div>* =C2=A0A RISC event (accoun=
t reset)</div><div>* =C2=A0Access log event=C2=A0</div><div>* =C2=A0OAuth /=
Connect events (e.g. reset session)</div><div><br></div><div>Normally each =
of these events would each have their own JTI.=C2=A0 There would be a separ=
ate subscriber for each.=C2=A0 But I can envision some systems operationall=
y that will want to look at these events together (e.g. devOps).</div><div>=
<br></div><div>It seems useful to have a common attribute =E2=80=9Ctxn=E2=
=80=9D which would be a unique identifier for the source transaction.=C2=A0=
 Thus if a system receives more than one event type (directly or indirectly=
) it can detect whether the 2 or more events are about the same transaction=
.</div><div><br></div><div>I propose to add this to the core spec as an opt=
ional value.</div><div><br></div><div>Any objections?</div><div><br><div><d=
iv>
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wra=
p:break-word"><div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-ali=
gn:start;text-indent:0px;text-transform:none;white-space:normal;word-spacin=
g:0px;word-wrap:break-word"><div><span style=3D"border-collapse:separate;li=
ne-height:normal;border-spacing:0px"><div style=3D"word-wrap:break-word"><d=
iv><div><div>Phil</div><div><br></div><div>@independentid</div><div><a href=
=3D"http://www.independentid.com" target=3D"_blank">www.independentid.com</=
a></div></div></div></div></span><a href=3D"mailto:phil.hunt@oracle.com" ta=
rget=3D"_blank">phil.hunt@oracle.com</a></div><div><br></div></div><br></di=
v><br><br>
</div>
<br></div></div></div><br>______________________________<wbr>______________=
___<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a=
><br>
<br></blockquote></div><br></div>

--001a113f993ef2ec00053c6e7094--


From nobody Tue Sep 13 19:30:15 2016
Return-Path: <alanhkarp@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86C9512B175 for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 19:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E4Gy2KIBDsg3 for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 19:30:11 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5009C12B13D for <id-event@ietf.org>; Tue, 13 Sep 2016 19:30:11 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id m11so1001529oif.1 for <id-event@ietf.org>; Tue, 13 Sep 2016 19:30:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=onTYLUFSWJq9rWuP1ct9q11/iaut68+2WtdqB4nLa2U=; b=Z2q6u1/HbTe/kgcqrl7257QVZ2erkVfqu4/cRfs+DvV2Ap1ODTZciyhbpywyZapPZK AyI1Urj+lcpJySa4gXQKJiGJZp4A3cGsrLF5+E14Wly+blXe13n+RFh4SKTHPXxQFBDn iDIQnRtJZZw0qcPho2kcTBcGZ2ClRzoFJ2Hh4lIzNTFfXJbeOH0XM5Pu5zfLu9N38HGB GvwTVzrnzmYIRQHBtG54xN7qOvZ7J5LwAEIzl8t5ZP/gtptlOf41y2vsYhIYCuYrUFkE C5izbRtYksJNCVLxgwkl4BnkAfQEtsrnxfGbgnNTyMhlbm3MfnHe2WNXTRTbyNkRdOZv Yyvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=onTYLUFSWJq9rWuP1ct9q11/iaut68+2WtdqB4nLa2U=; b=WhOObzmsEmiAJwFAk0y4E1UE4KN7v4w9PkIdCecO/izIuy3SjDDy+2L8LZKYdNxjFC 4n9MlsDXKBFfixjHIQErvHsmWdUjnXvWcUih8cANZQK4Up2FX8qir4yRg+CNs+XAVuIt v/1EzZh3aVHvnAQhJmE1e4qSKpcwhpO7V8hN16s4CvvWN/MWxhfV/RF51dZxprwxYvvp C6TKnF8+O5oqFWDhdb3JQ5tPyUO77SoUMY4pztTSrABXh5ORkcnDafoIdp1OAlgpf8hM iVtakAEh7/Ro/UZbu2/pHKuB/zwH+n38SGXRnVEi+5Qm2kXmeHsn3s1Ex1MQKvOuk7xG gbvQ==
X-Gm-Message-State: AE9vXwMvv7NI7sQU8/IsOhnSmlo8d1YCjOZ2BHUXQhIZxfDjDQNCOjbdEAwmLX/m2P1YCU36OfO/9pB6uJWhVQ==
X-Received: by 10.202.105.208 with SMTP id e199mr92689oic.159.1473820209685; Tue, 13 Sep 2016 19:30:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.39.54 with HTTP; Tue, 13 Sep 2016 19:30:09 -0700 (PDT)
In-Reply-To: <2EC6A66C-1219-4B40-9B95-FD557794C069@oracle.com>
References: <2EC6A66C-1219-4B40-9B95-FD557794C069@oracle.com>
From: Alan Karp <alanhkarp@gmail.com>
Date: Tue, 13 Sep 2016 19:30:09 -0700
Message-ID: <CANpA1Z2dw=vF_U7G8vihin8N65LBTRADJDoPMHZptSiupvYtHw@mail.gmail.com>
To: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary=001a1140339e0faa35053c6e82c3
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/iYIZBpL_wwIRffH0zdXtLjPQcKQ>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Ordering of SET events
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2016 02:30:14 -0000

--001a1140339e0faa35053c6e82c3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Be careful of relying on timestamps from different machines.  There are
systems, such as Cassandra, that have run into problems.


--------------
Alan Karp

On Tue, Sep 13, 2016 at 2:56 PM, Phil Hunt <phil.hunt@oracle.com> wrote:

> I think we may need to ensure we have the correct language on how
> subscribers can order events. Can they strictly depend on the order by
> which they are received, or can they use =E2=80=9Ciat=E2=80=9D?
>
> The issue is that when SETs are published they may be published by highly
> distributed systems were it is unreasonable to co-ordinate a sequence
> number in many cases.  This basically leads us to using timestamps.
>
> Would it be reasonable to use =E2=80=9Ciat=E2=80=9D for this purpose?  Ke=
ep in mind, we
> have discussed that =E2=80=9Ciat=E2=80=9D corresponds to the time of the =
SET being
> generated (and optionally signed) and might not be the transaction time.
>
> Do we need some sort of clarifying language on this?
>
> Phil
>
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
>
>
>
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>

--001a1140339e0faa35053c6e82c3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Be careful of relying on timestamps from different machine=
s.=C2=A0 There are systems, such as Cassandra, that have run into problems.=
</div><div class=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail=
_signature" data-smartmail=3D"gmail_signature"><br>--------------<br>Alan K=
arp</div></div>
<br><div class=3D"gmail_quote">On Tue, Sep 13, 2016 at 2:56 PM, Phil Hunt <=
span dir=3D"ltr">&lt;<a href=3D"mailto:phil.hunt@oracle.com" target=3D"_bla=
nk">phil.hunt@oracle.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div style=3D"word-wrap:break-word">I think we may need to ensure we =
have the correct language on how subscribers can order events. Can they str=
ictly depend on the order by which they are received, or can they use =E2=
=80=9Ciat=E2=80=9D?<div><br></div><div>The issue is that when SETs are publ=
ished they may be published by highly distributed systems were it is unreas=
onable to co-ordinate a sequence number in many cases.=C2=A0 This basically=
 leads us to using timestamps.</div><div><br></div><div>Would it be reasona=
ble to use =E2=80=9Ciat=E2=80=9D for this purpose?=C2=A0 Keep in mind, we h=
ave discussed that =E2=80=9Ciat=E2=80=9D corresponds to the time of the SET=
 being generated (and optionally signed) and might not be the transaction t=
ime.</div><div><br></div><div>Do we need some sort of clarifying language o=
n this?</div><div><br><div>
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wra=
p:break-word"><div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-ali=
gn:start;text-indent:0px;text-transform:none;white-space:normal;word-spacin=
g:0px;word-wrap:break-word"><div><span style=3D"border-collapse:separate;li=
ne-height:normal;border-spacing:0px"><div style=3D"word-wrap:break-word"><d=
iv><div><div>Phil</div><div><br></div><div>@independentid</div><div><a href=
=3D"http://www.independentid.com" target=3D"_blank">www.independentid.com</=
a></div></div></div></div></span><a href=3D"mailto:phil.hunt@oracle.com" ta=
rget=3D"_blank">phil.hunt@oracle.com</a></div><div><br></div></div><br></di=
v><br><br>
</div>
<br></div></div><br>______________________________<wbr>_________________<br=
>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a=
><br>
<br></blockquote></div><br></div>

--001a1140339e0faa35053c6e82c3--


From nobody Tue Sep 13 21:45:18 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F00C12B548 for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 21:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.728
X-Spam-Level: 
X-Spam-Status: No, score=-5.728 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3B7CrslaMuDz for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 21:45:14 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 289CB12B296 for <id-event@ietf.org>; Tue, 13 Sep 2016 21:45:14 -0700 (PDT)
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8E4jC2V002303 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2016 04:45:12 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u8E4jBPq030995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2016 04:45:12 GMT
Received: from abhmp0009.oracle.com (abhmp0009.oracle.com [141.146.116.15]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u8E4jAWF003133; Wed, 14 Sep 2016 04:45:11 GMT
Received: from [172.20.2.244] (/40.139.251.125) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 13 Sep 2016 21:45:10 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_DDBADD4D-D8E8-48E3-B7CF-52CB1B79F5E3"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Phil Hunt <phil.hunt@oracle.com>
In-Reply-To: <CA+wnMn_qSvH=pjxMUDrbyTtJ2SvM_f9EiMAvFLr439NoG655cA@mail.gmail.com>
Date: Tue, 13 Sep 2016 21:45:10 -0700
Message-Id: <360CFB17-D484-49C1-A6BD-A5FDB952E929@oracle.com>
References: <56279609-CC17-465B-B7C4-AFCB696D68D8@oracle.com> <CA+wnMn_qSvH=pjxMUDrbyTtJ2SvM_f9EiMAvFLr439NoG655cA@mail.gmail.com>
To: Chuck Mortimore <cmortimore@salesforce.com>
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0021.oracle.com [141.146.126.233]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/GVsL8bArVYaX9miDmmTcik817SE>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Transaction identifier for SETs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2016 04:45:17 -0000

--Apple-Mail=_DDBADD4D-D8E8-48E3-B7CF-52CB1B79F5E3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

To be clear, the scenario is the publisher is issuing multiple SETs =
against for a single transaction. So the publisher can for example =
generate a GUID and then just puts that value on each different SET =
issued against the same event.

In most cases, since each subscriber cares about a different =E2=80=9Cvers=
ion of the event=E2=80=9D (e.g. RISC vs. SCIM), they likely won=E2=80=99t =
need to correlate.=20

This seems to come up in DevOps when an operator is trying to trans what =
happened where.  The receiver of a RISC event could report back the TXN =
id, which might be useful to tracing it back in say an access log or =
some other system.

I agree with Marius, that if a sequential number is desired that could =
be very difficult to implement in practice assuming things like clusters =
and multi-data centers.

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>





> On Sep 13, 2016, at 7:25 PM, Chuck Mortimore =
<cmortimore@salesforce.com> wrote:
>=20
> If it's added, I'd make sure the txn identifier is clearly =
relative/unique by issuer.
>=20
> On Tue, Sep 13, 2016 at 2:52 PM, Phil Hunt <phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>> wrote:
> In discussing SET schema with a bunch of people, it is becoming clear =
that in many cases, a simple state change in a system could trigger many =
different types of SET feeds generating 4 or 5 SETs for the same =
transaction.
>=20
> For example, a user=E2=80=99s profile is changed in SCIM.  This could =
trigger:
>=20
> *  A SCIM modify event
> *  A RISC event (account reset)
> *  Access log event=20
> *  OAuth /Connect events (e.g. reset session)
>=20
> Normally each of these events would each have their own JTI.  There =
would be a separate subscriber for each.  But I can envision some =
systems operationally that will want to look at these events together =
(e.g. devOps).
>=20
> It seems useful to have a common attribute =E2=80=9Ctxn=E2=80=9D which =
would be a unique identifier for the source transaction.  Thus if a =
system receives more than one event type (directly or indirectly) it can =
detect whether the 2 or more events are about the same transaction.
>=20
> I propose to add this to the core spec as an optional value.
>=20
> Any objections?
>=20
> Phil
>=20
> @independentid
> www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org <mailto:Id-event@ietf.org>
> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
>=20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event


--Apple-Mail=_DDBADD4D-D8E8-48E3-B7CF-52CB1B79F5E3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">To be clear, the scenario is the publisher is issuing =
multiple SETs against for a single transaction. So the publisher can for =
example generate a GUID and then just puts that value on each different =
SET issued against the same event.<div class=3D""><br =
class=3D""></div><div class=3D"">In most cases, since each subscriber =
cares about a different =E2=80=9Cversion of the event=E2=80=9D (e.g. =
RISC vs. SCIM), they likely won=E2=80=99t need to =
correlate.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">This seems to come up in DevOps when an operator is trying to =
trans what happened where. &nbsp;The receiver of a RISC event could =
report back the TXN id, which might be useful to tracing it back in say =
an access log or some other system.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I agree with Marius, that if a =
sequential number is desired that could be very difficult to implement =
in practice assuming things like clusters and multi-data =
centers.</div><div class=3D""><br class=3D""></div><div class=3D""><div =
class=3D""><div class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Sep 13, 2016, at 7:25 PM, Chuck Mortimore &lt;<a =
href=3D"mailto:cmortimore@salesforce.com" =
class=3D"">cmortimore@salesforce.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">If it's added, I'd make sure the txn identifier is clearly =
relative/unique by issuer.</div><div class=3D"gmail_extra"><br =
class=3D""><div class=3D"gmail_quote">On Tue, Sep 13, 2016 at 2:52 PM, =
Phil Hunt <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" =
class=3D"">phil.hunt@oracle.com</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word" class=3D"">In discussing SET schema with =
a bunch of people, it is becoming clear that in many cases, a simple =
state change in a system could trigger many different types of SET feeds =
generating 4 or 5 SETs for the same transaction.<div class=3D""><br =
class=3D""></div><div class=3D"">For example, a user=E2=80=99s profile =
is changed in SCIM.&nbsp; This could trigger:</div><div class=3D""><br =
class=3D""></div><div class=3D"">* &nbsp;A SCIM modify event</div><div =
class=3D"">* &nbsp;A RISC event (account reset)</div><div class=3D"">* =
&nbsp;Access log event&nbsp;</div><div class=3D"">* &nbsp;OAuth /Connect =
events (e.g. reset session)</div><div class=3D""><br class=3D""></div><div=
 class=3D"">Normally each of these events would each have their own =
JTI.&nbsp; There would be a separate subscriber for each.&nbsp; But I =
can envision some systems operationally that will want to look at these =
events together (e.g. devOps).</div><div class=3D""><br =
class=3D""></div><div class=3D"">It seems useful to have a common =
attribute =E2=80=9Ctxn=E2=80=9D which would be a unique identifier for =
the source transaction.&nbsp; Thus if a system receives more than one =
event type (directly or indirectly) it can detect whether the 2 or more =
events are about the same transaction.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I propose to add this to the core spec =
as an optional value.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Any objections?</div><div class=3D""><br class=3D""><div =
class=3D""><div class=3D"">
<div style=3D"letter-spacing: normal; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; word-spacing: 0px; =
word-wrap: break-word;" class=3D""><div style=3D"letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; word-wrap: break-word;" class=3D""><div =
class=3D""><span =
style=3D"border-collapse:separate;line-height:normal;border-spacing:0px" =
class=3D""><div style=3D"word-wrap:break-word" class=3D""><div =
class=3D""><div class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com/" target=3D"_blank" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" =
class=3D"">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D""></div><br class=3D""><br class=3D"">=

</div>
<br class=3D""></div></div></div><br =
class=3D"">______________________________<wbr =
class=3D"">_________________<br class=3D"">
Id-event mailing list<br class=3D"">
<a href=3D"mailto:Id-event@ietf.org" class=3D"">Id-event@ietf.org</a><br =
class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/<wbr =
class=3D"">listinfo/id-event</a><br class=3D"">
<br class=3D""></blockquote></div><br class=3D""></div>
_______________________________________________<br class=3D"">Id-event =
mailing list<br class=3D""><a href=3D"mailto:Id-event@ietf.org" =
class=3D"">Id-event@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event<br =
class=3D""></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_DDBADD4D-D8E8-48E3-B7CF-52CB1B79F5E3--


From nobody Tue Sep 13 21:57:41 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECAE012B296 for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 21:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.728
X-Spam-Level: 
X-Spam-Status: No, score=-5.728 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nHuHlhWdQnmV for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 21:57:37 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 761D312B1A0 for <id-event@ietf.org>; Tue, 13 Sep 2016 21:57:37 -0700 (PDT)
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8E4vaIQ011838 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2016 04:57:36 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u8E4vYcv008879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2016 04:57:36 GMT
Received: from abhmp0006.oracle.com (abhmp0006.oracle.com [141.146.116.12]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u8E4vX0R006624; Wed, 14 Sep 2016 04:57:34 GMT
Received: from [172.20.2.244] (/40.139.251.125) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 13 Sep 2016 21:57:33 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_9526922D-6BCE-4B95-8562-2030BA4C525D"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Phil Hunt <phil.hunt@oracle.com>
In-Reply-To: <CA+wnMn-_TdC9GcCPYyd98Qhd8cwSAOSpxgU93KdKathEk7pzGA@mail.gmail.com>
Date: Tue, 13 Sep 2016 21:57:33 -0700
Message-Id: <26940C91-F9B9-46CD-9F80-BF53606ADF48@oracle.com>
References: <2EC6A66C-1219-4B40-9B95-FD557794C069@oracle.com> <CA+wnMn-_TdC9GcCPYyd98Qhd8cwSAOSpxgU93KdKathEk7pzGA@mail.gmail.com>
To: Chuck Mortimore <cmortimore@salesforce.com>
X-Mailer: Apple Mail (2.3124)
X-Source-IP: userv0021.oracle.com [156.151.31.71]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/9GVt-gk2AKNovHqY9g303JRxYvc>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Ordering of SET events
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2016 04:57:41 -0000

--Apple-Mail=_9526922D-6BCE-4B95-8562-2030BA4C525D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I tend to agree. Timestamps are problematic. Yet they can be =
individually asserted (skew issues aside).  There may  also be different =
transaction time vs. SET issued at times.  If for performance reasons =
the feed publisher runs on a separate thread or even a separate server, =
than transaction time vs. iat may be substantially different. (e.g. 10 =
mins).

Regarding Marius=E2=80=99s question, the use case probably is important =
to SCIM Event cases.  Subscribers need to be able to track what order =
events occurred in.  For example user x was created and then user x was =
modified.  If those come out of sequence it could cause different =
conclusions by the subscriber.

On the other hand, OIDC Logout doesn=E2=80=99t care about ordering at =
all. It is just saying a single thing is revoked.

I think it is in issue we should mention, but leave it to profiling =
specs to solve. For example, the SCIM WG will have to either agree to =
use the order events are received or come up with some other mechanism. =20=


Failing a specific attribute that gives and order, the only other method =
I can think of is for the client to assume that the order of receipt of =
an event may be interpreted as significant.  However I=E2=80=99m not =
convinced this is true in many cases.=20

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>





> On Sep 13, 2016, at 7:23 PM, Chuck Mortimore =
<cmortimore@salesforce.com> wrote:
>=20
> =46rom a protocol perspective, I don't believe it's reasonable to use =
iat for ordering purposes.  Either the use-cases demand ordered deliver, =
in which case you account for it in protocol and architecture, or they =
don't.   Trying to approximate it via timestamps isn't the right =
solution.
>=20
> On Tue, Sep 13, 2016 at 2:56 PM, Phil Hunt <phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>> wrote:
> I think we may need to ensure we have the correct language on how =
subscribers can order events. Can they strictly depend on the order by =
which they are received, or can they use =E2=80=9Ciat=E2=80=9D?
>=20
> The issue is that when SETs are published they may be published by =
highly distributed systems were it is unreasonable to co-ordinate a =
sequence number in many cases.  This basically leads us to using =
timestamps.
>=20
> Would it be reasonable to use =E2=80=9Ciat=E2=80=9D for this purpose?  =
Keep in mind, we have discussed that =E2=80=9Ciat=E2=80=9D corresponds =
to the time of the SET being generated (and optionally signed) and might =
not be the transaction time.
>=20
> Do we need some sort of clarifying language on this?
>=20
> Phil
>=20
> @independentid
> www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org <mailto:Id-event@ietf.org>
> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
>=20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event


--Apple-Mail=_9526922D-6BCE-4B95-8562-2030BA4C525D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">I tend to agree. Timestamps are problematic. Yet they can be =
individually asserted (skew issues aside). &nbsp;There may &nbsp;also be =
different transaction time vs. SET issued at times. &nbsp;If for =
performance reasons the feed publisher runs on a separate thread or even =
a separate server, than transaction time vs. iat may be substantially =
different. (e.g. 10 mins).<div class=3D""><br class=3D""></div><div =
class=3D"">Regarding Marius=E2=80=99s question, the use case probably is =
important to SCIM Event cases. &nbsp;Subscribers need to be able to =
track what order events occurred in. &nbsp;For example user x was =
created and then user x was modified. &nbsp;If those come out of =
sequence it could cause different conclusions by the =
subscriber.</div><div class=3D""><br class=3D""></div><div class=3D"">On =
the other hand, OIDC Logout doesn=E2=80=99t care about ordering at all. =
It is just saying a single thing is revoked.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I think it is in issue we should =
mention, but leave it to profiling specs to solve. For example, the SCIM =
WG will have to either agree to use the order events are received or =
come up with some other mechanism. &nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Failing a specific attribute that gives =
and order, the only other method I can think of is for the client to =
assume that the order of receipt of an event may be interpreted as =
significant. &nbsp;However I=E2=80=99m not convinced this is true in =
many cases.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D""><div class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Sep 13, 2016, at 7:23 PM, Chuck Mortimore &lt;<a =
href=3D"mailto:cmortimore@salesforce.com" =
class=3D"">cmortimore@salesforce.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">=46rom a protocol perspective, I don't believe it's =
reasonable to use iat for ordering purposes.&nbsp; Either the use-cases =
demand ordered deliver, in which case you account for it in protocol and =
architecture, or they don't. &nbsp; Trying to approximate it via =
timestamps isn't the right solution.</div><div class=3D"gmail_extra"><br =
class=3D""><div class=3D"gmail_quote">On Tue, Sep 13, 2016 at 2:56 PM, =
Phil Hunt <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" =
class=3D"">phil.hunt@oracle.com</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word" class=3D"">I think we may need to ensure =
we have the correct language on how subscribers can order events. Can =
they strictly depend on the order by which they are received, or can =
they use =E2=80=9Ciat=E2=80=9D?<div class=3D""><br class=3D""></div><div =
class=3D"">The issue is that when SETs are published they may be =
published by highly distributed systems were it is unreasonable to =
co-ordinate a sequence number in many cases.&nbsp; This basically leads =
us to using timestamps.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Would it be reasonable to use =E2=80=9Ciat=E2=80=9D for this =
purpose?&nbsp; Keep in mind, we have discussed that =E2=80=9Ciat=E2=80=9D =
corresponds to the time of the SET being generated (and optionally =
signed) and might not be the transaction time.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Do we need some sort of clarifying =
language on this?</div><div class=3D""><br class=3D""><div class=3D"">
<div style=3D"letter-spacing: normal; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; word-spacing: 0px; =
word-wrap: break-word;" class=3D""><div style=3D"letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; word-wrap: break-word;" class=3D""><div =
class=3D""><span =
style=3D"border-collapse:separate;line-height:normal;border-spacing:0px" =
class=3D""><div style=3D"word-wrap:break-word" class=3D""><div =
class=3D""><div class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com/" target=3D"_blank" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" =
class=3D"">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D""></div><br class=3D""><br class=3D"">=

</div>
<br class=3D""></div></div><br =
class=3D"">______________________________<wbr =
class=3D"">_________________<br class=3D"">
Id-event mailing list<br class=3D"">
<a href=3D"mailto:Id-event@ietf.org" class=3D"">Id-event@ietf.org</a><br =
class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/<wbr =
class=3D"">listinfo/id-event</a><br class=3D"">
<br class=3D""></blockquote></div><br class=3D""></div>
_______________________________________________<br class=3D"">Id-event =
mailing list<br class=3D""><a href=3D"mailto:Id-event@ietf.org" =
class=3D"">Id-event@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event<br =
class=3D""></div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_9526922D-6BCE-4B95-8562-2030BA4C525D--


From nobody Tue Sep 13 22:08:43 2016
Return-Path: <vivek_biswas@yahoo.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB62212B197 for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 22:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.227
X-Spam-Level: 
X-Spam-Status: No, score=-4.227 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nG9snaJQ5T6I for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 22:08:40 -0700 (PDT)
Received: from nm27-vm5.bullet.mail.ne1.yahoo.com (nm27-vm5.bullet.mail.ne1.yahoo.com [98.138.91.249]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0633A12B54A for <id-event@ietf.org>; Tue, 13 Sep 2016 22:08:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1473829719; bh=Jhy6UN2qRE3cna4Rk93RNrwFPbepy47vONiR0RbMr6Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=bBdFIEAQ97S10etCsCK5YnTG9426TECfFGgfzmqYLE0Rc65B1BuoQeHtzpHZIaA1AceeY4cSN5MqeFrGI8/WJ12YiYYPpFRtwRdKQrQnH1RE8+V4F6co7/m9PKXn0T6NfchFPj3WpoaL0SaUaoxP1sGUbDRcWAdDZ8+XyjZ2bP3A8+nAcgXA0lqWjSrUPQf0YLCZRdqj1v0sf8KRIBM3t5kx206BNdnuZ9cvhRQihpmEj/wD9aAdTQBV1MKdoKLch1/VCBkSwEMoKawbmleftaSN3K2v+XtfY9KKll0UyaqLUizl50F9XAVEr1cXbAetq4u61o5yT9TPaiy6Z/zhpw==
Received: from [98.138.101.131] by nm27.bullet.mail.ne1.yahoo.com with NNFMP;  14 Sep 2016 05:08:39 -0000
Received: from [98.138.87.1] by tm19.bullet.mail.ne1.yahoo.com with NNFMP; 14 Sep 2016 05:08:39 -0000
Received: from [127.0.0.1] by omp1001.mail.ne1.yahoo.com with NNFMP; 14 Sep 2016 05:08:39 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 342209.56355.bm@omp1001.mail.ne1.yahoo.com
X-YMail-OSG: mIEYvdgVM1k_Oo.vvE_idoU5q43ScXNO__6Klnu_fHerm94UGcixII5nS8TuvKP SLnk9DOrl_YxMvMb6dbQZtoVdguiQEz675BSR0iCrWeKpGuVGloMM9I0G6pfy0o1zc_md_DX8PAr NzleFj8_7HlXvCtKw66XuQxIVQjBFEWkRY1uof6VW9t3dbTdd5wbtfpXZSGNsw.PRl5b06PJfFdO m4Xd0H_wyfRKO1tMiy7PTEDTBBK_kHbQDZwKdiUindP.hYhe6OsuIjeCwRSUaHNEPoI8Oa2R1X_X qM0pSpqLyknaCxjwT.8JC85q0t2rFfKDBGnTyBdVTdTtweTo..a0OLvnjQYesF8p7KE8xJk_ftQ9 ENX1jUlhL2vuj05Xy6Y.Nugd1F4BahqEVIZhB4x0ZOH5uqcAyncWciWN0diQX_CPdef9UpVolAim lFwhLusvN8VCH92h1I4tVQ3VUGzhr272Mo2RRudIOqk6rpsZjXKvJypPHJZMd8UYaNQxU8OKGYDU nh2XyykTLMkKnhPR.RsLpG_dIKQ--
Received: from jws100255.mail.ne1.yahoo.com by sendmailws156.mail.ne1.yahoo.com; Wed, 14 Sep 2016 05:08:38 +0000; 1473829718.956
Date: Wed, 14 Sep 2016 05:06:06 +0000 (UTC)
From: Vivek Biswas <vivek_biswas@yahoo.com>
To: Phil Hunt <phil.hunt@oracle.com>,  Chuck Mortimore <cmortimore@salesforce.com>
Message-ID: <196747489.819946.1473829566915@mail.yahoo.com>
In-Reply-To: <26940C91-F9B9-46CD-9F80-BF53606ADF48@oracle.com>
References: <2EC6A66C-1219-4B40-9B95-FD557794C069@oracle.com> <CA+wnMn-_TdC9GcCPYyd98Qhd8cwSAOSpxgU93KdKathEk7pzGA@mail.gmail.com> <26940C91-F9B9-46CD-9F80-BF53606ADF48@oracle.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_819945_1469282543.1473829566907"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/ubfacBVAD-moBSHV84MNC5hsWdU>
Cc: "id-event@ietf.org" <id-event@ietf.org>
Subject: Re: [Id-event] Ordering of SET events
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Vivek Biswas <vivek_biswas@yahoo.com>
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2016 05:08:43 -0000

------=_Part_819945_1469282543.1473829566907
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The timestamps can be further more problematic if the order of events are a=
synchronous.Its best to let the implementer implement the logic of ordering=
 the events, if it is desired.Hence, the order of event field can be option=
al.-Vivek Biswas=C2=A0Consulting Member @Security=C2=A0Oracle=20
      From: Phil Hunt <phil.hunt@oracle.com>
 To: Chuck Mortimore <cmortimore@salesforce.com>=20
Cc: id-event@ietf.org
 Sent: Tuesday, September 13, 2016 9:57 PM
 Subject: Re: [Id-event] Ordering of SET events
  =20
I tend to agree. Timestamps are problematic. Yet they can be individually a=
sserted (skew issues aside). =C2=A0There may =C2=A0also be different transa=
ction time vs. SET issued at times. =C2=A0If for performance reasons the fe=
ed publisher runs on a separate thread or even a separate server, than tran=
saction time vs. iat may be substantially different. (e.g. 10 mins).
Regarding Marius=E2=80=99s question, the use case probably is important to =
SCIM Event cases. =C2=A0Subscribers need to be able to track what order eve=
nts occurred in. =C2=A0For example user x was created and then user x was m=
odified. =C2=A0If those come out of sequence it could cause different concl=
usions by the subscriber.
On the other hand, OIDC Logout doesn=E2=80=99t care about ordering at all. =
It is just saying a single thing is revoked.
I think it is in issue we should mention, but leave it to profiling specs t=
o solve. For example, the SCIM WG will have to either agree to use the orde=
r events are received or come up with some other mechanism. =C2=A0
Failing a specific attribute that gives and order, the only other method I =
can think of is for the client to assume that the order of receipt of an ev=
ent may be interpreted as significant. =C2=A0However I=E2=80=99m not convin=
ced this is true in many cases.=C2=A0
Phil
@independentidwww.independentid.comphil.hunt@oracle.com





On Sep 13, 2016, at 7:23 PM, Chuck Mortimore <cmortimore@salesforce.com> wr=
ote:
>From a protocol perspective, I don't believe it's reasonable to use iat for=
 ordering purposes.=C2=A0 Either the use-cases demand ordered deliver, in w=
hich case you account for it in protocol and architecture, or they don't. =
=C2=A0 Trying to approximate it via timestamps isn't the right solution.
On Tue, Sep 13, 2016 at 2:56 PM, Phil Hunt <phil.hunt@oracle.com> wrote:

I think we may need to ensure we have the correct language on how subscribe=
rs can order events. Can they strictly depend on the order by which they ar=
e received, or can they use =E2=80=9Ciat=E2=80=9D?
The issue is that when SETs are published they may be published by highly d=
istributed systems were it is unreasonable to co-ordinate a sequence number=
 in many cases.=C2=A0 This basically leads us to using timestamps.
Would it be reasonable to use =E2=80=9Ciat=E2=80=9D for this purpose?=C2=A0=
 Keep in mind, we have discussed that =E2=80=9Ciat=E2=80=9D corresponds to =
the time of the SET being generated (and optionally signed) and might not b=
e the transaction time.
Do we need some sort of clarifying language on this?
Phil
@independentidwww.independentid.comphil.hunt@oracle.com





______________________________ _________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/ listinfo/id-event



_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event



_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event


  =20
------=_Part_819945_1469282543.1473829566907
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:verdana, helvetica, sans-serif;font-size:16px"><div><span></span=
></div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_1473829358789_3=
673">The timestamps can be further more problematic if the order of events =
are asynchronous.</div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1=
_1473829358789_3737" dir=3D"ltr">Its best to let the implementer implement =
the logic of ordering the events, if it is desired.</div><div class=3D"qtdS=
eparateBR" id=3D"yui_3_16_0_ym19_1_1473829358789_3800" dir=3D"ltr">Hence, t=
he order of event field can be optional.</div><div class=3D"qtdSeparateBR" =
id=3D"yui_3_16_0_ym19_1_1473829358789_3853" dir=3D"ltr"></div><div class=3D=
"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_1473829358789_3854" dir=3D"ltr">-Vi=
vek Biswas</div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_147382=
9358789_3855" dir=3D"ltr">&nbsp;Consulting Member @Security</div><div class=
=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_1473829358789_3860" dir=3D"ltr">=
&nbsp;Oracle </div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_147=
3829358789_3861" dir=3D"ltr"></div><div class=3D"qtdSeparateBR" id=3D"yui_3=
_16_0_ym19_1_1473829358789_3801" dir=3D"ltr"></div><div class=3D"qtdSeparat=
eBR" id=3D"yui_3_16_0_ym19_1_1473829358789_3802" dir=3D"ltr"></div><div cla=
ss=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_1473829358789_3738" dir=3D"ltr=
"><br></div><div class=3D"yahoo_quoted" id=3D"yui_3_16_0_ym19_1_14738293587=
89_3572" style=3D"display: block;">  <div id=3D"yui_3_16_0_ym19_1_147382935=
8789_3571" style=3D"font-family: verdana, helvetica, sans-serif; font-size:=
 16px;"> <div id=3D"yui_3_16_0_ym19_1_1473829358789_3570" style=3D"font-fam=
ily: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-s=
erif; font-size: 16px;"> <div id=3D"yui_3_16_0_ym19_1_1473829358789_3569" d=
ir=3D"ltr"> <font id=3D"yui_3_16_0_ym19_1_1473829358789_3568" face=3D"Arial=
" size=3D"2"> <hr size=3D"1" id=3D"yui_3_16_0_ym19_1_1473829358789_3683"> <=
b id=3D"yui_3_16_0_ym19_1_1473829358789_3567"><span id=3D"yui_3_16_0_ym19_1=
_1473829358789_3566" style=3D"font-weight:bold;">From:</span></b> Phil Hunt=
 &lt;phil.hunt@oracle.com&gt;<br> <b><span style=3D"font-weight: bold;">To:=
</span></b> Chuck Mortimore &lt;cmortimore@salesforce.com&gt; <br><b><span =
style=3D"font-weight: bold;">Cc:</span></b> id-event@ietf.org<br> <b id=3D"=
yui_3_16_0_ym19_1_1473829358789_3590"><span id=3D"yui_3_16_0_ym19_1_1473829=
358789_3589" style=3D"font-weight: bold;">Sent:</span></b> Tuesday, Septemb=
er 13, 2016 9:57 PM<br> <b><span style=3D"font-weight: bold;">Subject:</spa=
n></b> Re: [Id-event] Ordering of SET events<br> </font> </div> <div class=
=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1473829358789_3684"><br><div i=
d=3D"yiv4424222023"><div id=3D"yui_3_16_0_ym19_1_1473829358789_3714">I tend=
 to agree. Timestamps are problematic. Yet they can be individually asserte=
d (skew issues aside). &nbsp;There may &nbsp;also be different transaction =
time vs. SET issued at times. &nbsp;If for performance reasons the feed pub=
lisher runs on a separate thread or even a separate server, than transactio=
n time vs. iat may be substantially different. (e.g. 10 mins).<div class=3D=
"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"none"></div><div class=
=3D"yiv4424222023">Regarding Marius=E2=80=99s question, the use case probab=
ly is important to SCIM Event cases. &nbsp;Subscribers need to be able to t=
rack what order events occurred in. &nbsp;For example user x was created an=
d then user x was modified. &nbsp;If those come out of sequence it could ca=
use different conclusions by the subscriber.</div><div class=3D"yiv44242220=
23"><br class=3D"yiv4424222023" clear=3D"none"></div><div class=3D"yiv44242=
22023">On the other hand, OIDC Logout doesn=E2=80=99t care about ordering a=
t all. It is just saying a single thing is revoked.</div><div class=3D"yiv4=
424222023"><br class=3D"yiv4424222023" clear=3D"none"></div><div class=3D"y=
iv4424222023">I think it is in issue we should mention, but leave it to pro=
filing specs to solve. For example, the SCIM WG will have to either agree t=
o use the order events are received or come up with some other mechanism. &=
nbsp;</div><div class=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=
=3D"none"></div><div class=3D"yiv4424222023">Failing a specific attribute t=
hat gives and order, the only other method I can think of is for the client=
 to assume that the order of receipt of an event may be interpreted as sign=
ificant. &nbsp;However I=E2=80=99m not convinced this is true in many cases=
.&nbsp;</div><div class=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=
=3D"none"></div><div class=3D"yiv4424222023"><div class=3D"yiv4424222023">
<div class=3D"yiv4424222023" style=3D"color:rgb(0, 0, 0);letter-spacing:nor=
mal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px=
;word-wrap:break-word;"><div class=3D"yiv4424222023" style=3D"color:rgb(0, =
0, 0);letter-spacing:normal;text-indent:0px;text-transform:none;white-space=
:normal;word-spacing:0px;word-wrap:break-word;"><div class=3D"yiv4424222023=
"><span class=3D"yiv4424222023Apple-style-span" style=3D"border-collapse:se=
parate;line-height:normal;border-spacing:0px;"></span><div class=3D"yiv4424=
222023" style=3D"word-wrap:break-word;"><div class=3D"yiv4424222023"><div c=
lass=3D"yiv4424222023"><div class=3D"yiv4424222023">Phil</div><div class=3D=
"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"none"></div><div class=
=3D"yiv4424222023">@independentid</div><div class=3D"yiv4424222023"><a clas=
s=3D"yiv4424222023" href=3D"http://www.independentid.com/" target=3D"_blank=
" rel=3D"nofollow" shape=3D"rect">www.independentid.com</a></div></div></di=
v></div><a class=3D"yiv4424222023" style=3D"orphans:2;widows:2;" href=3D"ma=
ilto:phil.hunt@oracle.com" target=3D"_blank" rel=3D"nofollow" shape=3D"rect=
" ymailto=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.com</a></div><di=
v class=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"none"></div>=
</div><br class=3D"yiv4424222023Apple-interchange-newline" clear=3D"none"><=
/div><br class=3D"yiv4424222023Apple-interchange-newline" clear=3D"none"><b=
r class=3D"yiv4424222023Apple-interchange-newline" clear=3D"none">
</div>
<br class=3D"yiv4424222023" clear=3D"none"><div><blockquote class=3D"yiv442=
4222023" type=3D"cite"><div class=3D"yiv4424222023yqt1252740025" id=3D"yiv4=
424222023yqtfd02643"><div class=3D"yiv4424222023">On Sep 13, 2016, at 7:23 =
PM, Chuck Mortimore &lt;<a class=3D"yiv4424222023" href=3D"mailto:cmortimor=
e@salesforce.com" target=3D"_blank" rel=3D"nofollow" shape=3D"rect" ymailto=
=3D"mailto:cmortimore@salesforce.com">cmortimore@salesforce.com</a>&gt; wro=
te:</div><br class=3D"yiv4424222023Apple-interchange-newline" clear=3D"none=
"><div class=3D"yiv4424222023"><div class=3D"yiv4424222023" dir=3D"ltr">Fro=
m a protocol perspective, I don't believe it's reasonable to use iat for or=
dering purposes.&nbsp; Either the use-cases demand ordered deliver, in whic=
h case you account for it in protocol and architecture, or they don't. &nbs=
p; Trying to approximate it via timestamps isn't the right solution.</div><=
div class=3D"yiv4424222023gmail_extra"><br class=3D"yiv4424222023" clear=3D=
"none"><div class=3D"yiv4424222023gmail_quote">On Tue, Sep 13, 2016 at 2:56=
 PM, Phil Hunt <span class=3D"yiv4424222023" dir=3D"ltr">&lt;<a class=3D"yi=
v4424222023" href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" rel=3D"=
nofollow" shape=3D"rect" ymailto=3D"mailto:phil.hunt@oracle.com">phil.hunt@=
oracle.com</a>&gt;</span> wrote:<br class=3D"yiv4424222023" clear=3D"none">=
<blockquote class=3D"yiv4424222023gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex;"><div class=3D"yiv4424222023" s=
tyle=3D"word-wrap:break-word;">I think we may need to ensure we have the co=
rrect language on how subscribers can order events. Can they strictly depen=
d on the order by which they are received, or can they use =E2=80=9Ciat=E2=
=80=9D?<div class=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"no=
ne"></div><div class=3D"yiv4424222023">The issue is that when SETs are publ=
ished they may be published by highly distributed systems were it is unreas=
onable to co-ordinate a sequence number in many cases.&nbsp; This basically=
 leads us to using timestamps.</div><div class=3D"yiv4424222023"><br class=
=3D"yiv4424222023" clear=3D"none"></div><div class=3D"yiv4424222023">Would =
it be reasonable to use =E2=80=9Ciat=E2=80=9D for this purpose?&nbsp; Keep =
in mind, we have discussed that =E2=80=9Ciat=E2=80=9D corresponds to the ti=
me of the SET being generated (and optionally signed) and might not be the =
transaction time.</div><div class=3D"yiv4424222023"><br class=3D"yiv4424222=
023" clear=3D"none"></div><div class=3D"yiv4424222023">Do we need some sort=
 of clarifying language on this?</div><div class=3D"yiv4424222023"><br clas=
s=3D"yiv4424222023" clear=3D"none"><div class=3D"yiv4424222023">
<div class=3D"yiv4424222023" style=3D"letter-spacing:normal;text-indent:0px=
;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-wo=
rd;"><div class=3D"yiv4424222023" style=3D"letter-spacing:normal;text-inden=
t:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:bre=
ak-word;"><div class=3D"yiv4424222023"><span class=3D"yiv4424222023" style=
=3D"border-collapse:separate;line-height:normal;border-spacing:0px;"></span=
><div class=3D"yiv4424222023" style=3D"word-wrap:break-word;"><div class=3D=
"yiv4424222023"><div class=3D"yiv4424222023"><div class=3D"yiv4424222023">P=
hil</div><div class=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"=
none"></div><div class=3D"yiv4424222023">@independentid</div><div class=3D"=
yiv4424222023"><a class=3D"yiv4424222023" href=3D"http://www.independentid.=
com/" target=3D"_blank" rel=3D"nofollow" shape=3D"rect">www.independentid.c=
om</a></div></div></div></div><a class=3D"yiv4424222023" href=3D"mailto:phi=
l.hunt@oracle.com" target=3D"_blank" rel=3D"nofollow" shape=3D"rect" ymailt=
o=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.com</a></div><div class=
=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"none"></div></div><=
br class=3D"yiv4424222023" clear=3D"none"></div><br class=3D"yiv4424222023"=
 clear=3D"none"><br class=3D"yiv4424222023" clear=3D"none">
</div>
<br class=3D"yiv4424222023" clear=3D"none"></div></div><br class=3D"yiv4424=
222023" clear=3D"none">______________________________ _________________<br =
class=3D"yiv4424222023" clear=3D"none">
Id-event mailing list<br class=3D"yiv4424222023" clear=3D"none">
<a class=3D"yiv4424222023" href=3D"mailto:Id-event@ietf.org" target=3D"_bla=
nk" rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Id-event@ietf.org">Id=
-event@ietf.org</a><br class=3D"yiv4424222023" clear=3D"none">
<a class=3D"yiv4424222023" href=3D"https://www.ietf.org/mailman/listinfo/id=
-event" target=3D"_blank" rel=3D"nofollow" shape=3D"rect">https://www.ietf.=
org/mailman/ listinfo/id-event</a><br class=3D"yiv4424222023" clear=3D"none=
">
<br class=3D"yiv4424222023" clear=3D"none"></blockquote></div><br class=3D"=
yiv4424222023" clear=3D"none"></div>
_______________________________________________<br class=3D"yiv4424222023" =
clear=3D"none">Id-event mailing list<br class=3D"yiv4424222023" clear=3D"no=
ne"><a class=3D"yiv4424222023" href=3D"mailto:Id-event@ietf.org" target=3D"=
_blank" rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Id-event@ietf.org=
">Id-event@ietf.org</a><br class=3D"yiv4424222023" clear=3D"none">https://w=
ww.ietf.org/mailman/listinfo/id-event<br class=3D"yiv4424222023" clear=3D"n=
one"></div></div></blockquote></div><div class=3D"yiv4424222023yqt125274002=
5" id=3D"yiv4424222023yqtfd57864"><br class=3D"yiv4424222023" clear=3D"none=
"></div></div></div></div><br><div class=3D"yqt1252740025" id=3D"yqtfd00547=
">_______________________________________________<br clear=3D"none">Id-even=
t mailing list<br clear=3D"none"><a href=3D"mailto:Id-event@ietf.org" shape=
=3D"rect" ymailto=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br cle=
ar=3D"none"><a href=3D"https://www.ietf.org/mailman/listinfo/id-event" targ=
et=3D"_blank" shape=3D"rect">https://www.ietf.org/mailman/listinfo/id-event=
</a><br clear=3D"none"></div><br><br></div> </div> </div>  </div></div></bo=
dy></html>
------=_Part_819945_1469282543.1473829566907--


From nobody Tue Sep 13 22:21:58 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDAED12B54F for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 22:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level: 
X-Spam-Status: No, score=-5.727 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ArtksaUJbrru for <id-event@ietfa.amsl.com>; Tue, 13 Sep 2016 22:21:54 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7804812B1D9 for <id-event@ietf.org>; Tue, 13 Sep 2016 22:21:54 -0700 (PDT)
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8E5Lro5031283 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2016 05:21:53 GMT
Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u8E5LqNV031980 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2016 05:21:53 GMT
Received: from abhmp0008.oracle.com (abhmp0008.oracle.com [141.146.116.14]) by userv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u8E5LoLO029691; Wed, 14 Sep 2016 05:21:52 GMT
Received: from [172.20.2.239] (/40.139.251.125) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 13 Sep 2016 22:21:50 -0700
Content-Type: multipart/alternative; boundary=Apple-Mail-25051884-D439-4268-9927-1D495ACBBC59
Mime-Version: 1.0 (1.0)
From: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
X-Mailer: iPhone Mail (13G36)
In-Reply-To: <196747489.819946.1473829566915@mail.yahoo.com>
Date: Tue, 13 Sep 2016 22:21:48 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <737F9477-7B62-4AF8-96AE-6EA4BA047742@oracle.com>
References: <2EC6A66C-1219-4B40-9B95-FD557794C069@oracle.com> <CA+wnMn-_TdC9GcCPYyd98Qhd8cwSAOSpxgU93KdKathEk7pzGA@mail.gmail.com> <26940C91-F9B9-46CD-9F80-BF53606ADF48@oracle.com> <196747489.819946.1473829566915@mail.yahoo.com>
To: Vivek Biswas <vivek_biswas@yahoo.com>
X-Source-IP: aserv0021.oracle.com [141.146.126.233]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/TDULcMCuhRxkYyuK4sA1dFmFsNs>
Cc: "id-event@ietf.org" <id-event@ietf.org>, Chuck Mortimore <cmortimore@salesforce.com>
Subject: Re: [Id-event] Ordering of SET events
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2016 05:21:57 -0000

--Apple-Mail-25051884-D439-4268-9927-1D495ACBBC59
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

+1=20

Other ideas? =20

Phil

> On Sep 13, 2016, at 10:06 PM, Vivek Biswas <vivek_biswas@yahoo.com> wrote:=

>=20
> The timestamps can be further more problematic if the order of events are a=
synchronous.
> Its best to let the implementer implement the logic of ordering the events=
, if it is desired.
> Hence, the order of event field can be optional.
> -Vivek Biswas
>  Consulting Member @Security
>  Oracle
>=20
> From: Phil Hunt <phil.hunt@oracle.com>
> To: Chuck Mortimore <cmortimore@salesforce.com>=20
> Cc: id-event@ietf.org
> Sent: Tuesday, September 13, 2016 9:57 PM
> Subject: Re: [Id-event] Ordering of SET events
>=20
> I tend to agree. Timestamps are problematic. Yet they can be individually a=
sserted (skew issues aside).  There may  also be different transaction time v=
s. SET issued at times.  If for performance reasons the feed publisher runs o=
n a separate thread or even a separate server, than transaction time vs. iat=
 may be substantially different. (e.g. 10 mins).
>=20
> Regarding Marius=E2=80=99s question, the use case probably is important to=
 SCIM Event cases.  Subscribers need to be able to track what order events o=
ccurred in.  For example user x was created and then user x was modified.  I=
f those come out of sequence it could cause different conclusions by the sub=
scriber.
>=20
> On the other hand, OIDC Logout doesn=E2=80=99t care about ordering at all.=
 It is just saying a single thing is revoked.
>=20
> I think it is in issue we should mention, but leave it to profiling specs t=
o solve. For example, the SCIM WG will have to either agree to use the order=
 events are received or come up with some other mechanism. =20
>=20
> Failing a specific attribute that gives and order, the only other method I=
 can think of is for the client to assume that the order of receipt of an ev=
ent may be interpreted as significant.  However I=E2=80=99m not convinced th=
is is true in many cases.=20
>=20
> Phil
>=20
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
>=20
>=20
>=20
>=20
>=20
>> On Sep 13, 2016, at 7:23 PM, Chuck Mortimore <cmortimore@salesforce.com> w=
rote:
>>=20
>> =46rom a protocol perspective, I don't believe it's reasonable to use iat=
 for ordering purposes.  Either the use-cases demand ordered deliver, in whi=
ch case you account for it in protocol and architecture, or they don't.   Tr=
ying to approximate it via timestamps isn't the right solution.
>>=20
>> On Tue, Sep 13, 2016 at 2:56 PM, Phil Hunt <phil.hunt@oracle.com> wrote:
>> I think we may need to ensure we have the correct language on how subscri=
bers can order events. Can they strictly depend on the order by which they a=
re received, or can they use =E2=80=9Ciat=E2=80=9D?
>>=20
>> The issue is that when SETs are published they may be published by highly=
 distributed systems were it is unreasonable to co-ordinate a sequence numbe=
r in many cases.  This basically leads us to using timestamps.
>>=20
>> Would it be reasonable to use =E2=80=9Ciat=E2=80=9D for this purpose?  Ke=
ep in mind, we have discussed that =E2=80=9Ciat=E2=80=9D corresponds to the t=
ime of the SET being generated (and optionally signed) and might not be the t=
ransaction time.
>>=20
>> Do we need some sort of clarifying language on this?
>>=20
>> Phil
>>=20
>> @independentid
>> www.independentid.com
>> phil.hunt@oracle.com
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> ______________________________ _________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/ listinfo/id-event
>>=20
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>=20
>=20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>=20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event

--Apple-Mail-25051884-D439-4268-9927-1D495ACBBC59
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>+1&nbsp;</div><div id=3D"AppleMailSign=
ature"><br></div><div id=3D"AppleMailSignature">Other ideas? &nbsp;<br><br>P=
hil</div><div><br>On Sep 13, 2016, at 10:06 PM, Vivek Biswas &lt;<a href=3D"=
mailto:vivek_biswas@yahoo.com">vivek_biswas@yahoo.com</a>&gt; wrote:<br><br>=
</div><blockquote type=3D"cite"><div><div style=3D"color:#000; background-co=
lor:#fff; font-family:verdana, helvetica, sans-serif;font-size:16px"><div><s=
pan></span></div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_147382=
9358789_3673">The timestamps can be further more problematic if the order of=
 events are asynchronous.</div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0=
_ym19_1_1473829358789_3737" dir=3D"ltr">Its best to let the implementer impl=
ement the logic of ordering the events, if it is desired.</div><div class=3D=
"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_1473829358789_3800" dir=3D"ltr">Henc=
e, the order of event field can be optional.</div><div class=3D"qtdSeparateB=
R" id=3D"yui_3_16_0_ym19_1_1473829358789_3853" dir=3D"ltr"></div><div class=3D=
"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_1473829358789_3854" dir=3D"ltr">-Viv=
ek Biswas</div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_14738293=
58789_3855" dir=3D"ltr">&nbsp;Consulting Member @Security</div><div class=3D=
"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_1473829358789_3860" dir=3D"ltr">&nbs=
p;Oracle </div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_1_14738293=
58789_3861" dir=3D"ltr"></div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_=
ym19_1_1473829358789_3801" dir=3D"ltr"></div><div class=3D"qtdSeparateBR" id=
=3D"yui_3_16_0_ym19_1_1473829358789_3802" dir=3D"ltr"></div><div class=3D"qt=
dSeparateBR" id=3D"yui_3_16_0_ym19_1_1473829358789_3738" dir=3D"ltr"><br></d=
iv><div class=3D"yahoo_quoted" id=3D"yui_3_16_0_ym19_1_1473829358789_3572" s=
tyle=3D"display: block;">  <div id=3D"yui_3_16_0_ym19_1_1473829358789_3571" s=
tyle=3D"font-family: verdana, helvetica, sans-serif; font-size: 16px;"> <div=
 id=3D"yui_3_16_0_ym19_1_1473829358789_3570" style=3D"font-family: Helvetica=
Neue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size=
: 16px;"> <div id=3D"yui_3_16_0_ym19_1_1473829358789_3569" dir=3D"ltr"> <fon=
t id=3D"yui_3_16_0_ym19_1_1473829358789_3568" face=3D"Arial" size=3D"2"> <hr=
 size=3D"1" id=3D"yui_3_16_0_ym19_1_1473829358789_3683"> <b id=3D"yui_3_16_0=
_ym19_1_1473829358789_3567"><span id=3D"yui_3_16_0_ym19_1_1473829358789_3566=
" style=3D"font-weight:bold;">From:</span></b> Phil Hunt &lt;<a href=3D"mail=
to:phil.hunt@oracle.com">phil.hunt@oracle.com</a>&gt;<br> <b><span style=3D"=
font-weight: bold;">To:</span></b> Chuck Mortimore &lt;<a href=3D"mailto:cmo=
rtimore@salesforce.com">cmortimore@salesforce.com</a>&gt; <br><b><span style=
=3D"font-weight: bold;">Cc:</span></b> <a href=3D"mailto:id-event@ietf.org">=
id-event@ietf.org</a><br> <b id=3D"yui_3_16_0_ym19_1_1473829358789_3590"><sp=
an id=3D"yui_3_16_0_ym19_1_1473829358789_3589" style=3D"font-weight: bold;">=
Sent:</span></b> Tuesday, September 13, 2016 9:57 PM<br> <b><span style=3D"f=
ont-weight: bold;">Subject:</span></b> Re: [Id-event] Ordering of SET events=
<br> </font> </div> <div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1=
473829358789_3684"><br><div id=3D"yiv4424222023"><div id=3D"yui_3_16_0_ym19_=
1_1473829358789_3714">I tend to agree. Timestamps are problematic. Yet they c=
an be individually asserted (skew issues aside). &nbsp;There may &nbsp;also b=
e different transaction time vs. SET issued at times. &nbsp;If for performan=
ce reasons the feed publisher runs on a separate thread or even a separate s=
erver, than transaction time vs. iat may be substantially different. (e.g. 1=
0 mins).<div class=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"no=
ne"></div><div class=3D"yiv4424222023">Regarding Marius=E2=80=99s question, t=
he use case probably is important to SCIM Event cases. &nbsp;Subscribers nee=
d to be able to track what order events occurred in. &nbsp;For example user x=
 was created and then user x was modified. &nbsp;If those come out of sequen=
ce it could cause different conclusions by the subscriber.</div><div class=3D=
"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"none"></div><div class=3D=
"yiv4424222023">On the other hand, OIDC Logout doesn=E2=80=99t care about or=
dering at all. It is just saying a single thing is revoked.</div><div class=3D=
"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"none"></div><div class=3D=
"yiv4424222023">I think it is in issue we should mention, but leave it to pr=
ofiling specs to solve. For example, the SCIM WG will have to either agree t=
o use the order events are received or come up with some other mechanism. &n=
bsp;</div><div class=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"=
none"></div><div class=3D"yiv4424222023">Failing a specific attribute that g=
ives and order, the only other method I can think of is for the client to as=
sume that the order of receipt of an event may be interpreted as significant=
. &nbsp;However I=E2=80=99m not convinced this is true in many cases.&nbsp;<=
/div><div class=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"none"=
></div><div class=3D"yiv4424222023"><div class=3D"yiv4424222023">
<div class=3D"yiv4424222023" style=3D"color:rgb(0, 0, 0);letter-spacing:norm=
al;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;w=
ord-wrap:break-word;"><div class=3D"yiv4424222023" style=3D"color:rgb(0, 0, 0=
);letter-spacing:normal;text-indent:0px;text-transform:none;white-space:norm=
al;word-spacing:0px;word-wrap:break-word;"><div class=3D"yiv4424222023"><spa=
n class=3D"yiv4424222023Apple-style-span" style=3D"border-collapse:separate;=
line-height:normal;border-spacing:0px;"></span><div class=3D"yiv4424222023" s=
tyle=3D"word-wrap:break-word;"><div class=3D"yiv4424222023"><div class=3D"yi=
v4424222023"><div class=3D"yiv4424222023">Phil</div><div class=3D"yiv4424222=
023"><br class=3D"yiv4424222023" clear=3D"none"></div><div class=3D"yiv44242=
22023">@independentid</div><div class=3D"yiv4424222023"><a class=3D"yiv44242=
22023" href=3D"http://www.independentid.com/" target=3D"_blank" rel=3D"nofol=
low" shape=3D"rect">www.independentid.com</a></div></div></div></div><a clas=
s=3D"yiv4424222023" style=3D"orphans:2;widows:2;" href=3D"mailto:phil.hunt@o=
racle.com" target=3D"_blank" rel=3D"nofollow" shape=3D"rect" ymailto=3D"mail=
to:phil.hunt@oracle.com">phil.hunt@oracle.com</a></div><div class=3D"yiv4424=
222023"><br class=3D"yiv4424222023" clear=3D"none"></div></div><br class=3D"=
yiv4424222023Apple-interchange-newline" clear=3D"none"></div><br class=3D"yi=
v4424222023Apple-interchange-newline" clear=3D"none"><br class=3D"yiv4424222=
023Apple-interchange-newline" clear=3D"none">
</div>
<br class=3D"yiv4424222023" clear=3D"none"><div><blockquote class=3D"yiv4424=
222023" type=3D"cite"><div class=3D"yiv4424222023yqt1252740025" id=3D"yiv442=
4222023yqtfd02643"><div class=3D"yiv4424222023">On Sep 13, 2016, at 7:23 PM,=
 Chuck Mortimore &lt;<a class=3D"yiv4424222023" href=3D"mailto:cmortimore@sa=
lesforce.com" target=3D"_blank" rel=3D"nofollow" shape=3D"rect" ymailto=3D"m=
ailto:cmortimore@salesforce.com">cmortimore@salesforce.com</a>&gt; wrote:</d=
iv><br class=3D"yiv4424222023Apple-interchange-newline" clear=3D"none"><div c=
lass=3D"yiv4424222023"><div class=3D"yiv4424222023" dir=3D"ltr">=46rom a pro=
tocol perspective, I don't believe it's reasonable to use iat for ordering p=
urposes.&nbsp; Either the use-cases demand ordered deliver, in which case yo=
u account for it in protocol and architecture, or they don't. &nbsp; Trying t=
o approximate it via timestamps isn't the right solution.</div><div class=3D=
"yiv4424222023gmail_extra"><br class=3D"yiv4424222023" clear=3D"none"><div c=
lass=3D"yiv4424222023gmail_quote">On Tue, Sep 13, 2016 at 2:56 PM, Phil Hunt=
 <span class=3D"yiv4424222023" dir=3D"ltr">&lt;<a class=3D"yiv4424222023" hr=
ef=3D"mailto:phil.hunt@oracle.com" target=3D"_blank" rel=3D"nofollow" shape=3D=
"rect" ymailto=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.com</a>&gt;<=
/span> wrote:<br class=3D"yiv4424222023" clear=3D"none"><blockquote class=3D=
"yiv4424222023gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex;"><div class=3D"yiv4424222023" style=3D"word-wrap:brea=
k-word;">I think we may need to ensure we have the correct language on how s=
ubscribers can order events. Can they strictly depend on the order by which t=
hey are received, or can they use =E2=80=9Ciat=E2=80=9D?<div class=3D"yiv442=
4222023"><br class=3D"yiv4424222023" clear=3D"none"></div><div class=3D"yiv4=
424222023">The issue is that when SETs are published they may be published b=
y highly distributed systems were it is unreasonable to co-ordinate a sequen=
ce number in many cases.&nbsp; This basically leads us to using timestamps.<=
/div><div class=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"none"=
></div><div class=3D"yiv4424222023">Would it be reasonable to use =E2=80=9Ci=
at=E2=80=9D for this purpose?&nbsp; Keep in mind, we have discussed that =E2=
=80=9Ciat=E2=80=9D corresponds to the time of the SET being generated (and o=
ptionally signed) and might not be the transaction time.</div><div class=3D"=
yiv4424222023"><br class=3D"yiv4424222023" clear=3D"none"></div><div class=3D=
"yiv4424222023">Do we need some sort of clarifying language on this?</div><d=
iv class=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"none"><div c=
lass=3D"yiv4424222023">
<div class=3D"yiv4424222023" style=3D"letter-spacing:normal;text-indent:0px;=
text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word=
;"><div class=3D"yiv4424222023" style=3D"letter-spacing:normal;text-indent:0=
px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-w=
ord;"><div class=3D"yiv4424222023"><span class=3D"yiv4424222023" style=3D"bo=
rder-collapse:separate;line-height:normal;border-spacing:0px;"></span><div c=
lass=3D"yiv4424222023" style=3D"word-wrap:break-word;"><div class=3D"yiv4424=
222023"><div class=3D"yiv4424222023"><div class=3D"yiv4424222023">Phil</div>=
<div class=3D"yiv4424222023"><br class=3D"yiv4424222023" clear=3D"none"></di=
v><div class=3D"yiv4424222023">@independentid</div><div class=3D"yiv44242220=
23"><a class=3D"yiv4424222023" href=3D"http://www.independentid.com/" target=
=3D"_blank" rel=3D"nofollow" shape=3D"rect">www.independentid.com</a></div><=
/div></div></div><a class=3D"yiv4424222023" href=3D"mailto:phil.hunt@oracle.=
com" target=3D"_blank" rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:phi=
l.hunt@oracle.com">phil.hunt@oracle.com</a></div><div class=3D"yiv4424222023=
"><br class=3D"yiv4424222023" clear=3D"none"></div></div><br class=3D"yiv442=
4222023" clear=3D"none"></div><br class=3D"yiv4424222023" clear=3D"none"><br=
 class=3D"yiv4424222023" clear=3D"none">
</div>
<br class=3D"yiv4424222023" clear=3D"none"></div></div><br class=3D"yiv44242=
22023" clear=3D"none">______________________________ _________________<br cl=
ass=3D"yiv4424222023" clear=3D"none">
Id-event mailing list<br class=3D"yiv4424222023" clear=3D"none">
<a class=3D"yiv4424222023" href=3D"mailto:Id-event@ietf.org" target=3D"_blan=
k" rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Id-event@ietf.org">Id-e=
vent@ietf.org</a><br class=3D"yiv4424222023" clear=3D"none">
<a class=3D"yiv4424222023" href=3D"https://www.ietf.org/mailman/listinfo/id-=
event" target=3D"_blank" rel=3D"nofollow" shape=3D"rect">https://www.ietf.or=
g/mailman/ listinfo/id-event</a><br class=3D"yiv4424222023" clear=3D"none">
<br class=3D"yiv4424222023" clear=3D"none"></blockquote></div><br class=3D"y=
iv4424222023" clear=3D"none"></div>
_______________________________________________<br class=3D"yiv4424222023" c=
lear=3D"none">Id-event mailing list<br class=3D"yiv4424222023" clear=3D"none=
"><a class=3D"yiv4424222023" href=3D"mailto:Id-event@ietf.org" target=3D"_bl=
ank" rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:Id-event@ietf.org">Id=
-event@ietf.org</a><br class=3D"yiv4424222023" clear=3D"none"><a href=3D"htt=
ps://www.ietf.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/li=
stinfo/id-event</a><br class=3D"yiv4424222023" clear=3D"none"></div></div></=
blockquote></div><div class=3D"yiv4424222023yqt1252740025" id=3D"yiv44242220=
23yqtfd57864"><br class=3D"yiv4424222023" clear=3D"none"></div></div></div><=
/div><br><div class=3D"yqt1252740025" id=3D"yqtfd00547">____________________=
___________________________<br clear=3D"none">Id-event mailing list<br clear=
=3D"none"><a href=3D"mailto:Id-event@ietf.org" shape=3D"rect" ymailto=3D"mai=
lto:Id-event@ietf.org">Id-event@ietf.org</a><br clear=3D"none"><a href=3D"ht=
tps://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank" shape=3D"rec=
t">https://www.ietf.org/mailman/listinfo/id-event</a><br clear=3D"none"></di=
v><br><br></div> </div> </div>  </div></div></div></blockquote><blockquote t=
ype=3D"cite"><div><span>_______________________________________________</spa=
n><br><span>Id-event mailing list</span><br><span><a href=3D"mailto:Id-event=
@ietf.org">Id-event@ietf.org</a></span><br><span><a href=3D"https://www.ietf=
.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/listinfo/id-eve=
nt</a></span><br></div></blockquote></body></html>=

--Apple-Mail-25051884-D439-4268-9927-1D495ACBBC59--


From nobody Thu Sep 15 15:28:58 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EFC712B075 for <id-event@ietfa.amsl.com>; Thu, 15 Sep 2016 15:28:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.728
X-Spam-Level: 
X-Spam-Status: No, score=-5.728 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fKuFPYhgX1oy for <id-event@ietfa.amsl.com>; Thu, 15 Sep 2016 15:28:55 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B17AA12B04D for <id-event@ietf.org>; Thu, 15 Sep 2016 15:28:55 -0700 (PDT)
Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8FMSsJH012466 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <id-event@ietf.org>; Thu, 15 Sep 2016 22:28:55 GMT
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0022.oracle.com (8.14.4/8.13.8) with ESMTP id u8FMSsEF027867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <id-event@ietf.org>; Thu, 15 Sep 2016 22:28:54 GMT
Received: from abhmp0018.oracle.com (abhmp0018.oracle.com [141.146.116.24]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u8FMSrFu029742 for <id-event@ietf.org>; Thu, 15 Sep 2016 22:28:53 GMT
Received: from [10.0.1.5] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 15 Sep 2016 15:28:53 -0700
From: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DC2D41EF-3592-4AB6-84C7-7F6E33D983B5"
Message-Id: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com>
Date: Thu, 15 Sep 2016 15:28:52 -0700
To: id-event@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-Source-IP: userv0022.oracle.com [156.151.31.74]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/gDOhq1437zt-E3zRCV1XVGm5UTs>
Subject: [Id-event] Proposed text for txn and ordering
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Sep 2016 22:28:57 -0000

--Apple-Mail=_DC2D41EF-3592-4AB6-84C7-7F6E33D983B5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Based on the feedback, I am proposing the following changes:

In the new attributes defined section, a new claim =E2=80=9Ctxn=E2=80=9D =
defined:
   txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.

Regarding Ordering, I am proposing the following section:
2.2.  Idempotency and Ordering Considerations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the "iat" value may give a rough indication of SET order, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are "idempotent" in the sense that the order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.
Thanks for your feedback.

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>






--Apple-Mail=_DC2D41EF-3592-4AB6-84C7-7F6E33D983B5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Based on the feedback, I am proposing the following =
changes:<div class=3D""><br class=3D""></div><div class=3D"">In the new =
attributes defined section, a new claim =E2=80=9Ctxn=E2=80=9D =
defined:</div><div class=3D""><div style=3D"margin: 0px; font-size: =
11px; line-height: normal; font-family: Monaco;" class=3D""><pre =
style=3D"word-wrap: break-word; white-space: pre-wrap;" class=3D"">   =
txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.
</pre><div class=3D""><br class=3D""></div></div><div class=3D"">Regarding=
 Ordering, I am proposing the following section:</div><div class=3D""><pre=
 style=3D"word-wrap: break-word; white-space: pre-wrap;" class=3D""><span =
style=3D"font-size: 11px;" class=3D"">2.2.  Idempotency and Ordering =
Considerations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the "iat" value may give a rough indication of SET order, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are "idempotent" in the sense that the order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.</span></pre></div><div class=3D"">Thanks for =
your feedback.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Phil</div><div class=3D""><div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
line-height: normal; border-spacing: 0px;"><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D""><br class=3D""></div><div =
class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_DC2D41EF-3592-4AB6-84C7-7F6E33D983B5--


From nobody Thu Sep 15 18:33:18 2016
Return-Path: <mscurtescu@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15DF312B0E5 for <id-event@ietfa.amsl.com>; Thu, 15 Sep 2016 18:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level: 
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SaVM110K1KxS for <id-event@ietfa.amsl.com>; Thu, 15 Sep 2016 18:33:13 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAA0312B0D0 for <id-event@ietf.org>; Thu, 15 Sep 2016 18:33:09 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id 1so14262777wmz.1 for <id-event@ietf.org>; Thu, 15 Sep 2016 18:33:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=I6m8ssiKIcGU+lzAsftkFOwvowI01+Pnvnq+94Dk6mw=; b=ReN2YfjdztKeb1rcxwBPtqovPugnWqMlTh+ZBGy5x56S3Jy7fwC0BBseY9QO8BpIaF +8GAykDwYuJ/BWyDTy9yyFmQlAZvGha0THJgQrxmKGuv9zcAs0Y99mjb0Aw45VdtAtKL Kpsh2/uH3+NGGsXtN/B7hi/eobWDNoNh3mRGNJSiQWrogtCH7dYgBfsIBbohNJ6Wwaz3 ryhxsXOn9z5b4eI+HogueQnN2MTqodyyKdC9hw48Nm6dQvcHiQriesdM34UeMXem1leE dAHjDsaz3dyTSMAp64KyHlbo9qMAhnnFAlXfpWQEpJ3BZUy8+2p0YrWuz/PZyHwxyYgr BpHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=I6m8ssiKIcGU+lzAsftkFOwvowI01+Pnvnq+94Dk6mw=; b=LeVa2ek1Xt9CnQtQzO2znCziI8GENeWBAyetcZ77dFTgUamEe0CRnyZ9Be/+sYPOJd yhMKVYZYXMds5qu5CoOQ5adH3gYYACL7ZcfJ//ZeEdKanmBg0pLQn6JaO120C5SpEeMl c+V5qTwbnmJ3nBxgPIfj/jdYIo4UFZJZm4BNFo/tpwQKiQ25Zyuv7rIYOuEZUmV0kyab 6NAXJobkt0U/bTPZ9AEuPRdjzq7YImMjHGbx9Q28tUKygwTeXyQ1SDcf337BavMmxxG1 RaklBQUQEe1ur908+ZNj9csXjp+IcT8kkStEDGWHUtfc+PwzXnY63bSEt9nbGjnSosg8 gzqA==
X-Gm-Message-State: AE9vXwMsg7yyl3U/ya/PGGaiJBb8brW70swmlOG0WXZcqZh+9FtLvQiPqK0S7oJfnu2PRSSkBW2KtXtrsNFvTCim
X-Received: by 10.194.122.137 with SMTP id ls9mr10776651wjb.29.1473989587843;  Thu, 15 Sep 2016 18:33:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.187.136 with HTTP; Thu, 15 Sep 2016 18:32:47 -0700 (PDT)
In-Reply-To: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com>
References: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Thu, 15 Sep 2016 18:32:47 -0700
Message-ID: <CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com>
To: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary=089e01177167c98e99053c95f167
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/2DzwmB6WE73RFGFSAZud99Etjys>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Proposed text for txn and ordering
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Sep 2016 01:33:16 -0000

--089e01177167c98e99053c95f167
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Sounds good to me.

Marius

On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <phil.hunt@oracle.com> wrote:

> Based on the feedback, I am proposing the following changes:
>
> In the new attributes defined section, a new claim =E2=80=9Ctxn=E2=80=9D =
defined:
>
>    txn
>       An OPTIONAL single-valued String value that represents a unique
>       transaction identifier.  In cases where multiple SETs are issued
>       based on different event URIs, the transaction identifier MAY be
>       used to correlate SETs to the same originating event or stateful
>       change.
>
>
> Regarding Ordering, I am proposing the following section:
>
> 2.2.  Idempotency and Ordering Considerations
>
>    In many cases SETs will be issued by highly distributed systems and
>    subscribers.  Without additional specification it is quite
>    conceivable that the order of SETs received by a subscriber MAY be
>    different from the order of the originating state changes or events.
>    While the "iat" value may give a rough indication of SET order, it
>    SHOULD NOT be relied upon unless the profiling SET token
>    specification provides clarification.
>
>    Profiling specifications are encouraged to consider whether the
>    nature of SETs defined are "idempotent" in the sense that the order
>    of receipt does not matter.  For example, in the case of token
>    revocations, each SET can stand on its own and order has no impact.
>    In contrast, a profiling SET specification related to provisioning
>    might be highly dependent on ordering.  As an example: one SET
>    indicates a new resource was created, while the next SET indicates
>    the same resource is modified.  Non-Idempotent SET event
>    specifications SHOULD choose to define a sequencing method such as aa
>    claim used for the purpose or identifying the order of SETs as
>    defined by the Feed Publisher or another method that is part of how
>    SETs are distributed.
>
> Thanks for your feedback.
>
> Phil
>
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
>
>
>
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>

--089e01177167c98e99053c95f167
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Sounds good to me.</div><div class=3D"gmail_extra"><br cle=
ar=3D"all"><div><div class=3D"gmail_signature" data-smartmail=3D"gmail_sign=
ature">Marius</div></div>
<br><div class=3D"gmail_quote">On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <=
span dir=3D"ltr">&lt;<a href=3D"mailto:phil.hunt@oracle.com" target=3D"_bla=
nk">phil.hunt@oracle.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div style=3D"word-wrap:break-word">Based on the feedback, I am propo=
sing the following changes:<div><br></div><div>In the new attributes define=
d section, a new claim =E2=80=9Ctxn=E2=80=9D defined:</div><div><div style=
=3D"margin:0px;font-size:11px;line-height:normal;font-family:Monaco"><pre s=
tyle=3D"word-wrap:break-word;white-space:pre-wrap">   txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.
</pre><div><br></div></div><div>Regarding Ordering, I am proposing the foll=
owing section:</div><div><pre style=3D"word-wrap:break-word;white-space:pre=
-wrap"><span style=3D"font-size:11px">2.2.  Idempotency and Ordering Consid=
erations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the &quot;iat&quot; value may give a rough indication of SET order=
, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are &quot;idempotent&quot; in the sense that the =
order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.</span></pre></div><div>Thanks for your feedback.</=
div><div><br></div><div>Phil</div><div><div style=3D"color:rgb(0,0,0);lette=
r-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white=
-space:normal;word-spacing:0px;word-wrap:break-word"><div style=3D"color:rg=
b(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transf=
orm:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div><sp=
an class=3D"m_-2137582900026257651Apple-style-span" style=3D"border-collaps=
e:separate;line-height:normal;border-spacing:0px"><div style=3D"word-wrap:b=
reak-word"><div><div><div><br></div><div>@independentid</div><div><a href=
=3D"http://www.independentid.com" target=3D"_blank">www.independentid.com</=
a></div></div></div></div></span><a href=3D"mailto:phil.hunt@oracle.com" ta=
rget=3D"_blank">phil.hunt@oracle.com</a></div><div><br></div></div><br clas=
s=3D"m_-2137582900026257651Apple-interchange-newline"></div><br class=3D"m_=
-2137582900026257651Apple-interchange-newline"><br class=3D"m_-213758290002=
6257651Apple-interchange-newline">
</div>
<br></div></div><br>______________________________<wbr>_________________<br=
>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a=
><br>
<br></blockquote></div><br></div>

--089e01177167c98e99053c95f167--


From nobody Fri Sep 16 07:15:38 2016
Return-Path: <nroy@internet2.edu>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD2612B25B for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 07:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.141
X-Spam-Level: 
X-Spam-Status: No, score=-1.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GtkN3QhRJxrP for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 07:15:34 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0092.outbound.protection.outlook.com [104.47.41.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EBC812B246 for <id-event@ietf.org>; Fri, 16 Sep 2016 07:15:34 -0700 (PDT)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=nroy@internet2.edu; 
Received: from htom.local (2601:283:4202:d50:b95b:ab0e:d5c7:6619) by BLUPR0801MB547.namprd08.prod.outlook.com (10.141.252.25) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.619.10; Fri, 16 Sep 2016 14:15:31 +0000
To: <id-event@ietf.org>
References: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com> <CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com>
From: Nicholas Roy <nroy@internet2.edu>
Message-ID: <a42b8067-02f8-a9ba-ea86-d129a0546ed4@internet2.edu>
Date: Fri, 16 Sep 2016 08:15:27 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------D3C4EA6F07EF2DF591E9A312"
X-Originating-IP: [2601:283:4202:d50:b95b:ab0e:d5c7:6619]
X-ClientProxiedBy: BN6PR20CA0008.namprd20.prod.outlook.com (10.173.158.146) To BLUPR0801MB547.namprd08.prod.outlook.com (10.141.252.25)
X-MS-Office365-Filtering-Correlation-Id: d3b02495-ff9e-436d-fb06-08d3de3beb16
X-Microsoft-Exchange-Diagnostics: 1; BLUPR0801MB547; 2:l4JExayZrhOigwCi/Vx6NNFhEvSJsdgCrP6pGQ9WVT5686eFufWNp8KGKLh2I30rr2It9tZVQKZHmBU90YP4TcAxCUTgfLG5yt+U1czvXg+2xoZ5WdONSiz3w7H1x2dJlP2eaJBHmcD83+oF464GjGHGwK9fPcXqI0oLM3FxQw6yFkyB091vlkvxzBrD1b8a; 3:A0kuEBzAMF4Yaeiof5p0kQjofn0VFkKA0AbFqExtze2MbV7vZJ03L8wMF3TSnRanwAdFmyVSHIQXCkHilkkIrnzxGzuiQ47m4OsQqy5eUIHXi5mQey1qGcxv97YrXs4x
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0801MB547;
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BLUPR0801MB547; 25:fXMX7OnlT/naEDDtr7kjzZJ7sZdn5dpOwO8pczRg?= =?us-ascii?Q?/UXg0W7HxCUFy7m27Yr8S+D+mz9e4cSdIo8NBTCpIPzY41KFvVwHFi8FOV40?= =?us-ascii?Q?d/nmB8NXL0s/tWwGvKSn1cymKzEOeZ5TnLxa1gtl8BG8xY0xM1BBM72Q+iJ7?= =?us-ascii?Q?jyqrHAvHR78/ZOWjGuPpLC9l+70XR22eLmv/YyF503TPm+MZZTwr9f6xkL6j?= =?us-ascii?Q?B0j/AiHxhav1fti2d1vafdniRGQ22pbHzhic3S/e18ZyxGpGtML+HHYxuiyh?= =?us-ascii?Q?PUcjCuhAei9KCDAFvl3Ln1QzUWRWtjvgblmE+G/nJf0E1KQJRDXT7Hsz266g?= =?us-ascii?Q?ktRDORpEQN01g74ikArFwaMkj5N1jA1RFDSqhABjkgnAGoOMg3FCiSqt36NY?= =?us-ascii?Q?eWz5EoSgNk6o11fone0uHjGcqTBGsUxg/Z6vnDswi25Su6Tfd10PpZHKPFDR?= =?us-ascii?Q?oGF2pl4dpOkT+StqJyYYnCp95/cmVYzNWJqsXDlre43hWA22m+FBZ4n7Wwpw?= =?us-ascii?Q?13euNBaMwxjTcep9JNUgnFodbX3Wg31KSOgDAEFLydiKVsAL6NfCyoPW8zyQ?= =?us-ascii?Q?+H/9A0U4y9n+u225AYcXXmFeFSsxHPe5lq1EInKLDmiD7j0CusfEO9Hlzpwl?= =?us-ascii?Q?Qq/GY1SBC3f28bOoq4PF7D80CjME+nAl0YB1Sfesp8WmB0DStUsZhlHRVOoP?= =?us-ascii?Q?uaUFBzUEFgB8Ywf64jxyDpz65yDx/atExhXNW4sOx1oTGETRUdGMmoj1Lx1M?= =?us-ascii?Q?WA41UMzVhdEYb1JjWD2LAyvJeUXf6yF4fuYzV4pirrRQ/H8kUeBCJogXCOXf?= =?us-ascii?Q?XbUg1mzJjRdpfbIhzWjMtJAzKoH8788DC3tNhTPtD2jIqrocxttQ3b14Wx9C?= =?us-ascii?Q?/5ZuX/l+yXonqnqFAEuDZ7hug6kLH1PjcJBkmbztTL/zPjOGEdZU4bVmgD13?= =?us-ascii?Q?EySl0APNJrONhrUJwBesv4r4jadeOLvkxXIDbDF2tHc68T79dVr/IRcn8Q8t?= =?us-ascii?Q?/UAAfKB2Rs1/qx8Ipa6rOThs?=
X-Microsoft-Exchange-Diagnostics: 1; BLUPR0801MB547; 31:mN9XwvO/GemyNm6SlYzus9x8CvqF9WacwOp62Q6sFhqoAaWrm83uhAlk7JVd4kNlTkdGEfgvNE+HvdzDwYZX2QsldGCeTfLNU1vTIdBQiOLGMNNoGsF8u5ndCSDFh95Om2rIGD6urADpVTWVCQ7m0XphfC4LBU6MvXMfLjJ97+Qjns96RsW0Px248cv7kKyQnShWAG8gKTxOrb4tfzR2abSZXz3sd/GUkYjpr9gUwgs=; 20:oVjKBtVRFDF+yQ/ExFTz1mQ8H1mctsmxm/o4Rr3bp6N9u66IvOZWRJ6sPiNJkSyuVt7yR39coQ6RELkm/cQfoO0DbhjqR4NzZE9VjMWS1zPJKcBN8uIwz8NkslLYTupDcPONL0SgaoL94UUrO+2p4QDoKwvvtptUwjSvmakEjtM=; 4:US+u7PszmxJTnetKuhVvUKLVAgUsySYrJZCugsMC7/yOh7GyrQB8plM8VOFgd61GduHi2RmArRT+fyVVGuv074GuPExTYp9OsKxvyIeU0trsJhZ8mUhKEzM3XCCU4NhwADoiBsycKlIvKOd55cQRKUVbP3WEUgOtI1Xk87hP3HUL25dedw0gt8p+23qVzfe9l74bIAjDTvxdlWPrDl8F8vPEfiYpn8bE/d16QjA0ViA03IvQ2jG2Z3NEsJHkpSmS41JWfWz4kxR/9kVb8lftASEcW4XCXvDGwdSqF21/Zah4pKbLha3Q1yp/HU+AakZJnvBtMw+A3bbxYWjjwbFqHJosFP5qGqImC0mdmK6t5Idv+qeheXVXFydwpUfjTNj+hA6Vc9cr8Bh3YvwKP5sXQf63jShU+MTwapANlgzTq1OQ5Xg+FYn5uR+lqAUpnHEw
X-Microsoft-Antispam-PRVS: <BLUPR0801MB54754BDBA4E03B834E319B883F30@BLUPR0801MB547.namprd08.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(146099531331640);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001);  SRVR:BLUPR0801MB547; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0801MB547; 
X-Forefront-PRVS: 0067A8BA2A
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(7916002)(377454003)(189002)(24454002)(199003)(68736007)(8676002)(64126003)(81166006)(81156014)(551934003)(89122001)(2351001)(5660300001)(7846002)(36756003)(65826007)(105586002)(54356999)(90282001)(106356001)(15975445007)(76176999)(31686004)(2950100001)(50986999)(42186005)(16236675004)(189998001)(450100001)(77096005)(2906002)(75432002)(101416001)(88552002)(33646002)(16601075003)(7906003)(4001350100001)(15974865002)(97736004)(65956001)(19617315012)(7736002)(92566002)(83506001)(6116002)(586003)(19580405001)(31696002)(110136003)(86362001)(107886002)(65806001)(512944002)(84326002)(19580395003)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR0801MB547; H:htom.local; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: internet2.edu does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BLUPR0801MB547; 23:a/TCUFmEDGU12peqbmh8jSns9p7o0/yXZ4zzC5cA?= =?us-ascii?Q?kPTgSs34LrxMywTgveEajt08DJtsR779//bcAtaZE9GHF0G0Pi/+rmJ9EAIh?= =?us-ascii?Q?W35ioP5L1PIA39gQcjIjBHDDWmzmiyhR6ifyU8wyIodV3gMqlnBVEbxDkHTI?= =?us-ascii?Q?ZwRKHExvGhUhy0diNPxsQoIMDGv5qNLiKrR5ZVH48bDkbEEdgEACX/nJfSSz?= =?us-ascii?Q?W76zpDfWYShcmhGf8PvfhKQzmxCCIxi4vnhnwpI30+LmApHVShXlJCcca9Pr?= =?us-ascii?Q?Yr078uuf3Ql9fpOqA6TfCJW6xwokWcigUnrNX828td/OqXkeO46+M5QsL5J9?= =?us-ascii?Q?Y3E8cy/wMdEELN4TXX19rxnzE/KeHIT5UDjrlFxqemgE3BQR4o1fWaN+GhW6?= =?us-ascii?Q?7MINHoEeBc0vIdccS3TyzdGSD7wZOmufZG1MnDPVYIBf9ueErPR+Z7XgcbqS?= =?us-ascii?Q?2f0b01yNV83zW64X3r9FuilhEV5l8Q+ploGSGAUBW4KHKdEOSF/f5aTTw7L4?= =?us-ascii?Q?WkAUNk8q+bgvudp4peD9mJO/rMsyJdSiOg5L0kdR+7/TAn9kYFoxoK/AGhYz?= =?us-ascii?Q?dyKc/V+OkZlFlPi2VZAS961B6j7WJ/HGIkjwZCmUwqOnIxWoHyM4vU35YIVD?= =?us-ascii?Q?Pph+lXVk3Nb861u8fzrdIuPMMUauI46uOD0ioMmGhV8nwEg0rurBeaKw2fo/?= =?us-ascii?Q?tgOe6hT5W/vm/moPMW5sJco2chQ0fhGuYXhLkKSgf2VzET/CT1nYJluu+8zC?= =?us-ascii?Q?JvbIXmjMuHnJ0/DRaYXebu8pWFj97CIZNKOMUxFoLMEb2itepPz10LqrEDBK?= =?us-ascii?Q?vokc6JG7sjolDtStOG37E92p9X3OWFCN+UahB98vFmPznLSwWP2D1/+iQEdc?= =?us-ascii?Q?nBUpwsOOi7aIdX78kqhkTseaxmE8oZnVGsMHHMHFITPo/HTrxC2jsdFD2h6y?= =?us-ascii?Q?807p4o1jGx+gIvZzR/O6X2gyBc9FxtWkPsdwiIkZmgYATTuRfu5cchZV+RD6?= =?us-ascii?Q?B228jN+0NfJQJFu6YmsVCxbR14vKkkPIGV4M2NMRLLMNHPMrkjjOkCTIP7Qp?= =?us-ascii?Q?7Go/U5s9+WopFZo06pGL7EKOMdsTw6kBbdi2i+2M9ry/h4At9KeJXdbz4h3G?= =?us-ascii?Q?C8sDzcNZXQJOb9kf/YUOHuHVGzc5LGVLvWOVb7YgOpVDU/cDfBmotxc+oKn0?= =?us-ascii?Q?eHutkUwZbktfh+Zc5gqPgezQW4j2cZJnHEYlOt4c8f0OkEjfcJbc6ukIND/M?= =?us-ascii?Q?F0jIaFXh01C6LUTWv0sVJ/Zgle6aQRXj1sXDMFcS+xPmLYdgJUePm3CWst78?= =?us-ascii?Q?3WAmXm34JbIc27V5uSI1F7W6OL4glYsU+319ATk20tTGKkO59HFISjZ8ZRYq?= =?us-ascii?Q?3MJ3Bn0mKGuealuCDU8uI64kJEV0HMFY8jWmZNVSA0NwZ/Au0BNYaBD3yjfG?= =?us-ascii?Q?20kbvOOoQ7yuaq6NqsVIODsYYjTNx8YSeUy1UA6SCJibrIwDFDAtSu30fM8o?= =?us-ascii?Q?1IQPTMaaAQ2A3w=3D=3D?=
X-Microsoft-Exchange-Diagnostics: 1; BLUPR0801MB547; 6:VgTZ08FhtVGaSehBuxmRPuiD8k+E3mj/tVA+Px8iVyKvgi09X2hxoCwBfMrmyGPjxNSPO2PB81TUw9NWC2N+RpkS3Ad92DSFCXZU/Jgc2OaCMNWrtU843Hq4gC/Ui/ne8bFACpEruNgwf/XojR8Vrathi5v4VMMN0CWaQGFf6WDyBV7K602ltPKxSvF+iP0grXkSm3o8nANrmAUpstcXPGaV3Pvkr4NxiZfxGnH8HBP3PtBSS0PtpZpcXbYxLSbjVf2r2mlVF8/+D44boN4idXuoif35tHilVfOu8I5YPrA=; 5:4He6UJxko63Kvgwmc3EHRqlHiSnJjlDY2uUtVWObn9fitRFnnnpA6Hqt+OGLkpFf64e2X6T81bny4ztybUqk78t62DxCNPxTw36G6Me/3NEmdgmgJ6N+9F3RTf/ujJeN7BXn8UL+d5MhKtwFtOjOqw==; 24:ZhxfJ7p+r1cdufcXCvK7mdbvhzs6HR56gfJGIXNeLhJNl62lkHowLdPfwS9OlCjxCOBgSUOjAERNM+enSYobwT2ecwbTaWGagJnmHfmWiag=; 7:I8gG9ETbS0bB8/BNYWmgqAJ1GiSW/Yjvj5z3DW+rdSymEBhs72GL/jiGSrP9QQ1fre7BLHL8sHaBBs/7LNaVrBhXXhyNjcHh+fb3sTkkbyq7TggzjOns0ktf1vVSFYPkaEVQj6pAmh8Kuk4h4VtwdexoqoO/hSXaYftoRrlRzNpUN++NI7GSCnwabk2cli+P7MXF+46ikG+U1VzKj2UjbtssDMvDSLhHqg7MkQrZfdumWETiUvTXYgm0c17cGMXD
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: internet2.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 Sep 2016 14:15:31.4667 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0801MB547
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/wa69WOBdxXsgp3oMkCxwfjWBzeM>
Subject: Re: [Id-event] Proposed text for txn and ordering
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Sep 2016 14:15:37 -0000

--------------D3C4EA6F07EF2DF591E9A312
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit

+1

Nick

On 9/15/16 7:32 PM, Marius Scurtescu wrote:
> Sounds good to me.
>
> Marius
>
> On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <phil.hunt@oracle.com 
> <mailto:phil.hunt@oracle.com>> wrote:
>
>     Based on the feedback, I am proposing the following changes:
>
>     In the new attributes defined section, a new claim “txn” defined:
>
>         txn
>            An OPTIONAL single-valued String value that represents a unique
>            transaction identifier.  In cases where multiple SETs are issued
>            based on different event URIs, the transaction identifier MAY be
>            used to correlate SETs to the same originating event or stateful
>            change.
>
>
>     Regarding Ordering, I am proposing the following section:
>
>     2.2. Idempotency and Ordering Considerations In many cases SETs
>     will be issued by highly distributed systems and subscribers.
>     Without additional specification it is quite conceivable that the
>     order of SETs received by a subscriber MAY be different from the
>     order of the originating state changes or events. While the "iat"
>     value may give a rough indication of SET order, it SHOULD NOT be
>     relied upon unless the profiling SET token specification provides
>     clarification. Profiling specifications are encouraged to consider
>     whether the nature of SETs defined are "idempotent" in the sense
>     that the order of receipt does not matter. For example, in the
>     case of token revocations, each SET can stand on its own and order
>     has no impact. In contrast, a profiling SET specification related
>     to provisioning might be highly dependent on ordering. As an
>     example: one SET indicates a new resource was created, while the
>     next SET indicates the same resource is modified. Non-Idempotent
>     SET event specifications SHOULD choose to define a sequencing
>     method such as aa claim used for the purpose or identifying the
>     order of SETs as defined by the Feed Publisher or another method
>     that is part of how SETs are distributed.
>
>     Thanks for your feedback.
>
>     Phil
>
>     @independentid
>     www.independentid.com <http://www.independentid.com>
>     phil.hunt@oracle.com <mailto:phil.hunt@oracle.com>
>
>
>
>
>
>
>     _______________________________________________
>     Id-event mailing list
>     Id-event@ietf.org <mailto:Id-event@ietf.org>
>     https://www.ietf.org/mailman/listinfo/id-event
>     <https://www.ietf.org/mailman/listinfo/id-event>
>
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event


--------------D3C4EA6F07EF2DF591E9A312
Content-Type: text/html; charset="windows-1252"
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    +1<br>
    <br>
    Nick<br>
    <br>
    <div class="moz-cite-prefix">On 9/15/16 7:32 PM, Marius Scurtescu
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div dir="ltr">Sounds good to me.</div>
      <div class="gmail_extra"><br clear="all">
        <div>
          <div class="gmail_signature" data-smartmail="gmail_signature">Marius</div>
        </div>
        <br>
        <div class="gmail_quote">On Thu, Sep 15, 2016 at 3:28 PM, Phil
          Hunt <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:phil.hunt@oracle.com" target="_blank">phil.hunt@oracle.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div style="word-wrap:break-word">Based on the feedback, I
              am proposing the following changes:
              <div><br>
              </div>
              <div>In the new attributes defined section, a new claim
                “txn” defined:</div>
              <div>
                <div
                  style="margin:0px;font-size:11px;line-height:normal;font-family:Monaco">
                  <pre style="word-wrap:break-word;white-space:pre-wrap">   txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.
</pre>
                  <div><br>
                  </div>
                </div>
                <div>Regarding Ordering, I am proposing the following
                  section:</div>
                <div>
                  <pre style="word-wrap:break-word;white-space:pre-wrap"><span style="font-size:11px">2.2.  Idempotency and Ordering Considerations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the "iat" value may give a rough indication of SET order, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are "idempotent" in the sense that the order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.</span></pre>
                </div>
                <div>Thanks for your feedback.</div>
                <div><br>
                </div>
                <div>Phil</div>
                <div>
                  <div
style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
                    <div
style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
                      <div><span
                          class="m_-2137582900026257651Apple-style-span"
style="border-collapse:separate;line-height:normal;border-spacing:0px">
                          <div style="word-wrap:break-word">
                            <div>
                              <div>
                                <div><br>
                                </div>
                                <div>@independentid</div>
                                <div><a moz-do-not-send="true"
                                    href="http://www.independentid.com"
                                    target="_blank">www.independentid.com</a></div>
                              </div>
                            </div>
                          </div>
                        </span><a moz-do-not-send="true"
                          href="mailto:phil.hunt@oracle.com"
                          target="_blank">phil.hunt@oracle.com</a></div>
                      <div><br>
                      </div>
                    </div>
                    <br
                      class="m_-2137582900026257651Apple-interchange-newline">
                  </div>
                  <br
                    class="m_-2137582900026257651Apple-interchange-newline">
                  <br
                    class="m_-2137582900026257651Apple-interchange-newline">
                </div>
                <br>
              </div>
            </div>
            <br>
            ______________________________<wbr>_________________<br>
            Id-event mailing list<br>
            <a moz-do-not-send="true" href="mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
            <a moz-do-not-send="true"
              href="https://www.ietf.org/mailman/listinfo/id-event"
              rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Id-event mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Id-event@ietf.org">Id-event@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/listinfo/id-event</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------D3C4EA6F07EF2DF591E9A312--


From nobody Fri Sep 16 14:00:20 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A66712B028 for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 14:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level: 
X-Spam-Status: No, score=-5.727 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nE0Fb9ESRSVz for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 14:00:16 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DE5D12B027 for <id-event@ietf.org>; Fri, 16 Sep 2016 14:00:16 -0700 (PDT)
Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8GL0EWp000575 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 16 Sep 2016 21:00:15 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0022.oracle.com (8.14.4/8.13.8) with ESMTP id u8GL0EWr025129 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Sep 2016 21:00:14 GMT
Received: from abhmp0002.oracle.com (abhmp0002.oracle.com [141.146.116.8]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u8GL0Aqq000530; Fri, 16 Sep 2016 21:00:11 GMT
Received: from [10.0.1.4] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 16 Sep 2016 14:00:10 -0700
Content-Type: multipart/alternative; boundary=Apple-Mail-75372C93-DBE4-4A7E-8DC1-B2B6CD86AED7
Mime-Version: 1.0 (1.0)
From: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
X-Mailer: iPhone Mail (14A403)
In-Reply-To: <a42b8067-02f8-a9ba-ea86-d129a0546ed4@internet2.edu>
Date: Fri, 16 Sep 2016 14:00:08 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <E6464A41-7619-4752-B5B6-F1EB54C03544@oracle.com>
References: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com> <CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com> <a42b8067-02f8-a9ba-ea86-d129a0546ed4@internet2.edu>
To: Nicholas Roy <nroy@internet2.edu>
X-Source-IP: userv0022.oracle.com [156.151.31.74]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/aS9y9iEyyQfv3kud5aFvuKXIDRg>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Proposed text for txn and ordering
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Sep 2016 21:00:18 -0000

--Apple-Mail-75372C93-DBE4-4A7E-8DC1-B2B6CD86AED7
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

It occurs to me that the terminology for idempotency is wrong. Scim is idemp=
otent in that any request can be repeated. However a series of transactions d=
oes have order and dependence.=20

I will look for another way to express this or just drop the idempotence ter=
m.=20

Phil

> On Sep 16, 2016, at 7:15 AM, Nicholas Roy <nroy@internet2.edu> wrote:
>=20
> +1
>=20
> Nick
>=20
>> On 9/15/16 7:32 PM, Marius Scurtescu wrote:
>> Sounds good to me.
>>=20
>> Marius
>>=20
>>> On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <phil.hunt@oracle.com> wrote:=

>>> Based on the feedback, I am proposing the following changes:
>>>=20
>>> In the new attributes defined section, a new claim =E2=80=9Ctxn=E2=80=9D=
 defined:
>>>    txn
>>>       An OPTIONAL single-valued String value that represents a unique
>>>       transaction identifier.  In cases where multiple SETs are issued
>>>       based on different event URIs, the transaction identifier MAY be
>>>       used to correlate SETs to the same originating event or stateful
>>>       change.
>>>=20
>>> Regarding Ordering, I am proposing the following section:
>>> 2.2.  Idempotency and Ordering Considerations
>>>=20
>>>    In many cases SETs will be issued by highly distributed systems and
>>>    subscribers.  Without additional specification it is quite
>>>    conceivable that the order of SETs received by a subscriber MAY be
>>>    different from the order of the originating state changes or events.
>>>    While the "iat" value may give a rough indication of SET order, it
>>>    SHOULD NOT be relied upon unless the profiling SET token
>>>    specification provides clarification.
>>>=20
>>>    Profiling specifications are encouraged to consider whether the
>>>    nature of SETs defined are "idempotent" in the sense that the order
>>>    of receipt does not matter.  For example, in the case of token
>>>    revocations, each SET can stand on its own and order has no impact.
>>>    In contrast, a profiling SET specification related to provisioning
>>>    might be highly dependent on ordering.  As an example: one SET
>>>    indicates a new resource was created, while the next SET indicates
>>>    the same resource is modified.  Non-Idempotent SET event
>>>    specifications SHOULD choose to define a sequencing method such as aa=

>>>    claim used for the purpose or identifying the order of SETs as
>>>    defined by the Feed Publisher or another method that is part of how
>>>    SETs are distributed.
>>> Thanks for your feedback.
>>>=20
>>> Phil
>>>=20
>>> @independentid
>>> www.independentid.com
>>> phil.hunt@oracle.com
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
>>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event

--Apple-Mail-75372C93-DBE4-4A7E-8DC1-B2B6CD86AED7
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><div style=3D"direction: inherit;">It o=
ccurs to me that the terminology for idempotency is wrong. Scim is idempoten=
t in that any request can be repeated. However a series of transactions does=
 have order and dependence.&nbsp;</div><div style=3D"direction: inherit;"><b=
r></div><div style=3D"direction: inherit;">I will look for another way to ex=
press this or just drop the idempotence term.&nbsp;</div><br>Phil</div><div>=
<br>On Sep 16, 2016, at 7:15 AM, Nicholas Roy &lt;<a href=3D"mailto:nroy@int=
ernet2.edu">nroy@internet2.edu</a>&gt; wrote:<br><br></div><blockquote type=3D=
"cite"><div>
 =20
    <meta content=3D"text/html; charset=3Dwindows-1252" http-equiv=3D"Conten=
t-Type">
 =20
 =20
    +1<br>
    <br>
    Nick<br>
    <br>
    <div class=3D"moz-cite-prefix">On 9/15/16 7:32 PM, Marius Scurtescu
      wrote:<br>
    </div>
    <blockquote cite=3D"mid:CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEo=
maw@mail.gmail.com" type=3D"cite">
      <meta http-equiv=3D"Content-Type" content=3D"text/html;
        charset=3Dwindows-1252">
      <div dir=3D"ltr">Sounds good to me.</div>
      <div class=3D"gmail_extra"><br clear=3D"all">
        <div>
          <div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">=
Marius</div>
        </div>
        <br>
        <div class=3D"gmail_quote">On Thu, Sep 15, 2016 at 3:28 PM, Phil
          Hunt <span dir=3D"ltr">&lt;<a moz-do-not-send=3D"true" href=3D"mai=
lto:phil.hunt@oracle.com" target=3D"_blank">phil.hunt@oracle.com</a>&gt;</sp=
an>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div style=3D"word-wrap:break-word">Based on the feedback, I
              am proposing the following changes:
              <div><br>
              </div>
              <div>In the new attributes defined section, a new claim
                =E2=80=9Ctxn=E2=80=9D defined:</div>
              <div>
                <div style=3D"margin:0px;font-size:11px;line-height:normal;f=
ont-family:Monaco">
                  <pre style=3D"word-wrap:break-word;white-space:pre-wrap"> =
  txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.
</pre>
                  <div><br>
                  </div>
                </div>
                <div>Regarding Ordering, I am proposing the following
                  section:</div>
                <div>
                  <pre style=3D"word-wrap:break-word;white-space:pre-wrap"><=
span style=3D"font-size:11px">2.2.  Idempotency and Ordering Considerations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the "iat" value may give a rough indication of SET order, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are "idempotent" in the sense that the order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.</span></pre>
                </div>
                <div>Thanks for your feedback.</div>
                <div><br>
                </div>
                <div>Phil</div>
                <div>
                  <div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-=
align:start;text-indent:0px;text-transform:none;white-space:normal;word-spac=
ing:0px;word-wrap:break-word">
                    <div style=3D"color:rgb(0,0,0);letter-spacing:normal;tex=
t-align:start;text-indent:0px;text-transform:none;white-space:normal;word-sp=
acing:0px;word-wrap:break-word">
                      <div><span class=3D"m_-2137582900026257651Apple-style-=
span" style=3D"border-collapse:separate;line-height:normal;border-spacing:0p=
x">
                          <div style=3D"word-wrap:break-word">
                            <div>
                              <div>
                                <div><br>
                                </div>
                                <div>@independentid</div>
                                <div><a moz-do-not-send=3D"true" href=3D"htt=
p://www.independentid.com" target=3D"_blank">www.independentid.com</a></div>=

                              </div>
                            </div>
                          </div>
                        </span><a moz-do-not-send=3D"true" href=3D"mailto:ph=
il.hunt@oracle.com" target=3D"_blank">phil.hunt@oracle.com</a></div>
                      <div><br>
                      </div>
                    </div>
                    <br class=3D"m_-2137582900026257651Apple-interchange-new=
line">
                  </div>
                  <br class=3D"m_-2137582900026257651Apple-interchange-newli=
ne">
                  <br class=3D"m_-2137582900026257651Apple-interchange-newli=
ne">
                </div>
                <br>
              </div>
            </div>
            <br>
            ______________________________<wbr>_________________<br>
            Id-event mailing list<br>
            <a moz-do-not-send=3D"true" href=3D"mailto:Id-event@ietf.org">Id=
-event@ietf.org</a><br>
            <a moz-do-not-send=3D"true" href=3D"https://www.ietf.org/mailman=
/listinfo/id-event" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.or=
g/mailman/<wbr>listinfo/id-event</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
Id-event mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Id-event@ietf.org">Id-e=
vent@ietf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/list=
info/id-event">https://www.ietf.org/mailman/listinfo/id-event</a>
</pre>
    </blockquote>
    <br>
 =20

</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>Id-event mailing list</span><br>=
<span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></span><br><=
span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www.=
ietf.org/mailman/listinfo/id-event</a></span><br></div></blockquote></body><=
/html>=

--Apple-Mail-75372C93-DBE4-4A7E-8DC1-B2B6CD86AED7--


From nobody Fri Sep 16 14:26:10 2016
Return-Path: <moransar@cisco.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B75B612B33C for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 14:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.028
X-Spam-Level: 
X-Spam-Status: No, score=-16.028 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5p6pVYb1mWnu for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 14:26:03 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E56112B33B for <id-event@ietf.org>; Fri, 16 Sep 2016 14:26:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12078; q=dns/txt; s=iport; t=1474061163; x=1475270763; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=6UOj+gpEsck/6vomBChOH6EmV/1Wcvu+bfb7hoTjf5M=; b=eqKKWwaslePF9cdRXXtbu14C9M4b0/Def1t4B2Ifdt2gWfkC1EHWXOY3 xw4Udl9T4CXYnV6FoueXnjaZIBc/okX2Mnzj6hPTHZnMv68Dk9s6UMLVk 8MnhMYWmlEWA2OG2xB5ffkSeqpoD+MbBMmef6vWyL3exA0/pYi2JyfKfQ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CgAQBWYtxX/5pdJa1eDgsBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYMHMwEBAQEBHld8B40sph6FD4IDGQEKhXoCgVk4FAECAQEBAQE?= =?us-ascii?q?BAV4nhGEBAQEEAQEBRiULEAIBCBEDAQIoBycLFAkIAgQBDQUJiEEOwScBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEchjaEVIRkHoUeBY5rhS2FVQGJJoY0j2iMYYN6AR4?= =?us-ascii?q?2gkeBaDtyhlF/AQEB?=
X-IronPort-AV: E=Sophos;i="5.30,346,1470700800";  d="scan'208,217";a="323089274"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Sep 2016 21:26:02 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u8GLQ2ON022069 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 16 Sep 2016 21:26:02 GMT
Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 16 Sep 2016 16:26:01 -0500
Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1210.000; Fri, 16 Sep 2016 16:26:01 -0500
From: "Morteza Ansari (moransar)" <moransar@cisco.com>
To: "Phil Hunt (IDM)" <phil.hunt@oracle.com>, Nicholas Roy <nroy@internet2.edu>
Thread-Topic: [Id-event] Proposed text for txn and ordering
Thread-Index: AQHSD6CP/7SKqh+/bkeTKJuTonDJdKB7qQWAgADVF4CAAHERAP//keCA
Date: Fri, 16 Sep 2016 21:26:00 +0000
Message-ID: <D401B0FE.48BE7%moransar@cisco.com>
References: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com> <CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com> <a42b8067-02f8-a9ba-ea86-d129a0546ed4@internet2.edu> <E6464A41-7619-4752-B5B6-F1EB54C03544@oracle.com>
In-Reply-To: <E6464A41-7619-4752-B5B6-F1EB54C03544@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.7.160722
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.48.122]
Content-Type: multipart/alternative; boundary="_000_D401B0FE48BE7moransarciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/Mg6zU4Xwy_UFhCafif7DBgYtWbQ>
Cc: "id-event@ietf.org" <id-event@ietf.org>
Subject: Re: [Id-event] Proposed text for txn and ordering
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Sep 2016 21:26:08 -0000

--_000_D401B0FE48BE7moransarciscocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Is this even something we could define for abstract events?  Doesn't that s=
emantics really associated with the type of event we are talking about?  I =
think this is a property that should be defined for a given type of event a=
nd not across all events.


Cheers,
Morteza

From: Id-event <id-event-bounces@ietf.org<mailto:id-event-bounces@ietf.org>=
> on behalf of Phil Hunt <phil.hunt@oracle.com<mailto:phil.hunt@oracle.com>=
>
Date: Friday, September 16, 2016 at 2:00 PM
To: Nicholas Roy <nroy@internet2.edu<mailto:nroy@internet2.edu>>
Cc: "id-event@ietf.org<mailto:id-event@ietf.org>" <id-event@ietf.org<mailto=
:id-event@ietf.org>>
Subject: Re: [Id-event] Proposed text for txn and ordering

It occurs to me that the terminology for idempotency is wrong. Scim is idem=
potent in that any request can be repeated. However a series of transaction=
s does have order and dependence.

I will look for another way to express this or just drop the idempotence te=
rm.

Phil

On Sep 16, 2016, at 7:15 AM, Nicholas Roy <nroy@internet2.edu<mailto:nroy@i=
nternet2.edu>> wrote:

+1

Nick

On 9/15/16 7:32 PM, Marius Scurtescu wrote:
Sounds good to me.

Marius

On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <phil.hunt@oracle.com<mailto:phi=
l.hunt@oracle.com>> wrote:
Based on the feedback, I am proposing the following changes:

In the new attributes defined section, a new claim "txn" defined:

   txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.


Regarding Ordering, I am proposing the following section:

2.2.  Idempotency and Ordering Considerations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the "iat" value may give a rough indication of SET order, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are "idempotent" in the sense that the order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.

Thanks for your feedback.

Phil

@independentid
www.independentid.com<http://www.independentid.com>
phil.hunt@oracle.com<mailto:phil.hunt@oracle.com>






_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>
https://www.ietf.org/mailman/listinfo/id-event





_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>https://www.ietf.org/mailman/lis=
tinfo/id-event

_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>
https://www.ietf.org/mailman/listinfo/id-event

--_000_D401B0FE48BE7moransarciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <0A4619CD7321FF4D9DF6D9D3A6F48861@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Is this even something we could define for abstract events? &nbsp;Does=
n&#8217;t that semantics really associated with the type of event we are ta=
lking about? &nbsp;I think this is a property that should be defined for a =
given type of event and not across all events.</div>
<div><br>
</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Morteza</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Id-event &lt;<a href=3D"mailt=
o:id-event-bounces@ietf.org">id-event-bounces@ietf.org</a>&gt; on behalf of=
 Phil Hunt &lt;<a href=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.com=
</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday, September 16, 2016 at=
 2:00 PM<br>
<span style=3D"font-weight:bold">To: </span>Nicholas Roy &lt;<a href=3D"mai=
lto:nroy@internet2.edu">nroy@internet2.edu</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:id-even=
t@ietf.org">id-event@ietf.org</a>&quot; &lt;<a href=3D"mailto:id-event@ietf=
.org">id-event@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [Id-event] Proposed te=
xt for txn and ordering<br>
</div>
<div><br>
</div>
<div>
<div dir=3D"auto">
<div>
<div style=3D"direction: inherit;">It occurs to me that the terminology for=
 idempotency is wrong. Scim is idempotent in that any request can be repeat=
ed. However a series of transactions does have order and dependence.&nbsp;<=
/div>
<div style=3D"direction: inherit;"><br>
</div>
<div style=3D"direction: inherit;">I will look for another way to express t=
his or just drop the idempotence term.&nbsp;</div>
<br>
Phil</div>
<div><br>
On Sep 16, 2016, at 7:15 AM, Nicholas Roy &lt;<a href=3D"mailto:nroy@intern=
et2.edu">nroy@internet2.edu</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>&#43;1<br>
<br>
Nick<br>
<br>
<div class=3D"moz-cite-prefix">On 9/15/16 7:32 PM, Marius Scurtescu wrote:<=
br>
</div>
<blockquote cite=3D"mid:CAGdjJp&#43;ndWYiPYb0KPN-TFh&#43;SN-hqR8JBO6poVWAT_=
OPEEomaw@mail.gmail.com" type=3D"cite">
<div dir=3D"ltr">Sounds good to me.</div>
<div class=3D"gmail_extra"><br clear=3D"all">
<div>
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">Marius</d=
iv>
</div>
<br>
<div class=3D"gmail_quote">On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <span=
 dir=3D"ltr">
&lt;<a moz-do-not-send=3D"true" href=3D"mailto:phil.hunt@oracle.com" target=
=3D"_blank">phil.hunt@oracle.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">Based on the feedback, I am proposing t=
he following changes:
<div><br>
</div>
<div>In the new attributes defined section, a new claim &#8220;txn&#8221; d=
efined:</div>
<div>
<div style=3D"margin:0px;font-size:11px;line-height:normal;font-family:Mona=
co">
<pre style=3D"word-wrap:break-word;white-space:pre-wrap">   txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.
</pre>
<div><br>
</div>
</div>
<div>Regarding Ordering, I am proposing the following section:</div>
<div>
<pre style=3D"word-wrap:break-word;white-space:pre-wrap"><span style=3D"fon=
t-size:11px">2.2.  Idempotency and Ordering Considerations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the &quot;iat&quot; value may give a rough indication of SET order=
, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are &quot;idempotent&quot; in the sense that the =
order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.</span></pre>
</div>
<div>Thanks for your feedback.</div>
<div><br>
</div>
<div>Phil</div>
<div>
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wra=
p:break-word">
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wra=
p:break-word">
<div><span class=3D"m_-2137582900026257651Apple-style-span" style=3D"border=
-collapse:separate;line-height:normal;border-spacing:0px">
<div style=3D"word-wrap:break-word">
<div>
<div>
<div><br>
</div>
<div>@independentid</div>
<div><a moz-do-not-send=3D"true" href=3D"http://www.independentid.com" targ=
et=3D"_blank">www.independentid.com</a></div>
</div>
</div>
</div>
</span><a moz-do-not-send=3D"true" href=3D"mailto:phil.hunt@oracle.com" tar=
get=3D"_blank">phil.hunt@oracle.com</a></div>
<div><br>
</div>
</div>
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
</div>
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
</div>
<br>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a moz-do-not-send=3D"true" href=3D"mailto:Id-event@ietf.org">Id-event@ietf=
.org</a><br>
<a moz-do-not-send=3D"true" href=3D"https://www.ietf.org/mailman/listinfo/i=
d-event" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/=
<wbr>listinfo/id-event</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset> <br>
<pre wrap=3D"">_______________________________________________
Id-event mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Id-event@ietf.org">Id-=
event@ietf.org</a><a class=3D"moz-txt-link-freetext" href=3D"https://www.ie=
tf.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/listinfo/id-=
event</a></pre>
</blockquote>
<br>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>Id-event mailing list</span><br>
<span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://ww=
w.ietf.org/mailman/listinfo/id-event</a></span><br>
</div>
</blockquote>
</div>
</div>
</span>
</body>
</html>

--_000_D401B0FE48BE7moransarciscocom_--


From nobody Fri Sep 16 17:34:56 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB8412B2FC for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 17:34:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.708
X-Spam-Level: 
X-Spam-Status: No, score=-5.708 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3GgYG0SV4KEC for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 17:34:52 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDC8512B0C1 for <id-event@ietf.org>; Fri, 16 Sep 2016 17:34:52 -0700 (PDT)
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8H0YnQa005005 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 17 Sep 2016 00:34:50 GMT
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u8H0Ynmk003003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 17 Sep 2016 00:34:49 GMT
Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u8H0YmNx010592; Sat, 17 Sep 2016 00:34:48 GMT
Received: from [25.102.123.34] (/24.114.68.215) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 16 Sep 2016 17:34:47 -0700
Content-Type: multipart/alternative; boundary=Apple-Mail-53DE9CCE-874E-4F1E-B846-31ED7D3D404D
Mime-Version: 1.0 (1.0)
From: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
X-Mailer: iPhone Mail (14A403)
In-Reply-To: <D401B0FE.48BE7%moransar@cisco.com>
Date: Fri, 16 Sep 2016 17:34:37 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <062AC5AC-AF95-4D0E-9427-1472732162F0@oracle.com>
References: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com> <CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com> <a42b8067-02f8-a9ba-ea86-d129a0546ed4@internet2.edu> <E6464A41-7619-4752-B5B6-F1EB54C03544@oracle.com> <D401B0FE.48BE7%moransar@cisco.com>
To: "Morteza Ansari (moransar)" <moransar@cisco.com>
X-Source-IP: aserv0021.oracle.com [141.146.126.233]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/-j_v8RQAMTb-KrBsRhsz94MUFXg>
Cc: Nicholas Roy <nroy@internet2.edu>, "id-event@ietf.org" <id-event@ietf.org>
Subject: Re: [Id-event] Proposed text for txn and ordering
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Sep 2016 00:34:55 -0000

--Apple-Mail-53DE9CCE-874E-4F1E-B846-31ED7D3D404D
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Txn needs to be available in all types.=20

Phil

> On Sep 16, 2016, at 2:26 PM, Morteza Ansari (moransar) <moransar@cisco.com=
> wrote:
>=20
> Is this even something we could define for abstract events?  Doesn=E2=80=99=
t that semantics really associated with the type of event we are talking abo=
ut?  I think this is a property that should be defined for a given type of e=
vent and not across all events.
>=20
>=20
> Cheers,
> Morteza
>=20
> From: Id-event <id-event-bounces@ietf.org> on behalf of Phil Hunt <phil.hu=
nt@oracle.com>
> Date: Friday, September 16, 2016 at 2:00 PM
> To: Nicholas Roy <nroy@internet2.edu>
> Cc: "id-event@ietf.org" <id-event@ietf.org>
> Subject: Re: [Id-event] Proposed text for txn and ordering
>=20
> It occurs to me that the terminology for idempotency is wrong. Scim is ide=
mpotent in that any request can be repeated. However a series of transaction=
s does have order and dependence.=20
>=20
> I will look for another way to express this or just drop the idempotence t=
erm.=20
>=20
> Phil
>=20
> On Sep 16, 2016, at 7:15 AM, Nicholas Roy <nroy@internet2.edu> wrote:
>=20
>> +1
>>=20
>> Nick
>>=20
>>> On 9/15/16 7:32 PM, Marius Scurtescu wrote:
>>> Sounds good to me.
>>>=20
>>> Marius
>>>=20
>>>> On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <phil.hunt@oracle.com> wrote=
:
>>>> Based on the feedback, I am proposing the following changes:
>>>>=20
>>>> In the new attributes defined section, a new claim =E2=80=9Ctxn=E2=80=9D=
 defined:
>>>>    txn
>>>>       An OPTIONAL single-valued String value that represents a unique
>>>>       transaction identifier.  In cases where multiple SETs are issued
>>>>       based on different event URIs, the transaction identifier MAY be
>>>>       used to correlate SETs to the same originating event or stateful
>>>>       change.
>>>>=20
>>>> Regarding Ordering, I am proposing the following section:
>>>> 2.2.  Idempotency and Ordering Considerations
>>>>=20
>>>>    In many cases SETs will be issued by highly distributed systems and
>>>>    subscribers.  Without additional specification it is quite
>>>>    conceivable that the order of SETs received by a subscriber MAY be
>>>>    different from the order of the originating state changes or events.=

>>>>    While the "iat" value may give a rough indication of SET order, it
>>>>    SHOULD NOT be relied upon unless the profiling SET token
>>>>    specification provides clarification.
>>>>=20
>>>>    Profiling specifications are encouraged to consider whether the
>>>>    nature of SETs defined are "idempotent" in the sense that the order
>>>>    of receipt does not matter.  For example, in the case of token
>>>>    revocations, each SET can stand on its own and order has no impact.
>>>>    In contrast, a profiling SET specification related to provisioning
>>>>    might be highly dependent on ordering.  As an example: one SET
>>>>    indicates a new resource was created, while the next SET indicates
>>>>    the same resource is modified.  Non-Idempotent SET event
>>>>    specifications SHOULD choose to define a sequencing method such as a=
a
>>>>    claim used for the purpose or identifying the order of SETs as
>>>>    defined by the Feed Publisher or another method that is part of how
>>>>    SETs are distributed.
>>>> Thanks for your feedback.
>>>>=20
>>>> Phil
>>>>=20
>>>> @independentid
>>>> www.independentid.com
>>>> phil.hunt@oracle.com
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> Id-event mailing list
>>>> Id-event@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/id-event
>>>>=20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.orghttps://www.ietf.org/mailman/listinfo/id-event
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event

--Apple-Mail-53DE9CCE-874E-4F1E-B846-31ED7D3D404D
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><div style=3D"direction: inherit;">Txn=
 needs to be available in all types.&nbsp;</div><br>Phil</div><div><br>On Se=
p 16, 2016, at 2:26 PM, Morteza Ansari (moransar) &lt;<a href=3D"mailto:mora=
nsar@cisco.com">moransar@cisco.com</a>&gt; wrote:<br><br></div><blockquote t=
ype=3D"cite"><div>

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-1=
">


<div>Is this even something we could define for abstract events? &nbsp;Doesn=
=E2=80=99t that semantics really associated with the type of event we are ta=
lking about? &nbsp;I think this is a property that should be defined for a g=
iven type of event and not across all events.</div>
<div><br>
</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Morteza</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:bl=
ack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0=
in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BO=
RDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Id-event &lt;<a href=3D"mailto=
:id-event-bounces@ietf.org">id-event-bounces@ietf.org</a>&gt; on behalf of P=
hil Hunt &lt;<a href=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.com</a=
>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday, September 16, 2016 at 2=
:00 PM<br>
<span style=3D"font-weight:bold">To: </span>Nicholas Roy &lt;<a href=3D"mail=
to:nroy@internet2.edu">nroy@internet2.edu</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>"<a href=3D"mailto:id-event@ietf=
.org">id-event@ietf.org</a>" &lt;<a href=3D"mailto:id-event@ietf.org">id-eve=
nt@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [Id-event] Proposed tex=
t for txn and ordering<br>
</div>
<div><br>
</div>
<div>
<div dir=3D"auto">
<div>
<div style=3D"direction: inherit;">It occurs to me that the terminology for i=
dempotency is wrong. Scim is idempotent in that any request can be repeated.=
 However a series of transactions does have order and dependence.&nbsp;</div=
>
<div style=3D"direction: inherit;"><br>
</div>
<div style=3D"direction: inherit;">I will look for another way to express th=
is or just drop the idempotence term.&nbsp;</div>
<br>
Phil</div>
<div><br>
On Sep 16, 2016, at 7:15 AM, Nicholas Roy &lt;<a href=3D"mailto:nroy@interne=
t2.edu">nroy@internet2.edu</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>+1<br>
<br>
Nick<br>
<br>
<div class=3D"moz-cite-prefix">On 9/15/16 7:32 PM, Marius Scurtescu wrote:<b=
r>
</div>
<blockquote cite=3D"mid:CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@=
mail.gmail.com" type=3D"cite">
<div dir=3D"ltr">Sounds good to me.</div>
<div class=3D"gmail_extra"><br clear=3D"all">
<div>
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">Marius</di=
v>
</div>
<br>
<div class=3D"gmail_quote">On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <span d=
ir=3D"ltr">
&lt;<a moz-do-not-send=3D"true" href=3D"mailto:phil.hunt@oracle.com" target=3D=
"_blank">phil.hunt@oracle.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">Based on the feedback, I am proposing th=
e following changes:
<div><br>
</div>
<div>In the new attributes defined section, a new claim =E2=80=9Ctxn=E2=80=9D=
 defined:</div>
<div>
<div style=3D"margin:0px;font-size:11px;line-height:normal;font-family:Monac=
o">
<pre style=3D"word-wrap:break-word;white-space:pre-wrap">   txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.
</pre>
<div><br>
</div>
</div>
<div>Regarding Ordering, I am proposing the following section:</div>
<div>
<pre style=3D"word-wrap:break-word;white-space:pre-wrap"><span style=3D"font=
-size:11px">2.2.  Idempotency and Ordering Considerations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the "iat" value may give a rough indication of SET order, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are "idempotent" in the sense that the order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.</span></pre>
</div>
<div>Thanks for your feedback.</div>
<div><br>
</div>
<div>Phil</div>
<div>
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:=
break-word">
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:=
break-word">
<div><span class=3D"m_-2137582900026257651Apple-style-span" style=3D"border-=
collapse:separate;line-height:normal;border-spacing:0px">
<div style=3D"word-wrap:break-word">
<div>
<div>
<div><br>
</div>
<div>@independentid</div>
<div><a moz-do-not-send=3D"true" href=3D"http://www.independentid.com" targe=
t=3D"_blank">www.independentid.com</a></div>
</div>
</div>
</div>
</span><a moz-do-not-send=3D"true" href=3D"mailto:phil.hunt@oracle.com" targ=
et=3D"_blank">phil.hunt@oracle.com</a></div>
<div><br>
</div>
</div>
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
</div>
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
</div>
<br>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a moz-do-not-send=3D"true" href=3D"mailto:Id-event@ietf.org">Id-event@ietf.=
org</a><br>
<a moz-do-not-send=3D"true" href=3D"https://www.ietf.org/mailman/listinfo/id=
-event" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<w=
br>listinfo/id-event</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset> <br>
<pre wrap=3D"">_______________________________________________
Id-event mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Id-event@ietf.org">Id-e=
vent@ietf.org</a><a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf=
.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/listinfo/id-eve=
nt</a></pre>
</blockquote>
<br>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>Id-event mailing list</span><br>
<span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www=
.ietf.org/mailman/listinfo/id-event</a></span><br>
</div>
</blockquote>
</div>
</div>
</span>


</div></blockquote></body></html>=

--Apple-Mail-53DE9CCE-874E-4F1E-B846-31ED7D3D404D--


From nobody Fri Sep 16 18:01:38 2016
Return-Path: <wdenniss@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C137112B100 for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 18:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level: 
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QcO2znyOzMYd for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 18:01:34 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE1D112B0A8 for <id-event@ietf.org>; Fri, 16 Sep 2016 18:01:33 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id g192so99840267ywh.1 for <id-event@ietf.org>; Fri, 16 Sep 2016 18:01:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IgFc9VgopJ4Up6SGYbuTkftVJQ8EWXCklJIs2MoVfGI=; b=f7PFBJU1vXghNtjXQDlGFoK524SgIpaxlJoKDRA4tbNKEkONCyHt3zwpoNLOrNgQzI dCdFi1f6TkBRWnWH0xsHNvBaomGCUuLBXmokAp1VXTaewcVWa1uBltvIocaxsaaX1gVz wglIbLEJcwlXD4Kmci00XDM+lKlyQahoNN7GFfU/1nZWnFwcS9Yo0ZR2tckDLslXtoxa xbRV1h7TYMeXs6Q+UoOFihqKASyDRnuMqe5U8VRyOMHQvytph1h5z0Ek3fa3O74/oeoQ bzOv8at4Mb7DtmrNB7XpYkK/jclYJcwB/Qz1hMjFz89hnkN8Vc6OzkUb3g1t3Y0CRoii 3WmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IgFc9VgopJ4Up6SGYbuTkftVJQ8EWXCklJIs2MoVfGI=; b=YjyG1pj1GiOvkZmOuuJICFO9l2uCWHIUox0EJeIT2ms2Sq8FO0o5Bse6VJltk8J2JY htp9YsTX2jWspaGENw0sJLysHsV5RAaBZOMptP/KbfIcJbkTfrM9wJ/qBkoK+Z+9j9U2 aNVOfAwnixdK3YqfuBLPgOT0nALV8ukod4kq0hbAfGkEz+7zrg2Ec1BaQ48ym/1YpXhQ f0QmRLyfJBtQOO5H5lOoboDDixIfAv7sjZzvrhbXpkSo34KgWsmRuuKJpa/izFAB1LJ7 GQd587rx5pMFNZgWcG34PmGC0WGD+wONcM+Td3fZ78gF7tRIkHHRLCtMt5nsjSZUSPo/ VDRA==
X-Gm-Message-State: AE9vXwNsRqMn98ZoGPhMYuL4ifuX9hUoP2Iwh5V5H3acmxDN3ZzLTEORmgsOW1eQvZv6V+zVYsSKW+9loX9x17cd
X-Received: by 10.13.236.196 with SMTP id v187mr16288527ywe.233.1474074092858;  Fri, 16 Sep 2016 18:01:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.108.143 with HTTP; Fri, 16 Sep 2016 18:01:12 -0700 (PDT)
In-Reply-To: <062AC5AC-AF95-4D0E-9427-1472732162F0@oracle.com>
References: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com> <CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com> <a42b8067-02f8-a9ba-ea86-d129a0546ed4@internet2.edu> <E6464A41-7619-4752-B5B6-F1EB54C03544@oracle.com> <D401B0FE.48BE7%moransar@cisco.com> <062AC5AC-AF95-4D0E-9427-1472732162F0@oracle.com>
From: William Denniss <wdenniss@google.com>
Date: Fri, 16 Sep 2016 18:01:12 -0700
Message-ID: <CAAP42hBmu+qB-F+ZJYqgc2Tct_mkgu-CH_h2OnJi=UMbkweyWQ@mail.gmail.com>
To: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary=94eb2c0840b6add1f1053ca99ed4
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/uEDDOjeASWZDcK_4fp_ReUgmsrA>
Cc: Nicholas Roy <nroy@internet2.edu>, "Morteza Ansari \(moransar\)" <moransar@cisco.com>, "id-event@ietf.org" <id-event@ietf.org>
Subject: Re: [Id-event] Proposed text for txn and ordering
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Sep 2016 01:01:37 -0000

--94eb2c0840b6add1f1053ca99ed4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

+1 looks good.

On Fri, Sep 16, 2016 at 5:34 PM, Phil Hunt (IDM) <phil.hunt@oracle.com>
wrote:

> Txn needs to be available in all types.
>
> Phil
>
> On Sep 16, 2016, at 2:26 PM, Morteza Ansari (moransar) <moransar@cisco.co=
m>
> wrote:
>
> Is this even something we could define for abstract events?  Doesn=E2=80=
=99t that
> semantics really associated with the type of event we are talking about? =
 I
> think this is a property that should be defined for a given type of event
> and not across all events.
>
>
> Cheers,
> Morteza
>
> From: Id-event <id-event-bounces@ietf.org> on behalf of Phil Hunt <
> phil.hunt@oracle.com>
> Date: Friday, September 16, 2016 at 2:00 PM
> To: Nicholas Roy <nroy@internet2.edu>
> Cc: "id-event@ietf.org" <id-event@ietf.org>
> Subject: Re: [Id-event] Proposed text for txn and ordering
>
> It occurs to me that the terminology for idempotency is wrong. Scim is
> idempotent in that any request can be repeated. However a series of
> transactions does have order and dependence.
>
> I will look for another way to express this or just drop the idempotence
> term.
>
> Phil
>
> On Sep 16, 2016, at 7:15 AM, Nicholas Roy <nroy@internet2.edu> wrote:
>
> +1
>
> Nick
>
> On 9/15/16 7:32 PM, Marius Scurtescu wrote:
>
> Sounds good to me.
>
> Marius
>
> On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <phil.hunt@oracle.com> wrote:
>
>> Based on the feedback, I am proposing the following changes:
>>
>> In the new attributes defined section, a new claim =E2=80=9Ctxn=E2=80=9D=
 defined:
>>
>>    txn
>>       An OPTIONAL single-valued String value that represents a unique
>>       transaction identifier.  In cases where multiple SETs are issued
>>       based on different event URIs, the transaction identifier MAY be
>>       used to correlate SETs to the same originating event or stateful
>>       change.
>>
>>
>> Regarding Ordering, I am proposing the following section:
>>
>> 2.2.  Idempotency and Ordering Considerations
>>
>>    In many cases SETs will be issued by highly distributed systems and
>>    subscribers.  Without additional specification it is quite
>>    conceivable that the order of SETs received by a subscriber MAY be
>>    different from the order of the originating state changes or events.
>>    While the "iat" value may give a rough indication of SET order, it
>>    SHOULD NOT be relied upon unless the profiling SET token
>>    specification provides clarification.
>>
>>    Profiling specifications are encouraged to consider whether the
>>    nature of SETs defined are "idempotent" in the sense that the order
>>    of receipt does not matter.  For example, in the case of token
>>    revocations, each SET can stand on its own and order has no impact.
>>    In contrast, a profiling SET specification related to provisioning
>>    might be highly dependent on ordering.  As an example: one SET
>>    indicates a new resource was created, while the next SET indicates
>>    the same resource is modified.  Non-Idempotent SET event
>>    specifications SHOULD choose to define a sequencing method such as aa
>>    claim used for the purpose or identifying the order of SETs as
>>    defined by the Feed Publisher or another method that is part of how
>>    SETs are distributed.
>>
>> Thanks for your feedback.
>>
>> Phil
>>
>> @independentid
>> www.independentid.com
>> phil.hunt@oracle.com
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>>
>
>
> _______________________________________________
> Id-event mailing listId-event@ietf.orghttps://www.ietf.org/mailman/listin=
fo/id-event
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>

--94eb2c0840b6add1f1053ca99ed4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">+1 looks good.</div><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Fri, Sep 16, 2016 at 5:34 PM, Phil Hunt (IDM) <span =
dir=3D"ltr">&lt;<a href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">p=
hil.hunt@oracle.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div dir=3D"auto"><div><div style=3D"direction:inherit">Txn needs to be av=
ailable in all types.=C2=A0</div><span class=3D"HOEnZb"><font color=3D"#888=
888"><br>Phil</font></span></div><div><div class=3D"h5"><div><br>On Sep 16,=
 2016, at 2:26 PM, Morteza Ansari (moransar) &lt;<a href=3D"mailto:moransar=
@cisco.com" target=3D"_blank">moransar@cisco.com</a>&gt; wrote:<br><br></di=
v><blockquote type=3D"cite"><div>




<div>Is this even something we could define for abstract events?=C2=A0 Does=
n=E2=80=99t that semantics really associated with the type of event we are =
talking about?=C2=A0 I think this is a property that should be defined for =
a given type of event and not across all events.</div>
<div><br>
</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Morteza</div>
<div><br>
</div>
<span id=3D"m_1847120859978767373OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri;font-size:11pt;text-align:left;color:blac=
k;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADD=
ING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:me=
dium none;PADDING-TOP:3pt">
<span style=3D"font-weight:bold">From: </span>Id-event &lt;<a href=3D"mailt=
o:id-event-bounces@ietf.org" target=3D"_blank">id-event-bounces@ietf.org</a=
>&gt; on behalf of Phil Hunt &lt;<a href=3D"mailto:phil.hunt@oracle.com" ta=
rget=3D"_blank">phil.hunt@oracle.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday, September 16, 2016 at=
 2:00 PM<br>
<span style=3D"font-weight:bold">To: </span>Nicholas Roy &lt;<a href=3D"mai=
lto:nroy@internet2.edu" target=3D"_blank">nroy@internet2.edu</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:id-even=
t@ietf.org" target=3D"_blank">id-event@ietf.org</a>&quot; &lt;<a href=3D"ma=
ilto:id-event@ietf.org" target=3D"_blank">id-event@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [Id-event] Proposed te=
xt for txn and ordering<br>
</div>
<div><br>
</div>
<div>
<div dir=3D"auto">
<div>
<div style=3D"direction:inherit">It occurs to me that the terminology for i=
dempotency is wrong. Scim is idempotent in that any request can be repeated=
. However a series of transactions does have order and dependence.=C2=A0</d=
iv>
<div style=3D"direction:inherit"><br>
</div>
<div style=3D"direction:inherit">I will look for another way to express thi=
s or just drop the idempotence term.=C2=A0</div>
<br>
Phil</div>
<div><br>
On Sep 16, 2016, at 7:15 AM, Nicholas Roy &lt;<a href=3D"mailto:nroy@intern=
et2.edu" target=3D"_blank">nroy@internet2.edu</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>+1<br>
<br>
Nick<br>
<br>
<div class=3D"m_1847120859978767373moz-cite-prefix">On 9/15/16 7:32 PM, Mar=
ius Scurtescu wrote:<br>
</div>
<blockquote type=3D"cite">
<div dir=3D"ltr">Sounds good to me.</div>
<div class=3D"gmail_extra"><br clear=3D"all">
<div>
<div class=3D"m_1847120859978767373gmail_signature" data-smartmail=3D"gmail=
_signature">Marius</div>
</div>
<br>
<div class=3D"gmail_quote">On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <span=
 dir=3D"ltr">
&lt;<a href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">phil.hunt@ora=
cle.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">Based on the feedback, I am proposing t=
he following changes:
<div><br>
</div>
<div>In the new attributes defined section, a new claim =E2=80=9Ctxn=E2=80=
=9D defined:</div>
<div>
<div style=3D"margin:0px;font-size:11px;line-height:normal;font-family:Mona=
co">
<pre style=3D"word-wrap:break-word;white-space:pre-wrap">   txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.
</pre>
<div><br>
</div>
</div>
<div>Regarding Ordering, I am proposing the following section:</div>
<div>
<pre style=3D"word-wrap:break-word;white-space:pre-wrap"><span style=3D"fon=
t-size:11px">2.2.  Idempotency and Ordering Considerations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the &quot;iat&quot; value may give a rough indication of SET order=
, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are &quot;idempotent&quot; in the sense that the =
order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.</span></pre>
</div>
<div>Thanks for your feedback.</div>
<div><br>
</div>
<div>Phil</div>
<div>
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wra=
p:break-word">
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wra=
p:break-word">
<div><span class=3D"m_1847120859978767373m_-2137582900026257651Apple-style-=
span" style=3D"border-collapse:separate;line-height:normal;border-spacing:0=
px">
<div style=3D"word-wrap:break-word">
<div>
<div>
<div><br>
</div>
<div>@independentid</div>
<div><a href=3D"http://www.independentid.com" target=3D"_blank">www.indepen=
dentid.com</a></div>
</div>
</div>
</div>
</span><a href=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">phil.hunt@=
oracle.com</a></div>
<div><br>
</div>
</div>
<br class=3D"m_1847120859978767373m_-2137582900026257651Apple-interchange-n=
ewline">
</div>
<br class=3D"m_1847120859978767373m_-2137582900026257651Apple-interchange-n=
ewline">
<br class=3D"m_1847120859978767373m_-2137582900026257651Apple-interchange-n=
ewline">
</div>
<br>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/id-event</a=
><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class=3D"m_1847120859978767373mimeAttachmentHeader"></fieldset> <=
br>
<pre>______________________________<wbr>_________________
Id-event mailing list
<a class=3D"m_1847120859978767373moz-txt-link-abbreviated" href=3D"mailto:I=
d-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a><a class=3D"m_1847=
120859978767373moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/=
listinfo/id-event" target=3D"_blank">https://www.<wbr>ietf.org/mailman/list=
info/id-<wbr>event</a></pre>
</blockquote>
<br>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>______________________________<wbr>_________________</span><br>
<span>Id-event mailing list</span><br>
<span><a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.=
org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"=
_blank">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a></span><br>
</div>
</blockquote>
</div>
</div>
</span>


</div></blockquote></div></div></div><br>______________________________<wbr=
>_________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/id-event</a=
><br>
<br></blockquote></div><br></div>

--94eb2c0840b6add1f1053ca99ed4--


From nobody Fri Sep 16 19:46:10 2016
Return-Path: <moransar@cisco.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 449FA12B217 for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 19:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.028
X-Spam-Level: 
X-Spam-Status: No, score=-16.028 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rwa3lhLhHOJx for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 19:46:07 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E90F12B037 for <id-event@ietf.org>; Fri, 16 Sep 2016 19:46:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13066; q=dns/txt; s=iport; t=1474080367; x=1475289967; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=MRTbjc67cfLUwuo6xynHKohcSqECoc+NXbx/EBc69eI=; b=Y0kvxxKa31DNkryLSScL5odXK1U5TPo1wNvkTSahKbVFIP/syhWyAKCn OvIjg3PCQLHjw/22C2u7jdbWl0MQNakBCcNWyLH7LFgL1c2OYSnGqjg0s ZFgA7U3GiPAooiI6H+SdUO9E7iVCfDUpETrmfm7O4Yn3q6g/KTqUspBMW U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CAAQD+rdxX/4MNJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgwczAQEBAQEeV3yNM6YqhQ+CAxkBCoV6AoFIOBQBAgEBAQEBAQF?= =?us-ascii?q?eJ4RhAQEBBAEBAUYlCxACAQgRAwECKAcnCxQJCAIEDgUJiEEOwUYBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEchjaBfIJYhGQegm+CLwWUGIVVAYkmhjSPaIxhg3oBHja?= =?us-ascii?q?CR4IjcocdAQEB?=
X-IronPort-AV: E=Sophos;i="5.30,348,1470700800";  d="scan'208,217";a="323831963"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Sep 2016 02:45:53 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u8H2jrNw022168 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 17 Sep 2016 02:45:53 GMT
Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 16 Sep 2016 21:45:52 -0500
Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1210.000; Fri, 16 Sep 2016 21:45:52 -0500
From: "Morteza Ansari (moransar)" <moransar@cisco.com>
To: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
Thread-Topic: [Id-event] Proposed text for txn and ordering
Thread-Index: AQHSD6CP/7SKqh+/bkeTKJuTonDJdKB7qQWAgADVF4CAAHERAP//keCAgACqDYD//9DbiA==
Date: Sat, 17 Sep 2016 02:45:52 +0000
Message-ID: <D085C3EE-2F98-47C8-A96B-0616C2CAB9DF@cisco.com>
References: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com> <CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com> <a42b8067-02f8-a9ba-ea86-d129a0546ed4@internet2.edu> <E6464A41-7619-4752-B5B6-F1EB54C03544@oracle.com> <D401B0FE.48BE7%moransar@cisco.com>, <062AC5AC-AF95-4D0E-9427-1472732162F0@oracle.com>
In-Reply-To: <062AC5AC-AF95-4D0E-9427-1472732162F0@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_D085C3EE2F9847C8A96B0616C2CAB9DFciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/HKiajOLDAY9jRwI6d-32bRDO2v4>
Cc: Nicholas Roy <nroy@internet2.edu>, "id-event@ietf.org" <id-event@ietf.org>
Subject: Re: [Id-event] Proposed text for txn and ordering
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Sep 2016 02:46:09 -0000

--_000_D085C3EE2F9847C8A96B0616C2CAB9DFciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Yes, I agree on that front. I was talking about semantics around txn such a=
s idempotency.


Cheers,
Morteza

On Sep 16, 2016, at 5:34 PM, Phil Hunt (IDM) <phil.hunt@oracle.com<mailto:p=
hil.hunt@oracle.com>> wrote:

Txn needs to be available in all types.

Phil

On Sep 16, 2016, at 2:26 PM, Morteza Ansari (moransar) <moransar@cisco.com<=
mailto:moransar@cisco.com>> wrote:

Is this even something we could define for abstract events?  Doesn't that s=
emantics really associated with the type of event we are talking about?  I =
think this is a property that should be defined for a given type of event a=
nd not across all events.


Cheers,
Morteza

From: Id-event <id-event-bounces@ietf.org<mailto:id-event-bounces@ietf.org>=
> on behalf of Phil Hunt <phil.hunt@oracle.com<mailto:phil.hunt@oracle.com>=
>
Date: Friday, September 16, 2016 at 2:00 PM
To: Nicholas Roy <nroy@internet2.edu<mailto:nroy@internet2.edu>>
Cc: "id-event@ietf.org<mailto:id-event@ietf.org>" <id-event@ietf.org<mailto=
:id-event@ietf.org>>
Subject: Re: [Id-event] Proposed text for txn and ordering

It occurs to me that the terminology for idempotency is wrong. Scim is idem=
potent in that any request can be repeated. However a series of transaction=
s does have order and dependence.

I will look for another way to express this or just drop the idempotence te=
rm.

Phil

On Sep 16, 2016, at 7:15 AM, Nicholas Roy <nroy@internet2.edu<mailto:nroy@i=
nternet2.edu>> wrote:

+1

Nick

On 9/15/16 7:32 PM, Marius Scurtescu wrote:
Sounds good to me.

Marius

On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <phil.hunt@oracle.com<mailto:phi=
l.hunt@oracle.com>> wrote:
Based on the feedback, I am proposing the following changes:

In the new attributes defined section, a new claim "txn" defined:

   txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.


Regarding Ordering, I am proposing the following section:

2.2.  Idempotency and Ordering Considerations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the "iat" value may give a rough indication of SET order, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are "idempotent" in the sense that the order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.

Thanks for your feedback.

Phil

@independentid
www.independentid.com<http://www.independentid.com>
phil.hunt@oracle.com<mailto:phil.hunt@oracle.com>






_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>
https://www.ietf.org/mailman/listinfo/id-event





_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>https://www.ietf.org/mailman/lis=
tinfo/id-event

_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>
https://www.ietf.org/mailman/listinfo/id-event

--_000_D085C3EE2F9847C8A96B0616C2CAB9DFciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>Yes, I agree on that front. I was talking about semantics around txn s=
uch as
<span style=3D"background-color: rgba(255, 255, 255, 0);">idempotency.&nbsp=
;</span><br>
<br>
<div><br>
</div>
Cheers,
<div>Morteza</div>
</div>
<div><br>
On Sep 16, 2016, at 5:34 PM, Phil Hunt (IDM) &lt;<a href=3D"mailto:phil.hun=
t@oracle.com">phil.hunt@oracle.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div>
<div style=3D"direction: inherit;">Txn needs to be available in all types.&=
nbsp;</div>
<br>
Phil</div>
<div><br>
On Sep 16, 2016, at 2:26 PM, Morteza Ansari (moransar) &lt;<a href=3D"mailt=
o:moransar@cisco.com">moransar@cisco.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div>Is this even something we could define for abstract events? &nbsp;Does=
n&#8217;t that semantics really associated with the type of event we are ta=
lking about? &nbsp;I think this is a property that should be defined for a =
given type of event and not across all events.</div>
<div><br>
</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Morteza</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Id-event &lt;<a href=3D"mailt=
o:id-event-bounces@ietf.org">id-event-bounces@ietf.org</a>&gt; on behalf of=
 Phil Hunt &lt;<a href=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.com=
</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday, September 16, 2016 at=
 2:00 PM<br>
<span style=3D"font-weight:bold">To: </span>Nicholas Roy &lt;<a href=3D"mai=
lto:nroy@internet2.edu">nroy@internet2.edu</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:id-even=
t@ietf.org">id-event@ietf.org</a>&quot; &lt;<a href=3D"mailto:id-event@ietf=
.org">id-event@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [Id-event] Proposed te=
xt for txn and ordering<br>
</div>
<div><br>
</div>
<div>
<div dir=3D"auto">
<div>
<div style=3D"direction: inherit;">It occurs to me that the terminology for=
 idempotency is wrong. Scim is idempotent in that any request can be repeat=
ed. However a series of transactions does have order and dependence.&nbsp;<=
/div>
<div style=3D"direction: inherit;"><br>
</div>
<div style=3D"direction: inherit;">I will look for another way to express t=
his or just drop the idempotence term.&nbsp;</div>
<br>
Phil</div>
<div><br>
On Sep 16, 2016, at 7:15 AM, Nicholas Roy &lt;<a href=3D"mailto:nroy@intern=
et2.edu">nroy@internet2.edu</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>&#43;1<br>
<br>
Nick<br>
<br>
<div class=3D"moz-cite-prefix">On 9/15/16 7:32 PM, Marius Scurtescu wrote:<=
br>
</div>
<blockquote cite=3D"mid:CAGdjJp&#43;ndWYiPYb0KPN-TFh&#43;SN-hqR8JBO6poVWAT_=
OPEEomaw@mail.gmail.com" type=3D"cite">
<div dir=3D"ltr">Sounds good to me.</div>
<div class=3D"gmail_extra"><br clear=3D"all">
<div>
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">Marius</d=
iv>
</div>
<br>
<div class=3D"gmail_quote">On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <span=
 dir=3D"ltr">
&lt;<a moz-do-not-send=3D"true" href=3D"mailto:phil.hunt@oracle.com" target=
=3D"_blank">phil.hunt@oracle.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">Based on the feedback, I am proposing t=
he following changes:
<div><br>
</div>
<div>In the new attributes defined section, a new claim &#8220;txn&#8221; d=
efined:</div>
<div>
<div style=3D"margin:0px;font-size:11px;line-height:normal;font-family:Mona=
co">
<pre style=3D"word-wrap:break-word;white-space:pre-wrap">   txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.
</pre>
<div><br>
</div>
</div>
<div>Regarding Ordering, I am proposing the following section:</div>
<div>
<pre style=3D"word-wrap:break-word;white-space:pre-wrap"><span style=3D"fon=
t-size:11px">2.2.  Idempotency and Ordering Considerations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the &quot;iat&quot; value may give a rough indication of SET order=
, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are &quot;idempotent&quot; in the sense that the =
order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.</span></pre>
</div>
<div>Thanks for your feedback.</div>
<div><br>
</div>
<div>Phil</div>
<div>
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wra=
p:break-word">
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wra=
p:break-word">
<div><span class=3D"m_-2137582900026257651Apple-style-span" style=3D"border=
-collapse:separate;line-height:normal;border-spacing:0px">
<div style=3D"word-wrap:break-word">
<div>
<div>
<div><br>
</div>
<div>@independentid</div>
<div><a moz-do-not-send=3D"true" href=3D"http://www.independentid.com" targ=
et=3D"_blank">www.independentid.com</a></div>
</div>
</div>
</div>
</span><a moz-do-not-send=3D"true" href=3D"mailto:phil.hunt@oracle.com" tar=
get=3D"_blank">phil.hunt@oracle.com</a></div>
<div><br>
</div>
</div>
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
</div>
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
</div>
<br>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a moz-do-not-send=3D"true" href=3D"mailto:Id-event@ietf.org">Id-event@ietf=
.org</a><br>
<a moz-do-not-send=3D"true" href=3D"https://www.ietf.org/mailman/listinfo/i=
d-event" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/=
<wbr>listinfo/id-event</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset> <br>
<pre wrap=3D"">_______________________________________________
Id-event mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Id-event@ietf.org">Id-=
event@ietf.org</a><a class=3D"moz-txt-link-freetext" href=3D"https://www.ie=
tf.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/listinfo/id-=
event</a></pre>
</blockquote>
<br>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>Id-event mailing list</span><br>
<span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://ww=
w.ietf.org/mailman/listinfo/id-event</a></span><br>
</div>
</blockquote>
</div>
</div>
</span></div>
</blockquote>
</div>
</blockquote>
</body>
</html>

--_000_D085C3EE2F9847C8A96B0616C2CAB9DFciscocom_--


From nobody Fri Sep 16 19:57:56 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2289E12B217 for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 19:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level: 
X-Spam-Status: No, score=-5.727 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mNH1oYQLDmvw for <id-event@ietfa.amsl.com>; Fri, 16 Sep 2016 19:57:52 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C50FD12B037 for <id-event@ietf.org>; Fri, 16 Sep 2016 19:57:52 -0700 (PDT)
Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8H2voOi019479 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 17 Sep 2016 02:57:51 GMT
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0022.oracle.com (8.14.4/8.13.8) with ESMTP id u8H2vown003706 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 17 Sep 2016 02:57:50 GMT
Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u8H2vnoB000593; Sat, 17 Sep 2016 02:57:49 GMT
Received: from [25.136.180.140] (/24.114.104.159) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 16 Sep 2016 19:57:49 -0700
Content-Type: multipart/alternative; boundary=Apple-Mail-BA2B530D-194B-4F22-940A-075827E4CADB
Mime-Version: 1.0 (1.0)
From: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
X-Mailer: iPhone Mail (14A403)
In-Reply-To: <D085C3EE-2F98-47C8-A96B-0616C2CAB9DF@cisco.com>
Date: Fri, 16 Sep 2016 19:57:43 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <21A579E3-A659-42EF-96E9-92EBCFF250AE@oracle.com>
References: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com> <CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com> <a42b8067-02f8-a9ba-ea86-d129a0546ed4@internet2.edu> <E6464A41-7619-4752-B5B6-F1EB54C03544@oracle.com> <D401B0FE.48BE7%moransar@cisco.com> <062AC5AC-AF95-4D0E-9427-1472732162F0@oracle.com> <D085C3EE-2F98-47C8-A96B-0616C2CAB9DF@cisco.com>
To: "Morteza Ansari (moransar)" <moransar@cisco.com>
X-Source-IP: userv0022.oracle.com [156.151.31.74]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/CTt6wa-QF9l7Vw2Q9TPp5H6rfG8>
Cc: Nicholas Roy <nroy@internet2.edu>, "id-event@ietf.org" <id-event@ietf.org>
Subject: Re: [Id-event] Proposed text for txn and ordering
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Sep 2016 02:57:55 -0000

--Apple-Mail-BA2B530D-194B-4F22-940A-075827E4CADB
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

:)

Phil

> On Sep 16, 2016, at 7:45 PM, Morteza Ansari (moransar) <moransar@cisco.com=
> wrote:
>=20
> Yes, I agree on that front. I was talking about semantics around txn such a=
s idempotency.=20
>=20
>=20
> Cheers,
> Morteza
>=20
> On Sep 16, 2016, at 5:34 PM, Phil Hunt (IDM) <phil.hunt@oracle.com> wrote:=

>=20
>> Txn needs to be available in all types.=20
>>=20
>> Phil
>>=20
>> On Sep 16, 2016, at 2:26 PM, Morteza Ansari (moransar) <moransar@cisco.co=
m> wrote:
>>=20
>>> Is this even something we could define for abstract events?  Doesn=E2=80=
=99t that semantics really associated with the type of event we are talking a=
bout?  I think this is a property that should be defined for a given type of=
 event and not across all events.
>>>=20
>>>=20
>>> Cheers,
>>> Morteza
>>>=20
>>> From: Id-event <id-event-bounces@ietf.org> on behalf of Phil Hunt <phil.=
hunt@oracle.com>
>>> Date: Friday, September 16, 2016 at 2:00 PM
>>> To: Nicholas Roy <nroy@internet2.edu>
>>> Cc: "id-event@ietf.org" <id-event@ietf.org>
>>> Subject: Re: [Id-event] Proposed text for txn and ordering
>>>=20
>>> It occurs to me that the terminology for idempotency is wrong. Scim is i=
dempotent in that any request can be repeated. However a series of transacti=
ons does have order and dependence.=20
>>>=20
>>> I will look for another way to express this or just drop the idempotence=
 term.=20
>>>=20
>>> Phil
>>>=20
>>> On Sep 16, 2016, at 7:15 AM, Nicholas Roy <nroy@internet2.edu> wrote:
>>>=20
>>>> +1
>>>>=20
>>>> Nick
>>>>=20
>>>>> On 9/15/16 7:32 PM, Marius Scurtescu wrote:
>>>>> Sounds good to me.
>>>>>=20
>>>>> Marius
>>>>>=20
>>>>>> On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <phil.hunt@oracle.com> wro=
te:
>>>>>> Based on the feedback, I am proposing the following changes:
>>>>>>=20
>>>>>> In the new attributes defined section, a new claim =E2=80=9Ctxn=E2=80=
=9D defined:
>>>>>>    txn
>>>>>>       An OPTIONAL single-valued String value that represents a unique=

>>>>>>       transaction identifier.  In cases where multiple SETs are issue=
d
>>>>>>       based on different event URIs, the transaction identifier MAY b=
e
>>>>>>       used to correlate SETs to the same originating event or statefu=
l
>>>>>>       change.
>>>>>>=20
>>>>>> Regarding Ordering, I am proposing the following section:
>>>>>> 2.2.  Idempotency and Ordering Considerations
>>>>>>=20
>>>>>>    In many cases SETs will be issued by highly distributed systems an=
d
>>>>>>    subscribers.  Without additional specification it is quite
>>>>>>    conceivable that the order of SETs received by a subscriber MAY be=

>>>>>>    different from the order of the originating state changes or event=
s.
>>>>>>    While the "iat" value may give a rough indication of SET order, it=

>>>>>>    SHOULD NOT be relied upon unless the profiling SET token
>>>>>>    specification provides clarification.
>>>>>>=20
>>>>>>    Profiling specifications are encouraged to consider whether the
>>>>>>    nature of SETs defined are "idempotent" in the sense that the orde=
r
>>>>>>    of receipt does not matter.  For example, in the case of token
>>>>>>    revocations, each SET can stand on its own and order has no impact=
.
>>>>>>    In contrast, a profiling SET specification related to provisioning=

>>>>>>    might be highly dependent on ordering.  As an example: one SET
>>>>>>    indicates a new resource was created, while the next SET indicates=

>>>>>>    the same resource is modified.  Non-Idempotent SET event
>>>>>>    specifications SHOULD choose to define a sequencing method such as=
 aa
>>>>>>    claim used for the purpose or identifying the order of SETs as
>>>>>>    defined by the Feed Publisher or another method that is part of ho=
w
>>>>>>    SETs are distributed.
>>>>>> Thanks for your feedback.
>>>>>>=20
>>>>>> Phil
>>>>>>=20
>>>>>> @independentid
>>>>>> www.independentid.com
>>>>>> phil.hunt@oracle.com
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> Id-event mailing list
>>>>>> Id-event@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/id-event
>>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> Id-event mailing list
>>>>> Id-event@ietf.orghttps://www.ietf.org/mailman/listinfo/id-event
>>>>=20
>>>> _______________________________________________
>>>> Id-event mailing list
>>>> Id-event@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/id-event

--Apple-Mail-BA2B530D-194B-4F22-940A-075827E4CADB
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><div style=3D"direction: inherit;">:)<=
/div><br>Phil</div><div><br>On Sep 16, 2016, at 7:45 PM, Morteza Ansari (mor=
ansar) &lt;<a href=3D"mailto:moransar@cisco.com">moransar@cisco.com</a>&gt; w=
rote:<br><br></div><blockquote type=3D"cite"><div>

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">=



<div>Yes, I agree on that front. I was talking about semantics around txn su=
ch as
<span style=3D"background-color: rgba(255, 255, 255, 0);">idempotency.&nbsp;=
</span><br>
<br>
<div><br>
</div>
Cheers,
<div>Morteza</div>
</div>
<div><br>
On Sep 16, 2016, at 5:34 PM, Phil Hunt (IDM) &lt;<a href=3D"mailto:phil.hunt=
@oracle.com">phil.hunt@oracle.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div>
<div style=3D"direction: inherit;">Txn needs to be available in all types.&n=
bsp;</div>
<br>
Phil</div>
<div><br>
On Sep 16, 2016, at 2:26 PM, Morteza Ansari (moransar) &lt;<a href=3D"mailto=
:moransar@cisco.com">moransar@cisco.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div>Is this even something we could define for abstract events? &nbsp;Doesn=
=E2=80=99t that semantics really associated with the type of event we are ta=
lking about? &nbsp;I think this is a property that should be defined for a g=
iven type of event and not across all events.</div>
<div><br>
</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Morteza</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:bl=
ack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0=
in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BO=
RDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Id-event &lt;<a href=3D"mailto=
:id-event-bounces@ietf.org">id-event-bounces@ietf.org</a>&gt; on behalf of P=
hil Hunt &lt;<a href=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.com</a=
>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday, September 16, 2016 at 2=
:00 PM<br>
<span style=3D"font-weight:bold">To: </span>Nicholas Roy &lt;<a href=3D"mail=
to:nroy@internet2.edu">nroy@internet2.edu</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>"<a href=3D"mailto:id-event@ietf=
.org">id-event@ietf.org</a>" &lt;<a href=3D"mailto:id-event@ietf.org">id-eve=
nt@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [Id-event] Proposed tex=
t for txn and ordering<br>
</div>
<div><br>
</div>
<div>
<div dir=3D"auto">
<div>
<div style=3D"direction: inherit;">It occurs to me that the terminology for i=
dempotency is wrong. Scim is idempotent in that any request can be repeated.=
 However a series of transactions does have order and dependence.&nbsp;</div=
>
<div style=3D"direction: inherit;"><br>
</div>
<div style=3D"direction: inherit;">I will look for another way to express th=
is or just drop the idempotence term.&nbsp;</div>
<br>
Phil</div>
<div><br>
On Sep 16, 2016, at 7:15 AM, Nicholas Roy &lt;<a href=3D"mailto:nroy@interne=
t2.edu">nroy@internet2.edu</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>+1<br>
<br>
Nick<br>
<br>
<div class=3D"moz-cite-prefix">On 9/15/16 7:32 PM, Marius Scurtescu wrote:<b=
r>
</div>
<blockquote cite=3D"mid:CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@=
mail.gmail.com" type=3D"cite">
<div dir=3D"ltr">Sounds good to me.</div>
<div class=3D"gmail_extra"><br clear=3D"all">
<div>
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">Marius</di=
v>
</div>
<br>
<div class=3D"gmail_quote">On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <span d=
ir=3D"ltr">
&lt;<a moz-do-not-send=3D"true" href=3D"mailto:phil.hunt@oracle.com" target=3D=
"_blank">phil.hunt@oracle.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">Based on the feedback, I am proposing th=
e following changes:
<div><br>
</div>
<div>In the new attributes defined section, a new claim =E2=80=9Ctxn=E2=80=9D=
 defined:</div>
<div>
<div style=3D"margin:0px;font-size:11px;line-height:normal;font-family:Monac=
o">
<pre style=3D"word-wrap:break-word;white-space:pre-wrap">   txn
      An OPTIONAL single-valued String value that represents a unique
      transaction identifier.  In cases where multiple SETs are issued
      based on different event URIs, the transaction identifier MAY be
      used to correlate SETs to the same originating event or stateful
      change.
</pre>
<div><br>
</div>
</div>
<div>Regarding Ordering, I am proposing the following section:</div>
<div>
<pre style=3D"word-wrap:break-word;white-space:pre-wrap"><span style=3D"font=
-size:11px">2.2.  Idempotency and Ordering Considerations

   In many cases SETs will be issued by highly distributed systems and
   subscribers.  Without additional specification it is quite
   conceivable that the order of SETs received by a subscriber MAY be
   different from the order of the originating state changes or events.
   While the "iat" value may give a rough indication of SET order, it
   SHOULD NOT be relied upon unless the profiling SET token
   specification provides clarification.

   Profiling specifications are encouraged to consider whether the
   nature of SETs defined are "idempotent" in the sense that the order
   of receipt does not matter.  For example, in the case of token
   revocations, each SET can stand on its own and order has no impact.
   In contrast, a profiling SET specification related to provisioning
   might be highly dependent on ordering.  As an example: one SET
   indicates a new resource was created, while the next SET indicates
   the same resource is modified.  Non-Idempotent SET event
   specifications SHOULD choose to define a sequencing method such as aa
   claim used for the purpose or identifying the order of SETs as
   defined by the Feed Publisher or another method that is part of how
   SETs are distributed.</span></pre>
</div>
<div>Thanks for your feedback.</div>
<div><br>
</div>
<div>Phil</div>
<div>
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:=
break-word">
<div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:=
break-word">
<div><span class=3D"m_-2137582900026257651Apple-style-span" style=3D"border-=
collapse:separate;line-height:normal;border-spacing:0px">
<div style=3D"word-wrap:break-word">
<div>
<div>
<div><br>
</div>
<div>@independentid</div>
<div><a moz-do-not-send=3D"true" href=3D"http://www.independentid.com" targe=
t=3D"_blank">www.independentid.com</a></div>
</div>
</div>
</div>
</span><a moz-do-not-send=3D"true" href=3D"mailto:phil.hunt@oracle.com" targ=
et=3D"_blank">phil.hunt@oracle.com</a></div>
<div><br>
</div>
</div>
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
</div>
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
<br class=3D"m_-2137582900026257651Apple-interchange-newline">
</div>
<br>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
Id-event mailing list<br>
<a moz-do-not-send=3D"true" href=3D"mailto:Id-event@ietf.org">Id-event@ietf.=
org</a><br>
<a moz-do-not-send=3D"true" href=3D"https://www.ietf.org/mailman/listinfo/id=
-event" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<w=
br>listinfo/id-event</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset> <br>
<pre wrap=3D"">_______________________________________________
Id-event mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Id-event@ietf.org">Id-e=
vent@ietf.org</a><a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf=
.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/listinfo/id-eve=
nt</a></pre>
</blockquote>
<br>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>Id-event mailing list</span><br>
<span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www=
.ietf.org/mailman/listinfo/id-event</a></span><br>
</div>
</blockquote>
</div>
</div>
</span></div>
</blockquote>
</div>
</blockquote>


</div></blockquote></body></html>=

--Apple-Mail-BA2B530D-194B-4F22-940A-075827E4CADB--


From nobody Sun Sep 18 16:56:52 2016
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86195128E19 for <id-event@ietfa.amsl.com>; Sun, 18 Sep 2016 16:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lR_CrwaN2mNi for <id-event@ietfa.amsl.com>; Sun, 18 Sep 2016 16:56:48 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0092.outbound.protection.outlook.com [104.47.37.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2AB912B097 for <id-event@ietf.org>; Sun, 18 Sep 2016 16:56:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=R3mJ0L1DDc66AE/FiWq+9p+ZA3ZNU1JL0FmahGAgj0g=; b=Qu+mKqzTtb0P7QO/v6WoJTztc1tYHKwkUPrpyiJvjH348hj4e1vlqeWMua4zuwOiXkX6fQuLqPEeMr2zcnO00lukBicH7zEvHNXR9C8sOT+vNdEjcLVEm+6Yyku0as0xjYQQ9Lntca665j0ajvYmrx4/aqEV3UJTdiIT3fj+Jd0=
Received: from BN3PR03MB2355.namprd03.prod.outlook.com (10.166.74.150) by BN3PR03MB2356.namprd03.prod.outlook.com (10.166.74.151) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.599.9; Sun, 18 Sep 2016 23:56:45 +0000
Received: from BN3PR03MB2355.namprd03.prod.outlook.com ([10.166.74.150]) by BN3PR03MB2355.namprd03.prod.outlook.com ([10.166.74.150]) with mapi id 15.01.0599.016; Sun, 18 Sep 2016 23:56:45 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "Phil Hunt (IDM)" <phil.hunt@oracle.com>, "Morteza Ansari (moransar)" <moransar@cisco.com>
Thread-Topic: [Id-event] Proposed text for txn and ordering
Thread-Index: AQHSD6CP7UtvIMrsrk+G87XGJbnpXaB7VTSAgADVFoCAAHERAIAABzoAgAA0s4CAACSsAIAAA0+AgALv0ZA=
Date: Sun, 18 Sep 2016 23:56:45 +0000
Message-ID: <BN3PR03MB23550A34902ADE3D4FCCB787F5F50@BN3PR03MB2355.namprd03.prod.outlook.com>
References: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com> <CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com> <a42b8067-02f8-a9ba-ea86-d129a0546ed4@internet2.edu> <E6464A41-7619-4752-B5B6-F1EB54C03544@oracle.com> <D401B0FE.48BE7%moransar@cisco.com> <062AC5AC-AF95-4D0E-9427-1472732162F0@oracle.com> <D085C3EE-2F98-47C8-A96B-0616C2CAB9DF@cisco.com> <21A579E3-A659-42EF-96E9-92EBCFF250AE@oracle.com>
In-Reply-To: <21A579E3-A659-42EF-96E9-92EBCFF250AE@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michael.Jones@microsoft.com; 
x-originating-ip: [12.130.119.130]
x-ms-office365-filtering-correlation-id: b9f2af1f-64b5-4e4d-b9b7-08d3e01f7274
x-microsoft-exchange-diagnostics: 1; BN3PR03MB2356; 6:lxILVq7EVQaWzZPFEM7ZPmChCzIGLxQpC+EP/zprS1bGc30Ex49ILXHpCscBhmsocwy0ql5JVa6KSF1LKyiYjCAChVLFlOexqknMbhvUBYlRdIpCL2YVm01QE9O2BuiyFNMm+X3FTFlSDonGfDK3CC3duTcV1R97xA3OYlxaq4t/4Z19n5ubLwsM6Zi9/5BUvVQ8Co2r9vDqCgIjgEUWIgzaV+6IosO9Oc7nT+ufQVjTYBqLcvWRhFIg1jj2tY+JzHt7fYHv3QrYRsjvLs9Uh0+754LWuebCnOD3qOIlxdHHIWiqZur8ZETlWP8YLMSBnZmC6XkaAuis4viqyKAKaQ==; 5:CgNC6KNnOe+Xbb6LyYqcwYWxMVfAlqIHxC1raOtykuyRy8zljBSNAOEJ+DBd8wpM01cgZWrBCzVMLbZoXrwGhZ4EYwx/rh5ww3BDL2RAyWFmtVAWDynQltBq47LuZwJWYd2orQf7QrKGsF6JFXD4Xw==; 24:63mtrMi2iuVaqB2IbVK2E+JZKJ6ewatB+yFpyInEgY9na4rM5xgEMLa08btPEeLwHH6t3mjV5v5wF+rSCmPsKo6IiPuXr1p4klebPYnsCu0=; 7:OGapZHWOjyJFnla8eIJyPSWOLy+VKc/4E4UYtoJU2tIOaaTaaWwrnQPN3xJ/XmrgSGNmjqQdpDlA6YRw1z1v6SxiIP5xZsoIVGcL6NbfpnV7+S032Nr1wk9NQm9K+x5lbemwxg2ifgncw3EcLb6+y1DtlAn7y5eGFVNkMIHZdufDVvm2oS//qtwSnzv5Mi7q5Ep1Fao4S3hwINlw7ajeXgDrcc4IL0XvSWL/FwCNqRKL2Zw9VoTjIy0Ip7Zv3Tkh5bmw8S9UbhobXdIkY5z3JcKVWyUiyo6pkk0XtLSjqKhvP5RGut9ciSTO6B/pLB/X
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN3PR03MB2356;
x-microsoft-antispam-prvs: <BN3PR03MB23562F93CE6E5785FF92F4E0F5F50@BN3PR03MB2356.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(95692535739014)(21748063052155)(146099531331640); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(61426038)(61427038); SRVR:BN3PR03MB2356; BCL:0; PCL:0; RULEID:; SRVR:BN3PR03MB2356; 
x-forefront-prvs: 0069246B74
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(43784003)(189002)(199003)(24454002)(377454003)(77096005)(19617315012)(551934003)(790700001)(6116002)(102836003)(19625215002)(19580395003)(10090500001)(99286002)(106116001)(3846002)(92566002)(19580405001)(105586002)(19609705001)(122556002)(5660300001)(11100500001)(86612001)(189998001)(76576001)(5002640100001)(7520500002)(3280700002)(8990500004)(16601075003)(106356001)(97736004)(5001770100001)(87936001)(33656002)(86362001)(586003)(15975445007)(16236675004)(93886004)(19300405004)(54356999)(76176999)(50986999)(2900100001)(66066001)(101416001)(2950100001)(74316002)(8676002)(10290500002)(5005710100001)(3660700001)(4326007)(9686002)(7736002)(7846002)(81156014)(81166006)(7906003)(7696004)(8936002)(10400500002)(68736007)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR03MB2356; H:BN3PR03MB2355.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN3PR03MB23550A34902ADE3D4FCCB787F5F50BN3PR03MB2355namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Sep 2016 23:56:45.6200 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR03MB2356
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/i8c8-MC41OeAWc-XvoxkSxwNKdA>
Cc: Nicholas Roy <nroy@internet2.edu>, "id-event@ietf.org" <id-event@ietf.org>
Subject: Re: [Id-event] Proposed text for txn and ordering
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Sep 2016 23:56:51 -0000

--_000_BN3PR03MB23550A34902ADE3D4FCCB787F5F50BN3PR03MB2355namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SeKAmWQgbGlrZSB0byBhZ3JlZSB3aXRoIE1vcnRlemEgdGhhdCB0cmFuc2FjdGlvbmFsIHNlbWFu
dGljcyBpcyBlbnRpcmVseSBkZXBlbmRlbnQgdXBvbiB0aGUgbmF0dXJlIGFuZCB1c2Ugb2YgdGhl
IEpXVCBhbmQgaXMgbm90IHNvbWV0aGluZyB3ZSBzaG91bGQgdHJ5IHRvIGRlc2NyaWJlIGdlbmVy
YWxseSwgYmVjYXVzZSBkb2luZyBzbyB3aWxsIG5lY2Vzc2FyaWx5IGV4Y2x1ZGUgaW1wb3J0YW50
IHVzZSBjYXNlcy4gIEnigJltIGZpbmUgd2l0aCBkZWZpbmluZyBhIOKAnHR4buKAnSAodHJhbnNh
Y3Rpb24gSUQpIGNsYWltIHNvbWV3aGVyZSBhcyBsb25nIGFzIHdlIG1ha2UgaXQgY2xlYXIgdGhh
dCBpdCBjYW4gYmUgdXNlZCBpbiBhbnkgSldUIGFuZCBpdCBpcyBpbiBubyB3YXkgU0VULXNwZWNp
ZmljLiAgV2Ugc2hvdWxkIGFsc28gc2F5IHRoYXQgdGhlIHByZWNpc2UgbWVhbmluZyBhbmQgdXNl
IG9mIHRoZSB0cmFuc2FjdGlvbiBpZGVudGlmaWVyIGlzIGRlcGVuZGVudCB1cG9uIHRoZSBhcHBs
aWNhdGlvbiB1c2UgY2FzZS4NCg0KSSB3b3VsZCBsZWF2ZSBvdXQgdGhlIGxhbmd1YWdlIGFib3V0
IOKAnGxpa2VseSB0byBiZSBoaWdobHkgZGlzdHJpYnV0ZWTigJ0sIGF0IGxlYXN0IGluIHRoZSBl
dmVudCB0b2tlbiBzcGVjLiAgSSBzYXkgdGhhdCBiZWNhdXNlIGV2ZW50cyB3aWxsIGFsc28gYmUg
dXNlZCBpbiBzaW1wbGUgcG9pbnQtdG8tcG9pbnQgZGVsaXZlcnkgcmVsYXRpb25zaGlwcyB3aXRo
IG5vdGhpbmcgZGlzdHJpYnV0ZWQgYWJvdXQgaXQuICBJIGRvbuKAmXQgd2FudCB0byBpbXBseSB0
aGF0IFNFVHMgYXJlbuKAmXQgYXBwcm9wcmlhdGUgZm9yIHNpbXBsZSwgbm9uLWRpc3RyaWJ1dGVk
IHVzZSBjYXNlcy4gIElmIHdlIHdhbnQgdG8gc2F5IHRoaW5ncyBhYm91dCBvcmRlcmluZywgdGhh
dCBzaG91bGQgcHJvYmFibHkgaGFwcGVuIGluIHRoZSB0cmFuc3BvcnQgc3BlYyBpZiBpdCBpcyBh
bnRpY2lwYXRlZCB0aGF0IGxlZ2FsIGltcGxlbWVudGF0aW9ucyBvZiB0aGUgdHJhbnNwb3J0IHNw
ZWMgd2lsbCBiZSBhYmxlIHJlc3VsdCBpbiBldmVudCByZW9yZGVyaW5nLg0KDQpQaGlsLCBjb3Vs
ZCB5b3UgcmV2aXNlIHlvdXIgcHJvcG9zZWQgd29yZGluZyBhY2NvcmRpbmdseSBhbmQgcmVjaXJj
dWxhdGUgZm9yIHJldmlldz8NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIFRoYW5rcyBhZ2FpbiwNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAtLSBNaWtlDQoNCkZyb206IElkLWV2ZW50
IFttYWlsdG86aWQtZXZlbnQtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFBoaWwgSHVu
dCAoSURNKQ0KU2VudDogRnJpZGF5LCBTZXB0ZW1iZXIgMTYsIDIwMTYgNzo1OCBQTQ0KVG86IE1v
cnRlemEgQW5zYXJpIChtb3JhbnNhcikgPG1vcmFuc2FyQGNpc2NvLmNvbT4NCkNjOiBOaWNob2xh
cyBSb3kgPG5yb3lAaW50ZXJuZXQyLmVkdT47IGlkLWV2ZW50QGlldGYub3JnDQpTdWJqZWN0OiBS
ZTogW0lkLWV2ZW50XSBQcm9wb3NlZCB0ZXh0IGZvciB0eG4gYW5kIG9yZGVyaW5nDQoNCjopDQoN
ClBoaWwNCg0KT24gU2VwIDE2LCAyMDE2LCBhdCA3OjQ1IFBNLCBNb3J0ZXphIEFuc2FyaSAobW9y
YW5zYXIpIDxtb3JhbnNhckBjaXNjby5jb208bWFpbHRvOm1vcmFuc2FyQGNpc2NvLmNvbT4+IHdy
b3RlOg0KWWVzLCBJIGFncmVlIG9uIHRoYXQgZnJvbnQuIEkgd2FzIHRhbGtpbmcgYWJvdXQgc2Vt
YW50aWNzIGFyb3VuZCB0eG4gc3VjaCBhcyBpZGVtcG90ZW5jeS4NCg0KQ2hlZXJzLA0KTW9ydGV6
YQ0KDQpPbiBTZXAgMTYsIDIwMTYsIGF0IDU6MzQgUE0sIFBoaWwgSHVudCAoSURNKSA8cGhpbC5o
dW50QG9yYWNsZS5jb208bWFpbHRvOnBoaWwuaHVudEBvcmFjbGUuY29tPj4gd3JvdGU6DQpUeG4g
bmVlZHMgdG8gYmUgYXZhaWxhYmxlIGluIGFsbCB0eXBlcy4NCg0KUGhpbA0KDQpPbiBTZXAgMTYs
IDIwMTYsIGF0IDI6MjYgUE0sIE1vcnRlemEgQW5zYXJpIChtb3JhbnNhcikgPG1vcmFuc2FyQGNp
c2NvLmNvbTxtYWlsdG86bW9yYW5zYXJAY2lzY28uY29tPj4gd3JvdGU6DQpJcyB0aGlzIGV2ZW4g
c29tZXRoaW5nIHdlIGNvdWxkIGRlZmluZSBmb3IgYWJzdHJhY3QgZXZlbnRzPyAgRG9lc27igJl0
IHRoYXQgc2VtYW50aWNzIHJlYWxseSBhc3NvY2lhdGVkIHdpdGggdGhlIHR5cGUgb2YgZXZlbnQg
d2UgYXJlIHRhbGtpbmcgYWJvdXQ/ICBJIHRoaW5rIHRoaXMgaXMgYSBwcm9wZXJ0eSB0aGF0IHNo
b3VsZCBiZSBkZWZpbmVkIGZvciBhIGdpdmVuIHR5cGUgb2YgZXZlbnQgYW5kIG5vdCBhY3Jvc3Mg
YWxsIGV2ZW50cy4NCg0KDQpDaGVlcnMsDQpNb3J0ZXphDQoNCkZyb206IElkLWV2ZW50IDxpZC1l
dmVudC1ib3VuY2VzQGlldGYub3JnPG1haWx0bzppZC1ldmVudC1ib3VuY2VzQGlldGYub3JnPj4g
b24gYmVoYWxmIG9mIFBoaWwgSHVudCA8cGhpbC5odW50QG9yYWNsZS5jb208bWFpbHRvOnBoaWwu
aHVudEBvcmFjbGUuY29tPj4NCkRhdGU6IEZyaWRheSwgU2VwdGVtYmVyIDE2LCAyMDE2IGF0IDI6
MDAgUE0NClRvOiBOaWNob2xhcyBSb3kgPG5yb3lAaW50ZXJuZXQyLmVkdTxtYWlsdG86bnJveUBp
bnRlcm5ldDIuZWR1Pj4NCkNjOiAiaWQtZXZlbnRAaWV0Zi5vcmc8bWFpbHRvOmlkLWV2ZW50QGll
dGYub3JnPiIgPGlkLWV2ZW50QGlldGYub3JnPG1haWx0bzppZC1ldmVudEBpZXRmLm9yZz4+DQpT
dWJqZWN0OiBSZTogW0lkLWV2ZW50XSBQcm9wb3NlZCB0ZXh0IGZvciB0eG4gYW5kIG9yZGVyaW5n
DQoNCkl0IG9jY3VycyB0byBtZSB0aGF0IHRoZSB0ZXJtaW5vbG9neSBmb3IgaWRlbXBvdGVuY3kg
aXMgd3JvbmcuIFNjaW0gaXMgaWRlbXBvdGVudCBpbiB0aGF0IGFueSByZXF1ZXN0IGNhbiBiZSBy
ZXBlYXRlZC4gSG93ZXZlciBhIHNlcmllcyBvZiB0cmFuc2FjdGlvbnMgZG9lcyBoYXZlIG9yZGVy
IGFuZCBkZXBlbmRlbmNlLg0KDQpJIHdpbGwgbG9vayBmb3IgYW5vdGhlciB3YXkgdG8gZXhwcmVz
cyB0aGlzIG9yIGp1c3QgZHJvcCB0aGUgaWRlbXBvdGVuY2UgdGVybS4NCg0KUGhpbA0KDQpPbiBT
ZXAgMTYsIDIwMTYsIGF0IDc6MTUgQU0sIE5pY2hvbGFzIFJveSA8bnJveUBpbnRlcm5ldDIuZWR1
PG1haWx0bzpucm95QGludGVybmV0Mi5lZHU+PiB3cm90ZToNCisxDQoNCk5pY2sNCk9uIDkvMTUv
MTYgNzozMiBQTSwgTWFyaXVzIFNjdXJ0ZXNjdSB3cm90ZToNClNvdW5kcyBnb29kIHRvIG1lLg0K
DQpNYXJpdXMNCg0KT24gVGh1LCBTZXAgMTUsIDIwMTYgYXQgMzoyOCBQTSwgUGhpbCBIdW50IDxw
aGlsLmh1bnRAb3JhY2xlLmNvbTxtYWlsdG86cGhpbC5odW50QG9yYWNsZS5jb20+PiB3cm90ZToN
CkJhc2VkIG9uIHRoZSBmZWVkYmFjaywgSSBhbSBwcm9wb3NpbmcgdGhlIGZvbGxvd2luZyBjaGFu
Z2VzOg0KDQpJbiB0aGUgbmV3IGF0dHJpYnV0ZXMgZGVmaW5lZCBzZWN0aW9uLCBhIG5ldyBjbGFp
bSDigJx0eG7igJ0gZGVmaW5lZDoNCg0KICAgdHhuDQoNCiAgICAgIEFuIE9QVElPTkFMIHNpbmds
ZS12YWx1ZWQgU3RyaW5nIHZhbHVlIHRoYXQgcmVwcmVzZW50cyBhIHVuaXF1ZQ0KDQogICAgICB0
cmFuc2FjdGlvbiBpZGVudGlmaWVyLiAgSW4gY2FzZXMgd2hlcmUgbXVsdGlwbGUgU0VUcyBhcmUg
aXNzdWVkDQoNCiAgICAgIGJhc2VkIG9uIGRpZmZlcmVudCBldmVudCBVUklzLCB0aGUgdHJhbnNh
Y3Rpb24gaWRlbnRpZmllciBNQVkgYmUNCg0KICAgICAgdXNlZCB0byBjb3JyZWxhdGUgU0VUcyB0
byB0aGUgc2FtZSBvcmlnaW5hdGluZyBldmVudCBvciBzdGF0ZWZ1bA0KDQogICAgICBjaGFuZ2Uu
DQoNClJlZ2FyZGluZyBPcmRlcmluZywgSSBhbSBwcm9wb3NpbmcgdGhlIGZvbGxvd2luZyBzZWN0
aW9uOg0KDQoyLjIuICBJZGVtcG90ZW5jeSBhbmQgT3JkZXJpbmcgQ29uc2lkZXJhdGlvbnMNCg0K
DQoNCiAgIEluIG1hbnkgY2FzZXMgU0VUcyB3aWxsIGJlIGlzc3VlZCBieSBoaWdobHkgZGlzdHJp
YnV0ZWQgc3lzdGVtcyBhbmQNCg0KICAgc3Vic2NyaWJlcnMuICBXaXRob3V0IGFkZGl0aW9uYWwg
c3BlY2lmaWNhdGlvbiBpdCBpcyBxdWl0ZQ0KDQogICBjb25jZWl2YWJsZSB0aGF0IHRoZSBvcmRl
ciBvZiBTRVRzIHJlY2VpdmVkIGJ5IGEgc3Vic2NyaWJlciBNQVkgYmUNCg0KICAgZGlmZmVyZW50
IGZyb20gdGhlIG9yZGVyIG9mIHRoZSBvcmlnaW5hdGluZyBzdGF0ZSBjaGFuZ2VzIG9yIGV2ZW50
cy4NCg0KICAgV2hpbGUgdGhlICJpYXQiIHZhbHVlIG1heSBnaXZlIGEgcm91Z2ggaW5kaWNhdGlv
biBvZiBTRVQgb3JkZXIsIGl0DQoNCiAgIFNIT1VMRCBOT1QgYmUgcmVsaWVkIHVwb24gdW5sZXNz
IHRoZSBwcm9maWxpbmcgU0VUIHRva2VuDQoNCiAgIHNwZWNpZmljYXRpb24gcHJvdmlkZXMgY2xh
cmlmaWNhdGlvbi4NCg0KDQoNCiAgIFByb2ZpbGluZyBzcGVjaWZpY2F0aW9ucyBhcmUgZW5jb3Vy
YWdlZCB0byBjb25zaWRlciB3aGV0aGVyIHRoZQ0KDQogICBuYXR1cmUgb2YgU0VUcyBkZWZpbmVk
IGFyZSAiaWRlbXBvdGVudCIgaW4gdGhlIHNlbnNlIHRoYXQgdGhlIG9yZGVyDQoNCiAgIG9mIHJl
Y2VpcHQgZG9lcyBub3QgbWF0dGVyLiAgRm9yIGV4YW1wbGUsIGluIHRoZSBjYXNlIG9mIHRva2Vu
DQoNCiAgIHJldm9jYXRpb25zLCBlYWNoIFNFVCBjYW4gc3RhbmQgb24gaXRzIG93biBhbmQgb3Jk
ZXIgaGFzIG5vIGltcGFjdC4NCg0KICAgSW4gY29udHJhc3QsIGEgcHJvZmlsaW5nIFNFVCBzcGVj
aWZpY2F0aW9uIHJlbGF0ZWQgdG8gcHJvdmlzaW9uaW5nDQoNCiAgIG1pZ2h0IGJlIGhpZ2hseSBk
ZXBlbmRlbnQgb24gb3JkZXJpbmcuICBBcyBhbiBleGFtcGxlOiBvbmUgU0VUDQoNCiAgIGluZGlj
YXRlcyBhIG5ldyByZXNvdXJjZSB3YXMgY3JlYXRlZCwgd2hpbGUgdGhlIG5leHQgU0VUIGluZGlj
YXRlcw0KDQogICB0aGUgc2FtZSByZXNvdXJjZSBpcyBtb2RpZmllZC4gIE5vbi1JZGVtcG90ZW50
IFNFVCBldmVudA0KDQogICBzcGVjaWZpY2F0aW9ucyBTSE9VTEQgY2hvb3NlIHRvIGRlZmluZSBh
IHNlcXVlbmNpbmcgbWV0aG9kIHN1Y2ggYXMgYWENCg0KICAgY2xhaW0gdXNlZCBmb3IgdGhlIHB1
cnBvc2Ugb3IgaWRlbnRpZnlpbmcgdGhlIG9yZGVyIG9mIFNFVHMgYXMNCg0KICAgZGVmaW5lZCBi
eSB0aGUgRmVlZCBQdWJsaXNoZXIgb3IgYW5vdGhlciBtZXRob2QgdGhhdCBpcyBwYXJ0IG9mIGhv
dw0KDQogICBTRVRzIGFyZSBkaXN0cmlidXRlZC4NClRoYW5rcyBmb3IgeW91ciBmZWVkYmFjay4N
Cg0KUGhpbA0KDQpAaW5kZXBlbmRlbnRpZA0Kd3d3LmluZGVwZW5kZW50aWQuY29tPGh0dHA6Ly93
d3cuaW5kZXBlbmRlbnRpZC5jb20+DQpwaGlsLmh1bnRAb3JhY2xlLmNvbTxtYWlsdG86cGhpbC5o
dW50QG9yYWNsZS5jb20+DQoNCg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCklkLWV2ZW50IG1haWxpbmcgbGlzdA0KSWQtZXZlbnRAaWV0Zi5v
cmc8bWFpbHRvOklkLWV2ZW50QGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9pZC1ldmVudA0KDQoNCg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQoNCklkLWV2ZW50IG1haWxpbmcgbGlzdA0KDQpJZC1ldmVu
dEBpZXRmLm9yZzxtYWlsdG86SWQtZXZlbnRAaWV0Zi5vcmc+aHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9pZC1ldmVudA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KSWQtZXZlbnQgbWFpbGluZyBsaXN0DQpJZC1ldmVudEBpZXRm
Lm9yZzxtYWlsdG86SWQtZXZlbnRAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2lkLWV2ZW50DQo=

--_000_BN3PR03MB23550A34902ADE3D4FCCB787F5F50BN3PR03MB2355namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5Ok1vbmFjbzsNCglw
YW5vc2UtMTowIDAgMCAwIDAgMCAwIDAgMCAwO30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpw
Lk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJ
bWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6
IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5k
ZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxp
bmU7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRN
TCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAx
cHQ7DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCnAu
bXNvbm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5h
bWU6bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDow
aW47DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZv
bnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0K
c3Bhbi5IVE1MUHJlZm9ybWF0dGVkQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiSFRNTCBQcmVmb3Jt
YXR0ZWQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJI
VE1MIFByZWZvcm1hdHRlZCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0Kc3Bhbi5tLTIxMzc1
ODI5MDAwMjYyNTc2NTFhcHBsZS1zdHlsZS1zcGFuDQoJe21zby1zdHlsZS1uYW1lOm1fLTIxMzc1
ODI5MDAwMjYyNTc2NTFhcHBsZS1zdHlsZS1zcGFuO30NCnNwYW4uRW1haWxTdHlsZTIxDQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmOw0KCWNvbG9yOiMwMDIwNjA7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5
cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30N
CmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRt
YXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4N
CjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRh
PSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJv
ZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0i
V29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMDAyMDYwIj5J4oCZZCBsaWtlIHRvIGFncmVlIHdpdGggTW9ydGV6YSB0aGF0IHRyYW5zYWN0
aW9uYWwgc2VtYW50aWNzIGlzIGVudGlyZWx5IGRlcGVuZGVudCB1cG9uIHRoZSBuYXR1cmUgYW5k
IHVzZSBvZiB0aGUgSldUIGFuZCBpcyBub3Qgc29tZXRoaW5nIHdlIHNob3VsZCB0cnkgdG8gZGVz
Y3JpYmUNCiBnZW5lcmFsbHksIGJlY2F1c2UgZG9pbmcgc28gd2lsbCBuZWNlc3NhcmlseSBleGNs
dWRlIGltcG9ydGFudCB1c2UgY2FzZXMuJm5ic3A7IEnigJltIGZpbmUgd2l0aCBkZWZpbmluZyBh
IOKAnHR4buKAnSAodHJhbnNhY3Rpb24gSUQpIGNsYWltIHNvbWV3aGVyZSBhcyBsb25nIGFzIHdl
IG1ha2UgaXQgY2xlYXIgdGhhdCBpdCBjYW4gYmUgdXNlZCBpbiBhbnkgSldUIGFuZCBpdCBpcyBp
biBubyB3YXkgU0VULXNwZWNpZmljLiZuYnNwOyBXZSBzaG91bGQgYWxzbyBzYXkgdGhhdA0KIHRo
ZSBwcmVjaXNlIG1lYW5pbmcgYW5kIHVzZSBvZiB0aGUgdHJhbnNhY3Rpb24gaWRlbnRpZmllciBp
cyBkZXBlbmRlbnQgdXBvbiB0aGUgYXBwbGljYXRpb24gdXNlIGNhc2UuPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMwMDIw
NjAiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMDAyMDYwIj5JIHdvdWxkIGxlYXZlIG91dCB0aGUgbGFuZ3Vh
Z2UgYWJvdXQg4oCcbGlrZWx5IHRvIGJlIGhpZ2hseSBkaXN0cmlidXRlZOKAnSwgYXQgbGVhc3Qg
aW4gdGhlIGV2ZW50IHRva2VuIHNwZWMuICZuYnNwO0kgc2F5IHRoYXQgYmVjYXVzZSBldmVudHMg
d2lsbCBhbHNvIGJlIHVzZWQgaW4gc2ltcGxlDQogcG9pbnQtdG8tcG9pbnQgZGVsaXZlcnkgcmVs
YXRpb25zaGlwcyB3aXRoIG5vdGhpbmcgZGlzdHJpYnV0ZWQgYWJvdXQgaXQuJm5ic3A7IEkgZG9u
4oCZdCB3YW50IHRvIGltcGx5IHRoYXQgU0VUcyBhcmVu4oCZdCBhcHByb3ByaWF0ZSBmb3Igc2lt
cGxlLCBub24tZGlzdHJpYnV0ZWQgdXNlIGNhc2VzLiZuYnNwOyBJZiB3ZSB3YW50IHRvIHNheSB0
aGluZ3MgYWJvdXQgb3JkZXJpbmcsIHRoYXQgc2hvdWxkIHByb2JhYmx5IGhhcHBlbiBpbiB0aGUg
dHJhbnNwb3J0IHNwZWMNCiBpZiBpdCBpcyBhbnRpY2lwYXRlZCB0aGF0IGxlZ2FsIGltcGxlbWVu
dGF0aW9ucyBvZiB0aGUgdHJhbnNwb3J0IHNwZWMgd2lsbCBiZSBhYmxlIHJlc3VsdCBpbiBldmVu
dCByZW9yZGVyaW5nLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMDAyMDYwIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzAwMjA2MCI+
UGhpbCwgY291bGQgeW91IHJldmlzZSB5b3VyIHByb3Bvc2VkIHdvcmRpbmcgYWNjb3JkaW5nbHkg
YW5kIHJlY2lyY3VsYXRlIGZvciByZXZpZXc/PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMwMDIwNjAiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjojMDAyMDYwIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgVGhh
bmtzIGFnYWluLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMDAyMDYwIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgLS0gTWlrZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxhIG5hbWU9Il9NYWlsRW5kQ29tcG9zZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMw
MDIwNjAiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvYT48L3A+DQo8c3BhbiBzdHlsZT0ibXNv
LWJvb2ttYXJrOl9NYWlsRW5kQ29tcG9zZSI+PC9zcGFuPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJv
cmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBp
biAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RnJv
bTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IElkLWV2ZW50IFttYWlsdG86aWQtZXZlbnQt
Ym91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+UGhpbCBIdW50IChJRE0pPGJy
Pg0KPGI+U2VudDo8L2I+IEZyaWRheSwgU2VwdGVtYmVyIDE2LCAyMDE2IDc6NTggUE08YnI+DQo8
Yj5Ubzo8L2I+IE1vcnRlemEgQW5zYXJpIChtb3JhbnNhcikgJmx0O21vcmFuc2FyQGNpc2NvLmNv
bSZndDs8YnI+DQo8Yj5DYzo8L2I+IE5pY2hvbGFzIFJveSAmbHQ7bnJveUBpbnRlcm5ldDIuZWR1
Jmd0OzsgaWQtZXZlbnRAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtJZC1ldmVu
dF0gUHJvcG9zZWQgdGV4dCBmb3IgdHhuIGFuZCBvcmRlcmluZzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Oik8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KUGhpbDxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0
b206MTIuMHB0Ij48YnI+DQpPbiBTZXAgMTYsIDIwMTYsIGF0IDc6NDUgUE0sIE1vcnRlemEgQW5z
YXJpIChtb3JhbnNhcikgJmx0OzxhIGhyZWY9Im1haWx0bzptb3JhbnNhckBjaXNjby5jb20iPm1v
cmFuc2FyQGNpc2NvLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4N
CjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206
MTIuMHB0Ij5ZZXMsIEkgYWdyZWUgb24gdGhhdCBmcm9udC4gSSB3YXMgdGFsa2luZyBhYm91dCBz
ZW1hbnRpY3MgYXJvdW5kIHR4biBzdWNoIGFzIGlkZW1wb3RlbmN5LiZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5DaGVlcnMsIDxvOnA+PC9vOnA+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk1vcnRlemE8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206
MTIuMHB0Ij48YnI+DQpPbiBTZXAgMTYsIDIwMTYsIGF0IDU6MzQgUE0sIFBoaWwgSHVudCAoSURN
KSAmbHQ7PGEgaHJlZj0ibWFpbHRvOnBoaWwuaHVudEBvcmFjbGUuY29tIj5waGlsLmh1bnRAb3Jh
Y2xlLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90
ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlR4biBuZWVkcyB0byBiZSBhdmFpbGFi
bGUgaW4gYWxsIHR5cGVzLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48YnI+DQpQaGlsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxicj4NCk9uIFNl
cCAxNiwgMjAxNiwgYXQgMjoyNiBQTSwgTW9ydGV6YSBBbnNhcmkgKG1vcmFuc2FyKSAmbHQ7PGEg
aHJlZj0ibWFpbHRvOm1vcmFuc2FyQGNpc2NvLmNvbSI+bW9yYW5zYXJAY2lzY28uY29tPC9hPiZn
dDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJn
aW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5JcyB0aGlzIGV2ZW4gc29tZXRoaW5nIHdlIGNvdWxkIGRlZmluZSBmb3Ig
YWJzdHJhY3QgZXZlbnRzPyAmbmJzcDtEb2VzbuKAmXQgdGhhdCBzZW1hbnRpY3MgcmVhbGx5IGFz
c29jaWF0ZWQgd2l0aCB0aGUgdHlwZSBvZiBldmVudCB3ZSBhcmUgdGFsa2luZyBhYm91dD8gJm5i
c3A7SSB0aGluayB0aGlzIGlzIGEgcHJvcGVydHkgdGhhdCBzaG91bGQgYmUgZGVmaW5lZCBmb3Ig
YSBnaXZlbiB0eXBlIG9mIGV2ZW50IGFuZCBub3QgYWNyb3NzDQogYWxsIGV2ZW50cy48bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5DaGVlcnMs
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Nb3J0
ZXphPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5Gcm9t
Og0KPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPklkLWV2ZW50ICZsdDs8
YSBocmVmPSJtYWlsdG86aWQtZXZlbnQtYm91bmNlc0BpZXRmLm9yZyI+aWQtZXZlbnQtYm91bmNl
c0BpZXRmLm9yZzwvYT4mZ3Q7IG9uIGJlaGFsZiBvZiBQaGlsIEh1bnQgJmx0OzxhIGhyZWY9Im1h
aWx0bzpwaGlsLmh1bnRAb3JhY2xlLmNvbSI+cGhpbC5odW50QG9yYWNsZS5jb208L2E+Jmd0Ozxi
cj4NCjxiPkRhdGU6IDwvYj5GcmlkYXksIFNlcHRlbWJlciAxNiwgMjAxNiBhdCAyOjAwIFBNPGJy
Pg0KPGI+VG86IDwvYj5OaWNob2xhcyBSb3kgJmx0OzxhIGhyZWY9Im1haWx0bzpucm95QGludGVy
bmV0Mi5lZHUiPm5yb3lAaW50ZXJuZXQyLmVkdTwvYT4mZ3Q7PGJyPg0KPGI+Q2M6IDwvYj4mcXVv
dDs8YSBocmVmPSJtYWlsdG86aWQtZXZlbnRAaWV0Zi5vcmciPmlkLWV2ZW50QGlldGYub3JnPC9h
PiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmlkLWV2ZW50QGlldGYub3JnIj5pZC1ldmVudEBp
ZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDogPC9iPlJlOiBbSWQtZXZlbnRdIFByb3Bv
c2VkIHRleHQgZm9yIHR4biBhbmQgb3JkZXJpbmc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkl0
IG9jY3VycyB0byBtZSB0aGF0IHRoZSB0ZXJtaW5vbG9neSBmb3IgaWRlbXBvdGVuY3kgaXMgd3Jv
bmcuIFNjaW0gaXMgaWRlbXBvdGVudCBpbiB0aGF0IGFueSByZXF1ZXN0IGNhbiBiZSByZXBlYXRl
ZC4gSG93ZXZlciBhIHNlcmllcyBvZiB0cmFuc2FjdGlvbnMgZG9lcyBoYXZlIG9yZGVyIGFuZCBk
ZXBlbmRlbmNlLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5JIHdpbGwgbG9vayBmb3IgYW5vdGhlciB3YXkgdG8gZXhwcmVzcyB0aGlz
IG9yIGp1c3QgZHJvcCB0aGUgaWRlbXBvdGVuY2UgdGVybS4mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KUGhpbDxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206
MTIuMHB0Ij48YnI+DQpPbiBTZXAgMTYsIDIwMTYsIGF0IDc6MTUgQU0sIE5pY2hvbGFzIFJveSAm
bHQ7PGEgaHJlZj0ibWFpbHRvOm5yb3lAaW50ZXJuZXQyLmVkdSI+bnJveUBpbnRlcm5ldDIuZWR1
PC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxl
PSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+JiM0MzsxPGJyPg0KPGJy
Pg0KTmljazxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIDkv
MTUvMTYgNzozMiBQTSwgTWFyaXVzIFNjdXJ0ZXNjdSB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1
LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U291bmRzIGdvb2QgdG8gbWUuPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnIgY2xl
YXI9ImFsbCI+DQo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+TWFyaXVzPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+T24gVGh1LCBTZXAgMTUsIDIwMTYgYXQgMzoyOCBQTSwgUGhpbCBIdW50ICZsdDs8YSBocmVm
PSJtYWlsdG86cGhpbC5odW50QG9yYWNsZS5jb20iIHRhcmdldD0iX2JsYW5rIj5waGlsLmh1bnRA
b3JhY2xlLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzow
aW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CYXNlZCBvbiB0aGUgZmVlZGJhY2ssIEkgYW0gcHJv
cG9zaW5nIHRoZSBmb2xsb3dpbmcgY2hhbmdlczoNCjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+SW4gdGhlIG5ldyBhdHRyaWJ1dGVzIGRlZmluZWQgc2VjdGlv
biwgYSBuZXcgY2xhaW0g4oCcdHhu4oCdIGRlZmluZWQ6PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8ZGl2Pg0KPHByZSBzdHlsZT0id29yZC13cmFwOmJyZWFrLXdvcmQ7d2hpdGUtc3Bh
Y2U6cHJlLXdyYXAiPiZuYnNwOyZuYnNwOyB0eG48bzpwPjwvbzpwPjwvcHJlPg0KPHByZT4mbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgQW4gT1BUSU9OQUwgc2luZ2xlLXZhbHVlZCBTdHJp
bmcgdmFsdWUgdGhhdCByZXByZXNlbnRzIGEgdW5pcXVlPG86cD48L286cD48L3ByZT4NCjxwcmU+
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRyYW5zYWN0aW9uIGlkZW50aWZpZXIuJm5i
c3A7IEluIGNhc2VzIHdoZXJlIG11bHRpcGxlIFNFVHMgYXJlIGlzc3VlZDxvOnA+PC9vOnA+PC9w
cmU+DQo8cHJlPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBiYXNlZCBvbiBkaWZmZXJl
bnQgZXZlbnQgVVJJcywgdGhlIHRyYW5zYWN0aW9uIGlkZW50aWZpZXIgTUFZIGJlPG86cD48L286
cD48L3ByZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHVzZWQgdG8gY29y
cmVsYXRlIFNFVHMgdG8gdGhlIHNhbWUgb3JpZ2luYXRpbmcgZXZlbnQgb3Igc3RhdGVmdWw8bzpw
PjwvbzpwPjwvcHJlPg0KPHByZT4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgY2hhbmdl
LjxvOnA+PC9vOnA+PC9wcmU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZTo4LjVwdDtmb250LWZhbWlseTomcXVvdDtNb25hY28mcXVvdDssc2VyaWYi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+UmVnYXJkaW5nIE9yZGVyaW5nLCBJIGFtIHByb3Bvc2luZyB0aGUg
Zm9sbG93aW5nIHNlY3Rpb246PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cHJlIHN0
eWxlPSJ3b3JkLXdyYXA6YnJlYWstd29yZDt3aGl0ZS1zcGFjZTpwcmUtd3JhcCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZTo4LjVwdCI+Mi4yLiZuYnNwOyBJZGVtcG90ZW5jeSBhbmQgT3JkZXJpbmcg
Q29uc2lkZXJhdGlvbnM8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZTo4LjVwdCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6OC41cHQiPiZuYnNwOyZuYnNwOyBJbiBtYW55IGNhc2VzIFNF
VHMgd2lsbCBiZSBpc3N1ZWQgYnkgaGlnaGx5IGRpc3RyaWJ1dGVkIHN5c3RlbXMgYW5kPG86cD48
L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OC41cHQiPiZu
YnNwOyZuYnNwOyBzdWJzY3JpYmVycy4mbmJzcDsgV2l0aG91dCBhZGRpdGlvbmFsIHNwZWNpZmlj
YXRpb24gaXQgaXMgcXVpdGU8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZTo4LjVwdCI+Jm5ic3A7Jm5ic3A7IGNvbmNlaXZhYmxlIHRoYXQgdGhlIG9y
ZGVyIG9mIFNFVHMgcmVjZWl2ZWQgYnkgYSBzdWJzY3JpYmVyIE1BWSBiZTxvOnA+PC9vOnA+PC9z
cGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguNXB0Ij4mbmJzcDsmbmJz
cDsgZGlmZmVyZW50IGZyb20gdGhlIG9yZGVyIG9mIHRoZSBvcmlnaW5hdGluZyBzdGF0ZSBjaGFu
Z2VzIG9yIGV2ZW50cy48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZTo4LjVwdCI+Jm5ic3A7Jm5ic3A7IFdoaWxlIHRoZSAmcXVvdDtpYXQmcXVvdDsg
dmFsdWUgbWF5IGdpdmUgYSByb3VnaCBpbmRpY2F0aW9uIG9mIFNFVCBvcmRlciwgaXQ8bzpwPjwv
bzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjVwdCI+Jm5i
c3A7Jm5ic3A7IFNIT1VMRCBOT1QgYmUgcmVsaWVkIHVwb24gdW5sZXNzIHRoZSBwcm9maWxpbmcg
U0VUIHRva2VuPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6OC41cHQiPiZuYnNwOyZuYnNwOyBzcGVjaWZpY2F0aW9uIHByb3ZpZGVzIGNsYXJpZmlj
YXRpb24uPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6OC41cHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjguNXB0Ij4mbmJzcDsmbmJzcDsgUHJvZmlsaW5nIHNwZWNpZmljYXRpb25z
IGFyZSBlbmNvdXJhZ2VkIHRvIGNvbnNpZGVyIHdoZXRoZXIgdGhlPG86cD48L286cD48L3NwYW4+
PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OC41cHQiPiZuYnNwOyZuYnNwOyBu
YXR1cmUgb2YgU0VUcyBkZWZpbmVkIGFyZSAmcXVvdDtpZGVtcG90ZW50JnF1b3Q7IGluIHRoZSBz
ZW5zZSB0aGF0IHRoZSBvcmRlcjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjguNXB0Ij4mbmJzcDsmbmJzcDsgb2YgcmVjZWlwdCBkb2VzIG5vdCBt
YXR0ZXIuJm5ic3A7IEZvciBleGFtcGxlLCBpbiB0aGUgY2FzZSBvZiB0b2tlbjxvOnA+PC9vOnA+
PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguNXB0Ij4mbmJzcDsm
bmJzcDsgcmV2b2NhdGlvbnMsIGVhY2ggU0VUIGNhbiBzdGFuZCBvbiBpdHMgb3duIGFuZCBvcmRl
ciBoYXMgbm8gaW1wYWN0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjguNXB0Ij4mbmJzcDsmbmJzcDsgSW4gY29udHJhc3QsIGEgcHJvZmlsaW5n
IFNFVCBzcGVjaWZpY2F0aW9uIHJlbGF0ZWQgdG8gcHJvdmlzaW9uaW5nPG86cD48L286cD48L3Nw
YW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OC41cHQiPiZuYnNwOyZuYnNw
OyBtaWdodCBiZSBoaWdobHkgZGVwZW5kZW50IG9uIG9yZGVyaW5nLiZuYnNwOyBBcyBhbiBleGFt
cGxlOiBvbmUgU0VUPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6OC41cHQiPiZuYnNwOyZuYnNwOyBpbmRpY2F0ZXMgYSBuZXcgcmVzb3VyY2Ugd2Fz
IGNyZWF0ZWQsIHdoaWxlIHRoZSBuZXh0IFNFVCBpbmRpY2F0ZXM8bzpwPjwvbzpwPjwvc3Bhbj48
L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjVwdCI+Jm5ic3A7Jm5ic3A7IHRo
ZSBzYW1lIHJlc291cmNlIGlzIG1vZGlmaWVkLiZuYnNwOyBOb24tSWRlbXBvdGVudCBTRVQgZXZl
bnQ8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo4
LjVwdCI+Jm5ic3A7Jm5ic3A7IHNwZWNpZmljYXRpb25zIFNIT1VMRCBjaG9vc2UgdG8gZGVmaW5l
IGEgc2VxdWVuY2luZyBtZXRob2Qgc3VjaCBhcyBhYTxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0K
PHByZT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguNXB0Ij4mbmJzcDsmbmJzcDsgY2xhaW0gdXNl
ZCBmb3IgdGhlIHB1cnBvc2Ugb3IgaWRlbnRpZnlpbmcgdGhlIG9yZGVyIG9mIFNFVHMgYXM8bzpw
PjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjVwdCI+
Jm5ic3A7Jm5ic3A7IGRlZmluZWQgYnkgdGhlIEZlZWQgUHVibGlzaGVyIG9yIGFub3RoZXIgbWV0
aG9kIHRoYXQgaXMgcGFydCBvZiBob3c8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjVwdCI+Jm5ic3A7Jm5ic3A7IFNFVHMgYXJlIGRpc3RyaWJ1
dGVkLjwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+VGhhbmtzIGZvciB5b3VyIGZlZWRiYWNrLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5QaGlsPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPkBpbmRlcGVuZGVudGlkPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImNvbG9yOmJsYWNrIj48YSBocmVmPSJodHRwOi8vd3d3LmluZGVwZW5kZW50aWQuY29tIiB0YXJn
ZXQ9Il9ibGFuayI+d3d3LmluZGVwZW5kZW50aWQuY29tPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48YSBocmVmPSJtYWlsdG86cGhpbC5odW50QG9yYWNs
ZS5jb20iIHRhcmdldD0iX2JsYW5rIj5waGlsLmh1bnRAb3JhY2xlLmNvbTwvYT48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iY29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48
YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4N
CklkLWV2ZW50IG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzpJZC1ldmVudEBpZXRm
Lm9yZyI+SWQtZXZlbnRAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZC1ldmVudCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaWQtZXZlbnQ8L2E+PG86cD48L286cD48L3A+
DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+DQo8YnI+DQo8YnI+
DQo8bzpwPjwvbzpwPjwvcD4NCjxwcmU+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX188bzpwPjwvbzpwPjwvcHJlPg0KPHByZT5JZC1ldmVudCBtYWlsaW5nIGxp
c3Q8bzpwPjwvbzpwPjwvcHJlPg0KPHByZT48YSBocmVmPSJtYWlsdG86SWQtZXZlbnRAaWV0Zi5v
cmciPklkLWV2ZW50QGlldGYub3JnPC9hPjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vaWQtZXZlbnQiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vaWQtZXZlbnQ8L2E+PG86cD48L286cD48L3ByZT4NCjwvYmxvY2txdW90ZT4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVv
dGU+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUu
MHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCklkLWV2ZW50IG1haWxpbmcgbGlzdDxicj4N
CjxhIGhyZWY9Im1haWx0bzpJZC1ldmVudEBpZXRmLm9yZyI+SWQtZXZlbnRAaWV0Zi5vcmc8L2E+
PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZC1l
dmVudCI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZC1ldmVudDwvYT48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvYmxv
Y2txdW90ZT4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_BN3PR03MB23550A34902ADE3D4FCCB787F5F50BN3PR03MB2355namp_--


From nobody Mon Sep 19 08:46:18 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A857412B1F3 for <id-event@ietfa.amsl.com>; Mon, 19 Sep 2016 08:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tWESGPmYWuBb for <id-event@ietfa.amsl.com>; Mon, 19 Sep 2016 08:46:14 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8809712B106 for <id-event@ietf.org>; Mon, 19 Sep 2016 08:46:13 -0700 (PDT)
Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8JFkB4r005262 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 19 Sep 2016 15:46:11 GMT
Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id u8JFk95X006103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 19 Sep 2016 15:46:10 GMT
Received: from abhmp0013.oracle.com (abhmp0013.oracle.com [141.146.116.19]) by userv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u8JFjvb6004280; Mon, 19 Sep 2016 15:46:08 GMT
Received: from [25.208.199.3] (/24.114.71.14) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 19 Sep 2016 08:45:56 -0700
Content-Type: multipart/alternative; boundary=Apple-Mail-12A507B7-A96F-409A-9FAA-EC3995880EB4
Content-Transfer-Encoding: 7bit
From: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 19 Sep 2016 08:34:37 -0700
Message-Id: <B0CD1384-54DF-4CB0-8B9F-F9AADE169F03@oracle.com>
References: <18F0D4DD-7B8B-4276-8DAF-1BC9963806DF@oracle.com> <CAGdjJp+ndWYiPYb0KPN-TFh+SN-hqR8JBO6poVWAT_OPEEomaw@mail.gmail.com> <a42b8067-02f8-a9ba-ea86-d129a0546ed4@internet2.edu> <E6464A41-7619-4752-B5B6-F1EB54C03544@oracle.com> <D401B0FE.48BE7%moransar@cisco.com> <062AC5AC-AF95-4D0E-9427-1472732162F0@oracle.com> <D085C3EE-2F98-47C8-A96B-0616C2CAB9DF@cisco.com> <21A579E3-A659-42EF-96E9-92EBCFF250AE@oracle.com> <BN3PR03MB23550A34902ADE3D4FCCB787F5F50@BN3PR03MB2355.namprd03.prod.outlook.com>
In-Reply-To: <BN3PR03MB23550A34902ADE3D4FCCB787F5F50@BN3PR03MB2355.namprd03.prod.outlook.com>
To: Mike Jones <Michael.Jones@microsoft.com>
X-Mailer: iPhone Mail (14A403)
X-Source-IP: aserv0022.oracle.com [141.146.126.234]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/l3E8VZcmjzCqXp-SGWRFoX8s5l0>
Cc: Nicholas Roy <nroy@internet2.edu>, "Morteza Ansari \(moransar\)" <moransar@cisco.com>, "id-event@ietf.org" <id-event@ietf.org>
Subject: Re: [Id-event] Proposed text for txn and ordering
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Sep 2016 15:46:17 -0000

--Apple-Mail-12A507B7-A96F-409A-9FAA-EC3995880EB4
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

We need to be able to correlate SETs back to a common initiating transaction=
.=20

However if I understand you are suggesting txn might be asserted inbound as k=
ind of a through the layers txn id (eg in an auth tkn).=20

Yes i can see that is ok. However usually oauth txns are usually multi trans=
actional. And so meaning is different.=20

Can you propose text?

Phil

> On Sep 18, 2016, at 4:56 PM, Mike Jones <Michael.Jones@microsoft.com> wrot=
e:
>=20
> I=E2=80=99d like to agree with Morteza that transactional semantics is ent=
irely dependent upon the nature and use of the JWT and is not something we s=
hould try to describe generally, because doing so will necessarily exclude i=
mportant use cases.  I=E2=80=99m fine with defining a =E2=80=9Ctxn=E2=80=9D (=
transaction ID) claim somewhere as long as we make it clear that it can be u=
sed in any JWT and it is in no way SET-specific.  We should also say that th=
e precise meaning and use of the transaction identifier is dependent upon th=
e application use case.
> =20
> I would leave out the language about =E2=80=9Clikely to be highly distribu=
ted=E2=80=9D, at least in the event token spec.  I say that because events w=
ill also be used in simple point-to-point delivery relationships with nothin=
g distributed about it.  I don=E2=80=99t want to imply that SETs aren=E2=80=99=
t appropriate for simple, non-distributed use cases.  If we want to say thin=
gs about ordering, that should probably happen in the transport spec if it i=
s anticipated that legal implementations of the transport spec will be able r=
esult in event reordering.
> =20
> Phil, could you revise your proposed wording accordingly and recirculate f=
or review?
> =20
>                                                        Thanks again,
>                                                        -- Mike
> =20
> From: Id-event [mailto:id-event-bounces@ietf.org] On Behalf Of Phil Hunt (=
IDM)
> Sent: Friday, September 16, 2016 7:58 PM
> To: Morteza Ansari (moransar) <moransar@cisco.com>
> Cc: Nicholas Roy <nroy@internet2.edu>; id-event@ietf.org
> Subject: Re: [Id-event] Proposed text for txn and ordering
> =20
> :)
>=20
> Phil
>=20
> On Sep 16, 2016, at 7:45 PM, Morteza Ansari (moransar) <moransar@cisco.com=
> wrote:
>=20
> Yes, I agree on that front. I was talking about semantics around txn such a=
s idempotency.=20
>=20
> =20
> Cheers,
> Morteza
>=20
> On Sep 16, 2016, at 5:34 PM, Phil Hunt (IDM) <phil.hunt@oracle.com> wrote:=

>=20
> Txn needs to be available in all types.=20
>=20
> Phil
>=20
> On Sep 16, 2016, at 2:26 PM, Morteza Ansari (moransar) <moransar@cisco.com=
> wrote:
>=20
> Is this even something we could define for abstract events?  Doesn=E2=80=99=
t that semantics really associated with the type of event we are talking abo=
ut?  I think this is a property that should be defined for a given type of e=
vent and not across all events.
> =20
> =20
> Cheers,
> Morteza
> =20
> From: Id-event <id-event-bounces@ietf.org> on behalf of Phil Hunt <phil.hu=
nt@oracle.com>
> Date: Friday, September 16, 2016 at 2:00 PM
> To: Nicholas Roy <nroy@internet2.edu>
> Cc: "id-event@ietf.org" <id-event@ietf.org>
> Subject: Re: [Id-event] Proposed text for txn and ordering
> =20
> It occurs to me that the terminology for idempotency is wrong. Scim is ide=
mpotent in that any request can be repeated. However a series of transaction=
s does have order and dependence.=20
> =20
> I will look for another way to express this or just drop the idempotence t=
erm.=20
>=20
> Phil
>=20
> On Sep 16, 2016, at 7:15 AM, Nicholas Roy <nroy@internet2.edu> wrote:
>=20
> +1
>=20
> Nick
>=20
> On 9/15/16 7:32 PM, Marius Scurtescu wrote:
> Sounds good to me.
>=20
> Marius
> =20
> On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt <phil.hunt@oracle.com> wrote:
> Based on the feedback, I am proposing the following changes:
> =20
> In the new attributes defined section, a new claim =E2=80=9Ctxn=E2=80=9D d=
efined:
>    txn
>       An OPTIONAL single-valued String value that represents a unique
>       transaction identifier.  In cases where multiple SETs are issued
>       based on different event URIs, the transaction identifier MAY be
>       used to correlate SETs to the same originating event or stateful
>       change.
> =20
> Regarding Ordering, I am proposing the following section:
> 2.2.  Idempotency and Ordering Considerations
> =20
>    In many cases SETs will be issued by highly distributed systems and
>    subscribers.  Without additional specification it is quite
>    conceivable that the order of SETs received by a subscriber MAY be
>    different from the order of the originating state changes or events.
>    While the "iat" value may give a rough indication of SET order, it
>    SHOULD NOT be relied upon unless the profiling SET token
>    specification provides clarification.
> =20
>    Profiling specifications are encouraged to consider whether the
>    nature of SETs defined are "idempotent" in the sense that the order
>    of receipt does not matter.  For example, in the case of token
>    revocations, each SET can stand on its own and order has no impact.
>    In contrast, a profiling SET specification related to provisioning
>    might be highly dependent on ordering.  As an example: one SET
>    indicates a new resource was created, while the next SET indicates
>    the same resource is modified.  Non-Idempotent SET event
>    specifications SHOULD choose to define a sequencing method such as aa
>    claim used for the purpose or identifying the order of SETs as
>    defined by the Feed Publisher or another method that is part of how
>    SETs are distributed.
> Thanks for your feedback.
> =20
> Phil
> =20
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
> =20
> =20
> =20
>=20
> =20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>=20
> =20
>=20
>=20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.orghttps://www.ietf.org/mailman/listinfo/id-event
> =20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event

--Apple-Mail-12A507B7-A96F-409A-9FAA-EC3995880EB4
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><div style=3D"direction: inherit;">We n=
eed to be able to correlate SETs back to a common initiating transaction.&nb=
sp;</div><div style=3D"direction: inherit;"><br></div><div style=3D"directio=
n: inherit;">However if I understand you are suggesting txn might be asserte=
d inbound as kind of a through the layers txn id (eg in an auth tkn).&nbsp;<=
/div><div style=3D"direction: inherit;"><br></div><div style=3D"direction: i=
nherit;">Yes i can see that is ok. However usually oauth txns are usually mu=
lti transactional. And so meaning is different.&nbsp;</div><div style=3D"dir=
ection: inherit;"><br></div><div style=3D"direction: inherit;">Can you propo=
se text?</div><div style=3D"direction: inherit;"><br></div>Phil</div><div><b=
r>On Sep 18, 2016, at 4:56 PM, Mike Jones &lt;<a href=3D"mailto:Michael.Jone=
s@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<br><br></div><bl=
ockquote type=3D"cite"><div>

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Monaco;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
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.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.m-2137582900026257651apple-style-span
	{mso-style-name:m_-2137582900026257651apple-style-span;}
span.EmailStyle21
	{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=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->


<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">I=E2=80=99d like to agree with Morteza t=
hat transactional semantics is entirely dependent upon the nature and use of=
 the JWT and is not something we should try to describe
 generally, because doing so will necessarily exclude important use cases.&n=
bsp; I=E2=80=99m fine with defining a =E2=80=9Ctxn=E2=80=9D (transaction ID)=
 claim somewhere as long as we make it clear that it can be used in any JWT a=
nd it is in no way SET-specific.&nbsp; We should also say that
 the precise meaning and use of the transaction identifier is dependent upon=
 the application use case.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">I would leave out the language about =E2=
=80=9Clikely to be highly distributed=E2=80=9D, at least in the event token s=
pec. &nbsp;I say that because events will also be used in simple
 point-to-point delivery relationships with nothing distributed about it.&nb=
sp; I don=E2=80=99t want to imply that SETs aren=E2=80=99t appropriate for s=
imple, non-distributed use cases.&nbsp; If we want to say things about order=
ing, that should probably happen in the transport spec
 if it is anticipated that legal implementations of the transport spec will b=
e able result in event reordering.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">Phil, could you revise your proposed wo=
rding accordingly and recirculate for review?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks again,<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,sans-serif;color:#002060">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"font-size:=
11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#002060"><o:p>&nbsp;=
</o:p></span></a></p>
<span style=3D"mso-bookmark:_MailEndCompose"></span>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0=
in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif"> Id-event [<a href=3D"mailto:id-ev=
ent-bounces@ietf.org">mailto:id-event-bounces@ietf.org</a>]
<b>On Behalf Of </b>Phil Hunt (IDM)<br>
<b>Sent:</b> Friday, September 16, 2016 7:58 PM<br>
<b>To:</b> Morteza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.co=
m">moransar@cisco.com</a>&gt;<br>
<b>Cc:</b> Nicholas Roy &lt;<a href=3D"mailto:nroy@internet2.edu">nroy@inter=
net2.edu</a>&gt;; <a href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a>=
<br>
<b>Subject:</b> Re: [Id-event] Proposed text for txn and ordering<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">:)<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
Phil<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Sep 16, 2016, at 7:45 PM, Morteza Ansari (moransar) &lt;<a href=3D"mailto=
:moransar@cisco.com">moransar@cisco.com</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Yes, I agree on that f=
ront. I was talking about semantics around txn such as idempotency.&nbsp;<o:=
p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">Cheers, <o:p></o:p></p>
<div>
<p class=3D"MsoNormal">Morteza<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Sep 16, 2016, at 5:34 PM, Phil Hunt (IDM) &lt;<a href=3D"mailto:phil.hunt=
@oracle.com">phil.hunt@oracle.com</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class=3D"MsoNormal">Txn needs to be available in all types.&nbsp;<o:p></o=
:p></p>
</div>
<p class=3D"MsoNormal"><br>
Phil<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Sep 16, 2016, at 2:26 PM, Morteza Ansari (moransar) &lt;<a href=3D"mailto=
:moransar@cisco.com">moransar@cisco.com</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Is this even something we could define for abstract e=
vents? &nbsp;Doesn=E2=80=99t that semantics really associated with the type o=
f event we are talking about? &nbsp;I think this is a property that should b=
e defined for a given type of event and not across
 all events.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Cheers,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Morteza<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0=
in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,sans-serif;color:black">From:
</span></b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,s=
ans-serif;color:black">Id-event &lt;<a href=3D"mailto:id-event-bounces@ietf.=
org">id-event-bounces@ietf.org</a>&gt; on behalf of Phil Hunt &lt;<a href=3D=
"mailto:phil.hunt@oracle.com">phil.hunt@oracle.com</a>&gt;<br>
<b>Date: </b>Friday, September 16, 2016 at 2:00 PM<br>
<b>To: </b>Nicholas Roy &lt;<a href=3D"mailto:nroy@internet2.edu">nroy@inter=
net2.edu</a>&gt;<br>
<b>Cc: </b>"<a href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a>" &lt;=
<a href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: [Id-event] Proposed text for txn and ordering<o:p></o:p>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal">It occurs to me that the terminology for idempotency i=
s wrong. Scim is idempotent in that any request can be repeated. However a s=
eries of transactions does have order and dependence.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I will look for another way to express this or just d=
rop the idempotence term.&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
Phil<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Sep 16, 2016, at 7:15 AM, Nicholas Roy &lt;<a href=3D"mailto:nroy@interne=
t2.edu">nroy@internet2.edu</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">+1<br>
<br>
Nick<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On 9/15/16 7:32 PM, Marius Scurtescu wrote:<o:p></o:p=
></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">Sounds good to me.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Marius<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Sep 15, 2016 at 3:28 PM, Phil Hunt &lt;<a hre=
f=3D"mailto:phil.hunt@oracle.com" target=3D"_blank">phil.hunt@oracle.com</a>=
&gt; wrote:<o:p></o:p></p>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0in=
 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class=3D"MsoNormal">Based on the feedback, I am proposing the following c=
hanges:
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In the new attributes defined section, a new claim =E2=
=80=9Ctxn=E2=80=9D defined:<o:p></o:p></p>
</div>
<div>
<div>
<pre style=3D"word-wrap:break-word;white-space:pre-wrap">&nbsp;&nbsp; txn<o:=
p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; An OPTIONAL single-valued String value t=
hat represents a unique<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; transaction identifier.&nbsp; In cases w=
here multiple SETs are issued<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; based on different event URIs, the trans=
action identifier MAY be<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; used to correlate SETs to the same origi=
nating event or stateful<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; change.<o:p></o:p></pre>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:8.5pt;font-family:&quot;Mona=
co&quot;,serif"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">Regarding Ordering, I am proposing the following sect=
ion:<o:p></o:p></p>
</div>
<div>
<pre style=3D"word-wrap:break-word;white-space:pre-wrap"><span style=3D"font=
-size:8.5pt">2.2.&nbsp; Idempotency and Ordering Considerations<o:p></o:p></=
span></pre>
<pre><span style=3D"font-size:8.5pt"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; In many cases SETs will be=
 issued by highly distributed systems and<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; subscribers.&nbsp; Without=
 additional specification it is quite<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; conceivable that the order=
 of SETs received by a subscriber MAY be<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; different from the order o=
f the originating state changes or events.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; While the "iat" value may g=
ive a rough indication of SET order, it<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; SHOULD NOT be relied upon u=
nless the profiling SET token<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; specification provides cla=
rification.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; Profiling specifications a=
re encouraged to consider whether the<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; nature of SETs defined are=
 "idempotent" in the sense that the order<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; of receipt does not matter=
.&nbsp; For example, in the case of token<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; revocations, each SET can s=
tand on its own and order has no impact.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; In contrast, a profiling S=
ET specification related to provisioning<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; might be highly dependent o=
n ordering.&nbsp; As an example: one SET<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; indicates a new resource w=
as created, while the next SET indicates<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; the same resource is modif=
ied.&nbsp; Non-Idempotent SET event<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; specifications SHOULD choo=
se to define a sequencing method such as aa<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; claim used for the purpose=
 or identifying the order of SETs as<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; defined by the Feed Publis=
her or another method that is part of how<o:p></o:p></span></pre>
<pre><span style=3D"font-size:8.5pt">&nbsp;&nbsp; SETs are distributed.</spa=
n><o:p></o:p></pre>
</div>
<div>
<p class=3D"MsoNormal">Thanks for your feedback.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Phil<o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">@independentid<o:p></o:p>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"http://www.ind=
ependentid.com" target=3D"_blank">www.independentid.com</a><o:p></o:p></span=
></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"mailto:phil.hu=
nt@oracle.com" target=3D"_blank">phil.hunt@oracle.com</a><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span><=
/p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/id-event</a><o:p></o:p></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Id-event mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><a href=3D"ht=
tps://www.ietf.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/l=
istinfo/id-event</a><o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www.ietf.=
org/mailman/listinfo/id-event</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>


</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>Id-event mailing list</span><br>=
<span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></span><br><=
span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www.=
ietf.org/mailman/listinfo/id-event</a></span><br></div></blockquote></body><=
/html>=

--Apple-Mail-12A507B7-A96F-409A-9FAA-EC3995880EB4--


From nobody Fri Sep 23 15:44:55 2016
Return-Path: <ietf@kuehlewind.net>
X-Original-To: id-event@ietf.org
Delivered-To: id-event@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3215E12B3E0; Fri, 23 Sep 2016 15:44:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Mirja Kuehlewind" <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.33.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147467068816.20357.14858326596460414254.idtracker@ietfa.amsl.com>
Date: Fri, 23 Sep 2016 15:44:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/Ev0vvB5F72KmFFouxGV9DRglE9w>
Cc: secevent-chairs@ietf.org, id-event@ietf.org
Subject: [Id-event] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_cha?= =?utf-8?q?rter-ietf-secevent-00-00=3A_=28with_COMMENT=29?=
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Sep 2016 22:44:48 -0000

Mirja KÃ¼hlewind has entered the following ballot position for
charter-ietf-secevent-00-00: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-secevent/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I find the milestone timeline quite agressive but okay.



From nobody Sat Sep 24 04:04:40 2016
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB34912B078 for <id-event@ietfa.amsl.com>; Sat, 24 Sep 2016 04:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=RmJhTrdD; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=SOkMH5yi
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GZdSlbL-r0DY for <id-event@ietfa.amsl.com>; Sat, 24 Sep 2016 04:04:35 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F27E612B051 for <id-event@ietf.org>; Sat, 24 Sep 2016 04:04:34 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 54C14205F2; Sat, 24 Sep 2016 07:04:34 -0400 (EDT)
Received: from web6 ([10.202.2.216]) by compute6.internal (MEProxy); Sat, 24 Sep 2016 07:04:34 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=NjvX/YG05AeDCGk4p7YK1f5BI0A=; b=RmJhTr dDnEgOwmt0SjRCxrD8Oz20sFRODZ9Xvl8hkMfBNIkEHNh/brAshUgwr3z/hbmH4K 05or6Xt+1+Crz9ctCAxwInMhFq7y6eGM6jENgIVJBrg15lbe0Rw1gxb//N7/jZJP YLg37rKIwstJ8TaYDCxYk/3NJlk9D30tqP4l4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=NjvX/YG05AeDCGk 4p7YK1f5BI0A=; b=SOkMH5yiLZVIzkawSyHp+Dw68J0Jz5nTebZsv+0J4xrCgoq Wj4/g/wBSPlrZXaXirNNPSvLLNoO9xHNq6d1bGAfGAHhsSrGL3Rki2enRMGk8Tmq f16hvsxsvZJ+DUsPv4kMpdDH560Bqk3PMq4iK4HzDUfPa+w9Juf96w7ahHZs=
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 033261EB85; Sat, 24 Sep 2016 07:04:33 -0400 (EDT)
Message-Id: <1474715073.2319843.735650465.3C69F11E@webmail.messagingengine.com>
X-Sasl-Enc: P6INwwLUWUAK+99PuwkW7V7/xCPRH/KSAW3qMlvsd8Sf 1474715073
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: William Denniss <wdenniss@google.com>, Mike Jones <Michael.Jones@microsoft.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_147471507323198430"; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-3ce3fca2
Date: Sat, 24 Sep 2016 12:04:33 +0100
In-Reply-To: <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/mvUd7mEbRu_jV8_1z-htPws03Xg>
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, id-event@ietf.org
Subject: [Id-event] Chartering of Security Events WG
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Sep 2016 11:04:38 -0000

This is a multi-part message in MIME format.

--_----------=_147471507323198430
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Hi,
Just to let everyone know: I started chartering of the WG. The WG will
be in the Security Area (it was a borderline between ART and Security)
and your responsible AD is going to be Kathleen Moriarty.

Best Regards,
Alexey

P.S. I picked "SECEVENT" as the short WG name, but if you have better
     suggestions, please let me know.

On Wed, Sep 7, 2016, at 01:04 AM, William Denniss wrote:
> Thank you Mike for revising the charter.
>
> I support it, and hope we can form a WG with this charter to continue
> our work.
>
> On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones
> <Michael.Jones@microsoft.com> wrote:
>> An updated and simplified charter is attached.  This draft has been
>> reviewed by Phil Hunt, William Denniss, Marius Scurtescu.____
>> __ __
>> Input from Alexey Melnikov is that we should probably charter a
>> working group, rather than try to go the AD-sponsored route.
>> Therefore, please review this draft charter and let us know if you
>> think it=E2=80=99s ready to go.____
>> __ __
>>                                                        Thanks,____
>>                                                        -- Mike____
>> __ __
>>
>> *From:* Sarah Squire [mailto:sarah@engageidentity.com] *Sent:*
>> Thursday, July 14, 2016 10:59 PM *To:* Phil Hunt (IDM)
>> <phil.hunt@oracle.com> *Cc:* Mike Jones
>> <Michael.Jones@microsoft.com>; Alan Karp <alanhkarp@gmail.com>; Vivek
>> Biswas <vivek_biswas@yahoo.com>; Morteza Ansari (moransar)
>> <moransar@cisco.com>; id-event@ietf.org
>>
>> *Subject:* Re: [Id-event] Straw man text for proposed charter____
>>
>> __ __
>> Just submitting my two cents in writing before we hopefully have a
>> chance to meet about this next week...____
>> __ __
>> Looking at this charter from the perspective of the OIDF HEART
>> working group, I think it's going down a good path. In terms of the
>> data format, this is less structured than what I was envisioning, but
>> we could easily do a healthcare-specific profile of whatever data
>> format comes out in the end, so it's better to be too broad than too
>> narrow as far as our interests are concerned.____
>> __ __
>> The transport layer however, has some added complexity. In our
>> context, we're shooting for interoperability, so we'd prefer
>> something constrained. I appreciate Mike's input that these are
>> application layer decisions. However, if we're talking about cloud
>> provider-to-cloud provider communication, that certainly is
>> facilitated by a well-defined transport layer. Again, we're willing
>> to profile whatever the group comes up with for our own ends, but I
>> don't really see the benefit of having a loosely defined transport
>> layer - it just seems like more work for all the implementers to
>> actually agree on endpoints on a case-by-case basis.____
>> __ __
>> Looking forward to discussing further in Berlin!____
>> __ __
>> Sarah____
>> ____
>> Sarah Squire____
>> Engage Identity____
>> http://engageidentity.com[1]____
>> __ __
>> On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM)
>> <phil.hunt@oracle.com> wrote:____
>>> We also set things up so even a domain specific event can be
>>> extended. ____
>>> __ __
>>> Eg on a password reset event, so event publishers may want to add
>>> security domain specific attributes. The spec lets them do that
>>> while avoiding interop issues. ____
>>> __ __
>>> I believe in the spec we had the example of an account reset and the
>>> publisher adds reset count as an extension.
>>>
>>> Phil____
>>>
>>> On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com>
>>> wrote:____
>>>> Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93=
 so common claims can
>>>> be defined once and then reused.____
>>>>  ____
>>>> *From: *Vivek Biswas[2]
>>>> *Sent: *Saturday, May 7, 2016 1:24 PM
>>>> *To: *Mike Jones[3]
>>>> *Cc: *Alan Karp[4];  Morteza Ansari (moransar)[5];  id-
>>>> event@ietf.org
>>>> *Subject: *Re: [Id-event] Straw man text for proposed charter____
>>>>  ____
>>>> Yes, I agree that the claims can be application specific, however
>>>> there is a possibility to define claims which are domain specific.
>>>> Thereby claims generated in one application could be understood by
>>>> another  application within the same domain.____
>>>> __ __
>>>> With microservices based architecture getting lot of attention, if
>>>> two different micro services defining different claims for the same
>>>> claim, it can create confusion.____
>>>> __ __
>>>> Nevertheless this well defined claims for a particular domain can
>>>> be an extension to the core specification.____
>>>> __ __
>>>> -Vivek Biswas____
>>>>   Consulting Member, Oracle
>>>>
>>>>  Sent from my iPhone____
>>>>
>>>> On May 7, 2016, at 1:04 PM, Mike Jones
>>>> <Michael.Jones@microsoft.com> wrote:____
>>>>> Thanks Alan,____
>>>>>  ____
>>>>> Interoperability will be on a per-application basis, just like JWT
>>>>> interoperability.  The claims needed in an identity event are applica=
tion-
>>>>> specific, just like claims are for JWTs.  This is the same
>>>>> standards posture and JWTs are a huge success =E2=80=93 including for
>>>>> interoperability, even if I do say so myself.____
>>>>>  ____
>>>>>                                                           Best wi-
>>>>>                                                           shes,__-
>>>>>                                                           __
>>>>>                                                           -- Mike-
>>>>>                                                           ____
>>>>>  ____
>>>>>  ____
>>>>>  ____
>>>>>  ____
>>>>> *From: *Alan Karp[6]
>>>>> *Sent: *Saturday, May 7, 2016 10:23 AM
>>>>> *To: *Mike Jones[7]
>>>>> *Cc: *Morteza Ansari (moransar)[8]; id-event@ietf.org
>>>>> *Subject: *Re: [Id-event] Straw man text for proposed charter____
>>>>>  ____
>>>>> As one who proposed doing more, I believe that your position is
>>>>> valid.  My only question is whether or not that will be enough for
>>>>> interoperability.____
>>>>> ____
>>>>>
>>>>> --------------
>>>>>  Alan Karp____
>>>>> __ __
>>>>> On Thu, May 5, 2016 at 10:00 PM, Mike Jones
>>>>> <Michael.Jones@microsoft.com> wrote:____
>>>>>> Thanks guys, for writing the initial charter text.  Reading it
>>>>>> now, I am extremely worried by the scope creep evident in the
>>>>>> proposal.____
>>>>>>  ____
>>>>>> I strongly support a working group to define an ID Events data
>>>>>> format.  I just as strongly believe that specific event delivery
>>>>>> mechanisms will necessarily be application-specific and therefore
>>>>>> MUST be explicitly be stated as being out of scope in the working
>>>>>> group charter.  Attempting to specify a particular event delivery
>>>>>> mechanism will take something that could be simple and quick to
>>>>>> approve and bog it down in necessarily application-specific
>>>>>> debates.____
>>>>>>  ____
>>>>>> Should event delivery be reliable?  That=E2=80=99s an application-
>>>>>> specific decision.____
>>>>>> Should events be idempotent?  That=E2=80=99s an application-specific
>>>>>> decision.____
>>>>>> Should events be unicast, multicast, or broadcast?  That=E2=80=99s a=
n application-
>>>>>> specific decision.____
>>>>>> Should events have categories with category-specific
>>>>>> subscriptions?  That=E2=80=99s an application-specific decision.____
>>>>>> Should only one party at a time be able to register for delivery
>>>>>> of events or should multiple parties be able to request delivery?
>>>>>> That=E2=80=99s an application-specific decision.____
>>>>>> I could continue with this list, but I think you all get the
>>>>>> point=E2=80=A6____
>>>>>>  ____
>>>>>> If we start debating application-specific event delivery
>>>>>> mechanisms, we=E2=80=99ll please almost no one, since nearly all
>>>>>> applications have different event delivery requirements.  We MUST
>>>>>> explicitly rule all delivery mechanisms as being out of
>>>>>> scope.____
>>>>>>  ____
>>>>>> If we define only a data format, we can quickly produce a very
>>>>>> useful specification.  If we don=E2=80=99t, we=E2=80=99ll get bogged=
 down in the
>>>>>> mud of debating which applications we=E2=80=99re catering to and whi=
ch we
>>>>>> aren=E2=80=99t =E2=80=93 an exercise of picking favorites and limiti=
ng
>>>>>> applicability of the specification.  That way is a slow, painful
>>>>>> descent into standards quicksand =E2=80=93 something we must avoid.
>>>>>> Having a standard ID events representation is far too important
>>>>>> to tie to a particular limited event delivery mechanism.____
>>>>>>  ____
>>>>>>                                                           Sincer-
>>>>>>                                                           ely,__-
>>>>>>                                                           __
>>>>>>                                                           -- Mik-
>>>>>>                                                           e____
>>>>>>  ____
>>>>>> *From:* Id-event [mailto:id-event-bounces@ietf.org] *On Behalf Of
>>>>>> *Alan Karp *Sent:* Thursday, May 5, 2016 9:43 PM *To:* Morteza
>>>>>> Ansari (moransar) <moransar@cisco.com> *Cc:* id-event@ietf.org
>>>>>> *Subject:* Re: [Id-event] Straw man text for proposed charter____
>>>>>>  ____
>>>>>> I don't see anything about access control for publishing events
>>>>>> and subscribing to them.  I also think the spec should allow
>>>>>> filters on subscriptions.____
>>>>>> ____
>>>>>>
>>>>>> --------------
>>>>>>  Alan Karp____
>>>>>>  ____
>>>>>> On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar)
>>>>>> <moransar@cisco.com> wrote:____
>>>>>>> Hi folks,____
>>>>>>>  ____
>>>>>>> At IIW a few of us (Phil, William, Adam, and I) huddled for a
>>>>>>> bit and put together the attached as a straw man charter
>>>>>>> proposal to start the discussion. Please send your comments and
>>>>>>> suggestions for any changes or propose a new one if you think
>>>>>>> its necessary.____
>>>>>>>  ____
>>>>>>>  ____
>>>>>>> Cheers,____
>>>>>>> Morteza____
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>>  Id-event mailing list
>>>>>>> Id-event@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/id-event____
>>>>>>  ____
>>>>> __ __
>>>>> _______________________________________________
>>>>>  Id-event mailing list
>>>>> Id-event@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/id-event____
>>>> _______________________________________________
>>>>  Id-event mailing list
>>>> Id-event@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/id-event____
>>>
>>> _______________________________________________
>>>  Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event____
>> __ __


Links:

  1. http://engageidentity.com/
  2. mailto:vivek_biswas@yahoo.com
  3. mailto:Michael.Jones@microsoft.com
  4. mailto:alanhkarp@gmail.com
  5. mailto:moransar@cisco.com
  6. mailto:alanhkarp@gmail.com
  7. mailto:Michael.Jones@microsoft.com
  8. mailto:moransar@cisco.com

--_----------=_147471507323198430
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>Hi,<br></div>
<div>Just to let everyone know: I started chartering of the WG. The WG will=
 be in the Security Area (it was a borderline between ART and Security) and=
 your responsible AD is going to be&nbsp;Kathleen Moriarty.</div>
<div id=3D"sig21611513"><div class=3D"signature"><br></div>
<div class=3D"signature">Best Regards,<br></div>
<div class=3D"signature">Alexey<br></div>
<div class=3D"signature"><br></div>
<div class=3D"signature">P.S. I picked "SECEVENT" as the short WG name, but=
 if you have better suggestions, please let me know.</div>
<div><br></div>
</div>
<div>On Wed, Sep 7, 2016, at 01:04 AM, William Denniss wrote:<br></div>
<blockquote type=3D"cite"><div dir=3D"ltr"><div>Thank you Mike for revising=
 the charter.&nbsp;<br></div>
<div><br></div>
<div>I support it, and hope we can form a WG with this charter to continue =
our work.<br></div>
</div>
<div><div><br></div>
<div defang_data-gmailquote=3D"yes"><div>On Tue, Sep 6, 2016 at 5:01 PM, Mi=
ke Jones <span dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.co=
m">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br></div>
<blockquote style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;marg=
in-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);bo=
rder-left-style:solid;padding-left:1ex;" defang_data-gmailquote=3D"yes"><di=
v lang=3D"EN-US"><div><p><span class=3D"colour" style=3D"color:rgb(0, 32, 9=
6)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span cl=
ass=3D"size" style=3D"font-size:11pt">An updated and simplified charter is =
attached.&nbsp; This draft has been reviewed by Phil Hunt, William Denniss,=
 Marius Scurtescu.<u></u><u></u></span></span></span><br></p><p><span class=
=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"fo=
nt-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt=
"><u></u>&nbsp;<u></u></span></span></span><br></p><p><span class=3D"colour=
" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:=
Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">Input fr=
om Alexey Melnikov is that we should probably charter a working group, rath=
er than try to go the AD-sponsored route.&nbsp; Therefore, please review th=
is draft
 charter and let us know if you think it=E2=80=99s ready to go.<u></u><u></=
u></span></span></span><br></p><p><span class=3D"colour" style=3D"color:rgb=
(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"=
><span class=3D"size" style=3D"font-size:11pt"><u></u>&nbsp;<u></u></span><=
/span></span><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 96=
)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span cla=
ss=3D"size" style=3D"font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<=
u></u><u></u></span></span></span><br></p><p><span class=3D"colour" style=
=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri=
, sans-serif"><span class=3D"size" style=3D"font-size:11pt">&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; -- Mike<u></u><u></u></span></span></span><br></p><p><a name=
=3D"m_5165357944078144809__MailEndCompose"><span class=3D"colour" style=3D"=
color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sa=
ns-serif"><span class=3D"size" style=3D"font-size:11pt"><u></u>&nbsp;<u></u=
></span></span></span></a><br></p><div><span></span><br></div>
<p><b><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span =
class=3D"size" style=3D"font-size:11pt">From:</span></span></b><span class=
=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" st=
yle=3D"font-size:11pt"> Sarah Squire [mailto:<a href=3D"mailto:sarah@engage=
identity.com">sarah@engageidentity.<wbr>com</a>] <br> <b>Sent:</b> Thursday=
, July 14, 2016 10:59 PM<br> <b>To:</b> Phil Hunt (IDM) &lt;<a href=3D"mail=
to:phil.hunt@oracle.com">phil.hunt@oracle.com</a>&gt;<br> <b>Cc:</b> Mike J=
ones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@micro=
soft.com</a>&gt;; Alan Karp &lt;<a href=3D"mailto:alanhkarp@gmail.com">alan=
hkarp@gmail.com</a>&gt;; Vivek Biswas &lt;<a href=3D"mailto:vivek_biswas@ya=
hoo.com">vivek_biswas@yahoo.com</a>&gt;; Morteza Ansari (moransar) &lt;<a h=
ref=3D"mailto:moransar@cisco.com">moransar@cisco.com</a>&gt;; <a href=3D"ma=
ilto:id-event@ietf.org">id-event@ietf.org</a></span></span></p><div><div><d=
iv><br></div>
<div><b>Subject:</b> Re: [Id-event] Straw man text for proposed charter<u><=
/u><u></u><br></div>
</div>
</div>
<p><br></p><div><div><p><u></u>&nbsp;<u></u><br></p><div><div><p>Just submi=
tting my two cents in writing before we hopefully have a chance to meet abo=
ut this next week...<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<p>Looking at this charter from the perspective of the OIDF HEART working g=
roup, I think it's going down a good path. In terms of the data format, thi=
s is less structured than what I was envisioning, but we could easily do a =
healthcare-specific
 profile of whatever data format comes out in the end, so it's better to be=
 too broad than too narrow as far as our interests are concerned.<u></u><u>=
</u><br></p><div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>The transport layer however, has some added complexity. In our cont=
ext, we're shooting for interoperability, so we'd prefer something constrai=
ned. I appreciate Mike's input that these are application layer decisions. =
However, if we're talking
 about cloud provider-to-cloud provider communication, that certainly is fa=
cilitated by a well-defined transport layer. Again, we're willing to profil=
e whatever the group comes up with for our own ends, but I don't really see=
 the benefit of having a loosely
 defined transport layer - it just seems like more work for all the impleme=
nters to actually agree on endpoints on a case-by-case basis.<u></u><u></u>=
<br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Looking forward to discussing further in Berlin!<u></u><u></u><br><=
/p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Sarah<u></u><u></u><br></p></div>
</div>
<div><p><u></u><u></u><br></p><div><div><div><div><p><span class=3D"colour"=
 style=3D"color:rgb(136, 136, 136)">Sarah Squire<u></u><u></u></span><br></=
p></div>
<div><p><span class=3D"colour" style=3D"color:rgb(136, 136, 136)">Engage Id=
entity<u></u><u></u></span><br></p></div>
<div><p><span class=3D"colour" style=3D"color:rgb(136, 136, 136)"><a href=
=3D"http://engageidentity.com/"><span class=3D"colour" style=3D"color:rgb(1=
7, 85, 204)">http://engageidentity.com</span></a><u></u><u></u></span><br><=
/p></div>
</div>
</div>
</div>
<p><u></u>&nbsp;<u></u><br></p><div><p>On Sat, May 7, 2016 at 6:53 PM, Phil=
 Hunt (IDM) &lt;<a href=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.co=
m</a>&gt; wrote:<u></u><u></u><br></p><blockquote style=3D"border-top-style=
:none;border-right-style:none;border-bottom-style:none;border-top-width:ini=
tial;border-right-width:initial;border-bottom-width:initial;border-top-colo=
r:initial;border-right-color:initial;border-bottom-color:initial;border-ima=
ge-source:initial;border-image-slice:initial;border-image-width:initial;bor=
der-image-outset:initial;border-image-repeat:initial;border-left-style:soli=
d;border-left-color:rgb(204, 204, 204);border-left-width:1pt;padding-top:0i=
n;padding-right:0in;padding-bottom:0in;padding-left:6pt;margin-left:4.8pt;m=
argin-right:0in;"><div><div><p>We also set things up so even a domain speci=
fic event can be extended.&nbsp;<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Eg on a password reset event, so event publishers may want to add s=
ecurity domain specific attributes. The spec lets them do that while avoidi=
ng interop issues.&nbsp;<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>I believe in the spec we had the example of an account reset and th=
e publisher adds reset count as an extension.&nbsp;<span class=3D"colour" s=
tyle=3D"color:rgb(136, 136, 136)"><br> <br> <span>Phil</span></span><u></u>=
<u></u></p></div>
<div><div><div><p style=3D"margin-bottom:12pt;"><div><br></div>
<div>On May 7, 2016, at 13:31, Mike Jones &lt;<a href=3D"mailto:Michael.Jon=
es@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<u></u><u></u><=
br></div>
</p></div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><div><p>Indeed=
, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 so common =
claims can be defined once and then reused.<u></u><u></u><br></p><p>&nbsp;<=
u></u><u></u><br></p><div style=3D"border-right-style:none;border-bottom-st=
yle:none;border-left-style:none;border-right-width:initial;border-bottom-wi=
dth:initial;border-left-width:initial;border-right-color:initial;border-bot=
tom-color:initial;border-left-color:initial;border-image-source:initial;bor=
der-image-slice:initial;border-image-width:initial;border-image-outset:init=
ial;border-image-repeat:initial;border-top-style:solid;border-top-color:rgb=
(225, 225, 225);border-top-width:1pt;padding-top:3pt;padding-right:0in;padd=
ing-bottom:0in;padding-left:0in;"><p><div><b>From: </b><a href=3D"mailto:vi=
vek_biswas@yahoo.com">Vivek Biswas</a><br></div>
<div> <b>Sent: </b>Saturday, May 7, 2016 1:24 PM<br></div>
<div> <b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com">Mike Jones<=
/a><br></div>
<div> <b>Cc: </b><a href=3D"mailto:alanhkarp@gmail.com">Alan Karp</a>; <a h=
ref=3D"mailto:moransar@cisco.com"> Morteza Ansari (moransar)</a>; <a href=
=3D"mailto:id-event@ietf.org"> id-event@ietf.org</a><br></div>
<div> <b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u>=
</u><u></u><br></div>
</p></div>
<p>&nbsp;<u></u><u></u><br></p></div>
<div><div><p>Yes, I agree that the claims can be application specific, howe=
ver there is a possibility to define claims which are domain specific. Ther=
eby claims generated in one application could be understood by another &nbs=
p;application within the same
 domain.<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>With microservices based architecture getting lot of attention, if =
two different micro services defining different claims for the same claim, =
it can create confusion.<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Nevertheless this well defined claims for a particular domain can b=
e an extension to the core specification.<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>-Vivek Biswas<u></u><u></u><br></p></div>
<div><p><div>&nbsp; Consulting Member, Oracle<br></div>
<div> <br></div>
<div> Sent from my iPhone<u></u><u></u><br></div>
</p></div>
<div><p style=3D"margin-bottom:12pt;"><div><br></div>
<div>On May 7, 2016, at 1:04 PM, Mike Jones &lt;<a href=3D"mailto:Michael.J=
ones@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<u></u><u></u=
><br></div>
</p></div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><div><p>Thanks=
 Alan,<u></u><u></u><br></p><p>&nbsp;<u></u><u></u><br></p><p><span class=
=3D"colour" style=3D"color:rgb(0, 32, 96)">Interoperability will be on a pe=
r-application basis, just like JWT interoperability.&nbsp; The claims neede=
d in an identity event are application-specific,
 just like claims are for JWTs.&nbsp; This is the same standards posture an=
d JWTs are a huge success =E2=80=93 including for interoperability, even if=
 I do say so myself.</span><u></u><u></u><br></p><p><span class=3D"colour" =
style=3D"color:rgb(0, 32, 96)">&nbsp;</span><u></u><u></u><br></p><p><span =
class=3D"colour" style=3D"color:rgb(0, 32, 96)">&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Best wishes,</span><u></u><u></u><br></p><p><span clas=
s=3D"colour" style=3D"color:rgb(0, 32, 96)">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<=
wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; -- Mike</span><u></u><u></u><br></p><p>&nbsp;<u></u><u></u=
><br></p><p>&nbsp;<u></u><u></u><br></p><p>&nbsp;<u></u><u></u><br></p><p>&=
nbsp;<u></u><u></u><br></p><div style=3D"border-right-style:none;border-bot=
tom-style:none;border-left-style:none;border-right-width:initial;border-bot=
tom-width:initial;border-left-width:initial;border-right-color:initial;bord=
er-bottom-color:initial;border-left-color:initial;border-image-source:initi=
al;border-image-slice:initial;border-image-width:initial;border-image-outse=
t:initial;border-image-repeat:initial;border-top-style:solid;border-top-col=
or:rgb(225, 225, 225);border-top-width:1pt;padding-top:3pt;padding-right:0i=
n;padding-bottom:0in;padding-left:0in;"><p><div><b>From: </b><a href=3D"mai=
lto:alanhkarp@gmail.com">Alan Karp</a><br></div>
<div> <b>Sent: </b>Saturday, May 7, 2016 10:23 AM<br></div>
<div> <b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com">Mike Jones<=
/a><br></div>
<div> <b>Cc: </b><a href=3D"mailto:moransar@cisco.com">Morteza Ansari (mora=
nsar)</a>; <a href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a><br></=
div>
<div> <b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u>=
</u><u></u><br></div>
</p></div>
<p>&nbsp;<u></u><u></u><br></p></div>
<div><div><p><span class=3D"size" style=3D"font-size:9.5pt">As one who prop=
osed doing more, I believe that your position is valid.&nbsp; My only quest=
ion is whether or not that will be enough for interoperability.</span><u></=
u><u></u><br></p></div>
<div><p><u></u><u></u><br></p><div><div><p><div><br></div>
<div>--------------<br></div>
<div> Alan Karp<u></u><u></u><br></div>
</p></div>
</div>
<p><u></u>&nbsp;<u></u><br></p><div><p>On Thu, May 5, 2016 at 10:00 PM, Mik=
e Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@mi=
crosoft.com</a>&gt; wrote:<u></u><u></u><br></p><blockquote style=3D"border=
-top-style:none;border-right-style:none;border-bottom-style:none;border-top=
-width:initial;border-right-width:initial;border-bottom-width:initial;borde=
r-top-color:initial;border-right-color:initial;border-bottom-color:initial;=
border-image-source:initial;border-image-slice:initial;border-image-width:i=
nitial;border-image-outset:initial;border-image-repeat:initial;border-left-=
style:solid;border-left-color:rgb(204, 204, 204);border-left-width:1pt;padd=
ing-top:0in;padding-right:0in;padding-bottom:0in;padding-left:6pt;margin-le=
ft:4.8pt;margin-right:0in;"><div><div><p><span class=3D"colour" style=3D"co=
lor:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans=
-serif"><span class=3D"size" style=3D"font-size:11pt">Thanks guys, for writ=
ing the initial charter text.&nbsp; Reading it now, I am extremely worried =
by the scope
 creep evident in the proposal.</span></span></span><u></u><u></u><br></p><=
p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font=
" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"f=
ont-size:11pt">&nbsp;</span></span></span><u></u><u></u><br></p><p><span cl=
ass=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D=
"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:1=
1pt">I strongly support a working group to define an ID Events data format.=
&nbsp; I just as strongly believe
 that specific event delivery mechanisms will necessarily be application-sp=
ecific and therefore MUST be explicitly be stated as being out of scope in =
the working group charter.&nbsp; Attempting to specify a particular event d=
elivery mechanism will take something
 that could be simple and quick to approve and bog it down in necessarily a=
pplication-specific debates.</span></span></span><u></u><u></u><br></p><p><=
span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:11pt">&nbsp;</span></span></span><u></u><u></u><br></p><p><span class=
=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"fo=
nt-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt=
">Should event delivery be reliable?&nbsp; That=E2=80=99s an application-sp=
ecific decision.</span></span></span><u></u><u></u><br></p><p><span class=
=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"fo=
nt-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt=
">Should events be idempotent?&nbsp; That=E2=80=99s an application-specific=
 decision.</span></span></span><u></u><u></u><br></p><p><span class=3D"colo=
ur" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-famil=
y:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">Should=
 events be unicast, multicast, or broadcast?&nbsp; That=E2=80=99s an applic=
ation-specific decision.</span></span></span><u></u><u></u><br></p><p><span=
 class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-siz=
e:11pt">Should events have categories with category-specific subscriptions?=
&nbsp; That=E2=80=99s an application-specific
 decision.</span></span></span><u></u><u></u><br></p><p><span class=3D"colo=
ur" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-famil=
y:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">Should=
 only one party at a time be able to register for delivery of events or sho=
uld multiple parties
 be able to request delivery?&nbsp; That=E2=80=99s an application-specific =
decision.</span></span></span><u></u><u></u><br></p><p><span class=3D"colou=
r" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family=
:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">I could=
 continue with this list, but I think you all get the point=E2=80=A6</span>=
</span></span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"colo=
r:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-s=
erif"><span class=3D"size" style=3D"font-size:11pt">&nbsp;</span></span></s=
pan><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 3=
2, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><spa=
n class=3D"size" style=3D"font-size:11pt">If we start debating application-=
specific event delivery mechanisms, we=E2=80=99ll please almost no one, sin=
ce
 nearly all applications have different event delivery requirements.&nbsp; =
We MUST explicitly rule all delivery mechanisms as being out of scope.</spa=
n></span></span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"co=
lor:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans=
-serif"><span class=3D"size" style=3D"font-size:11pt">&nbsp;</span></span><=
/span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0,=
 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><s=
pan class=3D"size" style=3D"font-size:11pt">If we define only a data format=
, we can quickly produce a very useful specification.&nbsp; If we don=E2=80=
=99t,
 we=E2=80=99ll get bogged down in the mud of debating which applications we=
=E2=80=99re catering to and which we aren=E2=80=99t =E2=80=93 an exercise o=
f picking favorites and limiting applicability of the specification.&nbsp; =
That way is a slow, painful descent into standards quicksand =E2=80=93 some=
thing
 we must avoid.&nbsp; Having a standard ID events representation is far too=
 important to tie to a particular limited event delivery mechanism.</span><=
/span></span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color=
:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-se=
rif"><span class=3D"size" style=3D"font-size:11pt">&nbsp;</span></span></sp=
an><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32=
, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span=
 class=3D"size" style=3D"font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; Sincerely,</span></span></span><u></u><u></u><br></p><p><span=
 class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-siz=
e:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span></spa=
n></span><u></u><u></u><br></p><p><a name=3D"m_5165357944078144809_m_302236=
7059336893565_m_1461024254222911"><span class=3D"colour" style=3D"color:rgb=
(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"=
><span class=3D"size" style=3D"font-size:11pt">&nbsp;</span></span></span><=
/a><u></u><u></u><br></p><p><b><span class=3D"font" style=3D"font-family:Ca=
libri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">From:</spa=
n></span></b><span class=3D"font" style=3D"font-family:Calibri, sans-serif"=
><span class=3D"size" style=3D"font-size:11pt"> Id-event [mailto:<a href=3D=
"mailto:id-event-bounces@ietf.org">id-event-bounces@ietf.<wbr>org</a>] <b>O=
n Behalf Of </b>Alan Karp<br> <b>Sent:</b> Thursday, May 5, 2016 9:43 PM<br=
> <b>To:</b> Morteza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco=
.com">moransar@cisco.com</a>&gt;<br> <b>Cc:</b> <a href=3D"mailto:id-event@=
ietf.org">id-event@ietf.org</a><br> <b>Subject:</b> Re: [Id-event] Straw ma=
n text for proposed charter</span></span><u></u><u></u></p><p>&nbsp;<u></u>=
<u></u><br></p><div><p>I don't see anything about access control for publis=
hing events and subscribing to them.&nbsp; I also think the spec should all=
ow filters on subscriptions.<u></u><u></u><br></p></div>
<div><p><u></u><u></u><br></p><div><div><p><div><br></div>
<div>--------------<br></div>
<div> Alan Karp<u></u><u></u><br></div>
</p></div>
</div>
<p>&nbsp;<u></u><u></u><br></p><div><p>On Thu, May 5, 2016 at 11:18 AM, Mor=
teza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.com">moransar@c=
isco.com</a>&gt; wrote:<u></u><u></u><br></p><blockquote style=3D"border-to=
p-style:none;border-right-style:none;border-bottom-style:none;border-top-wi=
dth:initial;border-right-width:initial;border-bottom-width:initial;border-t=
op-color:initial;border-right-color:initial;border-bottom-color:initial;bor=
der-image-source:initial;border-image-slice:initial;border-image-width:init=
ial;border-image-outset:initial;border-image-repeat:initial;border-left-sty=
le:solid;border-left-color:rgb(204, 204, 204);border-left-width:1pt;padding=
-top:0in;padding-right:0in;padding-bottom:0in;padding-left:6pt;margin-left:=
4.8pt;margin-top:5pt;margin-right:0in;margin-bottom:5pt;"><div><div><p><spa=
n class=3D"colour" style=3D"color:black"><span class=3D"font" style=3D"font=
-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:10.5pt=
">Hi folks,</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">&nbsp;</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">At IIW a few of us (Phil, William, Adam, and I) huddled for a=
 bit and put together the attached as a
 straw man charter proposal to start the discussion. Please send your comme=
nts and suggestions for any changes or propose a new one if you think its n=
ecessary.</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">&nbsp;</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">&nbsp;</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">Cheers,</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">Morteza</span></span></span><u></u><u></u><br></p></div>
</div>
<p style=3D"margin-bottom:12pt;"><div><br></div>
<div>______________________________<wbr>_________________<br></div>
<div> Id-event mailing list<br></div>
<div> <a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div> <a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://ww=
w.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
</p></blockquote></div>
<p>&nbsp;<u></u><u></u><br></p></div>
</div>
</div>
</blockquote></div>
<p><u></u>&nbsp;<u></u><br></p></div>
</div>
</div>
</blockquote><blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><=
p><div>______________________________<wbr>_________________<br></div>
<div> Id-event mailing list<br></div>
<div> <a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div> <a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://ww=
w.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
</p></div>
</blockquote></div>
</div>
</blockquote><blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><=
p><div>______________________________<wbr>_________________<br></div>
<div> Id-event mailing list<br></div>
<div> <a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div> <a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://ww=
w.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
</p></div>
</blockquote></div>
</div>
</div>
<p style=3D"margin-bottom:12pt;"><div><br></div>
<div>______________________________<wbr>_________________<br></div>
<div> Id-event mailing list<br></div>
<div> <a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div> <a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://ww=
w.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
</p></blockquote></div>
<p><u></u>&nbsp;<u></u><br></p></div>
</div>
</div>
</div>
</div>
</blockquote></div>
</div>
</blockquote><div><br></div>
</body>
</html>

--_----------=_147471507323198430--



From nobody Sat Sep 24 04:27:18 2016
Return-Path: <moransar@cisco.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00CE912BA7E for <id-event@ietfa.amsl.com>; Sat, 24 Sep 2016 04:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.836
X-Spam-Level: 
X-Spam-Status: No, score=-16.836 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8nJ6Pk9TQV_w for <id-event@ietfa.amsl.com>; Sat, 24 Sep 2016 04:27:13 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6751512BA63 for <id-event@ietf.org>; Sat, 24 Sep 2016 04:27:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=40785; q=dns/txt; s=iport; t=1474716433; x=1475926033; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=bmzphoI/JvuJ1eDomQU9s1FfQg/5dFRkA3ftZ24MB5Y=; b=YdYnqm2fBEipxJ7I3nw6Nqykjees9Dv8NcYVboqopZKH1xj+aHatyN/S AT+kvwWbqFtJPFXP32Ip1/eAnptz59Jit8lIWQ8Oby6RNiPI24iYzDIFa yQpDsmmyF3LFLTionJNANKQ9jH0lPmoXemrFeRpE3fuVEJwQVIlJpkdvu w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DtAgDlYeZX/5ldJa1UCRkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYMHNAEBAQEBHld8hCyJB5lUKoUEjEeCAQMZAQqEICSBNgKBVTg?= =?us-ascii?q?UAQIBAQEBAQEBXieEYQEBAQQBAQFrBQYQAgEIDgMBAwEBFgMIAQYHIQYLEwEDB?= =?us-ascii?q?ggCBA4FiDEDFw65ZA2DQgEBAQEBAQEBAQEBAQEBAQEBAQEBARyGN4F8CIFLgQW?= =?us-ascii?q?CR4FWA1oIAQ+CYYIvBYYZUQyBQGKFHIsNNQGGJoYGQwaCcoFuToQWh2yBLYhch?= =?us-ascii?q?A+DewEeNhqCRoIlcoRDgi4BAQE?=
X-IronPort-AV: E=Sophos;i="5.30,387,1470700800";  d="scan'208,217";a="150730587"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Sep 2016 11:27:12 +0000
Received: from XCH-RTP-002.cisco.com (xch-rtp-002.cisco.com [64.101.220.142]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u8OBRBSE008318 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 24 Sep 2016 11:27:11 GMT
Received: from xch-rtp-004.cisco.com (64.101.220.144) by XCH-RTP-002.cisco.com (64.101.220.142) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 24 Sep 2016 07:27:10 -0400
Received: from xch-rtp-004.cisco.com ([64.101.220.144]) by XCH-RTP-004.cisco.com ([64.101.220.144]) with mapi id 15.00.1210.000; Sat, 24 Sep 2016 07:27:10 -0400
From: "Morteza Ansari (moransar)" <moransar@cisco.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Thread-Topic: [Id-event] Chartering of Security Events WG
Thread-Index: AQHSFlN1sjAXmrCLrUCCk3mmMkyI0qCIgIds
Date: Sat, 24 Sep 2016 11:27:10 +0000
Message-ID: <D03F281C-3051-4E0D-81C8-0F0CC0854A10@cisco.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com>, <1474715073.2319843.735650465.3C69F11E@webmail.messagingengine.com>
In-Reply-To: <1474715073.2319843.735650465.3C69F11E@webmail.messagingengine.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_D03F281C30514E0D81C80F0CC0854A10ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/cDhubdWbOQhRTG4JnmMz2Z7Jtvc>
Cc: William Denniss <wdenniss@google.com>, Mike Jones <Michael.Jones@microsoft.com>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, "id-event@ietf.org" <id-event@ietf.org>
Subject: Re: [Id-event] Chartering of Security Events WG
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Sep 2016 11:27:17 -0000

--_000_D03F281C30514E0D81C80F0CC0854A10ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

This is great, thanks for helping speed up the process! Name is a name, so =
no comment on naming.


Cheers,
Morteza

On Sep 24, 2016, at 4:04 AM, Alexey Melnikov <aamelnikov@fastmail.fm<mailto=
:aamelnikov@fastmail.fm>> wrote:

Hi,
Just to let everyone know: I started chartering of the WG. The WG will be i=
n the Security Area (it was a borderline between ART and Security) and your=
 responsible AD is going to be Kathleen Moriarty.

Best Regards,
Alexey

P.S. I picked "SECEVENT" as the short WG name, but if you have better sugge=
stions, please let me know.

On Wed, Sep 7, 2016, at 01:04 AM, William Denniss wrote:
Thank you Mike for revising the charter.

I support it, and hope we can form a WG with this charter to continue our w=
ork.

On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <Michael.Jones@microsoft.com<mai=
lto:Michael.Jones@microsoft.com>> wrote:

An updated and simplified charter is attached.  This draft has been reviewe=
d by Phil Hunt, William Denniss, Marius Scurtescu.



Input from Alexey Melnikov is that we should probably charter a working gro=
up, rather than try to go the AD-sponsored route.  Therefore, please review=
 this draft charter and let us know if you think it=92s ready to go.



                                                       Thanks,

                                                       -- Mike




From: Sarah Squire [mailto:sarah@engageidentity.com<mailto:sarah@engageiden=
tity.com>]
Sent: Thursday, July 14, 2016 10:59 PM
To: Phil Hunt (IDM) <phil.hunt@oracle.com<mailto:phil.hunt@oracle.com>>
Cc: Mike Jones <Michael.Jones@microsoft.com<mailto:Michael.Jones@microsoft.=
com>>; Alan Karp <alanhkarp@gmail.com<mailto:alanhkarp@gmail.com>>; Vivek B=
iswas <vivek_biswas@yahoo.com<mailto:vivek_biswas@yahoo.com>>; Morteza Ansa=
ri (moransar) <moransar@cisco.com<mailto:moransar@cisco.com>>; id-event@iet=
f.org<mailto:id-event@ietf.org>

Subject: Re: [Id-event] Straw man text for proposed charter




Just submitting my two cents in writing before we hopefully have a chance t=
o meet about this next week...



Looking at this charter from the perspective of the OIDF HEART working grou=
p, I think it's going down a good path. In terms of the data format, this i=
s less structured than what I was envisioning, but we could easily do a hea=
lthcare-specific profile of whatever data format comes out in the end, so i=
t's better to be too broad than too narrow as far as our interests are conc=
erned.



The transport layer however, has some added complexity. In our context, we'=
re shooting for interoperability, so we'd prefer something constrained. I a=
ppreciate Mike's input that these are application layer decisions. However,=
 if we're talking about cloud provider-to-cloud provider communication, tha=
t certainly is facilitated by a well-defined transport layer. Again, we're =
willing to profile whatever the group comes up with for our own ends, but I=
 don't really see the benefit of having a loosely defined transport layer -=
 it just seems like more work for all the implementers to actually agree on=
 endpoints on a case-by-case basis.



Looking forward to discussing further in Berlin!



Sarah


Sarah Squire

Engage Identity

http://engageidentity.com<http://engageidentity.com/>



On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com<mailt=
o:phil.hunt@oracle.com>> wrote:

We also set things up so even a domain specific event can be extended.



Eg on a password reset event, so event publishers may want to add security =
domain specific attributes. The spec lets them do that while avoiding inter=
op issues.



I believe in the spec we had the example of an account reset and the publis=
her adds reset count as an extension.

Phil

On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com<mailto:Mi=
chael.Jones@microsoft.com>> wrote:

Indeed, that=92s why there=92s a claims registry =96 so common claims can b=
e defined once and then reused.



From: Vivek Biswas<mailto:vivek_biswas@yahoo.com>
Sent: Saturday, May 7, 2016 1:24 PM
To: Mike Jones<mailto:Michael.Jones@microsoft.com>
Cc: Alan Karp<mailto:alanhkarp@gmail.com>; Morteza Ansari (moransar)<mailto=
:moransar@cisco.com>; id-event@ietf.org<mailto:id-event@ietf.org>
Subject: Re: [Id-event] Straw man text for proposed charter



Yes, I agree that the claims can be application specific, however there is =
a possibility to define claims which are domain specific. Thereby claims ge=
nerated in one application could be understood by another  application with=
in the same domain.



With microservices based architecture getting lot of attention, if two diff=
erent micro services defining different claims for the same claim, it can c=
reate confusion.



Nevertheless this well defined claims for a particular domain can be an ext=
ension to the core specification.



-Vivek Biswas

  Consulting Member, Oracle

Sent from my iPhone

On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com<mailto:=
Michael.Jones@microsoft.com>> wrote:

Thanks Alan,



Interoperability will be on a per-application basis, just like JWT interope=
rability.  The claims needed in an identity event are application-specific,=
 just like claims are for JWTs.  This is the same standards posture and JWT=
s are a huge success =96 including for interoperability, even if I do say s=
o myself.



                                                          Best wishes,

                                                          -- Mike









From: Alan Karp<mailto:alanhkarp@gmail.com>
Sent: Saturday, May 7, 2016 10:23 AM
To: Mike Jones<mailto:Michael.Jones@microsoft.com>
Cc: Morteza Ansari (moransar)<mailto:moransar@cisco.com>; id-event@ietf.org=
<mailto:id-event@ietf.org>
Subject: Re: [Id-event] Straw man text for proposed charter



As one who proposed doing more, I believe that your position is valid.  My =
only question is whether or not that will be enough for interoperability.


--------------
Alan Karp



On Thu, May 5, 2016 at 10:00 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:

Thanks guys, for writing the initial charter text.  Reading it now, I am ex=
tremely worried by the scope creep evident in the proposal.



I strongly support a working group to define an ID Events data format.  I j=
ust as strongly believe that specific event delivery mechanisms will necess=
arily be application-specific and therefore MUST be explicitly be stated as=
 being out of scope in the working group charter.  Attempting to specify a =
particular event delivery mechanism will take something that could be simpl=
e and quick to approve and bog it down in necessarily application-specific =
debates.



Should event delivery be reliable?  That=92s an application-specific decisi=
on.

Should events be idempotent?  That=92s an application-specific decision.

Should events be unicast, multicast, or broadcast?  That=92s an application=
-specific decision.

Should events have categories with category-specific subscriptions?  That=
=92s an application-specific decision.

Should only one party at a time be able to register for delivery of events =
or should multiple parties be able to request delivery?  That=92s an applic=
ation-specific decision.

I could continue with this list, but I think you all get the point=85



If we start debating application-specific event delivery mechanisms, we=92l=
l please almost no one, since nearly all applications have different event =
delivery requirements.  We MUST explicitly rule all delivery mechanisms as =
being out of scope.



If we define only a data format, we can quickly produce a very useful speci=
fication.  If we don=92t, we=92ll get bogged down in the mud of debating wh=
ich applications we=92re catering to and which we aren=92t =96 an exercise =
of picking favorites and limiting applicability of the specification.  That=
 way is a slow, painful descent into standards quicksand =96 something we m=
ust avoid.  Having a standard ID events representation is far too important=
 to tie to a particular limited event delivery mechanism.



                                                          Sincerely,

                                                          -- Mike



From: Id-event [mailto:id-event-bounces@ietf.org<mailto:id-event-bounces@ie=
tf.org>] On Behalf Of Alan Karp
Sent: Thursday, May 5, 2016 9:43 PM
To: Morteza Ansari (moransar) <moransar@cisco.com<mailto:moransar@cisco.com=
>>
Cc: id-event@ietf.org<mailto:id-event@ietf.org>
Subject: Re: [Id-event] Straw man text for proposed charter



I don't see anything about access control for publishing events and subscri=
bing to them.  I also think the spec should allow filters on subscriptions.


--------------
Alan Karp



On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar) <moransar@cisco.=
com<mailto:moransar@cisco.com>> wrote:

Hi folks,



At IIW a few of us (Phil, William, Adam, and I) huddled for a bit and put t=
ogether the attached as a straw man charter proposal to start the discussio=
n. Please send your comments and suggestions for any changes or propose a n=
ew one if you think its necessary.





Cheers,

Morteza

_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>
https://www.ietf.org/mailman/listinfo/id-event





_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>
https://www.ietf.org/mailman/listinfo/id-event

_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>
https://www.ietf.org/mailman/listinfo/id-event

_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>
https://www.ietf.org/mailman/listinfo/id-event



_______________________________________________
Id-event mailing list
Id-event@ietf.org<mailto:Id-event@ietf.org>
https://www.ietf.org/mailman/listinfo/id-event

--_000_D03F281C30514E0D81C80F0CC0854A10ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>This is great, thanks for helping speed up the process! Name is a name=
, so no comment on naming.&nbsp;<br>
<br>
<div><br>
</div>
Cheers,
<div>Morteza</div>
</div>
<div><br>
On Sep 24, 2016, at 4:04 AM, Alexey Melnikov &lt;<a href=3D"mailto:aamelnik=
ov@fastmail.fm">aamelnikov@fastmail.fm</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<title></title>
<div>Hi,<br>
</div>
<div>Just to let everyone know: I started chartering of the WG. The WG will=
 be in the Security Area (it was a borderline between ART and Security) and=
 your responsible AD is going to be&nbsp;Kathleen Moriarty.</div>
<div id=3D"sig21611513">
<div class=3D"signature"><br>
</div>
<div class=3D"signature">Best Regards,<br>
</div>
<div class=3D"signature">Alexey<br>
</div>
<div class=3D"signature"><br>
</div>
<div class=3D"signature">P.S. I picked &quot;SECEVENT&quot; as the short WG=
 name, but if you have better suggestions, please let me know.</div>
<div><br>
</div>
</div>
<div>On Wed, Sep 7, 2016, at 01:04 AM, William Denniss wrote:<br>
</div>
<blockquote type=3D"cite">
<div dir=3D"ltr">
<div>Thank you Mike for revising the charter.&nbsp;<br>
</div>
<div><br>
</div>
<div>I support it, and hope we can form a WG with this charter to continue =
our work.<br>
</div>
</div>
<div>
<div><br>
</div>
<div defang_data-gmailquote=3D"yes">
<div>On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>&g=
t;</span> wrote:<br>
</div>
<blockquote style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;marg=
in-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);bo=
rder-left-style:solid;padding-left:1ex;" defang_data-gmailquote=3D"yes">
<div lang=3D"EN-US">
<div>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">An updated and simplified charter is attached.&nbsp; This d=
raft has been reviewed by Phil Hunt, William Denniss,
 Marius Scurtescu.<u></u><u></u></span></span></span><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt"><u></u>&nbsp;<u></u></span></span></span><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">Input from Alexey Melnikov is that we should probably chart=
er a working group, rather than try to go the
 AD-sponsored route.&nbsp; Therefore, please review this draft charter and =
let us know if you think it=92s ready to go.<u></u><u></u></span></span></s=
pan><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt"><u></u>&nbsp;<u></u></span></span></span><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<u></u><u></u></span><=
/span></span><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<u></u><u></u></span><=
/span></span><br>
</p>
<p><a name=3D"m_5165357944078144809__MailEndCompose"><span class=3D"colour"=
 style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:C=
alibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt"><u></u>&n=
bsp;<u></u></span></span></span></a><br>
</p>
<div><span></span><br>
</div>
<p><b><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span =
class=3D"size" style=3D"font-size:11pt">From:</span></span></b><span class=
=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" st=
yle=3D"font-size:11pt"> Sarah Squire [mailto:<a href=3D"mailto:sarah@engage=
identity.com">sarah@engageidentity.<wbr>com</a>]
<br>
<b>Sent:</b> Thursday, July 14, 2016 10:59 PM<br>
<b>To:</b> Phil Hunt (IDM) &lt;<a href=3D"mailto:phil.hunt@oracle.com">phil=
.hunt@oracle.com</a>&gt;<br>
<b>Cc:</b> Mike Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com">Mi=
chael.Jones@microsoft.com</a>&gt;; Alan Karp &lt;<a href=3D"mailto:alanhkar=
p@gmail.com">alanhkarp@gmail.com</a>&gt;; Vivek Biswas &lt;<a href=3D"mailt=
o:vivek_biswas@yahoo.com">vivek_biswas@yahoo.com</a>&gt;;
 Morteza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.com">morans=
ar@cisco.com</a>&gt;;
<a href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a></span></span></p=
>
<div>
<div>
<div><br>
</div>
<div><b>Subject:</b> Re: [Id-event] Straw man text for proposed charter<u><=
/u><u></u><br>
</div>
</div>
</div>
<p><br>
</p>
<div>
<div>
<p><u></u>&nbsp;<u></u><br>
</p>
<div>
<div>
<p>Just submitting my two cents in writing before we hopefully have a chanc=
e to meet about this next week...<u></u><u></u><br>
</p>
</div>
<div>
<p><u></u>&nbsp;<u></u><br>
</p>
</div>
<p>Looking at this charter from the perspective of the OIDF HEART working g=
roup, I think it's going down a good path. In terms of the data format, thi=
s is less structured than what I was envisioning, but we could easily do a =
healthcare-specific profile of whatever
 data format comes out in the end, so it's better to be too broad than too =
narrow as far as our interests are concerned.<u></u><u></u><br>
</p>
<div>
<p><u></u>&nbsp;<u></u><br>
</p>
</div>
<div>
<p>The transport layer however, has some added complexity. In our context, =
we're shooting for interoperability, so we'd prefer something constrained. =
I appreciate Mike's input that these are application layer decisions. Howev=
er, if we're talking about cloud
 provider-to-cloud provider communication, that certainly is facilitated by=
 a well-defined transport layer. Again, we're willing to profile whatever t=
he group comes up with for our own ends, but I don't really see the benefit=
 of having a loosely defined transport
 layer - it just seems like more work for all the implementers to actually =
agree on endpoints on a case-by-case basis.<u></u><u></u><br>
</p>
</div>
<div>
<p><u></u>&nbsp;<u></u><br>
</p>
</div>
<div>
<p>Looking forward to discussing further in Berlin!<u></u><u></u><br>
</p>
</div>
<div>
<p><u></u>&nbsp;<u></u><br>
</p>
</div>
<div>
<p>Sarah<u></u><u></u><br>
</p>
</div>
</div>
<div>
<p><u></u><u></u><br>
</p>
<div>
<div>
<div>
<div>
<p><span class=3D"colour" style=3D"color:rgb(136, 136, 136)">Sarah Squire<u=
></u><u></u></span><br>
</p>
</div>
<div>
<p><span class=3D"colour" style=3D"color:rgb(136, 136, 136)">Engage Identit=
y<u></u><u></u></span><br>
</p>
</div>
<div>
<p><span class=3D"colour" style=3D"color:rgb(136, 136, 136)"><a href=3D"htt=
p://engageidentity.com/"><span class=3D"colour" style=3D"color:rgb(17, 85, =
204)">http://engageidentity.com</span></a><u></u><u></u></span><br>
</p>
</div>
</div>
</div>
</div>
<p><u></u>&nbsp;<u></u><br>
</p>
<div>
<p>On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) &lt;<a href=3D"mailto:ph=
il.hunt@oracle.com">phil.hunt@oracle.com</a>&gt; wrote:<u></u><u></u><br>
</p>
<blockquote style=3D"border-top-style:none;border-right-style:none;border-b=
ottom-style:none;border-top-width:initial;border-right-width:initial;border=
-bottom-width:initial;border-top-color:initial;border-right-color:initial;b=
order-bottom-color:initial;border-image-source:initial;border-image-slice:i=
nitial;border-image-width:initial;border-image-outset:initial;border-image-=
repeat:initial;border-left-style:solid;border-left-color:rgb(204, 204, 204)=
;border-left-width:1pt;padding-top:0in;padding-right:0in;padding-bottom:0in=
;padding-left:6pt;margin-left:4.8pt;margin-right:0in;">
<div>
<div>
<p>We also set things up so even a domain specific event can be extended.&n=
bsp;<u></u><u></u><br>
</p>
</div>
<div>
<p><u></u>&nbsp;<u></u><br>
</p>
</div>
<div>
<p>Eg on a password reset event, so event publishers may want to add securi=
ty domain specific attributes. The spec lets them do that while avoiding in=
terop issues.&nbsp;<u></u><u></u><br>
</p>
</div>
<div>
<p><u></u>&nbsp;<u></u><br>
</p>
</div>
<div>
<p>I believe in the spec we had the example of an account reset and the pub=
lisher adds reset count as an extension.&nbsp;<span class=3D"colour" style=
=3D"color:rgb(136, 136, 136)"><br>
<br>
<span>Phil</span></span><u></u><u></u></p>
</div>
<div>
<div>
<div>
<p style=3D"margin-bottom:12pt;"></p>
<div><br>
</div>
<div>On May 7, 2016, at 13:31, Mike Jones &lt;<a href=3D"mailto:Michael.Jon=
es@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<u></u><u></u><=
br>
</div>
<p></p>
</div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt;">
<div>
<div>
<p>Indeed, that=92s why there=92s a claims registry =96 so common claims ca=
n be defined once and then reused.<u></u><u></u><br>
</p>
<p>&nbsp;<u></u><u></u><br>
</p>
<div style=3D"border-right-style:none;border-bottom-style:none;border-left-=
style:none;border-right-width:initial;border-bottom-width:initial;border-le=
ft-width:initial;border-right-color:initial;border-bottom-color:initial;bor=
der-left-color:initial;border-image-source:initial;border-image-slice:initi=
al;border-image-width:initial;border-image-outset:initial;border-image-repe=
at:initial;border-top-style:solid;border-top-color:rgb(225, 225, 225);borde=
r-top-width:1pt;padding-top:3pt;padding-right:0in;padding-bottom:0in;paddin=
g-left:0in;">
<p></p>
<div><b>From: </b><a href=3D"mailto:vivek_biswas@yahoo.com">Vivek Biswas</a=
><br>
</div>
<div><b>Sent: </b>Saturday, May 7, 2016 1:24 PM<br>
</div>
<div><b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com">Mike Jones</=
a><br>
</div>
<div><b>Cc: </b><a href=3D"mailto:alanhkarp@gmail.com">Alan Karp</a>; <a hr=
ef=3D"mailto:moransar@cisco.com">
Morteza Ansari (moransar)</a>; <a href=3D"mailto:id-event@ietf.org">id-even=
t@ietf.org</a><br>
</div>
<div><b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u><=
/u><u></u><br>
</div>
<p></p>
</div>
<p>&nbsp;<u></u><u></u><br>
</p>
</div>
<div>
<div>
<p>Yes, I agree that the claims can be application specific, however there =
is a possibility to define claims which are domain specific. Thereby claims=
 generated in one application could be understood by another &nbsp;applicat=
ion within the same domain.<u></u><u></u><br>
</p>
</div>
<div>
<p><u></u>&nbsp;<u></u><br>
</p>
</div>
<div>
<p>With microservices based architecture getting lot of attention, if two d=
ifferent micro services defining different claims for the same claim, it ca=
n create confusion.<u></u><u></u><br>
</p>
</div>
<div>
<p><u></u>&nbsp;<u></u><br>
</p>
</div>
<div>
<p>Nevertheless this well defined claims for a particular domain can be an =
extension to the core specification.<u></u><u></u><br>
</p>
</div>
<div>
<p><u></u>&nbsp;<u></u><br>
</p>
</div>
<div>
<p>-Vivek Biswas<u></u><u></u><br>
</p>
</div>
<div>
<p></p>
<div>&nbsp; Consulting Member, Oracle<br>
</div>
<div><br>
</div>
<div>Sent from my iPhone<u></u><u></u><br>
</div>
<p></p>
</div>
<div>
<p style=3D"margin-bottom:12pt;"></p>
<div><br>
</div>
<div>On May 7, 2016, at 1:04 PM, Mike Jones &lt;<a href=3D"mailto:Michael.J=
ones@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<u></u><u></u=
><br>
</div>
<p></p>
</div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt;">
<div>
<div>
<p>Thanks Alan,<u></u><u></u><br>
</p>
<p>&nbsp;<u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)">Interoperability w=
ill be on a per-application basis, just like JWT interoperability.&nbsp; Th=
e claims needed in an identity event are application-specific, just like cl=
aims are for JWTs.&nbsp; This is the same standards
 posture and JWTs are a huge success =96 including for interoperability, ev=
en if I do say so myself.</span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)">&nbsp;</span><u></=
u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Best wishes,</span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><u></u><u></u><br>
</p>
<p>&nbsp;<u></u><u></u><br>
</p>
<p>&nbsp;<u></u><u></u><br>
</p>
<p>&nbsp;<u></u><u></u><br>
</p>
<p>&nbsp;<u></u><u></u><br>
</p>
<div style=3D"border-right-style:none;border-bottom-style:none;border-left-=
style:none;border-right-width:initial;border-bottom-width:initial;border-le=
ft-width:initial;border-right-color:initial;border-bottom-color:initial;bor=
der-left-color:initial;border-image-source:initial;border-image-slice:initi=
al;border-image-width:initial;border-image-outset:initial;border-image-repe=
at:initial;border-top-style:solid;border-top-color:rgb(225, 225, 225);borde=
r-top-width:1pt;padding-top:3pt;padding-right:0in;padding-bottom:0in;paddin=
g-left:0in;">
<p></p>
<div><b>From: </b><a href=3D"mailto:alanhkarp@gmail.com">Alan Karp</a><br>
</div>
<div><b>Sent: </b>Saturday, May 7, 2016 10:23 AM<br>
</div>
<div><b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com">Mike Jones</=
a><br>
</div>
<div><b>Cc: </b><a href=3D"mailto:moransar@cisco.com">Morteza Ansari (moran=
sar)</a>;
<a href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a><br>
</div>
<div><b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u><=
/u><u></u><br>
</div>
<p></p>
</div>
<p>&nbsp;<u></u><u></u><br>
</p>
</div>
<div>
<div>
<p><span class=3D"size" style=3D"font-size:9.5pt">As one who proposed doing=
 more, I believe that your position is valid.&nbsp; My only question is whe=
ther or not that will be enough for interoperability.</span><u></u><u></u><=
br>
</p>
</div>
<div>
<p><u></u><u></u><br>
</p>
<div>
<div>
<p></p>
<div><br>
</div>
<div>--------------<br>
</div>
<div>Alan Karp<u></u><u></u><br>
</div>
<p></p>
</div>
</div>
<p><u></u>&nbsp;<u></u><br>
</p>
<div>
<p>On Thu, May 5, 2016 at 10:00 PM, Mike Jones &lt;<a href=3D"mailto:Michae=
l.Jones@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<u></u><u>=
</u><br>
</p>
<blockquote style=3D"border-top-style:none;border-right-style:none;border-b=
ottom-style:none;border-top-width:initial;border-right-width:initial;border=
-bottom-width:initial;border-top-color:initial;border-right-color:initial;b=
order-bottom-color:initial;border-image-source:initial;border-image-slice:i=
nitial;border-image-width:initial;border-image-outset:initial;border-image-=
repeat:initial;border-left-style:solid;border-left-color:rgb(204, 204, 204)=
;border-left-width:1pt;padding-top:0in;padding-right:0in;padding-bottom:0in=
;padding-left:6pt;margin-left:4.8pt;margin-right:0in;">
<div>
<div>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">Thanks guys, for writing the initial charter text.&nbsp; Re=
ading it now, I am extremely worried by the scope
 creep evident in the proposal.</span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">&nbsp;</span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">I strongly support a working group to define an ID Events d=
ata format.&nbsp; I just as strongly believe that
 specific event delivery mechanisms will necessarily be application-specifi=
c and therefore MUST be explicitly be stated as being out of scope in the w=
orking group charter.&nbsp; Attempting to specify a particular event delive=
ry mechanism will take something that
 could be simple and quick to approve and bog it down in necessarily applic=
ation-specific debates.</span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">&nbsp;</span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">Should event delivery be reliable?&nbsp; That=92s an applic=
ation-specific decision.</span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">Should events be idempotent?&nbsp; That=92s an application-=
specific decision.</span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">Should events be unicast, multicast, or broadcast?&nbsp; Th=
at=92s an application-specific decision.</span></span></span><u></u><u></u>=
<br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">Should events have categories with category-specific subscr=
iptions?&nbsp; That=92s an application-specific decision.</span></span></sp=
an><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">Should only one party at a time be able to register for del=
ivery of events or should multiple parties be
 able to request delivery?&nbsp; That=92s an application-specific decision.=
</span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">I could continue with this list, but I think you all get th=
e point=85</span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">&nbsp;</span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">If we start debating application-specific event delivery me=
chanisms, we=92ll please almost no one, since
 nearly all applications have different event delivery requirements.&nbsp; =
We MUST explicitly rule all delivery mechanisms as being out of scope.</spa=
n></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">&nbsp;</span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">If we define only a data format, we can quickly produce a v=
ery useful specification.&nbsp; If we don=92t, we=92ll
 get bogged down in the mud of debating which applications we=92re catering=
 to and which we aren=92t =96 an exercise of picking favorites and limiting=
 applicability of the specification.&nbsp; That way is a slow, painful desc=
ent into standards quicksand =96 something we
 must avoid.&nbsp; Having a standard ID events representation is far too im=
portant to tie to a particular limited event delivery mechanism.</span></sp=
an></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">&nbsp;</span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sincerely,<=
/span></span></span><u></u><u></u><br>
</p>
<p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</sp=
an></span></span><u></u><u></u><br>
</p>
<p><a name=3D"m_5165357944078144809_m_3022367059336893565_m_146102425422291=
1"><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"fon=
t" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"=
font-size:11pt">&nbsp;</span></span></span></a><u></u><u></u><br>
</p>
<p><b><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span =
class=3D"size" style=3D"font-size:11pt">From:</span></span></b><span class=
=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" st=
yle=3D"font-size:11pt"> Id-event [mailto:<a href=3D"mailto:id-event-bounces=
@ietf.org">id-event-bounces@ietf.<wbr>org</a>]
<b>On Behalf Of </b>Alan Karp<br>
<b>Sent:</b> Thursday, May 5, 2016 9:43 PM<br>
<b>To:</b> Morteza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.c=
om">moransar@cisco.com</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a><br>
<b>Subject:</b> Re: [Id-event] Straw man text for proposed charter</span></=
span><u></u><u></u></p>
<p>&nbsp;<u></u><u></u><br>
</p>
<div>
<p>I don't see anything about access control for publishing events and subs=
cribing to them.&nbsp; I also think the spec should allow filters on subscr=
iptions.<u></u><u></u><br>
</p>
</div>
<div>
<p><u></u><u></u><br>
</p>
<div>
<div>
<p></p>
<div><br>
</div>
<div>--------------<br>
</div>
<div>Alan Karp<u></u><u></u><br>
</div>
<p></p>
</div>
</div>
<p>&nbsp;<u></u><u></u><br>
</p>
<div>
<p>On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar) &lt;<a href=
=3D"mailto:moransar@cisco.com">moransar@cisco.com</a>&gt; wrote:<u></u><u><=
/u><br>
</p>
<blockquote style=3D"border-top-style:none;border-right-style:none;border-b=
ottom-style:none;border-top-width:initial;border-right-width:initial;border=
-bottom-width:initial;border-top-color:initial;border-right-color:initial;b=
order-bottom-color:initial;border-image-source:initial;border-image-slice:i=
nitial;border-image-width:initial;border-image-outset:initial;border-image-=
repeat:initial;border-left-style:solid;border-left-color:rgb(204, 204, 204)=
;border-left-width:1pt;padding-top:0in;padding-right:0in;padding-bottom:0in=
;padding-left:6pt;margin-left:4.8pt;margin-top:5pt;margin-right:0in;margin-=
bottom:5pt;">
<div>
<div>
<p><span class=3D"colour" style=3D"color:black"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-siz=
e:10.5pt">Hi folks,</span></span></span><u></u><u></u><br>
</p>
</div>
<div>
<p><span class=3D"colour" style=3D"color:black"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-siz=
e:10.5pt">&nbsp;</span></span></span><u></u><u></u><br>
</p>
</div>
<div>
<p><span class=3D"colour" style=3D"color:black"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-siz=
e:10.5pt">At IIW a few of us (Phil, William, Adam, and I) huddled for a bit=
 and put together the attached as a straw man
 charter proposal to start the discussion. Please send your comments and su=
ggestions for any changes or propose a new one if you think its necessary.<=
/span></span></span><u></u><u></u><br>
</p>
</div>
<div>
<p><span class=3D"colour" style=3D"color:black"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-siz=
e:10.5pt">&nbsp;</span></span></span><u></u><u></u><br>
</p>
</div>
<div>
<p><span class=3D"colour" style=3D"color:black"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-siz=
e:10.5pt">&nbsp;</span></span></span><u></u><u></u><br>
</p>
</div>
<div>
<p><span class=3D"colour" style=3D"color:black"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-siz=
e:10.5pt">Cheers,</span></span></span><u></u><u></u><br>
</p>
</div>
<div>
<p><span class=3D"colour" style=3D"color:black"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-siz=
e:10.5pt">Morteza</span></span></span><u></u><u></u><br>
</p>
</div>
</div>
<p style=3D"margin-bottom:12pt;"></p>
<div><br>
</div>
<div>______________________________<wbr>_________________<br>
</div>
<div>Id-event mailing list<br>
</div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
</div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www=
.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br>
</div>
<p></p>
</blockquote>
</div>
<p>&nbsp;<u></u><u></u><br>
</p>
</div>
</div>
</div>
</blockquote>
</div>
<p><u></u>&nbsp;<u></u><br>
</p>
</div>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt;">
<div>
<p></p>
<div>______________________________<wbr>_________________<br>
</div>
<div>Id-event mailing list<br>
</div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
</div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www=
.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br>
</div>
<p></p>
</div>
</blockquote>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt;">
<div>
<p></p>
<div>______________________________<wbr>_________________<br>
</div>
<div>Id-event mailing list<br>
</div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
</div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www=
.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br>
</div>
<p></p>
</div>
</blockquote>
</div>
</div>
</div>
<p style=3D"margin-bottom:12pt;"></p>
<div><br>
</div>
<div>______________________________<wbr>_________________<br>
</div>
<div>Id-event mailing list<br>
</div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br>
</div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www=
.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br>
</div>
<p></p>
</blockquote>
</div>
<p><u></u>&nbsp;<u></u><br>
</p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<div><br>
</div>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>Id-event mailing list</span><br>
<span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://ww=
w.ietf.org/mailman/listinfo/id-event</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_D03F281C30514E0D81C80F0CC0854A10ciscocom_--


From nobody Sat Sep 24 04:56:34 2016
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA0DF12BC1C for <id-event@ietfa.amsl.com>; Sat, 24 Sep 2016 04:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=H7E1cwwU; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=M2iwE2Uw
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LEnVXjMnoZG4 for <id-event@ietfa.amsl.com>; Sat, 24 Sep 2016 04:56:28 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89E7612BC2C for <id-event@ietf.org>; Sat, 24 Sep 2016 04:56:28 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id DFE972038F; Sat, 24 Sep 2016 07:56:27 -0400 (EDT)
Received: from web6 ([10.202.2.216]) by compute6.internal (MEProxy); Sat, 24 Sep 2016 07:56:27 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=pqy90NsDJSxh8xDu/OGjxQwEitI=; b=H7E1cw wUoDJhIhQty77e4sIdpeUKqzflwc3jX96qkX4rn7qG3Pyj1Q8jjEvFPLjcscW2o2 Gw/E1GBz2Sx0lrQTQznwkCuSxb5Fp6s03OSUJ/moP+HoR43sVdoo3F4lYyDT0q9W MiARXabLWA3x7CERK8KznrLU1PRNwtPXY1OyM=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=pqy90NsDJSxh8xD u/OGjxQwEitI=; b=M2iwE2UwVFGsWECBiFCE+2ooPIeGpK604kevUyJSGMQ47BC NHCE3BI4dt+VvkMRYOnr4RrbE1TukUFkPNXhGltntk9IoK5tPVn1JrCFyrHiIu7W iaNMxTGlXgG5dk8qclAjlSsrfuo0zCZOZMUQXQpcaer+t2Sc2MSy3pEVZmPM=
Received: by mailuser.nyi.internal (Postfix, from userid 99) id A14E01EB85; Sat, 24 Sep 2016 07:56:27 -0400 (EDT)
Message-Id: <1474718187.2329006.735672633.371888A0@webmail.messagingengine.com>
X-Sasl-Enc: sC8vYN+bJ1wPez8Rdaoi3tgqokZQMv66Cey2T4xk7m8l 1474718187
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: "Morteza Ansari (moransar)" <moransar@cisco.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_147471818723290060"; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-3ce3fca2
Date: Sat, 24 Sep 2016 12:56:27 +0100
In-Reply-To: <D03F281C-3051-4E0D-81C8-0F0CC0854A10@cisco.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com>, <1474715073.2319843.735650465.3C69F11E@webmail.messagingengine.com> <D03F281C-3051-4E0D-81C8-0F0CC0854A10@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/zhsq3Su_7qThmc_XdHKPgZd8Mv8>
Cc: William Denniss <wdenniss@google.com>, Mike Jones <Michael.Jones@microsoft.com>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, id-event@ietf.org
Subject: Re: [Id-event] Chartering of Security Events WG
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Sep 2016 11:56:32 -0000

This is a multi-part message in MIME format.

--_----------=_147471818723290060
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

This also reminded me: how much time does this group want to request for
face-to-face meeting in Seoul?

On Sat, Sep 24, 2016, at 12:27 PM, Morteza Ansari (moransar) wrote:
> This is great, thanks for helping speed up the process! Name is a
> name, so no comment on naming.
>
>
>
> Cheers,
> Morteza
>
> On Sep 24, 2016, at 4:04 AM, Alexey Melnikov
> <aamelnikov@fastmail.fm> wrote:
>
>> Hi,
>> Just to let everyone know: I started chartering of the WG. The WG
>> will be in the Security Area (it was a borderline between ART and
>> Security) and your responsible AD is going to be Kathleen Moriarty.
>>
>> Best Regards,
>> Alexey
>>
>> P.S. I picked "SECEVENT" as the short WG name, but if you have better
>>      suggestions, please let me know.
>>
>> On Wed, Sep 7, 2016, at 01:04 AM, William Denniss wrote:
>>> Thank you Mike for revising the charter.
>>>
>>> I support it, and hope we can form a WG with this charter to
>>> continue our work.
>>>
>>> On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones
>>> <Michael.Jones@microsoft.com> wrote:
>>>> An updated and simplified charter is attached.  This draft has been
>>>> reviewed by Phil Hunt, William Denniss, Marius Scurtescu.____
>>>> __ __
>>>> Input from Alexey Melnikov is that we should probably charter a
>>>> working group, rather than try to go the AD-sponsored route.
>>>> Therefore, please review this draft charter and let us know if you
>>>> think it=E2=80=99s ready to go.____
>>>> __ __
>>>>                                                        Thanks,____
>>>>                                                        -- Mike____
>>>> __ __
>>>>
>>>> *From:* Sarah Squire [mailto:sarah@engageidentity.com] *Sent:*
>>>> Thursday, July 14, 2016 10:59 PM *To:* Phil Hunt (IDM)
>>>> <phil.hunt@oracle.com> *Cc:* Mike Jones
>>>> <Michael.Jones@microsoft.com>; Alan Karp <alanhkarp@gmail.com>;
>>>> Vivek Biswas <vivek_biswas@yahoo.com>; Morteza Ansari (moransar)
>>>> <moransar@cisco.com>; id-event@ietf.org
>>>>
>>>> *Subject:* Re: [Id-event] Straw man text for proposed charter____
>>>>
>>>> __ __
>>>> Just submitting my two cents in writing before we hopefully have a
>>>> chance to meet about this next week...____
>>>> __ __
>>>> Looking at this charter from the perspective of the OIDF HEART
>>>> working group, I think it's going down a good path. In terms of the
>>>> data format, this is less structured than what I was envisioning,
>>>> but we could easily do a healthcare-specific profile of whatever
>>>> data format comes out in the end, so it's better to be too broad
>>>> than too narrow as far as our interests are concerned.____
>>>> __ __
>>>> The transport layer however, has some added complexity. In our
>>>> context, we're shooting for interoperability, so we'd prefer
>>>> something constrained. I appreciate Mike's input that these are
>>>> application layer decisions. However, if we're talking about cloud
>>>> provider-to-cloud provider communication, that certainly is
>>>> facilitated by a well-defined transport layer. Again, we're willing
>>>> to profile whatever the group comes up with for our own ends, but I
>>>> don't really see the benefit of having a loosely defined transport
>>>> layer - it just seems like more work for all the implementers to
>>>> actually agree on endpoints on a case-by-case basis.____
>>>> __ __
>>>> Looking forward to discussing further in Berlin!____
>>>> __ __
>>>> Sarah____
>>>> ____
>>>> Sarah Squire____
>>>> Engage Identity____
>>>> http://engageidentity.com[1]____
>>>> __ __
>>>> On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM)
>>>> <phil.hunt@oracle.com> wrote:____
>>>>> We also set things up so even a domain specific event can be
>>>>> extended. ____
>>>>> __ __
>>>>> Eg on a password reset event, so event publishers may want to add
>>>>> security domain specific attributes. The spec lets them do that
>>>>> while avoiding interop issues. ____
>>>>> __ __
>>>>> I believe in the spec we had the example of an account reset and
>>>>> the publisher adds reset count as an extension.
>>>>>
>>>>> Phil____
>>>>>
>>>>>
>>>>> On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com>
>>>>> wrote:____
>>>>>
>>>>>> Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=
=93 so common claims
>>>>>> can be defined once and then reused.____
>>>>>>  ____
>>>>>>
>>>>>> *From: *Vivek Biswas[2]
>>>>>> *Sent: *Saturday, May 7, 2016 1:24 PM
>>>>>> *To: *Mike Jones[3]
>>>>>> *Cc: *Alan Karp[4];  Morteza Ansari (moransar)[5]; id-
>>>>>> event@ietf.org
>>>>>> *Subject: *Re: [Id-event] Straw man text for proposed charter____
>>>>>>
>>>>>>  ____
>>>>>> Yes, I agree that the claims can be application specific, however
>>>>>> there is a possibility to define claims which are domain
>>>>>> specific. Thereby claims generated in one application could be
>>>>>> understood by another  application within the same domain.____
>>>>>> __ __
>>>>>> With microservices based architecture getting lot of attention,
>>>>>> if two different micro services defining different claims for the
>>>>>> same claim, it can create confusion.____
>>>>>> __ __
>>>>>> Nevertheless this well defined claims for a particular domain can
>>>>>> be an extension to the core specification.____
>>>>>> __ __
>>>>>> -Vivek Biswas____
>>>>>>
>>>>>>   Consulting Member, Oracle
>>>>>>
>>>>>> Sent from my iPhone____
>>>>>>
>>>>>>
>>>>>>
>>>>>> On May 7, 2016, at 1:04 PM, Mike Jones
>>>>>> <Michael.Jones@microsoft.com> wrote:____
>>>>>>
>>>>>>> Thanks Alan,____
>>>>>>>  ____
>>>>>>> Interoperability will be on a per-application basis, just like
>>>>>>> JWT interoperability.  The claims needed in an identity event
>>>>>>> are application-specific, just like claims are for JWTs.  This
>>>>>>> is the same standards posture and JWTs are a huge success =E2=80=93
>>>>>>> including for interoperability, even if I do say so myself.____
>>>>>>>  ____
>>>>>>>                                                           Best
>>>>>>>                                                           wishe-
>>>>>>>                                                           s,____
>>>>>>>                                                           -- Mi-
>>>>>>>                                                           ke____
>>>>>>>  ____
>>>>>>>  ____
>>>>>>>  ____
>>>>>>>  ____
>>>>>>>
>>>>>>> *From: *Alan Karp[6]
>>>>>>> *Sent: *Saturday, May 7, 2016 10:23 AM
>>>>>>> *To: *Mike Jones[7]
>>>>>>> *Cc: *Morteza Ansari (moransar)[8]; id-event@ietf.org
>>>>>>> *Subject: *Re: [Id-event] Straw man text for proposed
>>>>>>> charter____
>>>>>>>
>>>>>>>  ____
>>>>>>> As one who proposed doing more, I believe that your position is
>>>>>>> valid.  My only question is whether or not that will be enough
>>>>>>> for interoperability.____
>>>>>>> ____
>>>>>>>
>>>>>>>
>>>>>>> --------------
>>>>>>> Alan Karp____
>>>>>>>
>>>>>>> __ __
>>>>>>> On Thu, May 5, 2016 at 10:00 PM, Mike Jones
>>>>>>> <Michael.Jones@microsoft.com> wrote:____
>>>>>>>> Thanks guys, for writing the initial charter text.  Reading it
>>>>>>>> now, I am extremely worried by the scope creep evident in the
>>>>>>>> proposal.____
>>>>>>>>  ____
>>>>>>>> I strongly support a working group to define an ID Events data
>>>>>>>> format.  I just as strongly believe that specific event
>>>>>>>> delivery mechanisms will necessarily be application-specific
>>>>>>>> and therefore MUST be explicitly be stated as being out of
>>>>>>>> scope in the working group charter.  Attempting to specify a
>>>>>>>> particular event delivery mechanism will take something that
>>>>>>>> could be simple and quick to approve and bog it down in
>>>>>>>> necessarily application-specific debates.____
>>>>>>>>  ____
>>>>>>>> Should event delivery be reliable?  That=E2=80=99s an application-
>>>>>>>> specific decision.____
>>>>>>>> Should events be idempotent?  That=E2=80=99s an application-specif=
ic
>>>>>>>> decision.____
>>>>>>>> Should events be unicast, multicast, or broadcast?  That=E2=80=99s=
 an
>>>>>>>> application-specific decision.____
>>>>>>>> Should events have categories with category-specific
>>>>>>>> subscriptions?  That=E2=80=99s an application-specific decision.__=
__
>>>>>>>> Should only one party at a time be able to register for
>>>>>>>> delivery of events or should multiple parties be able to
>>>>>>>> request delivery?  That=E2=80=99s an application-specific decision=
.____
>>>>>>>> I could continue with this list, but I think you all get the
>>>>>>>> point=E2=80=A6____
>>>>>>>>  ____
>>>>>>>> If we start debating application-specific event delivery
>>>>>>>> mechanisms, we=E2=80=99ll please almost no one, since nearly all
>>>>>>>> applications have different event delivery requirements.  We
>>>>>>>> MUST explicitly rule all delivery mechanisms as being out of
>>>>>>>> scope.____
>>>>>>>>  ____
>>>>>>>> If we define only a data format, we can quickly produce a very
>>>>>>>> useful specification.  If we don=E2=80=99t, we=E2=80=99ll get bogg=
ed down in
>>>>>>>> the mud of debating which applications we=E2=80=99re catering to a=
nd
>>>>>>>> which we aren=E2=80=99t =E2=80=93 an exercise of picking favorites=
 and limiting
>>>>>>>> applicability of the specification.  That way is a slow,
>>>>>>>> painful descent into standards quicksand =E2=80=93 something we mu=
st
>>>>>>>> avoid.  Having a standard ID events representation is far too
>>>>>>>> important to tie to a particular limited event delivery
>>>>>>>> mechanism.____
>>>>>>>>  ____
>>>>>>>>                                                           Sinc-
>>>>>>>>                                                           erel-
>>>>>>>>                                                           y,__-
>>>>>>>>                                                           __
>>>>>>>>                                                           --
>>>>>>>>                                                           Mike-
>>>>>>>>                                                           ____
>>>>>>>>  ____
>>>>>>>> *From:* Id-event [mailto:id-event-bounces@ietf.org] *On Behalf
>>>>>>>> Of *Alan Karp *Sent:* Thursday, May 5, 2016 9:43 PM *To:*
>>>>>>>> Morteza Ansari (moransar) <moransar@cisco.com> *Cc:* id-
>>>>>>>> event@ietf.org *Subject:* Re: [Id-event] Straw man text for
>>>>>>>> proposed charter____
>>>>>>>>  ____
>>>>>>>> I don't see anything about access control for publishing events
>>>>>>>> and subscribing to them.  I also think the spec should allow
>>>>>>>> filters on subscriptions.____
>>>>>>>> ____
>>>>>>>>
>>>>>>>>
>>>>>>>> --------------
>>>>>>>> Alan Karp____
>>>>>>>>
>>>>>>>>  ____
>>>>>>>> On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar)
>>>>>>>> <moransar@cisco.com> wrote:____
>>>>>>>>> Hi folks,____
>>>>>>>>>  ____
>>>>>>>>> At IIW a few of us (Phil, William, Adam, and I) huddled for a
>>>>>>>>> bit and put together the attached as a straw man charter
>>>>>>>>> proposal to start the discussion. Please send your comments
>>>>>>>>> and suggestions for any changes or propose a new one if you
>>>>>>>>> think its necessary.____
>>>>>>>>>  ____
>>>>>>>>>  ____
>>>>>>>>> Cheers,____
>>>>>>>>> Morteza____
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Id-event mailing list
>>>>>>>>> Id-event@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/id-event____
>>>>>>>>>
>>>>>>>>  ____
>>>>>>> __ __
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Id-event mailing list
>>>>>>> Id-event@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/id-event____
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Id-event mailing list
>>>>>> Id-event@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/id-event____
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Id-event mailing list
>>>>> Id-event@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/id-event____
>>>>>
>>>> __ __
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event

Links:

  1. http://engageidentity.com/
  2. mailto:vivek_biswas@yahoo.com
  3. mailto:Michael.Jones@microsoft.com
  4. mailto:alanhkarp@gmail.com
  5. mailto:moransar@cisco.com
  6. mailto:alanhkarp@gmail.com
  7. mailto:Michael.Jones@microsoft.com
  8. mailto:moransar@cisco.com

--_----------=_147471818723290060
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>This also reminded me: how much time does this group want to req=
uest for face-to-face meeting in Seoul?<br></div>
<div><br></div>
<div>On Sat, Sep 24, 2016, at 12:27 PM, Morteza Ansari (moransar) wrote:<br=
></div>
<blockquote type=3D"cite"><div><div>This is great, thanks for helping speed=
 up the process! Name is a name, so no comment on naming.&nbsp;<br></div>
<div> <br></div>
<div> <br></div>
<div><br></div>
<div>Cheers,<br></div>
<div>Morteza<br></div>
</div>
<div><div><br></div>
<div>On Sep 24, 2016, at 4:04 AM, Alexey Melnikov &lt;<a href=3D"mailto:aam=
elnikov@fastmail.fm">aamelnikov@fastmail.fm</a>&gt; wrote:<br></div>
<div> <br></div>
</div>
<blockquote type=3D"cite"><div><div>Hi,<br></div>
<div>Just to let everyone know: I started chartering of the WG. The WG will=
 be in the Security Area (it was a borderline between ART and Security) and=
 your responsible AD is going to be&nbsp;Kathleen Moriarty.<br></div>
<div><div><br></div>
<div>Best Regards,<br></div>
<div>Alexey<br></div>
<div><br></div>
<div>P.S. I picked "SECEVENT" as the short WG name, but if you have better =
suggestions, please let me know.<br></div>
<div><br></div>
</div>
<div>On Wed, Sep 7, 2016, at 01:04 AM, William Denniss wrote:<br></div>
<blockquote type=3D"cite"><div dir=3D"ltr"><div>Thank you Mike for revising=
 the charter.&nbsp;<br></div>
<div><br></div>
<div>I support it, and hope we can form a WG with this charter to continue =
our work.<br></div>
</div>
<div><div><br></div>
<div><div>On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <span dir=3D"ltr">&lt;=
<a href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com<=
/a>&gt;</span> wrote:<br></div>
<blockquote style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;marg=
in-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);bo=
rder-left-style:solid;padding-left:1ex;"><div lang=3D"EN-US"><div><p><span =
class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-siz=
e:11pt">An updated and simplified charter is attached.&nbsp; This draft has=
 been reviewed by Phil Hunt, William Denniss,
 Marius Scurtescu.<u></u><u></u></span></span></span><br></p><p><span class=
=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"fo=
nt-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt=
"><u></u>&nbsp;<u></u></span></span></span><br></p><p><span class=3D"colour=
" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:=
Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">Input fr=
om Alexey Melnikov is that we should probably charter a working group, rath=
er than try to go the
 AD-sponsored route.&nbsp; Therefore, please review this draft charter and =
let us know if you think it=E2=80=99s ready to go.<u></u><u></u></span></sp=
an></span><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)">=
<span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=
=3D"size" style=3D"font-size:11pt"><u></u>&nbsp;<u></u></span></span></span=
><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span cla=
ss=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" =
style=3D"font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<u></u><u></u=
></span></span></span><br></p><p><span class=3D"colour" style=3D"color:rgb(=
0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif">=
<span class=3D"size" style=3D"font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 -- Mike<u></u><u></u></span></span></span><br></p><p><a name=3D"m_51653579=
44078144809__MailEndCompose"><span class=3D"colour" style=3D"color:rgb(0, 3=
2, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><spa=
n class=3D"size" style=3D"font-size:11pt"><u></u>&nbsp;<u></u></span></span=
></span></a><br></p><div><span></span><br></div>
<p><b><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span =
class=3D"size" style=3D"font-size:11pt">From:</span></span></b><span class=
=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" st=
yle=3D"font-size:11pt"> Sarah Squire [mailto:<a href=3D"mailto:sarah@engage=
identity.com">sarah@engageidentity.<wbr>com</a>] <br> <b>Sent:</b> Thursday=
, July 14, 2016 10:59 PM<br> <b>To:</b> Phil Hunt (IDM) &lt;<a href=3D"mail=
to:phil.hunt@oracle.com">phil.hunt@oracle.com</a>&gt;<br> <b>Cc:</b> Mike J=
ones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@micro=
soft.com</a>&gt;; Alan Karp &lt;<a href=3D"mailto:alanhkarp@gmail.com">alan=
hkarp@gmail.com</a>&gt;; Vivek Biswas &lt;<a href=3D"mailto:vivek_biswas@ya=
hoo.com">vivek_biswas@yahoo.com</a>&gt;;
 Morteza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.com">morans=
ar@cisco.com</a>&gt;; <a href=3D"mailto:id-event@ietf.org">id-event@ietf.or=
g</a></span></span></p><div><div><div><br></div>
<div><b>Subject:</b> Re: [Id-event] Straw man text for proposed charter<u><=
/u><u></u><br></div>
</div>
</div>
<p><br></p><div><div><p><u></u>&nbsp;<u></u><br></p><div><div><p>Just submi=
tting my two cents in writing before we hopefully have a chance to meet abo=
ut this next week...<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<p>Looking at this charter from the perspective of the OIDF HEART working g=
roup, I think it's going down a good path. In terms of the data format, thi=
s is less structured than what I was envisioning, but we could easily do a =
healthcare-specific profile of whatever
 data format comes out in the end, so it's better to be too broad than too =
narrow as far as our interests are concerned.<u></u><u></u><br></p><div><p>=
<u></u>&nbsp;<u></u><br></p></div>
<div><p>The transport layer however, has some added complexity. In our cont=
ext, we're shooting for interoperability, so we'd prefer something constrai=
ned. I appreciate Mike's input that these are application layer decisions. =
However, if we're talking about cloud
 provider-to-cloud provider communication, that certainly is facilitated by=
 a well-defined transport layer. Again, we're willing to profile whatever t=
he group comes up with for our own ends, but I don't really see the benefit=
 of having a loosely defined transport
 layer - it just seems like more work for all the implementers to actually =
agree on endpoints on a case-by-case basis.<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Looking forward to discussing further in Berlin!<u></u><u></u><br><=
/p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Sarah<u></u><u></u><br></p></div>
</div>
<div><p><u></u><u></u><br></p><div><div><div><div><p><span class=3D"colour"=
 style=3D"color:rgb(136, 136, 136)">Sarah Squire<u></u><u></u></span><br></=
p></div>
<div><p><span class=3D"colour" style=3D"color:rgb(136, 136, 136)">Engage Id=
entity<u></u><u></u></span><br></p></div>
<div><p><span class=3D"colour" style=3D"color:rgb(136, 136, 136)"><a href=
=3D"http://engageidentity.com/"><span class=3D"colour" style=3D"color:rgb(1=
7, 85, 204)">http://engageidentity.com</span></a><u></u><u></u></span><br><=
/p></div>
</div>
</div>
</div>
<p><u></u>&nbsp;<u></u><br></p><div><p>On Sat, May 7, 2016 at 6:53 PM, Phil=
 Hunt (IDM) &lt;<a href=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.co=
m</a>&gt; wrote:<u></u><u></u><br></p><blockquote style=3D"border-top-style=
:none;border-right-style:none;border-bottom-style:none;border-top-width:ini=
tial;border-right-width:initial;border-bottom-width:initial;border-top-colo=
r:initial;border-right-color:initial;border-bottom-color:initial;border-ima=
ge-source:initial;border-image-slice:initial;border-image-width:initial;bor=
der-image-outset:initial;border-image-repeat:initial;border-left-style:soli=
d;border-left-color:rgb(204, 204, 204);border-left-width:1pt;padding-top:0i=
n;padding-right:0in;padding-bottom:0in;padding-left:6pt;margin-left:4.8pt;m=
argin-right:0in;"><div><div><p>We also set things up so even a domain speci=
fic event can be extended.&nbsp;<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Eg on a password reset event, so event publishers may want to add s=
ecurity domain specific attributes. The spec lets them do that while avoidi=
ng interop issues.&nbsp;<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>I believe in the spec we had the example of an account reset and th=
e publisher adds reset count as an extension.&nbsp;<span class=3D"colour" s=
tyle=3D"color:rgb(136, 136, 136)"><br> <br> <span>Phil</span></span><u></u>=
<u></u></p></div>
<div><div><div><p style=3D"margin-bottom:12pt;"><br></p><div><br></div>
<div>On May 7, 2016, at 13:31, Mike Jones &lt;<a href=3D"mailto:Michael.Jon=
es@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<u></u><u></u><=
br></div>
<p><br></p></div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><div><p>Indeed=
, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 so common =
claims can be defined once and then reused.<u></u><u></u><br></p><p>&nbsp;<=
u></u><u></u><br></p><div style=3D"border-right-style:none;border-bottom-st=
yle:none;border-left-style:none;border-right-width:initial;border-bottom-wi=
dth:initial;border-left-width:initial;border-right-color:initial;border-bot=
tom-color:initial;border-left-color:initial;border-image-source:initial;bor=
der-image-slice:initial;border-image-width:initial;border-image-outset:init=
ial;border-image-repeat:initial;border-top-style:solid;border-top-color:rgb=
(225, 225, 225);border-top-width:1pt;padding-top:3pt;padding-right:0in;padd=
ing-bottom:0in;padding-left:0in;"><p><br></p><div><b>From: </b><a href=3D"m=
ailto:vivek_biswas@yahoo.com">Vivek Biswas</a><br></div>
<div><b>Sent: </b>Saturday, May 7, 2016 1:24 PM<br></div>
<div><b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com">Mike Jones</=
a><br></div>
<div><b>Cc: </b><a href=3D"mailto:alanhkarp@gmail.com">Alan Karp</a>; <a hr=
ef=3D"mailto:moransar@cisco.com"> Morteza Ansari (moransar)</a>; <a href=3D=
"mailto:id-event@ietf.org">id-event@ietf.org</a><br></div>
<div><b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u><=
/u><u></u><br></div>
<p><br></p></div>
<p>&nbsp;<u></u><u></u><br></p></div>
<div><div><p>Yes, I agree that the claims can be application specific, howe=
ver there is a possibility to define claims which are domain specific. Ther=
eby claims generated in one application could be understood by another &nbs=
p;application within the same domain.<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>With microservices based architecture getting lot of attention, if =
two different micro services defining different claims for the same claim, =
it can create confusion.<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Nevertheless this well defined claims for a particular domain can b=
e an extension to the core specification.<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>-Vivek Biswas<u></u><u></u><br></p></div>
<div><p><br></p><div>&nbsp; Consulting Member, Oracle<br></div>
<div><br></div>
<div>Sent from my iPhone<u></u><u></u><br></div>
<p><br></p></div>
<div><p style=3D"margin-bottom:12pt;"><br></p><div><br></div>
<div>On May 7, 2016, at 1:04 PM, Mike Jones &lt;<a href=3D"mailto:Michael.J=
ones@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<u></u><u></u=
><br></div>
<p><br></p></div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><div><p>Thanks=
 Alan,<u></u><u></u><br></p><p>&nbsp;<u></u><u></u><br></p><p><span class=
=3D"colour" style=3D"color:rgb(0, 32, 96)">Interoperability will be on a pe=
r-application basis, just like JWT interoperability.&nbsp; The claims neede=
d in an identity event are application-specific, just like claims are for J=
WTs.&nbsp; This is the same standards
 posture and JWTs are a huge success =E2=80=93 including for interoperabili=
ty, even if I do say so myself.</span><u></u><u></u><br></p><p><span class=
=3D"colour" style=3D"color:rgb(0, 32, 96)">&nbsp;</span><u></u><u></u><br><=
/p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)">&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Best wishes,</span><u></u><u></u><br></p><=
p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><u></u><u></u><br></p><p>&nbsp;<=
u></u><u></u><br></p><p>&nbsp;<u></u><u></u><br></p><p>&nbsp;<u></u><u></u>=
<br></p><p>&nbsp;<u></u><u></u><br></p><div style=3D"border-right-style:non=
e;border-bottom-style:none;border-left-style:none;border-right-width:initia=
l;border-bottom-width:initial;border-left-width:initial;border-right-color:=
initial;border-bottom-color:initial;border-left-color:initial;border-image-=
source:initial;border-image-slice:initial;border-image-width:initial;border=
-image-outset:initial;border-image-repeat:initial;border-top-style:solid;bo=
rder-top-color:rgb(225, 225, 225);border-top-width:1pt;padding-top:3pt;padd=
ing-right:0in;padding-bottom:0in;padding-left:0in;"><p><br></p><div><b>From=
: </b><a href=3D"mailto:alanhkarp@gmail.com">Alan Karp</a><br></div>
<div><b>Sent: </b>Saturday, May 7, 2016 10:23 AM<br></div>
<div><b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com">Mike Jones</=
a><br></div>
<div><b>Cc: </b><a href=3D"mailto:moransar@cisco.com">Morteza Ansari (moran=
sar)</a>; <a href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a><br></d=
iv>
<div><b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u><=
/u><u></u><br></div>
<p><br></p></div>
<p>&nbsp;<u></u><u></u><br></p></div>
<div><div><p><span class=3D"size" style=3D"font-size:9.5pt">As one who prop=
osed doing more, I believe that your position is valid.&nbsp; My only quest=
ion is whether or not that will be enough for interoperability.</span><u></=
u><u></u><br></p></div>
<div><p><u></u><u></u><br></p><div><div><p><br></p><div><br></div>
<div>--------------<br></div>
<div>Alan Karp<u></u><u></u><br></div>
<p><br></p></div>
</div>
<p><u></u>&nbsp;<u></u><br></p><div><p>On Thu, May 5, 2016 at 10:00 PM, Mik=
e Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@mi=
crosoft.com</a>&gt; wrote:<u></u><u></u><br></p><blockquote style=3D"border=
-top-style:none;border-right-style:none;border-bottom-style:none;border-top=
-width:initial;border-right-width:initial;border-bottom-width:initial;borde=
r-top-color:initial;border-right-color:initial;border-bottom-color:initial;=
border-image-source:initial;border-image-slice:initial;border-image-width:i=
nitial;border-image-outset:initial;border-image-repeat:initial;border-left-=
style:solid;border-left-color:rgb(204, 204, 204);border-left-width:1pt;padd=
ing-top:0in;padding-right:0in;padding-bottom:0in;padding-left:6pt;margin-le=
ft:4.8pt;margin-right:0in;"><div><div><p><span class=3D"colour" style=3D"co=
lor:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans=
-serif"><span class=3D"size" style=3D"font-size:11pt">Thanks guys, for writ=
ing the initial charter text.&nbsp; Reading it now, I am extremely worried =
by the scope
 creep evident in the proposal.</span></span></span><u></u><u></u><br></p><=
p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font=
" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"f=
ont-size:11pt">&nbsp;</span></span></span><u></u><u></u><br></p><p><span cl=
ass=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D=
"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:1=
1pt">I strongly support a working group to define an ID Events data format.=
&nbsp; I just as strongly believe that
 specific event delivery mechanisms will necessarily be application-specifi=
c and therefore MUST be explicitly be stated as being out of scope in the w=
orking group charter.&nbsp; Attempting to specify a particular event delive=
ry mechanism will take something that
 could be simple and quick to approve and bog it down in necessarily applic=
ation-specific debates.</span></span></span><u></u><u></u><br></p><p><span =
class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-siz=
e:11pt">&nbsp;</span></span></span><u></u><u></u><br></p><p><span class=3D"=
colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-f=
amily:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">Sh=
ould event delivery be reliable?&nbsp; That=E2=80=99s an application-specif=
ic decision.</span></span></span><u></u><u></u><br></p><p><span class=3D"co=
lour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-fam=
ily:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">Shou=
ld events be idempotent?&nbsp; That=E2=80=99s an application-specific decis=
ion.</span></span></span><u></u><u></u><br></p><p><span class=3D"colour" st=
yle=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Cali=
bri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">Should event=
s be unicast, multicast, or broadcast?&nbsp; That=E2=80=99s an application-=
specific decision.</span></span></span><u></u><u></u><br></p><p><span class=
=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"fo=
nt-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt=
">Should events have categories with category-specific subscriptions?&nbsp;=
 That=E2=80=99s an application-specific decision.</span></span></span><u></=
u><u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><=
span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=
=3D"size" style=3D"font-size:11pt">Should only one party at a time be able =
to register for delivery of events or should multiple parties be
 able to request delivery?&nbsp; That=E2=80=99s an application-specific dec=
ision.</span></span></span><u></u><u></u><br></p><p><span class=3D"colour" =
style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Ca=
libri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">I could co=
ntinue with this list, but I think you all get the point=E2=80=A6</span></s=
pan></span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:r=
gb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-seri=
f"><span class=3D"size" style=3D"font-size:11pt">&nbsp;</span></span></span=
><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32, =
96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span c=
lass=3D"size" style=3D"font-size:11pt">If we start debating application-spe=
cific event delivery mechanisms, we=E2=80=99ll please almost no one, since
 nearly all applications have different event delivery requirements.&nbsp; =
We MUST explicitly rule all delivery mechanisms as being out of scope.</spa=
n></span></span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"co=
lor:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans=
-serif"><span class=3D"size" style=3D"font-size:11pt">&nbsp;</span></span><=
/span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0,=
 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><s=
pan class=3D"size" style=3D"font-size:11pt">If we define only a data format=
, we can quickly produce a very useful specification.&nbsp; If we don=E2=80=
=99t, we=E2=80=99ll
 get bogged down in the mud of debating which applications we=E2=80=99re ca=
tering to and which we aren=E2=80=99t =E2=80=93 an exercise of picking favo=
rites and limiting applicability of the specification.&nbsp; That way is a =
slow, painful descent into standards quicksand =E2=80=93 something we
 must avoid.&nbsp; Having a standard ID events representation is far too im=
portant to tie to a particular limited event delivery mechanism.</span></sp=
an></span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:rg=
b(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif=
"><span class=3D"size" style=3D"font-size:11pt">&nbsp;</span></span></span>=
<u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 9=
6)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span cl=
ass=3D"size" style=3D"font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; Sincerely,</span></span></span><u></u><u></u><br></p><p><span cl=
ass=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D=
"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:1=
1pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span></span><=
/span><u></u><u></u><br></p><p><a name=3D"m_5165357944078144809_m_302236705=
9336893565_m_1461024254222911"><span class=3D"colour" style=3D"color:rgb(0,=
 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><s=
pan class=3D"size" style=3D"font-size:11pt">&nbsp;</span></span></span></a>=
<u></u><u></u><br></p><p><b><span class=3D"font" style=3D"font-family:Calib=
ri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">From:</span><=
/span></b><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><s=
pan class=3D"size" style=3D"font-size:11pt"> Id-event [mailto:<a href=3D"ma=
ilto:id-event-bounces@ietf.org">id-event-bounces@ietf.<wbr>org</a>] <b>On B=
ehalf Of </b>Alan Karp<br> <b>Sent:</b> Thursday, May 5, 2016 9:43 PM<br> <=
b>To:</b> Morteza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.co=
m">moransar@cisco.com</a>&gt;<br> <b>Cc:</b> <a href=3D"mailto:id-event@iet=
f.org">id-event@ietf.org</a><br> <b>Subject:</b> Re: [Id-event] Straw man t=
ext for proposed charter</span></span><u></u><u></u></p><p>&nbsp;<u></u><u>=
</u><br></p><div><p>I don't see anything about access control for publishin=
g events and subscribing to them.&nbsp; I also think the spec should allow =
filters on subscriptions.<u></u><u></u><br></p></div>
<div><p><u></u><u></u><br></p><div><div><p><br></p><div><br></div>
<div>--------------<br></div>
<div>Alan Karp<u></u><u></u><br></div>
<p><br></p></div>
</div>
<p>&nbsp;<u></u><u></u><br></p><div><p>On Thu, May 5, 2016 at 11:18 AM, Mor=
teza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.com">moransar@c=
isco.com</a>&gt; wrote:<u></u><u></u><br></p><blockquote style=3D"border-to=
p-style:none;border-right-style:none;border-bottom-style:none;border-top-wi=
dth:initial;border-right-width:initial;border-bottom-width:initial;border-t=
op-color:initial;border-right-color:initial;border-bottom-color:initial;bor=
der-image-source:initial;border-image-slice:initial;border-image-width:init=
ial;border-image-outset:initial;border-image-repeat:initial;border-left-sty=
le:solid;border-left-color:rgb(204, 204, 204);border-left-width:1pt;padding=
-top:0in;padding-right:0in;padding-bottom:0in;padding-left:6pt;margin-left:=
4.8pt;margin-top:5pt;margin-right:0in;margin-bottom:5pt;"><div><div><p><spa=
n class=3D"colour" style=3D"color:black"><span class=3D"font" style=3D"font=
-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:10.5pt=
">Hi folks,</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">&nbsp;</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">At IIW a few of us (Phil, William, Adam, and I) huddled for a=
 bit and put together the attached as a straw man
 charter proposal to start the discussion. Please send your comments and su=
ggestions for any changes or propose a new one if you think its necessary.<=
/span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">&nbsp;</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">&nbsp;</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">Cheers,</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font=
-size:10.5pt">Morteza</span></span></span><u></u><u></u><br></p></div>
</div>
<p style=3D"margin-bottom:12pt;"><br></p><div><br></div>
<div>______________________________<wbr>_________________<br></div>
<div>Id-event mailing list<br></div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www=
.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
<p><br></p></blockquote></div>
<p>&nbsp;<u></u><u></u><br></p></div>
</div>
</div>
</blockquote></div>
<p><u></u>&nbsp;<u></u><br></p></div>
</div>
</div>
</blockquote><blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><=
p><br></p><div>______________________________<wbr>_________________<br></di=
v>
<div>Id-event mailing list<br></div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www=
.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
<p><br></p></div>
</blockquote></div>
</div>
</blockquote><blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><=
p><br></p><div>______________________________<wbr>_________________<br></di=
v>
<div>Id-event mailing list<br></div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www=
.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
<p><br></p></div>
</blockquote></div>
</div>
</div>
<p style=3D"margin-bottom:12pt;"><br></p><div><br></div>
<div>______________________________<wbr>_________________<br></div>
<div>Id-event mailing list<br></div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www=
.ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
<p><br></p></blockquote></div>
<p><u></u>&nbsp;<u></u><br></p></div>
</div>
</div>
</div>
</div>
</blockquote></div>
</div>
</blockquote><div><br></div>
</div>
</blockquote><blockquote type=3D"cite"><div><div><span>____________________=
___________________________</span><br></div>
<div> <span>Id-event mailing list</span><br></div>
<div> <span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></spa=
n><br></div>
<div> <span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">http=
s://www.ietf.org/mailman/listinfo/id-event</a></span><br></div>
</div>
</blockquote></blockquote></body>
</html>

--_----------=_147471818723290060--



From nobody Sat Sep 24 08:56:51 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF0B112B1FC for <id-event@ietfa.amsl.com>; Sat, 24 Sep 2016 08:56:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wffLaZNC_zRI for <id-event@ietfa.amsl.com>; Sat, 24 Sep 2016 08:56:46 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9306412B135 for <id-event@ietf.org>; Sat, 24 Sep 2016 08:56:46 -0700 (PDT)
Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8OFueAB024779 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 24 Sep 2016 15:56:40 GMT
Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id u8OFud3a002976 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 24 Sep 2016 15:56:40 GMT
Received: from abhmp0003.oracle.com (abhmp0003.oracle.com [141.146.116.9]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u8OFubF1014135; Sat, 24 Sep 2016 15:56:37 GMT
Received: from [192.168.1.6] (/174.7.250.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 24 Sep 2016 08:56:36 -0700
Content-Type: multipart/alternative; boundary=Apple-Mail-35362907-0C53-4D1A-961A-6B1FD54DEBDB
Mime-Version: 1.0 (1.0)
From: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
X-Mailer: iPhone Mail (14A403)
In-Reply-To: <1474718187.2329006.735672633.371888A0@webmail.messagingengine.com>
Date: Sat, 24 Sep 2016 08:56:34 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <E6BF4F8B-5176-4BA4-A644-DBEE33619161@oracle.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com> <1474715073.2319843.735650465.3C69F11E@webmail.messagingengine.com> <D03F281C-3051-4E0D-81C8-0F0CC0854A10@cisco.com> <1474718187.2329006.735672633.371888A0@webmail.messagingengine.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Source-IP: aserv0022.oracle.com [141.146.126.234]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/jErTVteiPsFdNany8hGXXB7Llu0>
Cc: William Denniss <wdenniss@google.com>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, Mike Jones <Michael.Jones@microsoft.com>, "Morteza Ansari \(moransar\)" <moransar@cisco.com>, id-event@ietf.org
Subject: Re: [Id-event] Chartering of Security Events WG
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Sep 2016 15:56:50 -0000

--Apple-Mail-35362907-0C53-4D1A-961A-6B1FD54DEBDB
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Alexy,

Thanks for helping this forwards.=20

The name is fine.=20

Phil

> On Sep 24, 2016, at 4:56 AM, Alexey Melnikov <aamelnikov@fastmail.fm> wrot=
e:
>=20
> This also reminded me: how much time does this group want to request for f=
ace-to-face meeting in Seoul?
>=20
>> On Sat, Sep 24, 2016, at 12:27 PM, Morteza Ansari (moransar) wrote:
>> This is great, thanks for helping speed up the process! Name is a name, s=
o no comment on naming.=20
>>=20
>>=20
>>=20
>> Cheers,
>> Morteza
>>=20
>> On Sep 24, 2016, at 4:04 AM, Alexey Melnikov <aamelnikov@fastmail.fm> wro=
te:
>>=20
>>> Hi,
>>> Just to let everyone know: I started chartering of the WG. The WG will b=
e in the Security Area (it was a borderline between ART and Security) and yo=
ur responsible AD is going to be Kathleen Moriarty.
>>>=20
>>> Best Regards,
>>> Alexey
>>>=20
>>> P.S. I picked "SECEVENT" as the short WG name, but if you have better su=
ggestions, please let me know.
>>>=20
>>>> On Wed, Sep 7, 2016, at 01:04 AM, William Denniss wrote:
>>>> Thank you Mike for revising the charter.=20
>>>>=20
>>>> I support it, and hope we can form a WG with this charter to continue o=
ur work.
>>>>=20
>>>> On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <Michael.Jones@microsoft.com=
> wrote:
>>>> An updated and simplified charter is attached.  This draft has been rev=
iewed by Phil Hunt, William Denniss, Marius Scurtescu.
>>>>=20
>>>> =20
>>>>=20
>>>> Input from Alexey Melnikov is that we should probably charter a working=
 group, rather than try to go the AD-sponsored route.  Therefore, please rev=
iew this draft charter and let us know if you think it=E2=80=99s ready to go=
.
>>>>=20
>>>> =20
>>>>=20
>>>>                                                        Thanks,
>>>>=20
>>>>                                                        -- Mike
>>>>=20
>>>> =20
>>>>=20
>>>>=20
>>>> From: Sarah Squire [mailto:sarah@engageidentity.com]=20
>>>> Sent: Thursday, July 14, 2016 10:59 PM
>>>> To: Phil Hunt (IDM) <phil.hunt@oracle.com>
>>>> Cc: Mike Jones <Michael.Jones@microsoft.com>; Alan Karp <alanhkarp@gmai=
l.com>; Vivek Biswas <vivek_biswas@yahoo.com>; Morteza Ansari (moransar) <mo=
ransar@cisco.com>; id-event@ietf.org
>>>>=20
>>>>=20
>>>> Subject: Re: [Id-event] Straw man text for proposed charter
>>>>=20
>>>>=20
>>>> =20
>>>>=20
>>>> Just submitting my two cents in writing before we hopefully have a chan=
ce to meet about this next week...
>>>>=20
>>>> =20
>>>>=20
>>>> Looking at this charter from the perspective of the OIDF HEART working g=
roup, I think it's going down a good path. In terms of the data format, this=
 is less structured than what I was envisioning, but we could easily do a he=
althcare-specific profile of whatever data format comes out in the end, so i=
t's better to be too broad than too narrow as far as our interests are conce=
rned.
>>>>=20
>>>> =20
>>>>=20
>>>> The transport layer however, has some added complexity. In our context,=
 we're shooting for interoperability, so we'd prefer something constrained. I=
 appreciate Mike's input that these are application layer decisions. However=
, if we're talking about cloud provider-to-cloud provider communication, tha=
t certainly is facilitated by a well-defined transport layer. Again, we're w=
illing to profile whatever the group comes up with for our own ends, but I d=
on't really see the benefit of having a loosely defined transport layer - it=
 just seems like more work for all the implementers to actually agree on end=
points on a case-by-case basis.
>>>>=20
>>>> =20
>>>>=20
>>>> Looking forward to discussing further in Berlin!
>>>>=20
>>>> =20
>>>>=20
>>>> Sarah
>>>>=20
>>>>=20
>>>>=20
>>>> Sarah Squire
>>>>=20
>>>> Engage Identity
>>>>=20
>>>> http://engageidentity.com
>>>>=20
>>>> =20
>>>>=20
>>>> On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com> w=
rote:
>>>>=20
>>>> We also set things up so even a domain specific event can be extended.=20=

>>>>=20
>>>> =20
>>>>=20
>>>> Eg on a password reset event, so event publishers may want to add secur=
ity domain specific attributes. The spec lets them do that while avoiding in=
terop issues.=20
>>>>=20
>>>> =20
>>>>=20
>>>> I believe in the spec we had the example of an account reset and the pu=
blisher adds reset count as an extension.=20
>>>>=20
>>>> Phil
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com> wrot=
e:
>>>>=20
>>>>=20
>>>> Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 s=
o common claims can be defined once and then reused.
>>>>=20
>>>> =20
>>>>=20
>>>>=20
>>>>=20
>>>> From: Vivek Biswas
>>>> Sent: Saturday, May 7, 2016 1:24 PM
>>>> To: Mike Jones
>>>> Cc: Alan Karp; Morteza Ansari (moransar); id-event@ietf.org
>>>> Subject: Re: [Id-event] Straw man text for proposed charter
>>>>=20
>>>>=20
>>>> =20
>>>>=20
>>>> Yes, I agree that the claims can be application specific, however there=
 is a possibility to define claims which are domain specific. Thereby claims=
 generated in one application could be understood by another  application wi=
thin the same domain.
>>>>=20
>>>> =20
>>>>=20
>>>> With microservices based architecture getting lot of attention, if two d=
ifferent micro services defining different claims for the same claim, it can=
 create confusion.
>>>>=20
>>>> =20
>>>>=20
>>>> Nevertheless this well defined claims for a particular domain can be an=
 extension to the core specification.
>>>>=20
>>>> =20
>>>>=20
>>>> -Vivek Biswas
>>>>=20
>>>>=20
>>>>=20
>>>>   Consulting Member, Oracle
>>>>=20
>>>> Sent from my iPhone
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com> wr=
ote:
>>>>=20
>>>>=20
>>>> Thanks Alan,
>>>>=20
>>>> =20
>>>>=20
>>>> Interoperability will be on a per-application basis, just like JWT inte=
roperability.  The claims needed in an identity event are application-specif=
ic, just like claims are for JWTs.  This is the same standards posture and J=
WTs are a huge success =E2=80=93 including for interoperability, even if I d=
o say so myself.
>>>>=20
>>>> =20
>>>>=20
>>>>                                                           Best wishes,
>>>>=20
>>>>                                                           -- Mike
>>>>=20
>>>> =20
>>>>=20
>>>> =20
>>>>=20
>>>> =20
>>>>=20
>>>> =20
>>>>=20
>>>>=20
>>>>=20
>>>> From: Alan Karp
>>>> Sent: Saturday, May 7, 2016 10:23 AM
>>>> To: Mike Jones
>>>> Cc: Morteza Ansari (moransar); id-event@ietf.org
>>>> Subject: Re: [Id-event] Straw man text for proposed charter
>>>>=20
>>>>=20
>>>> =20
>>>>=20
>>>> As one who proposed doing more, I believe that your position is valid. =
 My only question is whether or not that will be enough for interoperability=
.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> --------------
>>>> Alan Karp
>>>>=20
>>>>=20
>>>> =20
>>>>=20
>>>> On Thu, May 5, 2016 at 10:00 PM, Mike Jones <Michael.Jones@microsoft.co=
m> wrote:
>>>>=20
>>>> Thanks guys, for writing the initial charter text.  Reading it now, I a=
m extremely worried by the scope creep evident in the proposal.
>>>>=20
>>>> =20
>>>>=20
>>>> I strongly support a working group to define an ID Events data format. =
 I just as strongly believe that specific event delivery mechanisms will nec=
essarily be application-specific and therefore MUST be explicitly be stated a=
s being out of scope in the working group charter.  Attempting to specify a p=
articular event delivery mechanism will take something that could be simple a=
nd quick to approve and bog it down in necessarily application-specific deba=
tes.
>>>>=20
>>>> =20
>>>>=20
>>>> Should event delivery be reliable?  That=E2=80=99s an application-speci=
fic decision.
>>>>=20
>>>> Should events be idempotent?  That=E2=80=99s an application-specific de=
cision.
>>>>=20
>>>> Should events be unicast, multicast, or broadcast?  That=E2=80=99s an a=
pplication-specific decision.
>>>>=20
>>>> Should events have categories with category-specific subscriptions?  Th=
at=E2=80=99s an application-specific decision.
>>>>=20
>>>> Should only one party at a time be able to register for delivery of eve=
nts or should multiple parties be able to request delivery?  That=E2=80=99s a=
n application-specific decision.
>>>>=20
>>>> I could continue with this list, but I think you all get the point=E2=80=
=A6
>>>>=20
>>>> =20
>>>>=20
>>>> If we start debating application-specific event delivery mechanisms, we=
=E2=80=99ll please almost no one, since nearly all applications have differe=
nt event delivery requirements.  We MUST explicitly rule all delivery mechan=
isms as being out of scope.
>>>>=20
>>>> =20
>>>>=20
>>>> If we define only a data format, we can quickly produce a very useful s=
pecification.  If we don=E2=80=99t, we=E2=80=99ll get bogged down in the mud=
 of debating which applications we=E2=80=99re catering to and which we aren=E2=
=80=99t =E2=80=93 an exercise of picking favorites and limiting applicabilit=
y of the specification.  That way is a slow, painful descent into standards q=
uicksand =E2=80=93 something we must avoid.  Having a standard ID events rep=
resentation is far too important to tie to a particular limited event delive=
ry mechanism.
>>>>=20
>>>> =20
>>>>=20
>>>>                                                           Sincerely,
>>>>=20
>>>>                                                           -- Mike
>>>>=20
>>>> =20
>>>>=20
>>>> From: Id-event [mailto:id-event-bounces@ietf.org] On Behalf Of Alan Kar=
p
>>>> Sent: Thursday, May 5, 2016 9:43 PM
>>>> To: Morteza Ansari (moransar) <moransar@cisco.com>
>>>> Cc: id-event@ietf.org
>>>> Subject: Re: [Id-event] Straw man text for proposed charter
>>>>=20
>>>> =20
>>>>=20
>>>> I don't see anything about access control for publishing events and sub=
scribing to them.  I also think the spec should allow filters on subscriptio=
ns.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> --------------
>>>> Alan Karp
>>>>=20
>>>>=20
>>>> =20
>>>>=20
>>>> On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar) <moransar@ci=
sco.com> wrote:
>>>>=20
>>>> Hi folks,
>>>>=20
>>>> =20
>>>>=20
>>>> At IIW a few of us (Phil, William, Adam, and I) huddled for a bit and p=
ut together the attached as a straw man charter proposal to start the discus=
sion. Please send your comments and suggestions for any changes or propose a=
 new one if you think its necessary.
>>>>=20
>>>> =20
>>>>=20
>>>> =20
>>>>=20
>>>> Cheers,
>>>>=20
>>>> Morteza
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> Id-event mailing list
>>>> Id-event@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/id-event
>>>>=20
>>>>=20
>>>> =20
>>>>=20
>>>> =20
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> Id-event mailing list
>>>> Id-event@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/id-event
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> Id-event mailing list
>>>> Id-event@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/id-event
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> Id-event mailing list
>>>> Id-event@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/id-event
>>>>=20
>>>>=20
>>>> =20
>>>>=20
>>>=20
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event

--Apple-Mail-35362907-0C53-4D1A-961A-6B1FD54DEBDB
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><div style=3D"direction: inherit;">Ale=
xy,</div><div style=3D"direction: inherit;"><br></div><div style=3D"directio=
n: inherit;">Thanks for helping this forwards.&nbsp;</div><div style=3D"dire=
ction: inherit;"><br></div><div style=3D"direction: inherit;">The name is fi=
ne.&nbsp;</div><br>Phil</div><div><br>On Sep 24, 2016, at 4:56 AM, Alexey Me=
lnikov &lt;<a href=3D"mailto:aamelnikov@fastmail.fm">aamelnikov@fastmail.fm<=
/a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div>


<title></title>

<div>This also reminded me: how much time does this group want to request fo=
r face-to-face meeting in Seoul?<br></div>
<div><br></div>
<div>On Sat, Sep 24, 2016, at 12:27 PM, Morteza Ansari (moransar) wrote:<br>=
</div>
<blockquote type=3D"cite"><div><div>This is great, thanks for helping speed u=
p the process! Name is a name, so no comment on naming.&nbsp;<br></div>
<div> <br></div>
<div> <br></div>
<div><br></div>
<div>Cheers,<br></div>
<div>Morteza<br></div>
</div>
<div><div><br></div>
<div>On Sep 24, 2016, at 4:04 AM, Alexey Melnikov &lt;<a href=3D"mailto:aame=
lnikov@fastmail.fm">aamelnikov@fastmail.fm</a>&gt; wrote:<br></div>
<div> <br></div>
</div>
<blockquote type=3D"cite"><div><div>Hi,<br></div>
<div>Just to let everyone know: I started chartering of the WG. The WG will b=
e in the Security Area (it was a borderline between ART and Security) and yo=
ur responsible AD is going to be&nbsp;Kathleen Moriarty.<br></div>
<div><div><br></div>
<div>Best Regards,<br></div>
<div>Alexey<br></div>
<div><br></div>
<div>P.S. I picked "SECEVENT" as the short WG name, but if you have better s=
uggestions, please let me know.<br></div>
<div><br></div>
</div>
<div>On Wed, Sep 7, 2016, at 01:04 AM, William Denniss wrote:<br></div>
<blockquote type=3D"cite"><div dir=3D"ltr"><div>Thank you Mike for revising t=
he charter.&nbsp;<br></div>
<div><br></div>
<div>I support it, and hope we can form a WG with this charter to continue o=
ur work.<br></div>
</div>
<div><div><br></div>
<div><div>On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <span dir=3D"ltr">&lt;<=
a href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a=
>&gt;</span> wrote:<br></div>
<blockquote style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;margi=
n-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);bord=
er-left-style:solid;padding-left:1ex;"><div lang=3D"EN-US"><div><p><span cla=
ss=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"f=
ont-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt=
">An updated and simplified charter is attached.&nbsp; This draft has been r=
eviewed by Phil Hunt, William Denniss,
 Marius Scurtescu.<u></u><u></u></span></span></span><br></p><p><span class=3D=
"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-f=
amily:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt"><u>=
</u>&nbsp;<u></u></span></span></span><br></p><p><span class=3D"colour" styl=
e=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri=
, sans-serif"><span class=3D"size" style=3D"font-size:11pt">Input from Alexe=
y Melnikov is that we should probably charter a working group, rather than t=
ry to go the
 AD-sponsored route.&nbsp; Therefore, please review this draft charter and l=
et us know if you think it=E2=80=99s ready to go.<u></u><u></u></span></span=
></span><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><sp=
an class=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"s=
ize" style=3D"font-size:11pt"><u></u>&nbsp;<u></u></span></span></span><br><=
/p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"f=
ont" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D=
"font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<u></u><u></u></span></spa=
n></span><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><s=
pan class=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"=
size" style=3D"font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<u></u><u></=
u></span></span></span><br></p><p><a name=3D"m_5165357944078144809__MailEndC=
ompose"><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D=
"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D=
"font-size:11pt"><u></u>&nbsp;<u></u></span></span></span></a><br></p><div><=
span></span><br></div>
<p><b><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span c=
lass=3D"size" style=3D"font-size:11pt">From:</span></span></b><span class=3D=
"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D=
"font-size:11pt"> Sarah Squire [mailto:<a href=3D"mailto:sarah@engageidentit=
y.com">sarah@engageidentity.<wbr>com</a>] <br> <b>Sent:</b> Thursday, July 1=
4, 2016 10:59 PM<br> <b>To:</b> Phil Hunt (IDM) &lt;<a href=3D"mailto:phil.h=
unt@oracle.com">phil.hunt@oracle.com</a>&gt;<br> <b>Cc:</b> Mike Jones &lt;<=
a href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a=
>&gt;; Alan Karp &lt;<a href=3D"mailto:alanhkarp@gmail.com">alanhkarp@gmail.=
com</a>&gt;; Vivek Biswas &lt;<a href=3D"mailto:vivek_biswas@yahoo.com">vive=
k_biswas@yahoo.com</a>&gt;;
 Morteza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.com">moransa=
r@cisco.com</a>&gt;; <a href=3D"mailto:id-event@ietf.org">id-event@ietf.org<=
/a></span></span></p><div><div><div><br></div>
<div><b>Subject:</b> Re: [Id-event] Straw man text for proposed charter<u></=
u><u></u><br></div>
</div>
</div>
<p><br></p><div><div><p><u></u>&nbsp;<u></u><br></p><div><div><p>Just submit=
ting my two cents in writing before we hopefully have a chance to meet about=
 this next week...<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<p>Looking at this charter from the perspective of the OIDF HEART working gr=
oup, I think it's going down a good path. In terms of the data format, this i=
s less structured than what I was envisioning, but we could easily do a heal=
thcare-specific profile of whatever
 data format comes out in the end, so it's better to be too broad than too n=
arrow as far as our interests are concerned.<u></u><u></u><br></p><div><p><u=
></u>&nbsp;<u></u><br></p></div>
<div><p>The transport layer however, has some added complexity. In our conte=
xt, we're shooting for interoperability, so we'd prefer something constraine=
d. I appreciate Mike's input that these are application layer decisions. How=
ever, if we're talking about cloud
 provider-to-cloud provider communication, that certainly is facilitated by a=
 well-defined transport layer. Again, we're willing to profile whatever the g=
roup comes up with for our own ends, but I don't really see the benefit of h=
aving a loosely defined transport
 layer - it just seems like more work for all the implementers to actually a=
gree on endpoints on a case-by-case basis.<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Looking forward to discussing further in Berlin!<u></u><u></u><br></=
p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Sarah<u></u><u></u><br></p></div>
</div>
<div><p><u></u><u></u><br></p><div><div><div><div><p><span class=3D"colour" s=
tyle=3D"color:rgb(136, 136, 136)">Sarah Squire<u></u><u></u></span><br></p><=
/div>
<div><p><span class=3D"colour" style=3D"color:rgb(136, 136, 136)">Engage Ide=
ntity<u></u><u></u></span><br></p></div>
<div><p><span class=3D"colour" style=3D"color:rgb(136, 136, 136)"><a href=3D=
"http://engageidentity.com/"><span class=3D"colour" style=3D"color:rgb(17, 8=
5, 204)">http://engageidentity.com</span></a><u></u><u></u></span><br></p></=
div>
</div>
</div>
</div>
<p><u></u>&nbsp;<u></u><br></p><div><p>On Sat, May 7, 2016 at 6:53 PM, Phil H=
unt (IDM) &lt;<a href=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.com</=
a>&gt; wrote:<u></u><u></u><br></p><blockquote style=3D"border-top-style:non=
e;border-right-style:none;border-bottom-style:none;border-top-width:initial;=
border-right-width:initial;border-bottom-width:initial;border-top-color:init=
ial;border-right-color:initial;border-bottom-color:initial;border-image-sour=
ce:initial;border-image-slice:initial;border-image-width:initial;border-imag=
e-outset:initial;border-image-repeat:initial;border-left-style:solid;border-=
left-color:rgb(204, 204, 204);border-left-width:1pt;padding-top:0in;padding-=
right:0in;padding-bottom:0in;padding-left:6pt;margin-left:4.8pt;margin-right=
:0in;"><div><div><p>We also set things up so even a domain specific event ca=
n be extended.&nbsp;<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Eg on a password reset event, so event publishers may want to add se=
curity domain specific attributes. The spec lets them do that while avoiding=
 interop issues.&nbsp;<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>I believe in the spec we had the example of an account reset and the=
 publisher adds reset count as an extension.&nbsp;<span class=3D"colour" sty=
le=3D"color:rgb(136, 136, 136)"><br> <br> <span>Phil</span></span><u></u><u>=
</u></p></div>
<div><div><div><p style=3D"margin-bottom:12pt;"><br></p><div><br></div>
<div>On May 7, 2016, at 13:31, Mike Jones &lt;<a href=3D"mailto:Michael.Jone=
s@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<u></u><u></u><br=
></div>
<p><br></p></div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><div><p>Indeed,=
 that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 so common cl=
aims can be defined once and then reused.<u></u><u></u><br></p><p>&nbsp;<u><=
/u><u></u><br></p><div style=3D"border-right-style:none;border-bottom-style:=
none;border-left-style:none;border-right-width:initial;border-bottom-width:i=
nitial;border-left-width:initial;border-right-color:initial;border-bottom-co=
lor:initial;border-left-color:initial;border-image-source:initial;border-ima=
ge-slice:initial;border-image-width:initial;border-image-outset:initial;bord=
er-image-repeat:initial;border-top-style:solid;border-top-color:rgb(225, 225=
, 225);border-top-width:1pt;padding-top:3pt;padding-right:0in;padding-bottom=
:0in;padding-left:0in;"><p><br></p><div><b>From: </b><a href=3D"mailto:vivek=
_biswas@yahoo.com">Vivek Biswas</a><br></div>
<div><b>Sent: </b>Saturday, May 7, 2016 1:24 PM<br></div>
<div><b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com">Mike Jones</a=
><br></div>
<div><b>Cc: </b><a href=3D"mailto:alanhkarp@gmail.com">Alan Karp</a>; <a hre=
f=3D"mailto:moransar@cisco.com"> Morteza Ansari (moransar)</a>; <a href=3D"m=
ailto:id-event@ietf.org">id-event@ietf.org</a><br></div>
<div><b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u></=
u><u></u><br></div>
<p><br></p></div>
<p>&nbsp;<u></u><u></u><br></p></div>
<div><div><p>Yes, I agree that the claims can be application specific, howev=
er there is a possibility to define claims which are domain specific. Thereb=
y claims generated in one application could be understood by another &nbsp;a=
pplication within the same domain.<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>With microservices based architecture getting lot of attention, if t=
wo different micro services defining different claims for the same claim, it=
 can create confusion.<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>Nevertheless this well defined claims for a particular domain can be=
 an extension to the core specification.<u></u><u></u><br></p></div>
<div><p><u></u>&nbsp;<u></u><br></p></div>
<div><p>-Vivek Biswas<u></u><u></u><br></p></div>
<div><p><br></p><div>&nbsp; Consulting Member, Oracle<br></div>
<div><br></div>
<div>Sent from my iPhone<u></u><u></u><br></div>
<p><br></p></div>
<div><p style=3D"margin-bottom:12pt;"><br></p><div><br></div>
<div>On May 7, 2016, at 1:04 PM, Mike Jones &lt;<a href=3D"mailto:Michael.Jo=
nes@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<u></u><u></u><=
br></div>
<p><br></p></div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><div><p>Thanks A=
lan,<u></u><u></u><br></p><p>&nbsp;<u></u><u></u><br></p><p><span class=3D"c=
olour" style=3D"color:rgb(0, 32, 96)">Interoperability will be on a per-appl=
ication basis, just like JWT interoperability.&nbsp; The claims needed in an=
 identity event are application-specific, just like claims are for JWTs.&nbs=
p; This is the same standards
 posture and JWTs are a huge success =E2=80=93 including for interoperabilit=
y, even if I do say so myself.</span><u></u><u></u><br></p><p><span class=3D=
"colour" style=3D"color:rgb(0, 32, 96)">&nbsp;</span><u></u><u></u><br></p><=
p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)">&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; Best wishes,</span><u></u><u></u><br></p><p><span cl=
ass=3D"colour" style=3D"color:rgb(0, 32, 96)">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<w=
br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; -- Mike</span><u></u><u></u><br></p><p>&nbsp;<u></u><u></u><br=
></p><p>&nbsp;<u></u><u></u><br></p><p>&nbsp;<u></u><u></u><br></p><p>&nbsp;=
<u></u><u></u><br></p><div style=3D"border-right-style:none;border-bottom-st=
yle:none;border-left-style:none;border-right-width:initial;border-bottom-wid=
th:initial;border-left-width:initial;border-right-color:initial;border-botto=
m-color:initial;border-left-color:initial;border-image-source:initial;border=
-image-slice:initial;border-image-width:initial;border-image-outset:initial;=
border-image-repeat:initial;border-top-style:solid;border-top-color:rgb(225,=
 225, 225);border-top-width:1pt;padding-top:3pt;padding-right:0in;padding-bo=
ttom:0in;padding-left:0in;"><p><br></p><div><b>From: </b><a href=3D"mailto:a=
lanhkarp@gmail.com">Alan Karp</a><br></div>
<div><b>Sent: </b>Saturday, May 7, 2016 10:23 AM<br></div>
<div><b>To: </b><a href=3D"mailto:Michael.Jones@microsoft.com">Mike Jones</a=
><br></div>
<div><b>Cc: </b><a href=3D"mailto:moransar@cisco.com">Morteza Ansari (morans=
ar)</a>; <a href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a><br></div=
>
<div><b>Subject: </b>Re: [Id-event] Straw man text for proposed charter<u></=
u><u></u><br></div>
<p><br></p></div>
<p>&nbsp;<u></u><u></u><br></p></div>
<div><div><p><span class=3D"size" style=3D"font-size:9.5pt">As one who propo=
sed doing more, I believe that your position is valid.&nbsp; My only questio=
n is whether or not that will be enough for interoperability.</span><u></u><=
u></u><br></p></div>
<div><p><u></u><u></u><br></p><div><div><p><br></p><div><br></div>
<div>--------------<br></div>
<div>Alan Karp<u></u><u></u><br></div>
<p><br></p></div>
</div>
<p><u></u>&nbsp;<u></u><br></p><div><p>On Thu, May 5, 2016 at 10:00 PM, Mike=
 Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@micr=
osoft.com</a>&gt; wrote:<u></u><u></u><br></p><blockquote style=3D"border-to=
p-style:none;border-right-style:none;border-bottom-style:none;border-top-wid=
th:initial;border-right-width:initial;border-bottom-width:initial;border-top=
-color:initial;border-right-color:initial;border-bottom-color:initial;border=
-image-source:initial;border-image-slice:initial;border-image-width:initial;=
border-image-outset:initial;border-image-repeat:initial;border-left-style:so=
lid;border-left-color:rgb(204, 204, 204);border-left-width:1pt;padding-top:0=
in;padding-right:0in;padding-bottom:0in;padding-left:6pt;margin-left:4.8pt;m=
argin-right:0in;"><div><div><p><span class=3D"colour" style=3D"color:rgb(0, 3=
2, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span=
 class=3D"size" style=3D"font-size:11pt">Thanks guys, for writing the initia=
l charter text.&nbsp; Reading it now, I am extremely worried by the scope
 creep evident in the proposal.</span></span></span><u></u><u></u><br></p><p=
><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-=
size:11pt">&nbsp;</span></span></span><u></u><u></u><br></p><p><span class=3D=
"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-f=
amily:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">I s=
trongly support a working group to define an ID Events data format.&nbsp; I j=
ust as strongly believe that
 specific event delivery mechanisms will necessarily be application-specific=
 and therefore MUST be explicitly be stated as being out of scope in the wor=
king group charter.&nbsp; Attempting to specify a particular event delivery m=
echanism will take something that
 could be simple and quick to approve and bog it down in necessarily applica=
tion-specific debates.</span></span></span><u></u><u></u><br></p><p><span cl=
ass=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"=
font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size:11p=
t">&nbsp;</span></span></span><u></u><u></u><br></p><p><span class=3D"colour=
" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:C=
alibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">Should eve=
nt delivery be reliable?&nbsp; That=E2=80=99s an application-specific decisi=
on.</span></span></span><u></u><u></u><br></p><p><span class=3D"colour" styl=
e=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri=
, sans-serif"><span class=3D"size" style=3D"font-size:11pt">Should events be=
 idempotent?&nbsp; That=E2=80=99s an application-specific decision.</span></=
span></span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:r=
gb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif=
"><span class=3D"size" style=3D"font-size:11pt">Should events be unicast, mu=
lticast, or broadcast?&nbsp; That=E2=80=99s an application-specific decision=
.</span></span></span><u></u><u></u><br></p><p><span class=3D"colour" style=3D=
"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sa=
ns-serif"><span class=3D"size" style=3D"font-size:11pt">Should events have c=
ategories with category-specific subscriptions?&nbsp; That=E2=80=99s an appl=
ication-specific decision.</span></span></span><u></u><u></u><br></p><p><spa=
n class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=
=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-size=
:11pt">Should only one party at a time be able to register for delivery of e=
vents or should multiple parties be
 able to request delivery?&nbsp; That=E2=80=99s an application-specific deci=
sion.</span></span></span><u></u><u></u><br></p><p><span class=3D"colour" st=
yle=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calib=
ri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">I could contin=
ue with this list, but I think you all get the point=E2=80=A6</span></span><=
/span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 3=
2, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span=
 class=3D"size" style=3D"font-size:11pt">&nbsp;</span></span></span><u></u><=
u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span=
 class=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"siz=
e" style=3D"font-size:11pt">If we start debating application-specific event d=
elivery mechanisms, we=E2=80=99ll please almost no one, since
 nearly all applications have different event delivery requirements.&nbsp; W=
e MUST explicitly rule all delivery mechanisms as being out of scope.</span>=
</span></span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color=
:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-ser=
if"><span class=3D"size" style=3D"font-size:11pt">&nbsp;</span></span></span=
><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 9=
6)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span cla=
ss=3D"size" style=3D"font-size:11pt">If we define only a data format, we can=
 quickly produce a very useful specification.&nbsp; If we don=E2=80=99t, we=E2=
=80=99ll
 get bogged down in the mud of debating which applications we=E2=80=99re cat=
ering to and which we aren=E2=80=99t =E2=80=93 an exercise of picking favori=
tes and limiting applicability of the specification.&nbsp; That way is a slo=
w, painful descent into standards quicksand =E2=80=93 something we
 must avoid.&nbsp; Having a standard ID events representation is far too imp=
ortant to tie to a particular limited event delivery mechanism.</span></span=
></span><u></u><u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0=
, 32, 96)"><span class=3D"font" style=3D"font-family:Calibri, sans-serif"><s=
pan class=3D"size" style=3D"font-size:11pt">&nbsp;</span></span></span><u></=
u><u></u><br></p><p><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><s=
pan class=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"=
size" style=3D"font-size:11pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S=
incerely,</span></span></span><u></u><u></u><br></p><p><span class=3D"colour=
" style=3D"color:rgb(0, 32, 96)"><span class=3D"font" style=3D"font-family:C=
alibri, sans-serif"><span class=3D"size" style=3D"font-size:11pt">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;<wbr>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span></span></span><u></u><u></u>=
<br></p><p><a name=3D"m_5165357944078144809_m_3022367059336893565_m_14610242=
54222911"><span class=3D"colour" style=3D"color:rgb(0, 32, 96)"><span class=3D=
"font" style=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D=
"font-size:11pt">&nbsp;</span></span></span></a><u></u><u></u><br></p><p><b>=
<span class=3D"font" style=3D"font-family:Calibri, sans-serif"><span class=3D=
"size" style=3D"font-size:11pt">From:</span></span></b><span class=3D"font" s=
tyle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-=
size:11pt"> Id-event [mailto:<a href=3D"mailto:id-event-bounces@ietf.org">id=
-event-bounces@ietf.<wbr>org</a>] <b>On Behalf Of </b>Alan Karp<br> <b>Sent:=
</b> Thursday, May 5, 2016 9:43 PM<br> <b>To:</b> Morteza Ansari (moransar) &=
lt;<a href=3D"mailto:moransar@cisco.com">moransar@cisco.com</a>&gt;<br> <b>C=
c:</b> <a href=3D"mailto:id-event@ietf.org">id-event@ietf.org</a><br> <b>Sub=
ject:</b> Re: [Id-event] Straw man text for proposed charter</span></span><u=
></u><u></u></p><p>&nbsp;<u></u><u></u><br></p><div><p>I don't see anything a=
bout access control for publishing events and subscribing to them.&nbsp; I a=
lso think the spec should allow filters on subscriptions.<u></u><u></u><br><=
/p></div>
<div><p><u></u><u></u><br></p><div><div><p><br></p><div><br></div>
<div>--------------<br></div>
<div>Alan Karp<u></u><u></u><br></div>
<p><br></p></div>
</div>
<p>&nbsp;<u></u><u></u><br></p><div><p>On Thu, May 5, 2016 at 11:18 AM, Mort=
eza Ansari (moransar) &lt;<a href=3D"mailto:moransar@cisco.com">moransar@cis=
co.com</a>&gt; wrote:<u></u><u></u><br></p><blockquote style=3D"border-top-s=
tyle:none;border-right-style:none;border-bottom-style:none;border-top-width:=
initial;border-right-width:initial;border-bottom-width:initial;border-top-co=
lor:initial;border-right-color:initial;border-bottom-color:initial;border-im=
age-source:initial;border-image-slice:initial;border-image-width:initial;bor=
der-image-outset:initial;border-image-repeat:initial;border-left-style:solid=
;border-left-color:rgb(204, 204, 204);border-left-width:1pt;padding-top:0in;=
padding-right:0in;padding-bottom:0in;padding-left:6pt;margin-left:4.8pt;marg=
in-top:5pt;margin-right:0in;margin-bottom:5pt;"><div><div><p><span class=3D"=
colour" style=3D"color:black"><span class=3D"font" style=3D"font-family:Cali=
bri, sans-serif"><span class=3D"size" style=3D"font-size:10.5pt">Hi folks,</=
span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" st=
yle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-s=
ize:10.5pt">&nbsp;</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" st=
yle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-s=
ize:10.5pt">At IIW a few of us (Phil, William, Adam, and I) huddled for a bi=
t and put together the attached as a straw man
 charter proposal to start the discussion. Please send your comments and sug=
gestions for any changes or propose a new one if you think its necessary.</s=
pan></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" st=
yle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-s=
ize:10.5pt">&nbsp;</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" st=
yle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-s=
ize:10.5pt">&nbsp;</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" st=
yle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-s=
ize:10.5pt">Cheers,</span></span></span><u></u><u></u><br></p></div>
<div><p><span class=3D"colour" style=3D"color:black"><span class=3D"font" st=
yle=3D"font-family:Calibri, sans-serif"><span class=3D"size" style=3D"font-s=
ize:10.5pt">Morteza</span></span></span><u></u><u></u><br></p></div>
</div>
<p style=3D"margin-bottom:12pt;"><br></p><div><br></div>
<div>______________________________<wbr>_________________<br></div>
<div>Id-event mailing list<br></div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www.=
ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
<p><br></p></blockquote></div>
<p>&nbsp;<u></u><u></u><br></p></div>
</div>
</div>
</blockquote></div>
<p><u></u>&nbsp;<u></u><br></p></div>
</div>
</div>
</blockquote><blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><p=
><br></p><div>______________________________<wbr>_________________<br></div>=

<div>Id-event mailing list<br></div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www.=
ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
<p><br></p></div>
</blockquote></div>
</div>
</blockquote><blockquote style=3D"margin-top:5pt;margin-bottom:5pt;"><div><p=
><br></p><div>______________________________<wbr>_________________<br></div>=

<div>Id-event mailing list<br></div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www.=
ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
<p><br></p></div>
</blockquote></div>
</div>
</div>
<p style=3D"margin-bottom:12pt;"><br></p><div><br></div>
<div>______________________________<wbr>_________________<br></div>
<div>Id-event mailing list<br></div>
<div><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a><br></div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www.=
ietf.org/mailman/<wbr>listinfo/id-event</a><u></u><u></u><br></div>
<p><br></p></blockquote></div>
<p><u></u>&nbsp;<u></u><br></p></div>
</div>
</div>
</div>
</div>
</blockquote></div>
</div>
</blockquote><div><br></div>
</div>
</blockquote><blockquote type=3D"cite"><div><div><span>_____________________=
__________________________</span><br></div>
<div> <span>Id-event mailing list</span><br></div>
<div> <span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></span=
><br></div>
<div> <span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https=
://www.ietf.org/mailman/listinfo/id-event</a></span><br></div>
</div>
</blockquote></blockquote>

</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>Id-event mailing list</span><br>=
<span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></span><br><=
span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">https://www.=
ietf.org/mailman/listinfo/id-event</a></span><br></div></blockquote></body><=
/html>=

--Apple-Mail-35362907-0C53-4D1A-961A-6B1FD54DEBDB--


From nobody Mon Sep 26 06:46:36 2016
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF26412B26C for <id-event@ietfa.amsl.com>; Mon, 26 Sep 2016 06:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MXvM5DBGccfc for <id-event@ietfa.amsl.com>; Mon, 26 Sep 2016 06:46:33 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C385D12B223 for <id-event@ietf.org>; Mon, 26 Sep 2016 06:46:32 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id v205so56971852vke.1 for <id-event@ietf.org>; Mon, 26 Sep 2016 06:46:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=YNiIn8wLUtI1knvCHqqt4tiU1/D/3bFNx4pYAtzW6Yk=; b=R+T92DhSEn/ovPCtkx95h+7J+ddwomXODxtgWN0RcPk9GYr8QfQOwlIW+Rl+HvNtJX v52z81d9fubTjc0w1smwlN1Ft2N40nJLnCO6jlNUb7xKZidV/y9A5vVn6pk3T9GmJhf2 w3yFirJHZhRY+IN2Dq1h7ssurPEmK4AFnQaxrS2Hqi5g0o0oBx9ZeA+r2AY6Bv0SqwoW iTR8lVezul05jo73akanmTs9pWo/dXm3NSbjekwv/eKYFgdyTUzRWqud+QEDMLQMTHDO OdrnwfVMC7WmZ2J++G8YP0GFwtIuoGE50Y1UzVmoGQG/dPnvtEo0WCSVbYJJOZdPxVcs UaKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=YNiIn8wLUtI1knvCHqqt4tiU1/D/3bFNx4pYAtzW6Yk=; b=YjzUn4sS4w3oTq/xdlUX2I0qT26pTJtEgQkQdfnshEryyH38+odV7rFUn498ioWu9x KXijdQmOtBYPZ0xdtCtep25l/i4wgLLpQBTiPq2sbFB59s1jRo+QbvHNdv1F3FYWQyFi VR/9eObZ9bt+w4VB37/N/5PkUdgJD9CRGnBLeE6D/noViJbWGp1+J/a7GoBBT0Jc0isV zg7bbNxZn1tjgekaU391Uz+l23zsdMqRDDYFcuZocU4Sf0o5LE3jTytw8KSM9n+g0y0D LuJ5BKb4eBwCycN5bfJqJcjYJhrCzW49ETkmmAp/+j/Z5X2jw3hXWAPyWTVSX4YR1Ssm /OtQ==
X-Gm-Message-State: AA6/9RnfMqJluzzZGc1Y4xeMzxKxu7UhLn+XH/n85vLBxSLOzH0iuBEL08g1VsKV0WV5S/2IZ0uwobRsJppRPw==
X-Received: by 10.31.59.75 with SMTP id i72mr8862529vka.115.1474897448641; Mon, 26 Sep 2016 06:44:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.65.8 with HTTP; Mon, 26 Sep 2016 06:44:07 -0700 (PDT)
In-Reply-To: <E6BF4F8B-5176-4BA4-A644-DBEE33619161@oracle.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com> <1474715073.2319843.735650465.3C69F11E@webmail.messagingengine.com> <D03F281C-3051-4E0D-81C8-0F0CC0854A10@cisco.com> <1474718187.2329006.735672633.371888A0@webmail.messagingengine.com> <E6BF4F8B-5176-4BA4-A644-DBEE33619161@oracle.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Mon, 26 Sep 2016 09:44:07 -0400
Message-ID: <CAHbuEH4uGOUrbn03LxTTgVLy+ErCa-K3b=HvSD8AZYGXLrkPWw@mail.gmail.com>
To: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/nNcdj-U_L9RzGjMhhxJKo3lKhT0>
Cc: William Denniss <wdenniss@google.com>, Mike Jones <Michael.Jones@microsoft.com>, "Morteza Ansari \(moransar\)" <moransar@cisco.com>, id-event@ietf.org, Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Re: [Id-event] Chartering of Security Events WG
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Sep 2016 13:46:36 -0000

Hi,

It would be good to get a mail message to the SAAG list to announce
this, that it crosses areas and that I'll be the AD along with the
charter and other information.  Is there any other information that
should be in such an announcement?

Thanks,
Kathleen

On Sat, Sep 24, 2016 at 11:56 AM, Phil Hunt (IDM) <phil.hunt@oracle.com> wr=
ote:
> Alexy,
>
> Thanks for helping this forwards.
>
> The name is fine.
>
> Phil
>
> On Sep 24, 2016, at 4:56 AM, Alexey Melnikov <aamelnikov@fastmail.fm> wro=
te:
>
> This also reminded me: how much time does this group want to request for
> face-to-face meeting in Seoul?
>
> On Sat, Sep 24, 2016, at 12:27 PM, Morteza Ansari (moransar) wrote:
>
> This is great, thanks for helping speed up the process! Name is a name, s=
o
> no comment on naming.
>
>
>
> Cheers,
> Morteza
>
> On Sep 24, 2016, at 4:04 AM, Alexey Melnikov <aamelnikov@fastmail.fm> wro=
te:
>
> Hi,
> Just to let everyone know: I started chartering of the WG. The WG will be=
 in
> the Security Area (it was a borderline between ART and Security) and your
> responsible AD is going to be Kathleen Moriarty.
>
> Best Regards,
> Alexey
>
> P.S. I picked "SECEVENT" as the short WG name, but if you have better
> suggestions, please let me know.
>
> On Wed, Sep 7, 2016, at 01:04 AM, William Denniss wrote:
>
> Thank you Mike for revising the charter.
>
> I support it, and hope we can form a WG with this charter to continue our
> work.
>
> On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:
>
> An updated and simplified charter is attached.  This draft has been revie=
wed
> by Phil Hunt, William Denniss, Marius Scurtescu.
>
>
>
> Input from Alexey Melnikov is that we should probably charter a working
> group, rather than try to go the AD-sponsored route.  Therefore, please
> review this draft charter and let us know if you think it=E2=80=99s ready=
 to go.
>
>
>
>                                                        Thanks,
>
>                                                        -- Mike
>
>
>
>
> From: Sarah Squire [mailto:sarah@engageidentity.com]
> Sent: Thursday, July 14, 2016 10:59 PM
> To: Phil Hunt (IDM) <phil.hunt@oracle.com>
> Cc: Mike Jones <Michael.Jones@microsoft.com>; Alan Karp
> <alanhkarp@gmail.com>; Vivek Biswas <vivek_biswas@yahoo.com>; Morteza Ans=
ari
> (moransar) <moransar@cisco.com>; id-event@ietf.org
>
>
> Subject: Re: [Id-event] Straw man text for proposed charter
>
>
>
>
> Just submitting my two cents in writing before we hopefully have a chance=
 to
> meet about this next week...
>
>
>
> Looking at this charter from the perspective of the OIDF HEART working
> group, I think it's going down a good path. In terms of the data format,
> this is less structured than what I was envisioning, but we could easily =
do
> a healthcare-specific profile of whatever data format comes out in the en=
d,
> so it's better to be too broad than too narrow as far as our interests ar=
e
> concerned.
>
>
>
> The transport layer however, has some added complexity. In our context,
> we're shooting for interoperability, so we'd prefer something constrained=
. I
> appreciate Mike's input that these are application layer decisions. Howev=
er,
> if we're talking about cloud provider-to-cloud provider communication, th=
at
> certainly is facilitated by a well-defined transport layer. Again, we're
> willing to profile whatever the group comes up with for our own ends, but=
 I
> don't really see the benefit of having a loosely defined transport layer =
-
> it just seems like more work for all the implementers to actually agree o=
n
> endpoints on a case-by-case basis.
>
>
>
> Looking forward to discussing further in Berlin!
>
>
>
> Sarah
>
>
> Sarah Squire
>
> Engage Identity
>
> http://engageidentity.com
>
>
>
> On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com>
> wrote:
>
> We also set things up so even a domain specific event can be extended.
>
>
>
> Eg on a password reset event, so event publishers may want to add securit=
y
> domain specific attributes. The spec lets them do that while avoiding
> interop issues.
>
>
>
> I believe in the spec we had the example of an account reset and the
> publisher adds reset count as an extension.
>
> Phil
>
>
>
> On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com> wrote:
>
>
> Indeed, that=E2=80=99s why there=E2=80=99s a claims registry =E2=80=93 so=
 common claims can be
> defined once and then reused.
>
>
>
>
> From: Vivek Biswas
> Sent: Saturday, May 7, 2016 1:24 PM
> To: Mike Jones
> Cc: Alan Karp; Morteza Ansari (moransar); id-event@ietf.org
> Subject: Re: [Id-event] Straw man text for proposed charter
>
>
>
>
> Yes, I agree that the claims can be application specific, however there i=
s a
> possibility to define claims which are domain specific. Thereby claims
> generated in one application could be understood by another  application
> within the same domain.
>
>
>
> With microservices based architecture getting lot of attention, if two
> different micro services defining different claims for the same claim, it
> can create confusion.
>
>
>
> Nevertheless this well defined claims for a particular domain can be an
> extension to the core specification.
>
>
>
> -Vivek Biswas
>
>
>   Consulting Member, Oracle
>
> Sent from my iPhone
>
>
>
>
> On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com> wrot=
e:
>
>
> Thanks Alan,
>
>
>
> Interoperability will be on a per-application basis, just like JWT
> interoperability.  The claims needed in an identity event are
> application-specific, just like claims are for JWTs.  This is the same
> standards posture and JWTs are a huge success =E2=80=93 including for
> interoperability, even if I do say so myself.
>
>
>
>                                                           Best wishes,
>
>                                                           -- Mike
>
>
>
>
>
>
>
>
>
>
> From: Alan Karp
> Sent: Saturday, May 7, 2016 10:23 AM
> To: Mike Jones
> Cc: Morteza Ansari (moransar); id-event@ietf.org
> Subject: Re: [Id-event] Straw man text for proposed charter
>
>
>
>
> As one who proposed doing more, I believe that your position is valid.  M=
y
> only question is whether or not that will be enough for interoperability.
>
>
>
>
> --------------
> Alan Karp
>
>
>
>
> On Thu, May 5, 2016 at 10:00 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:
>
> Thanks guys, for writing the initial charter text.  Reading it now, I am
> extremely worried by the scope creep evident in the proposal.
>
>
>
> I strongly support a working group to define an ID Events data format.  I
> just as strongly believe that specific event delivery mechanisms will
> necessarily be application-specific and therefore MUST be explicitly be
> stated as being out of scope in the working group charter.  Attempting to
> specify a particular event delivery mechanism will take something that co=
uld
> be simple and quick to approve and bog it down in necessarily
> application-specific debates.
>
>
>
> Should event delivery be reliable?  That=E2=80=99s an application-specifi=
c decision.
>
> Should events be idempotent?  That=E2=80=99s an application-specific deci=
sion.
>
> Should events be unicast, multicast, or broadcast?  That=E2=80=99s an
> application-specific decision.
>
> Should events have categories with category-specific subscriptions?  That=
=E2=80=99s
> an application-specific decision.
>
> Should only one party at a time be able to register for delivery of event=
s
> or should multiple parties be able to request delivery?  That=E2=80=99s a=
n
> application-specific decision.
>
> I could continue with this list, but I think you all get the point=E2=80=
=A6
>
>
>
> If we start debating application-specific event delivery mechanisms, we=
=E2=80=99ll
> please almost no one, since nearly all applications have different event
> delivery requirements.  We MUST explicitly rule all delivery mechanisms a=
s
> being out of scope.
>
>
>
> If we define only a data format, we can quickly produce a very useful
> specification.  If we don=E2=80=99t, we=E2=80=99ll get bogged down in the=
 mud of debating
> which applications we=E2=80=99re catering to and which we aren=E2=80=99t =
=E2=80=93 an exercise of
> picking favorites and limiting applicability of the specification.  That =
way
> is a slow, painful descent into standards quicksand =E2=80=93 something w=
e must
> avoid.  Having a standard ID events representation is far too important t=
o
> tie to a particular limited event delivery mechanism.
>
>
>
>                                                           Sincerely,
>
>                                                           -- Mike
>
>
>
> From: Id-event [mailto:id-event-bounces@ietf.org] On Behalf Of Alan Karp
> Sent: Thursday, May 5, 2016 9:43 PM
> To: Morteza Ansari (moransar) <moransar@cisco.com>
> Cc: id-event@ietf.org
> Subject: Re: [Id-event] Straw man text for proposed charter
>
>
>
> I don't see anything about access control for publishing events and
> subscribing to them.  I also think the spec should allow filters on
> subscriptions.
>
>
>
>
> --------------
> Alan Karp
>
>
>
>
> On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar)
> <moransar@cisco.com> wrote:
>
> Hi folks,
>
>
>
> At IIW a few of us (Phil, William, Adam, and I) huddled for a bit and put
> together the attached as a straw man charter proposal to start the
> discussion. Please send your comments and suggestions for any changes or
> propose a new one if you think its necessary.
>
>
>
>
>
> Cheers,
>
> Morteza
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>
>
>
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
>
>
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event



--=20

Best regards,
Kathleen


From nobody Mon Sep 26 13:21:16 2016
Return-Path: <moransar@cisco.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE4F812B015 for <id-event@ietfa.amsl.com>; Mon, 26 Sep 2016 13:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.837
X-Spam-Level: 
X-Spam-Status: No, score=-16.837 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uDqgDrmzZaW8 for <id-event@ietfa.amsl.com>; Mon, 26 Sep 2016 13:21:12 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 069C412B011 for <id-event@ietf.org>; Mon, 26 Sep 2016 13:21:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11858; q=dns/txt; s=iport; t=1474921272; x=1476130872; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=uICSb99egGFvbmgIs6tvTZsxmRu1l4LOzjTAFJMRikg=; b=GgHvhdVWCxc3RqcXvynnm5/D/w6hWCoklIVdWK9vU6rmcmPP0xjMhJy9 OmB/O393QQ++OHmr3y9sJTXrfaSzgMTFd+/nZYytsN5wzWta3WVdV22lY ByEGJvEmhEo8jLA33NSSSz5o98F+yD35rp2QH6+L2pmsFuGdJn8Cgl+by Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BWAgC9gulX/4ENJK1UCRkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM9AQEBAQEeV3wHjSyZWoUujEeCBBkLgmeBXYE2AoFiOBQBAgE?= =?us-ascii?q?BAQEBAQFeJ4RhAQEBBAEBAWsFBhACAQgRAQMBAQEVAw8HIQYLEwEDBggCBAENB?= =?us-ascii?q?R+IEgMXDrtgDYNJAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIY3g0+BBYJHgVYDBwE?= =?us-ascii?q?BGwcxBw+FEAEEhhlRDIFAhX6LDTUBhiaGBkMGgnKBbk6EFodsgS2IXIQPg3sBH?= =?us-ascii?q?jaFBXIBhTcPF4EJfwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.30,401,1470700800"; d="scan'208";a="327546797"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 26 Sep 2016 20:21:10 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u8QKLAcG014726 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 26 Sep 2016 20:21:10 GMT
Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 26 Sep 2016 15:21:09 -0500
Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1210.000; Mon, 26 Sep 2016 15:21:09 -0500
From: "Morteza Ansari (moransar)" <moransar@cisco.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, "Phil Hunt (IDM)" <phil.hunt@oracle.com>
Thread-Topic: [Id-event] Chartering of Security Events WG
Thread-Index: AQHSFlN1sjAXmrCLrUCCk3mmMkyI0qCIgIdsgABLPICAAFPaAIAC/6iA///5lAA=
Date: Mon, 26 Sep 2016 20:21:09 +0000
Message-ID: <D40EC92D.49B31%moransar@cisco.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com> <1474715073.2319843.735650465.3C69F11E@webmail.messagingengine.com> <D03F281C-3051-4E0D-81C8-0F0CC0854A10@cisco.com> <1474718187.2329006.735672633.371888A0@webmail.messagingengine.com> <E6BF4F8B-5176-4BA4-A644-DBEE33619161@oracle.com> <CAHbuEH4uGOUrbn03LxTTgVLy+ErCa-K3b=HvSD8AZYGXLrkPWw@mail.gmail.com>
In-Reply-To: <CAHbuEH4uGOUrbn03LxTTgVLy+ErCa-K3b=HvSD8AZYGXLrkPWw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.8.160830
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.53.212]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <49B0B5301BBC7549905A7EB0E37F2898@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/j49f1eKTNJ8Q4BJG88bXQ2_WL68>
Cc: William Denniss <wdenniss@google.com>, Mike Jones <Michael.Jones@microsoft.com>, "id-event@ietf.org" <id-event@ietf.org>, Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Re: [Id-event] Chartering of Security Events WG
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Sep 2016 20:21:15 -0000

Hi Kathleen,

Great idea and hopefully it will get us some fresh blood in the WG for
contribution and reviews. I can=B9t think of anything else to include beyon=
d
what you suggested. We can do a complete review of the drafts in the works
in Seoul to catch up any new folks interested in participating (I won=B9t b=
e
there in person, but will join the meeting remotely).

I assume you or Alexey will send the note, but if you want one of us to
send it just let us know.


Cheers,
Morteza

On 9/26/16, 6:44 AM, "Kathleen Moriarty"
<kathleen.moriarty.ietf@gmail.com> wrote:

>Hi,
>
>It would be good to get a mail message to the SAAG list to announce
>this, that it crosses areas and that I'll be the AD along with the
>charter and other information.  Is there any other information that
>should be in such an announcement?
>
>Thanks,
>Kathleen
>
>On Sat, Sep 24, 2016 at 11:56 AM, Phil Hunt (IDM) <phil.hunt@oracle.com>
>wrote:
>> Alexy,
>>
>> Thanks for helping this forwards.
>>
>> The name is fine.
>>
>> Phil
>>
>> On Sep 24, 2016, at 4:56 AM, Alexey Melnikov <aamelnikov@fastmail.fm>
>>wrote:
>>
>> This also reminded me: how much time does this group want to request for
>> face-to-face meeting in Seoul?
>>
>> On Sat, Sep 24, 2016, at 12:27 PM, Morteza Ansari (moransar) wrote:
>>
>> This is great, thanks for helping speed up the process! Name is a name,
>>so
>> no comment on naming.
>>
>>
>>
>> Cheers,
>> Morteza
>>
>> On Sep 24, 2016, at 4:04 AM, Alexey Melnikov <aamelnikov@fastmail.fm>
>>wrote:
>>
>> Hi,
>> Just to let everyone know: I started chartering of the WG. The WG will
>>be in
>> the Security Area (it was a borderline between ART and Security) and
>>your
>> responsible AD is going to be Kathleen Moriarty.
>>
>> Best Regards,
>> Alexey
>>
>> P.S. I picked "SECEVENT" as the short WG name, but if you have better
>> suggestions, please let me know.
>>
>> On Wed, Sep 7, 2016, at 01:04 AM, William Denniss wrote:
>>
>> Thank you Mike for revising the charter.
>>
>> I support it, and hope we can form a WG with this charter to continue
>>our
>> work.
>>
>> On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <Michael.Jones@microsoft.com>
>> wrote:
>>
>> An updated and simplified charter is attached.  This draft has been
>>reviewed
>> by Phil Hunt, William Denniss, Marius Scurtescu.
>>
>>
>>
>> Input from Alexey Melnikov is that we should probably charter a working
>> group, rather than try to go the AD-sponsored route.  Therefore, please
>> review this draft charter and let us know if you think it=B9s ready to g=
o.
>>
>>
>>
>>                                                        Thanks,
>>
>>                                                        -- Mike
>>
>>
>>
>>
>> From: Sarah Squire [mailto:sarah@engageidentity.com]
>> Sent: Thursday, July 14, 2016 10:59 PM
>> To: Phil Hunt (IDM) <phil.hunt@oracle.com>
>> Cc: Mike Jones <Michael.Jones@microsoft.com>; Alan Karp
>> <alanhkarp@gmail.com>; Vivek Biswas <vivek_biswas@yahoo.com>; Morteza
>>Ansari
>> (moransar) <moransar@cisco.com>; id-event@ietf.org
>>
>>
>> Subject: Re: [Id-event] Straw man text for proposed charter
>>
>>
>>
>>
>> Just submitting my two cents in writing before we hopefully have a
>>chance to
>> meet about this next week...
>>
>>
>>
>> Looking at this charter from the perspective of the OIDF HEART working
>> group, I think it's going down a good path. In terms of the data format,
>> this is less structured than what I was envisioning, but we could
>>easily do
>> a healthcare-specific profile of whatever data format comes out in the
>>end,
>> so it's better to be too broad than too narrow as far as our interests
>>are
>> concerned.
>>
>>
>>
>> The transport layer however, has some added complexity. In our context,
>> we're shooting for interoperability, so we'd prefer something
>>constrained. I
>> appreciate Mike's input that these are application layer decisions.
>>However,
>> if we're talking about cloud provider-to-cloud provider communication,
>>that
>> certainly is facilitated by a well-defined transport layer. Again, we're
>> willing to profile whatever the group comes up with for our own ends,
>>but I
>> don't really see the benefit of having a loosely defined transport
>>layer -
>> it just seems like more work for all the implementers to actually agree
>>on
>> endpoints on a case-by-case basis.
>>
>>
>>
>> Looking forward to discussing further in Berlin!
>>
>>
>>
>> Sarah
>>
>>
>> Sarah Squire
>>
>> Engage Identity
>>
>> http://engageidentity.com
>>
>>
>>
>> On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com>
>> wrote:
>>
>> We also set things up so even a domain specific event can be extended.
>>
>>
>>
>> Eg on a password reset event, so event publishers may want to add
>>security
>> domain specific attributes. The spec lets them do that while avoiding
>> interop issues.
>>
>>
>>
>> I believe in the spec we had the example of an account reset and the
>> publisher adds reset count as an extension.
>>
>> Phil
>>
>>
>>
>> On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com>
>>wrote:
>>
>>
>> Indeed, that=B9s why there=B9s a claims registry =AD so common claims ca=
n be
>> defined once and then reused.
>>
>>
>>
>>
>> From: Vivek Biswas
>> Sent: Saturday, May 7, 2016 1:24 PM
>> To: Mike Jones
>> Cc: Alan Karp; Morteza Ansari (moransar); id-event@ietf.org
>> Subject: Re: [Id-event] Straw man text for proposed charter
>>
>>
>>
>>
>> Yes, I agree that the claims can be application specific, however there
>>is a
>> possibility to define claims which are domain specific. Thereby claims
>> generated in one application could be understood by another  application
>> within the same domain.
>>
>>
>>
>> With microservices based architecture getting lot of attention, if two
>> different micro services defining different claims for the same claim,
>>it
>> can create confusion.
>>
>>
>>
>> Nevertheless this well defined claims for a particular domain can be an
>> extension to the core specification.
>>
>>
>>
>> -Vivek Biswas
>>
>>
>>   Consulting Member, Oracle
>>
>> Sent from my iPhone
>>
>>
>>
>>
>> On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com>
>>wrote:
>>
>>
>> Thanks Alan,
>>
>>
>>
>> Interoperability will be on a per-application basis, just like JWT
>> interoperability.  The claims needed in an identity event are
>> application-specific, just like claims are for JWTs.  This is the same
>> standards posture and JWTs are a huge success =AD including for
>> interoperability, even if I do say so myself.
>>
>>
>>
>>                                                           Best wishes,
>>
>>                                                           -- Mike
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> From: Alan Karp
>> Sent: Saturday, May 7, 2016 10:23 AM
>> To: Mike Jones
>> Cc: Morteza Ansari (moransar); id-event@ietf.org
>> Subject: Re: [Id-event] Straw man text for proposed charter
>>
>>
>>
>>
>> As one who proposed doing more, I believe that your position is valid.
>>My
>> only question is whether or not that will be enough for
>>interoperability.
>>
>>
>>
>>
>> --------------
>> Alan Karp
>>
>>
>>
>>
>> On Thu, May 5, 2016 at 10:00 PM, Mike Jones
>><Michael.Jones@microsoft.com>
>> wrote:
>>
>> Thanks guys, for writing the initial charter text.  Reading it now, I am
>> extremely worried by the scope creep evident in the proposal.
>>
>>
>>
>> I strongly support a working group to define an ID Events data format.
>>I
>> just as strongly believe that specific event delivery mechanisms will
>> necessarily be application-specific and therefore MUST be explicitly be
>> stated as being out of scope in the working group charter.  Attempting
>>to
>> specify a particular event delivery mechanism will take something that
>>could
>> be simple and quick to approve and bog it down in necessarily
>> application-specific debates.
>>
>>
>>
>> Should event delivery be reliable?  That=B9s an application-specific
>>decision.
>>
>> Should events be idempotent?  That=B9s an application-specific decision.
>>
>> Should events be unicast, multicast, or broadcast?  That=B9s an
>> application-specific decision.
>>
>> Should events have categories with category-specific subscriptions?
>>That=B9s
>> an application-specific decision.
>>
>> Should only one party at a time be able to register for delivery of
>>events
>> or should multiple parties be able to request delivery?  That=B9s an
>> application-specific decision.
>>
>> I could continue with this list, but I think you all get the point=8A
>>
>>
>>
>> If we start debating application-specific event delivery mechanisms,
>>we=B9ll
>> please almost no one, since nearly all applications have different event
>> delivery requirements.  We MUST explicitly rule all delivery mechanisms
>>as
>> being out of scope.
>>
>>
>>
>> If we define only a data format, we can quickly produce a very useful
>> specification.  If we don=B9t, we=B9ll get bogged down in the mud of
>>debating
>> which applications we=B9re catering to and which we aren=B9t =AD an exer=
cise
>>of
>> picking favorites and limiting applicability of the specification.
>>That way
>> is a slow, painful descent into standards quicksand =AD something we mus=
t
>> avoid.  Having a standard ID events representation is far too important
>>to
>> tie to a particular limited event delivery mechanism.
>>
>>
>>
>>                                                           Sincerely,
>>
>>                                                           -- Mike
>>
>>
>>
>> From: Id-event [mailto:id-event-bounces@ietf.org] On Behalf Of Alan Karp
>> Sent: Thursday, May 5, 2016 9:43 PM
>> To: Morteza Ansari (moransar) <moransar@cisco.com>
>> Cc: id-event@ietf.org
>> Subject: Re: [Id-event] Straw man text for proposed charter
>>
>>
>>
>> I don't see anything about access control for publishing events and
>> subscribing to them.  I also think the spec should allow filters on
>> subscriptions.
>>
>>
>>
>>
>> --------------
>> Alan Karp
>>
>>
>>
>>
>> On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar)
>> <moransar@cisco.com> wrote:
>>
>> Hi folks,
>>
>>
>>
>> At IIW a few of us (Phil, William, Adam, and I) huddled for a bit and
>>put
>> together the attached as a straw man charter proposal to start the
>> discussion. Please send your comments and suggestions for any changes or
>> propose a new one if you think its necessary.
>>
>>
>>
>>
>>
>> Cheers,
>>
>> Morteza
>>
>>
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>>
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>>
>>
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>>
>>
>>
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>
>
>
>--=20
>
>Best regards,
>Kathleen


From nobody Mon Sep 26 18:21:03 2016
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF3012B3B2 for <id-event@ietfa.amsl.com>; Mon, 26 Sep 2016 18:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QhQwyNQvQ4Hb for <id-event@ietfa.amsl.com>; Mon, 26 Sep 2016 18:20:59 -0700 (PDT)
Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B25812B047 for <id-event@ietf.org>; Mon, 26 Sep 2016 18:20:59 -0700 (PDT)
Received: by mail-ua0-x22d.google.com with SMTP id u68so5586360uau.1 for <id-event@ietf.org>; Mon, 26 Sep 2016 18:20:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=QoDzf2MoQ2B2APb1ozXCSg6OPRfXrphjlfCUmlmfsVQ=; b=RvXdS4VBCjy6QygwKUnwa5zvcYzbmU2FINqUJLp5zonuoxt5VbCewGF+KRdvXtX+Lp XvRZYN/M6yGh8LQoDbRD2OuplZa8/RXt7nyzNZmGCq/fAtO/YLXAKnuzf6v+IkYYA0Rz ozFUrsmOhAFN8FNvNAJjVBFVH7zA8dD9aVziBwz7brFMTVNelqPTr8xUSkkaEMcdRMGN WhV7GRhhpCqvVwSCZzwaSyNgLWRP705fXISjeBV+RyXUJf+rRNTUorkV8UmuREc36Nx9 oDducU+8NZSaG9qFSNaIrTasmogxb8scnTrmQPZG3gvmRbaRmKs/osIYeACUBUqU8TOa VtpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=QoDzf2MoQ2B2APb1ozXCSg6OPRfXrphjlfCUmlmfsVQ=; b=JXPib89mA2zFU4n+eojm30tWMLLOdAwMB4oSBgYPjVi2iLtPVOxmH2Xv/VEM7Ijmpq HMzNvwE9GogI2cQD81syuLqxE0AxJhvVxRHrrTuEKo91XZVc8Lqqd1vA72Al4xnZ9QgF Nf5uWvk1TvHWSXwglIO726me1COPMkelHSfBz3dUuh3O7CKXTnyE8Vy3J9FS9OtiGJz9 QUtpdJ+vs2IbSlBo+lppB8/He9kV9/0e4mmFvU7K/P7r2W5Bq22gtT2dIC61pz0cSPsw +TJtIowFCwQLbjvf1rOwyC/4v08aQKbu0icAElxP5S3/L2SmGHEl3g9KLVj33k4Qwy3A YKYg==
X-Gm-Message-State: AA6/9RkGqWZ8ScbBj1Ijch1MZwD45lhhhTyDa/rMB43kifPrx1q40GesW9C7t6ejcPm9Y5jwIsCRHnQB7YvfKQ==
X-Received: by 10.176.6.200 with SMTP id g66mr1094669uag.138.1474939258488; Mon, 26 Sep 2016 18:20:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.65.8 with HTTP; Mon, 26 Sep 2016 18:20:57 -0700 (PDT)
In-Reply-To: <D40EC92D.49B31%moransar@cisco.com>
References: <D350D889.2C7B5%moransar@cisco.com> <CANpA1Z0qPoDWLS6JpPS2pj0HWkvXFN_6i6985_o4xxLgz+MzcQ@mail.gmail.com> <SN1PR0301MB16454DDD82325703ACC961C4F57D0@SN1PR0301MB1645.namprd03.prod.outlook.com> <CANpA1Z01XJ2Lh4zcFcTvjEUwSQZkavJusp2arnq3fYOGx5SHuA@mail.gmail.com> <SN1PR0301MB164585318932F90C48CDDD5CF57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <C1AFFF5B-0873-45AD-9878-92727F8346DA@yahoo.com> <SN1PR0301MB1645DD56619DFBEDB69D6A62F57E0@SN1PR0301MB1645.namprd03.prod.outlook.com> <42194DA6-B018-4879-B472-A180EB131A04@oracle.com> <CAN1PkMaemjgOjPm4Ce4=e0DtYNkXcUcBrWi34uBMyHNTbTezbg@mail.gmail.com> <DM2PR0301MB06372A620DA2352F9FCE1EC0F5F80@DM2PR0301MB0637.namprd03.prod.outlook.com> <CAAP42hD594AXSy1SdBwV-oY==kP2yRdir5kp5QzMsgHoS92rtA@mail.gmail.com> <1474715073.2319843.735650465.3C69F11E@webmail.messagingengine.com> <D03F281C-3051-4E0D-81C8-0F0CC0854A10@cisco.com> <1474718187.2329006.735672633.371888A0@webmail.messagingengine.com> <E6BF4F8B-5176-4BA4-A644-DBEE33619161@oracle.com> <CAHbuEH4uGOUrbn03LxTTgVLy+ErCa-K3b=HvSD8AZYGXLrkPWw@mail.gmail.com> <D40EC92D.49B31%moransar@cisco.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Mon, 26 Sep 2016 21:20:57 -0400
Message-ID: <CAHbuEH4J0_HH0cMBxW-UXUqSFOgDeECxq9LeMmzWqxrtq=oOSQ@mail.gmail.com>
To: "Morteza Ansari (moransar)" <moransar@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/j0YLvEgrRp-Oy9xXKyc0IAKxXQw>
Cc: William Denniss <wdenniss@google.com>, Mike Jones <Michael.Jones@microsoft.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, "id-event@ietf.org" <id-event@ietf.org>, "Phil Hunt \(IDM\)" <phil.hunt@oracle.com>
Subject: Re: [Id-event] Chartering of Security Events WG
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2016 01:21:02 -0000

Hi Morteza,

On Mon, Sep 26, 2016 at 4:21 PM, Morteza Ansari (moransar)
<moransar@cisco.com> wrote:
> Hi Kathleen,
>
> Great idea and hopefully it will get us some fresh blood in the WG for
> contribution and reviews. I can=C2=B9t think of anything else to include =
beyond
> what you suggested. We can do a complete review of the drafts in the work=
s
> in Seoul to catch up any new folks interested in participating (I won=C2=
=B9t be
> there in person, but will join the meeting remotely).
>
> I assume you or Alexey will send the note, but if you want one of us to
> send it just let us know.

I don't mind sending it, but will wait to chat with Alexey first so we
are all coordinated.  Hopefully it will bring some new interest.

Thanks,
Kathleen

>
>
> Cheers,
> Morteza
>
> On 9/26/16, 6:44 AM, "Kathleen Moriarty"
> <kathleen.moriarty.ietf@gmail.com> wrote:
>
>>Hi,
>>
>>It would be good to get a mail message to the SAAG list to announce
>>this, that it crosses areas and that I'll be the AD along with the
>>charter and other information.  Is there any other information that
>>should be in such an announcement?
>>
>>Thanks,
>>Kathleen
>>
>>On Sat, Sep 24, 2016 at 11:56 AM, Phil Hunt (IDM) <phil.hunt@oracle.com>
>>wrote:
>>> Alexy,
>>>
>>> Thanks for helping this forwards.
>>>
>>> The name is fine.
>>>
>>> Phil
>>>
>>> On Sep 24, 2016, at 4:56 AM, Alexey Melnikov <aamelnikov@fastmail.fm>
>>>wrote:
>>>
>>> This also reminded me: how much time does this group want to request fo=
r
>>> face-to-face meeting in Seoul?
>>>
>>> On Sat, Sep 24, 2016, at 12:27 PM, Morteza Ansari (moransar) wrote:
>>>
>>> This is great, thanks for helping speed up the process! Name is a name,
>>>so
>>> no comment on naming.
>>>
>>>
>>>
>>> Cheers,
>>> Morteza
>>>
>>> On Sep 24, 2016, at 4:04 AM, Alexey Melnikov <aamelnikov@fastmail.fm>
>>>wrote:
>>>
>>> Hi,
>>> Just to let everyone know: I started chartering of the WG. The WG will
>>>be in
>>> the Security Area (it was a borderline between ART and Security) and
>>>your
>>> responsible AD is going to be Kathleen Moriarty.
>>>
>>> Best Regards,
>>> Alexey
>>>
>>> P.S. I picked "SECEVENT" as the short WG name, but if you have better
>>> suggestions, please let me know.
>>>
>>> On Wed, Sep 7, 2016, at 01:04 AM, William Denniss wrote:
>>>
>>> Thank you Mike for revising the charter.
>>>
>>> I support it, and hope we can form a WG with this charter to continue
>>>our
>>> work.
>>>
>>> On Tue, Sep 6, 2016 at 5:01 PM, Mike Jones <Michael.Jones@microsoft.com=
>
>>> wrote:
>>>
>>> An updated and simplified charter is attached.  This draft has been
>>>reviewed
>>> by Phil Hunt, William Denniss, Marius Scurtescu.
>>>
>>>
>>>
>>> Input from Alexey Melnikov is that we should probably charter a working
>>> group, rather than try to go the AD-sponsored route.  Therefore, please
>>> review this draft charter and let us know if you think it=C2=B9s ready =
to go.
>>>
>>>
>>>
>>>                                                        Thanks,
>>>
>>>                                                        -- Mike
>>>
>>>
>>>
>>>
>>> From: Sarah Squire [mailto:sarah@engageidentity.com]
>>> Sent: Thursday, July 14, 2016 10:59 PM
>>> To: Phil Hunt (IDM) <phil.hunt@oracle.com>
>>> Cc: Mike Jones <Michael.Jones@microsoft.com>; Alan Karp
>>> <alanhkarp@gmail.com>; Vivek Biswas <vivek_biswas@yahoo.com>; Morteza
>>>Ansari
>>> (moransar) <moransar@cisco.com>; id-event@ietf.org
>>>
>>>
>>> Subject: Re: [Id-event] Straw man text for proposed charter
>>>
>>>
>>>
>>>
>>> Just submitting my two cents in writing before we hopefully have a
>>>chance to
>>> meet about this next week...
>>>
>>>
>>>
>>> Looking at this charter from the perspective of the OIDF HEART working
>>> group, I think it's going down a good path. In terms of the data format=
,
>>> this is less structured than what I was envisioning, but we could
>>>easily do
>>> a healthcare-specific profile of whatever data format comes out in the
>>>end,
>>> so it's better to be too broad than too narrow as far as our interests
>>>are
>>> concerned.
>>>
>>>
>>>
>>> The transport layer however, has some added complexity. In our context,
>>> we're shooting for interoperability, so we'd prefer something
>>>constrained. I
>>> appreciate Mike's input that these are application layer decisions.
>>>However,
>>> if we're talking about cloud provider-to-cloud provider communication,
>>>that
>>> certainly is facilitated by a well-defined transport layer. Again, we'r=
e
>>> willing to profile whatever the group comes up with for our own ends,
>>>but I
>>> don't really see the benefit of having a loosely defined transport
>>>layer -
>>> it just seems like more work for all the implementers to actually agree
>>>on
>>> endpoints on a case-by-case basis.
>>>
>>>
>>>
>>> Looking forward to discussing further in Berlin!
>>>
>>>
>>>
>>> Sarah
>>>
>>>
>>> Sarah Squire
>>>
>>> Engage Identity
>>>
>>> http://engageidentity.com
>>>
>>>
>>>
>>> On Sat, May 7, 2016 at 6:53 PM, Phil Hunt (IDM) <phil.hunt@oracle.com>
>>> wrote:
>>>
>>> We also set things up so even a domain specific event can be extended.
>>>
>>>
>>>
>>> Eg on a password reset event, so event publishers may want to add
>>>security
>>> domain specific attributes. The spec lets them do that while avoiding
>>> interop issues.
>>>
>>>
>>>
>>> I believe in the spec we had the example of an account reset and the
>>> publisher adds reset count as an extension.
>>>
>>> Phil
>>>
>>>
>>>
>>> On May 7, 2016, at 13:31, Mike Jones <Michael.Jones@microsoft.com>
>>>wrote:
>>>
>>>
>>> Indeed, that=C2=B9s why there=C2=B9s a claims registry =C2=AD so common=
 claims can be
>>> defined once and then reused.
>>>
>>>
>>>
>>>
>>> From: Vivek Biswas
>>> Sent: Saturday, May 7, 2016 1:24 PM
>>> To: Mike Jones
>>> Cc: Alan Karp; Morteza Ansari (moransar); id-event@ietf.org
>>> Subject: Re: [Id-event] Straw man text for proposed charter
>>>
>>>
>>>
>>>
>>> Yes, I agree that the claims can be application specific, however there
>>>is a
>>> possibility to define claims which are domain specific. Thereby claims
>>> generated in one application could be understood by another  applicatio=
n
>>> within the same domain.
>>>
>>>
>>>
>>> With microservices based architecture getting lot of attention, if two
>>> different micro services defining different claims for the same claim,
>>>it
>>> can create confusion.
>>>
>>>
>>>
>>> Nevertheless this well defined claims for a particular domain can be an
>>> extension to the core specification.
>>>
>>>
>>>
>>> -Vivek Biswas
>>>
>>>
>>>   Consulting Member, Oracle
>>>
>>> Sent from my iPhone
>>>
>>>
>>>
>>>
>>> On May 7, 2016, at 1:04 PM, Mike Jones <Michael.Jones@microsoft.com>
>>>wrote:
>>>
>>>
>>> Thanks Alan,
>>>
>>>
>>>
>>> Interoperability will be on a per-application basis, just like JWT
>>> interoperability.  The claims needed in an identity event are
>>> application-specific, just like claims are for JWTs.  This is the same
>>> standards posture and JWTs are a huge success =C2=AD including for
>>> interoperability, even if I do say so myself.
>>>
>>>
>>>
>>>                                                           Best wishes,
>>>
>>>                                                           -- Mike
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> From: Alan Karp
>>> Sent: Saturday, May 7, 2016 10:23 AM
>>> To: Mike Jones
>>> Cc: Morteza Ansari (moransar); id-event@ietf.org
>>> Subject: Re: [Id-event] Straw man text for proposed charter
>>>
>>>
>>>
>>>
>>> As one who proposed doing more, I believe that your position is valid.
>>>My
>>> only question is whether or not that will be enough for
>>>interoperability.
>>>
>>>
>>>
>>>
>>> --------------
>>> Alan Karp
>>>
>>>
>>>
>>>
>>> On Thu, May 5, 2016 at 10:00 PM, Mike Jones
>>><Michael.Jones@microsoft.com>
>>> wrote:
>>>
>>> Thanks guys, for writing the initial charter text.  Reading it now, I a=
m
>>> extremely worried by the scope creep evident in the proposal.
>>>
>>>
>>>
>>> I strongly support a working group to define an ID Events data format.
>>>I
>>> just as strongly believe that specific event delivery mechanisms will
>>> necessarily be application-specific and therefore MUST be explicitly be
>>> stated as being out of scope in the working group charter.  Attempting
>>>to
>>> specify a particular event delivery mechanism will take something that
>>>could
>>> be simple and quick to approve and bog it down in necessarily
>>> application-specific debates.
>>>
>>>
>>>
>>> Should event delivery be reliable?  That=C2=B9s an application-specific
>>>decision.
>>>
>>> Should events be idempotent?  That=C2=B9s an application-specific decis=
ion.
>>>
>>> Should events be unicast, multicast, or broadcast?  That=C2=B9s an
>>> application-specific decision.
>>>
>>> Should events have categories with category-specific subscriptions?
>>>That=C2=B9s
>>> an application-specific decision.
>>>
>>> Should only one party at a time be able to register for delivery of
>>>events
>>> or should multiple parties be able to request delivery?  That=C2=B9s an
>>> application-specific decision.
>>>
>>> I could continue with this list, but I think you all get the point=C5=
=A0
>>>
>>>
>>>
>>> If we start debating application-specific event delivery mechanisms,
>>>we=C2=B9ll
>>> please almost no one, since nearly all applications have different even=
t
>>> delivery requirements.  We MUST explicitly rule all delivery mechanisms
>>>as
>>> being out of scope.
>>>
>>>
>>>
>>> If we define only a data format, we can quickly produce a very useful
>>> specification.  If we don=C2=B9t, we=C2=B9ll get bogged down in the mud=
 of
>>>debating
>>> which applications we=C2=B9re catering to and which we aren=C2=B9t =C2=
=AD an exercise
>>>of
>>> picking favorites and limiting applicability of the specification.
>>>That way
>>> is a slow, painful descent into standards quicksand =C2=AD something we=
 must
>>> avoid.  Having a standard ID events representation is far too important
>>>to
>>> tie to a particular limited event delivery mechanism.
>>>
>>>
>>>
>>>                                                           Sincerely,
>>>
>>>                                                           -- Mike
>>>
>>>
>>>
>>> From: Id-event [mailto:id-event-bounces@ietf.org] On Behalf Of Alan Kar=
p
>>> Sent: Thursday, May 5, 2016 9:43 PM
>>> To: Morteza Ansari (moransar) <moransar@cisco.com>
>>> Cc: id-event@ietf.org
>>> Subject: Re: [Id-event] Straw man text for proposed charter
>>>
>>>
>>>
>>> I don't see anything about access control for publishing events and
>>> subscribing to them.  I also think the spec should allow filters on
>>> subscriptions.
>>>
>>>
>>>
>>>
>>> --------------
>>> Alan Karp
>>>
>>>
>>>
>>>
>>> On Thu, May 5, 2016 at 11:18 AM, Morteza Ansari (moransar)
>>> <moransar@cisco.com> wrote:
>>>
>>> Hi folks,
>>>
>>>
>>>
>>> At IIW a few of us (Phil, William, Adam, and I) huddled for a bit and
>>>put
>>> together the attached as a straw man charter proposal to start the
>>> discussion. Please send your comments and suggestions for any changes o=
r
>>> propose a new one if you think its necessary.
>>>
>>>
>>>
>>>
>>>
>>> Cheers,
>>>
>>> Morteza
>>>
>>>
>>>
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
>>>
>>>
>>>
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
>>>
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
>>
>>
>>
>>--
>>
>>Best regards,
>>Kathleen
>



--=20

Best regards,
Kathleen


From nobody Tue Sep 27 09:56:27 2016
Return-Path: <alissa@cooperw.in>
X-Original-To: id-event@ietf.org
Delivered-To: id-event@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5618E12B0CE; Tue, 27 Sep 2016 09:56:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alissa Cooper" <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147499538530.4539.17647914860327036397.idtracker@ietfa.amsl.com>
Date: Tue, 27 Sep 2016 09:56:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/4D223MJIWK2r6Dmw-pMLDKZtsC8>
Cc: secevent-chairs@ietf.org, id-event@ietf.org
Subject: [Id-event] Alissa Cooper's No Objection on charter-ietf-secevent-00-00: (with COMMENT)
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2016 16:56:25 -0000

Alissa Cooper has entered the following ballot position for
charter-ietf-secevent-00-00: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-secevent/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I think this charter is missing a note about other WGs or groups that it
is going to coordinate with.



From nobody Tue Sep 27 13:56:34 2016
Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
X-Original-To: id-event@ietf.org
Delivered-To: id-event@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 24D27127076; Tue, 27 Sep 2016 13:56:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147500979310.11691.18383160173083918592.idtracker@ietfa.amsl.com>
Date: Tue, 27 Sep 2016 13:56:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/qDCslnQdX4btytyhXeIpb1xcU1Q>
Cc: secevent-chairs@ietf.org, id-event@ietf.org
Subject: [Id-event] Kathleen Moriarty's No Objection on charter-ietf-secevent-00-00: (with COMMENT)
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2016 20:56:33 -0000

Kathleen Moriarty has entered the following ballot position for
charter-ietf-secevent-00-00: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-secevent/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Shouldn't the method for delivering the event be a secure method?



From nobody Tue Sep 27 14:42:03 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5C1D12B290; Tue, 27 Sep 2016 14:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S8U-FPPi71rh; Tue, 27 Sep 2016 14:41:54 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E19C012B268; Tue, 27 Sep 2016 14:41:53 -0700 (PDT)
Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8RLfpQO007002 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 27 Sep 2016 21:41:52 GMT
Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0022.oracle.com (8.14.4/8.13.8) with ESMTP id u8RLfpsp028978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 27 Sep 2016 21:41:51 GMT
Received: from abhmp0011.oracle.com (abhmp0011.oracle.com [141.146.116.17]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u8RLfpZv025938; Tue, 27 Sep 2016 21:41:51 GMT
Received: from [25.91.185.169] (/72.143.227.70) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 27 Sep 2016 14:41:50 -0700
Content-Type: multipart/alternative; boundary=Apple-Mail-18D20F0D-4630-44D8-A615-DB6A9AEFC5EB
Mime-Version: 1.0 (1.0)
From: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
X-Mailer: iPhone Mail (14A403)
In-Reply-To: <147500979310.11691.18383160173083918592.idtracker@ietfa.amsl.com>
Date: Tue, 27 Sep 2016 14:41:43 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <6289BB24-733D-4BFA-A19C-C445FAF71AE8@oracle.com>
References: <147500979310.11691.18383160173083918592.idtracker@ietfa.amsl.com>
To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
X-Source-IP: userv0022.oracle.com [156.151.31.74]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/ZcbXAEsV0wCUSlZMTRYr2kGhPgo>
Cc: secevent-chairs@ietf.org, The IESG <iesg@ietf.org>, id-event@ietf.org
Subject: Re: [Id-event] Kathleen Moriarty's No Objection on charter-ietf-secevent-00-00: (with COMMENT)
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2016 21:41:56 -0000

--Apple-Mail-18D20F0D-4630-44D8-A615-DB6A9AEFC5EB
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

No objections to adding that in the charter. However SETs could be delivered=
 through open channels using JWE.=20

At minimum we should have security considerations stating the requirements.=20=


Phil

> On Sep 27, 2016, at 1:56 PM, Kathleen Moriarty <Kathleen.Moriarty.ietf@gma=
il.com> wrote:
>=20
> Kathleen Moriarty has entered the following ballot position for
> charter-ietf-secevent-00-00: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>=20
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-secevent/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> Shouldn't the method for delivering the event be a secure method?
>=20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event

--Apple-Mail-18D20F0D-4630-44D8-A615-DB6A9AEFC5EB
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><div style=3D"direction: inherit;">No o=
bjections to adding that in the charter. However SETs could be delivered thr=
ough open channels using JWE.&nbsp;</div><div style=3D"direction: inherit;">=
<br></div><div style=3D"direction: inherit;">At minimum we should have secur=
ity considerations stating the requirements.&nbsp;</div><br>Phil</div><div><=
br>On Sep 27, 2016, at 1:56 PM, Kathleen Moriarty &lt;<a href=3D"mailto:Kath=
leen.Moriarty.ietf@gmail.com">Kathleen.Moriarty.ietf@gmail.com</a>&gt; wrote=
:<br><br></div><blockquote type=3D"cite"><div><span>Kathleen Moriarty has en=
tered the following ballot position for</span><br><span>charter-ietf-seceven=
t-00-00: No Objection</span><br><span></span><br><span>When responding, plea=
se keep the subject line intact and reply to all</span><br><span>email addre=
sses included in the To and CC lines. (Feel free to cut this</span><br><span=
>introductory paragraph, however.)</span><br><span></span><br><span></span><=
br><span></span><br><span>The document, along with other ballot positions, c=
an be found here:</span><br><span><a href=3D"https://datatracker.ietf.org/do=
c/charter-ietf-secevent/">https://datatracker.ietf.org/doc/charter-ietf-sece=
vent/</a></span><br><span></span><br><span></span><br><span></span><br><span=
>----------------------------------------------------------------------</spa=
n><br><span>COMMENT:</span><br><span>---------------------------------------=
-------------------------------</span><br><span></span><br><span>Shouldn't t=
he method for delivering the event be a secure method?</span><br><span></spa=
n><br><span></span><br><span>_______________________________________________=
</span><br><span>Id-event mailing list</span><br><span><a href=3D"mailto:Id-=
event@ietf.org">Id-event@ietf.org</a></span><br><span><a href=3D"https://www=
.ietf.org/mailman/listinfo/id-event">https://www.ietf.org/mailman/listinfo/i=
d-event</a></span><br></div></blockquote></body></html>=

--Apple-Mail-18D20F0D-4630-44D8-A615-DB6A9AEFC5EB--


From nobody Tue Sep 27 16:22:53 2016
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: id-event@ietf.org
Delivered-To: id-event@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 44A4312B524; Tue, 27 Sep 2016 16:22:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147501856979.11715.9173343529334358981.idtracker@ietfa.amsl.com>
Date: Tue, 27 Sep 2016 16:22:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/fJHn9ev8VSpLdX7Hl1I3PvCmfbQ>
Cc: secevent-chairs@ietf.org, id-event@ietf.org
Subject: [Id-event] Spencer Dawkins' No Objection on charter-ietf-secevent-00-00: (with COMMENT)
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2016 23:22:50 -0000

Spencer Dawkins has entered the following ballot position for
charter-ietf-secevent-00-00: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-secevent/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I have the same question Kathleen asked (so I'll watch the discussion in
that thread).



From nobody Tue Sep 27 17:43:25 2016
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B55A612B38F; Tue, 27 Sep 2016 17:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a_bAQd0lTxXJ; Tue, 27 Sep 2016 17:43:16 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA8D812B008; Tue, 27 Sep 2016 17:43:15 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id 38so15693548qte.1; Tue, 27 Sep 2016 17:43:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+cZxOApFKE0/dVSxGgLDfwh1ncPA56ZS3U31N3Z2v1Y=; b=g3b1YyckbYI7Ruu8H+4QYzPD6rQiuaY1+X09SlaYUgIF3W9CQI0weVjelgjg06y/Q1 7nVekUGNNGl07IftEqZ94Ijyfz4xBx1z29lWk3dCOwBN+546qEEfZUUmlhSJi6euXIoc 3G211CiD2pa1jeUvqp5yElJcD+H6P/vb+a1+QM3t3gC0PArfSka/ioOtlYqNxuRKTlOx UrKZI5w/lPhxQwguve5OUeevfwhs7YtuXnJ8miwouxI62YhNsUAsI+k3Al6P0JmkH/G7 asAHjofIVYGKtizCxF7aEDm55PiAU3MHgnCPsBikz8HkqucEp+XGcXiNMCqq0j1RPwjd XKMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+cZxOApFKE0/dVSxGgLDfwh1ncPA56ZS3U31N3Z2v1Y=; b=LJ+vSANIBaHTj6QJ9680KzHsf1tLQmX9GHAjUYqzQRIypa92Qu8oB5Yskn0Vx8V1qN RB2iSharype5o8KOENWi0rReFHu7bG9d1Pb/8tYaa/pE3D4Ccgt/PDoSiMtFiZ2qBW3N D7S4hJyP9Gym5GABfRzBVtTpPku7+/YReSpzMxVTUP86Bi99NNyomX3TvKNChOlU4P+w GW8Rfu4AECE8D21jIF28b3aJ2DbGNtjFskwVIeqJwGUvi0wGBIpwQ4xg/VWxuXWUnOjP cPZA1wELE2MZS9PuFaefGE1oYxxpQySZxXG6kNZBMiBObbExAaT57FmzMooHMsavJ13g 0BOg==
X-Gm-Message-State: AA6/9Rku8XGnHlM7bmaGv6Gcc8ralReOqWaZ9exBktZap38QL+xg2x7t/QOm4K3wplOnxA==
X-Received: by 10.237.33.111 with SMTP id 102mr30833131qtc.56.1475023395114; Tue, 27 Sep 2016 17:43:15 -0700 (PDT)
Received: from [192.168.1.8] (209-6-124-204.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.124.204]) by smtp.gmail.com with ESMTPSA id f76sm2643043qke.37.2016.09.27.17.43.14 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 27 Sep 2016 17:43:14 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-AA225A13-F8AE-4509-9D63-5B02B75CF52A
Mime-Version: 1.0 (1.0)
From: kathleen.moriarty.ietf@gmail.com
X-Mailer: iPhone Mail (13G36)
In-Reply-To: <6289BB24-733D-4BFA-A19C-C445FAF71AE8@oracle.com>
Date: Tue, 27 Sep 2016 20:43:14 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <DBA7B4C8-E423-4C25-A2FA-F919ADE4A86D@gmail.com>
References: <147500979310.11691.18383160173083918592.idtracker@ietfa.amsl.com> <6289BB24-733D-4BFA-A19C-C445FAF71AE8@oracle.com>
To: "Phil Hunt (IDM)" <phil.hunt@oracle.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/Y0VT4I5a5kwWTFYf7ndaA45UFJc>
Cc: secevent-chairs@ietf.org, The IESG <iesg@ietf.org>, id-event@ietf.org
Subject: Re: [Id-event] Kathleen Moriarty's No Objection on charter-ietf-secevent-00-00: (with COMMENT)
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2016 00:43:19 -0000

--Apple-Mail-AA225A13-F8AE-4509-9D63-5B02B75CF52A
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi Phil,

Please excuse typos, sent from handheld device=20

> On Sep 27, 2016, at 5:41 PM, Phil Hunt (IDM) <phil.hunt@oracle.com> wrote:=

>=20
> No objections to adding that in the charter. However SETs could be deliver=
ed through open channels using JWE.=20
>=20
> At minimum we should have security considerations stating the requirements=
.=20

Yes, I'm not interested to see it specified in the charter, just to somehow s=
ay a secure method would be used.

Thanks,
Kathleen=20
>=20
> Phil
>=20
>> On Sep 27, 2016, at 1:56 PM, Kathleen Moriarty <Kathleen.Moriarty.ietf@gm=
ail.com> wrote:
>>=20
>> Kathleen Moriarty has entered the following ballot position for
>> charter-ietf-secevent-00-00: No Objection
>>=20
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>=20
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/charter-ietf-secevent/
>>=20
>>=20
>>=20
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>=20
>> Shouldn't the method for delivering the event be a secure method?
>>=20
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event

--Apple-Mail-AA225A13-F8AE-4509-9D63-5B02B75CF52A
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Hi Phil,<br><br>Please excuse typos, s=
ent from handheld device&nbsp;</div><div><br>On Sep 27, 2016, at 5:41 PM, Ph=
il Hunt (IDM) &lt;<a href=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.c=
om</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><meta http-equ=
iv=3D"content-type" content=3D"text/html; charset=3Dutf-8"><div><div style=3D=
"direction: inherit;">No objections to adding that in the charter. However S=
ETs could be delivered through open channels using JWE.&nbsp;</div><div styl=
e=3D"direction: inherit;"><br></div><div style=3D"direction: inherit;">At mi=
nimum we should have security considerations stating the requirements.&nbsp;=
</div></div></div></blockquote><div><br></div>Yes, I'm not interested to see=
 it specified in the charter, just to somehow say a secure method would be u=
sed.<div><br></div><div>Thanks,</div><div>Kathleen&nbsp;<br><blockquote type=
=3D"cite"><div><div><br>Phil</div><div><br>On Sep 27, 2016, at 1:56 PM, Kath=
leen Moriarty &lt;<a href=3D"mailto:Kathleen.Moriarty.ietf@gmail.com">Kathle=
en.Moriarty.ietf@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"c=
ite"><div><span>Kathleen Moriarty has entered the following ballot position f=
or</span><br><span>charter-ietf-secevent-00-00: No Objection</span><br><span=
></span><br><span>When responding, please keep the subject line intact and r=
eply to all</span><br><span>email addresses included in the To and CC lines.=
 (Feel free to cut this</span><br><span>introductory paragraph, however.)</s=
pan><br><span></span><br><span></span><br><span></span><br><span>The documen=
t, along with other ballot positions, can be found here:</span><br><span><a h=
ref=3D"https://datatracker.ietf.org/doc/charter-ietf-secevent/">https://data=
tracker.ietf.org/doc/charter-ietf-secevent/</a></span><br><span></span><br><=
span></span><br><span></span><br><span>-------------------------------------=
---------------------------------</span><br><span>COMMENT:</span><br><span>-=
---------------------------------------------------------------------</span>=
<br><span></span><br><span>Shouldn't the method for delivering the event be a=
 secure method?</span><br><span></span><br><span></span><br><span>__________=
_____________________________________</span><br><span>Id-event mailing list<=
/span><br><span><a href=3D"mailto:Id-event@ietf.org">Id-event@ietf.org</a></=
span><br><span><a href=3D"https://www.ietf.org/mailman/listinfo/id-event">ht=
tps://www.ietf.org/mailman/listinfo/id-event</a></span><br></div></blockquot=
e></div></blockquote></div></body></html>=

--Apple-Mail-AA225A13-F8AE-4509-9D63-5B02B75CF52A--


From nobody Wed Sep 28 05:31:57 2016
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA72212B113 for <id-event@ietfa.amsl.com>; Wed, 28 Sep 2016 05:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=RMTo0+T2; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=B54lPwZu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QBDEmEl41vA3 for <id-event@ietfa.amsl.com>; Wed, 28 Sep 2016 05:31:51 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5B6712B124 for <id-event@ietf.org>; Wed, 28 Sep 2016 05:31:28 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 1791120880 for <id-event@ietf.org>; Wed, 28 Sep 2016 08:31:28 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute4.internal (MEProxy); Wed, 28 Sep 2016 08:31:28 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=vFG r9tpnniepy6lRM9AkBfC1dpg=; b=RMTo0+T2x2yKAqWv9uSTRvkVC/Ep24V1yJN fV+9tI3ZVAu8Q4jEk0y0+CJKTgbK6CNeh+XoxXLbDcApapWQzZ+gcikK6OVT+TX5 msvsb8SYVI1b8e1pz0zi0K5HFYvFd9g/mVOSm0xGsPRK07SJqNGKocAk36xIbslk JfOLEL+8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=vFGr9tpnniepy6lRM9AkBfC1dpg=; b=B54lP wZubAsYgwqwc3YYIfLPKvI0rV4Zl29N6dmTZUL3wUhPiArJRkvR0/89KDnasvUsX 8TUGC29oRCfS4UoV4kU5NRHEWnWD+CzNl7C0e5SQ7hKjSlZyLCbMe/Pm7a6B6bym IneWCJPD3IkSYmTc1dNHHER39Yfi69qWDVSu1s=
Received: by mailuser.nyi.internal (Postfix, from userid 99) id E8FD197146; Wed, 28 Sep 2016 08:31:27 -0400 (EDT)
Message-Id: <1475065887.1936753.739580601.5C36D6AC@webmail.messagingengine.com>
X-Sasl-Enc: +XM7X6p1/N5eVEqkG3NxI56Nodu4aRROcRpR41pWaLTx 1475065887
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: id-event@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-3ce3fca2
Date: Wed, 28 Sep 2016 13:31:27 +0100
X-Forwarded-Message-Id: <CA1C13E6-ADCA-4E34-95C3-C8392183376B@juniper.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/hFvyFmji8or_i_GPyy6eeJwLGm4>
Subject: [Id-event] Fwd: Re: [saag] SecEvent Charter
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2016 12:31:55 -0000

Does anybody have an answer on this? Was netconf considered?
Is there shipping code for drafts in scope for SecEvent?

----- Original message -----
From: Kent Watsen <kwatsen@juniper.net>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>,
"saag@ietf.org" <saag@ietf.org>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Re: [saag] SecEvent Charter
Date: Wed, 28 Sep 2016 00:38:44 +0000


Did anyone consider the overlap between this and event notifications
effort in the NETCONF working group?

  draft-ietf-netconf-rfc5277bis
  draft-ietf-netconf-netconf-event-notifications
  draft-ietf-netconf-restconf-notif
  draft-ietf-netconf-yang-push

It may not have the same focus, but it can get the job done, right?

Thanks,
Kent


On 9/27/16, 5:00 PM, "saag on behalf of Kathleen Moriarty"
<saag-bounces@ietf.org on behalf of kathleen.moriarty.ietf@gmail.com>
wrote:

    Hello,
    
    A new working group has been proposed, SecEvent, that crosses
    between
    the ART and security areas.  This builds off of SCIM work, also
    leveraging OAuth, and will incorporate use of JWT from JOSE.  The
    working group, if approved, will go into the security area and I've
    agreed to AD it.  Please take a look at the charter under review:
    
    https://datatracker.ietf.org/doc/charter-ietf-secevent/
    
    And join the mailing list for discussion:
    https://mailarchive.ietf.org/arch/search/?email_list=id-event
    
    -- 
    
    Best regards,
    Kathleen
    
    _______________________________________________
    saag mailing list
    saag@ietf.org
    https://www.ietf.org/mailman/listinfo/saag
    


From nobody Thu Sep 29 09:54:44 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E0E012B114 for <id-event@ietfa.amsl.com>; Thu, 29 Sep 2016 09:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.517
X-Spam-Level: 
X-Spam-Status: No, score=-6.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YxpAr6qdB9xD for <id-event@ietfa.amsl.com>; Thu, 29 Sep 2016 09:54:40 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A81912B1A5 for <id-event@ietf.org>; Thu, 29 Sep 2016 09:54:40 -0700 (PDT)
Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8TGsa2J029633 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 29 Sep 2016 16:54:37 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id u8TGsa78019470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 29 Sep 2016 16:54:36 GMT
Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u8TGsXGf013021; Thu, 29 Sep 2016 16:54:35 GMT
Received: from [10.0.1.5] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 29 Sep 2016 09:54:33 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_8993BEA1-CB14-4FAE-9B25-251368B9C025"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Phil Hunt <phil.hunt@oracle.com>
In-Reply-To: <1475065887.1936753.739580601.5C36D6AC@webmail.messagingengine.com>
Date: Thu, 29 Sep 2016 09:54:32 -0700
Message-Id: <7579D533-3DC6-487F-9AC1-7BA079DE4B8C@oracle.com>
References: <1475065887.1936753.739580601.5C36D6AC@webmail.messagingengine.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0022.oracle.com [141.146.126.234]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/9_1MM86AtqDfXOsI4C3seApANB8>
Cc: id-event@ietf.org
Subject: Re: [Id-event] Fwd: Re: [saag] SecEvent Charter
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2016 16:54:42 -0000

--Apple-Mail=_8993BEA1-CB14-4FAE-9B25-251368B9C025
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Alexey,

Great question. There are certainly some overlap in requirements and =
goals around subscription management.

Regarding Implementation,
The SET Event work so far is a profile of the JWT (RFC7519) for secure =
event tokens and SCIM (RFC7643/7644) for subscription management so that =
we can build on existing implementations and stacks for rapid adoption.  =
We have proposed a very simple HTTP POST over TLS for delivery. The key =
profiling aspect of HTTP POST is to require the subscriber must not =
respond with acceptance (e.g. HTTP Status 202) unless the receiver was =
able to validate the message.

The OpenID Connect and RISC working groups have been putting events into =
test and are feeding back into the specs directly.  Connect=E2=80=99s =
Logout spec has already re-aligned with the SET token.

Regarding NETCONF,=20
The community of participants (SCIM, OAuth, RISC, Connect, HEART, =E2=80=A6=
) are largely focused on co-ordinating events between HTTPS based =
systems and endpoints using mostly JSON centric payloads.=20

In contrast, my perception of NETCONF is it is working at a lower layer =
(network devices) and as such supports transmission using SSH (which is =
MTI) with largely XML structured data.  The current NETCONF MTI =
requirements would not be workable.

My perception of intent by most participants is to establish a =
contextual web of pub/sub relationships rather than message bus. So, =
there may not be much to be gained from aligning with NETCONF since the =
network configuration components are kept distant from the application =
security components. =20

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>





> On Sep 28, 2016, at 5:31 AM, Alexey Melnikov <aamelnikov@fastmail.fm> =
wrote:
>=20
> Does anybody have an answer on this? Was netconf considered?
> Is there shipping code for drafts in scope for SecEvent?
>=20
> ----- Original message -----
> From: Kent Watsen <kwatsen@juniper.net>
> To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>,
> "saag@ietf.org" <saag@ietf.org>
> Cc: Alexey Melnikov <aamelnikov@fastmail.fm>
> Subject: Re: [saag] SecEvent Charter
> Date: Wed, 28 Sep 2016 00:38:44 +0000
>=20
>=20
> Did anyone consider the overlap between this and event notifications
> effort in the NETCONF working group?
>=20
>  draft-ietf-netconf-rfc5277bis
>  draft-ietf-netconf-netconf-event-notifications
>  draft-ietf-netconf-restconf-notif
>  draft-ietf-netconf-yang-push
>=20
> It may not have the same focus, but it can get the job done, right?
>=20
> Thanks,
> Kent
>=20
>=20
> On 9/27/16, 5:00 PM, "saag on behalf of Kathleen Moriarty"
> <saag-bounces@ietf.org on behalf of kathleen.moriarty.ietf@gmail.com>
> wrote:
>=20
>    Hello,
>=20
>    A new working group has been proposed, SecEvent, that crosses
>    between
>    the ART and security areas.  This builds off of SCIM work, also
>    leveraging OAuth, and will incorporate use of JWT from JOSE.  The
>    working group, if approved, will go into the security area and I've
>    agreed to AD it.  Please take a look at the charter under review:
>=20
>    https://datatracker.ietf.org/doc/charter-ietf-secevent/
>=20
>    And join the mailing list for discussion:
>    https://mailarchive.ietf.org/arch/search/?email_list=3Did-event
>=20
>    --=20
>=20
>    Best regards,
>    Kathleen
>=20
>    _______________________________________________
>    saag mailing list
>    saag@ietf.org
>    https://www.ietf.org/mailman/listinfo/saag
>=20
>=20
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event


--Apple-Mail=_8993BEA1-CB14-4FAE-9B25-251368B9C025
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Alexey,<div class=3D""><br class=3D""></div><div =
class=3D"">Great question. There are certainly some overlap in =
requirements and goals around subscription management.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Regarding =
Implementation,</div><div class=3D"">The SET Event work so far is a =
profile of the JWT (RFC7519) for secure event tokens and SCIM =
(RFC7643/7644) for subscription management so that we can build on =
existing implementations and stacks for rapid adoption. &nbsp;We have =
proposed a very simple HTTP POST over TLS for delivery. The key =
profiling aspect of HTTP POST is to require the subscriber must not =
respond with acceptance (e.g. HTTP Status 202) unless the receiver was =
able to validate the message.</div><div class=3D""><br =
class=3D""></div><div class=3D"">The OpenID Connect and RISC working =
groups have been putting events into test and are feeding back into the =
specs directly. &nbsp;Connect=E2=80=99s Logout spec has already =
re-aligned with the SET token.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Regarding NETCONF,&nbsp;</div><div =
class=3D"">The community of participants (SCIM, OAuth, RISC, Connect, =
HEART, =E2=80=A6) are largely focused on co-ordinating events between =
HTTPS based systems and endpoints using mostly JSON centric =
payloads.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">In contrast, my perception of NETCONF is it is working at a =
lower layer (network devices) and as such supports transmission using =
SSH (which is MTI) with largely XML structured data. &nbsp;The current =
NETCONF MTI requirements would not be workable.</div><div class=3D""><br =
class=3D""></div><div class=3D"">My perception of intent by most =
participants is to establish a contextual web of pub/sub relationships =
rather than message bus. So, there may not be much to be gained from =
aligning with NETCONF since the network configuration components are =
kept distant from the application security components. &nbsp;</div><div =
class=3D""><br class=3D""></div><div class=3D""><div class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Sep 28, 2016, at 5:31 AM, Alexey Melnikov &lt;<a =
href=3D"mailto:aamelnikov@fastmail.fm" =
class=3D"">aamelnikov@fastmail.fm</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Does =
anybody have an answer on this? Was netconf considered?<br class=3D"">Is =
there shipping code for drafts in scope for SecEvent?<br class=3D""><br =
class=3D"">----- Original message -----<br class=3D"">From: Kent Watsen =
&lt;<a href=3D"mailto:kwatsen@juniper.net" =
class=3D"">kwatsen@juniper.net</a>&gt;<br class=3D"">To: Kathleen =
Moriarty &lt;<a href=3D"mailto:kathleen.moriarty.ietf@gmail.com" =
class=3D"">kathleen.moriarty.ietf@gmail.com</a>&gt;,<br class=3D"">"<a =
href=3D"mailto:saag@ietf.org" class=3D"">saag@ietf.org</a>" &lt;<a =
href=3D"mailto:saag@ietf.org" class=3D"">saag@ietf.org</a>&gt;<br =
class=3D"">Cc: Alexey Melnikov &lt;<a =
href=3D"mailto:aamelnikov@fastmail.fm" =
class=3D"">aamelnikov@fastmail.fm</a>&gt;<br class=3D"">Subject: Re: =
[saag] SecEvent Charter<br class=3D"">Date: Wed, 28 Sep 2016 00:38:44 =
+0000<br class=3D""><br class=3D""><br class=3D"">Did anyone consider =
the overlap between this and event notifications<br class=3D"">effort in =
the NETCONF working group?<br class=3D""><br class=3D""> =
&nbsp;draft-ietf-netconf-rfc5277bis<br class=3D""> =
&nbsp;draft-ietf-netconf-netconf-event-notifications<br class=3D""> =
&nbsp;draft-ietf-netconf-restconf-notif<br class=3D""> =
&nbsp;draft-ietf-netconf-yang-push<br class=3D""><br class=3D"">It may =
not have the same focus, but it can get the job done, right?<br =
class=3D""><br class=3D"">Thanks,<br class=3D"">Kent<br class=3D""><br =
class=3D""><br class=3D"">On 9/27/16, 5:00 PM, "saag on behalf of =
Kathleen Moriarty"<br class=3D"">&lt;<a =
href=3D"mailto:saag-bounces@ietf.org" class=3D"">saag-bounces@ietf.org</a>=
 on behalf of <a href=3D"mailto:kathleen.moriarty.ietf@gmail.com" =
class=3D"">kathleen.moriarty.ietf@gmail.com</a>&gt;<br =
class=3D"">wrote:<br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;Hello,<br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;A new working group has been proposed, SecEvent, that =
crosses<br class=3D""> &nbsp;&nbsp;&nbsp;between<br class=3D""> =
&nbsp;&nbsp;&nbsp;the ART and security areas. &nbsp;This builds off of =
SCIM work, also<br class=3D""> &nbsp;&nbsp;&nbsp;leveraging OAuth, and =
will incorporate use of JWT from JOSE. &nbsp;The<br class=3D""> =
&nbsp;&nbsp;&nbsp;working group, if approved, will go into the security =
area and I've<br class=3D""> &nbsp;&nbsp;&nbsp;agreed to AD it. =
&nbsp;Please take a look at the charter under review:<br class=3D""><br =
class=3D""> &nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/charter-ietf-secevent/" =
class=3D"">https://datatracker.ietf.org/doc/charter-ietf-secevent/</a><br =
class=3D""><br class=3D""> &nbsp;&nbsp;&nbsp;And join the mailing list =
for discussion:<br class=3D""> &nbsp;&nbsp;&nbsp;<a =
href=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Did-event" =
class=3D"">https://mailarchive.ietf.org/arch/search/?email_list=3Did-event=
</a><br class=3D""><br class=3D""> &nbsp;&nbsp;&nbsp;-- <br class=3D""><br=
 class=3D""> &nbsp;&nbsp;&nbsp;Best regards,<br class=3D""> =
&nbsp;&nbsp;&nbsp;Kathleen<br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;_______________________________________________<br =
class=3D""> &nbsp;&nbsp;&nbsp;saag mailing list<br class=3D""> =
&nbsp;&nbsp;&nbsp;<a href=3D"mailto:saag@ietf.org" =
class=3D"">saag@ietf.org</a><br class=3D""> &nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/mailman/listinfo/saag" =
class=3D"">https://www.ietf.org/mailman/listinfo/saag</a><br =
class=3D""><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">Id-event mailing list<br class=3D""><a =
href=3D"mailto:Id-event@ietf.org" class=3D"">Id-event@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event<br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_8993BEA1-CB14-4FAE-9B25-251368B9C025--


From nobody Thu Sep 29 15:27:20 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF98012B314; Thu, 29 Sep 2016 15:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.517
X-Spam-Level: 
X-Spam-Status: No, score=-6.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kenhRKcs_pPC; Thu, 29 Sep 2016 15:27:13 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B380912B213; Thu, 29 Sep 2016 15:27:13 -0700 (PDT)
Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8TMRCUL009914 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 29 Sep 2016 22:27:12 GMT
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0022.oracle.com (8.14.4/8.13.8) with ESMTP id u8TMRBhV031693 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 29 Sep 2016 22:27:12 GMT
Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u8TMRBuf002031; Thu, 29 Sep 2016 22:27:11 GMT
Received: from [10.0.1.5] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 29 Sep 2016 15:27:11 -0700
From: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4755B4CE-2298-43E4-B7C4-F507A973F110"
Message-Id: <5B0B1CA9-E542-4C70-895D-35273032BC42@oracle.com>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Date: Thu, 29 Sep 2016 15:27:09 -0700
References: <147518730587.18511.15769334083378030049.idtracker@ietfa.amsl.com>
To: id-event@ietf.org
X-Mailer: Apple Mail (2.3124)
X-Source-IP: userv0022.oracle.com [156.151.31.74]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/E_3B8_tlditvJjt2ECyCxBwc2KM>
Cc: "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
Subject: [Id-event] Fwd: New Version Notification for draft-hunt-idevent-distribution-01.txt
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2016 22:27:16 -0000

--Apple-Mail=_4755B4CE-2298-43E4-B7C4-F507A973F110
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

This is a substantial re-work of the distribution draft that Marius, =
Morteza and myself have been working on.

The following major changes:

1.  Specifies a fairly simple HTTP POST delivery method for now that =
provides assured delivery
2.  Proposes a registry so that new methods may be defined as needed.
3.  Profiles SCIM for subscription registration and management including =
appropriate metadata

This more or less should line up with the distribution objective in the =
charter as a starting point for discussion.

I would like to thank my co-author Marius and the OIDF RISC working =
group for providing substantial input into the draft.

Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>





> Begin forwarded message:
>=20
> From: internet-drafts@ietf.org
> Subject: New Version Notification for =
draft-hunt-idevent-distribution-01.txt
> Date: September 29, 2016 at 3:15:05 PM PDT
> To: "Phil Hunt" <phil.hunt@yahoo.com>, "Morteza Ansari" =
<morteza.ansari@cisco.com>, "Marius Scurtescu" <mscurtescu@google.com>
>=20
>=20
> A new version of I-D, draft-hunt-idevent-distribution-01.txt
> has been successfully submitted by Phil Hunt and posted to the
> IETF repository.
>=20
> Name:		draft-hunt-idevent-distribution
> Revision:	01
> Title:		SET Token Distribution and Subscription =
Management Profile
> Document date:	2016-09-29
> Group:		Individual Submission
> Pages:		30
> URL:            =
https://www.ietf.org/internet-drafts/draft-hunt-idevent-distribution-01.tx=
t
> Status:         =
https://datatracker.ietf.org/doc/draft-hunt-idevent-distribution/
> Htmlized:       =
https://tools.ietf.org/html/draft-hunt-idevent-distribution-01
> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-distribution-01
>=20
> Abstract:
>   The specification defines how a subscriber to a feed of security
>   events (SETs) may query for, subscribe and receive SETs from a
>   security event feed.  The specification defines a single mandatory-
>   to-implement method using HTTP Post to deliver events to registered
>   subscribers and a registry for new methods.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20


--Apple-Mail=_4755B4CE-2298-43E4-B7C4-F507A973F110
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">This is a substantial re-work of the distribution draft that =
Marius, Morteza and myself have been working on.<div class=3D""><br =
class=3D""></div><div class=3D"">The following major changes:</div><div =
class=3D""><br class=3D""></div><div class=3D"">1. &nbsp;Specifies a =
fairly simple HTTP POST delivery method for now that provides assured =
delivery</div><div class=3D"">2. &nbsp;Proposes a registry so that new =
methods may be defined as needed.</div><div class=3D"">3. &nbsp;Profiles =
SCIM for subscription registration and management including appropriate =
metadata</div><div class=3D""><br class=3D""></div><div class=3D"">This =
more or less should line up with the distribution objective in the =
charter as a starting point for discussion.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I would like to thank my co-author =
Marius and the OIDF RISC working group for providing substantial input =
into the draft.</div><div class=3D""><br class=3D""><div class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>

<div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a =
href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">New Version =
Notification for draft-hunt-idevent-distribution-01.txt</b><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">September 29, 2016 at 3:15:05 =
PM PDT<br class=3D""></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">"Phil Hunt" &lt;<a =
href=3D"mailto:phil.hunt@yahoo.com" =
class=3D"">phil.hunt@yahoo.com</a>&gt;, "Morteza Ansari" &lt;<a =
href=3D"mailto:morteza.ansari@cisco.com" =
class=3D"">morteza.ansari@cisco.com</a>&gt;, "Marius Scurtescu" &lt;<a =
href=3D"mailto:mscurtescu@google.com" =
class=3D"">mscurtescu@google.com</a>&gt;<br class=3D""></span></div><br =
class=3D""><div class=3D""><div class=3D""><br class=3D"">A new version =
of I-D, draft-hunt-idevent-distribution-01.txt<br class=3D"">has been =
successfully submitted by Phil Hunt and posted to the<br class=3D"">IETF =
repository.<br class=3D""><br class=3D"">Name:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-hunt-idevent-distribution<br class=3D"">Revision:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>01<br =
class=3D"">Title:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>SET Token Distribution and Subscription Management Profile<br =
class=3D"">Document date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2016-09-29<br =
class=3D"">Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Individual Submission<br class=3D"">Pages:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>30<br =
class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/internet-drafts/draft-hunt-idevent-distributi=
on-01.txt" =
class=3D"">https://www.ietf.org/internet-drafts/draft-hunt-idevent-distrib=
ution-01.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-hunt-idevent-distribution/"=
 =
class=3D"">https://datatracker.ietf.org/doc/draft-hunt-idevent-distributio=
n/</a><br class=3D"">Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-hunt-idevent-distribution-01" =
class=3D"">https://tools.ietf.org/html/draft-hunt-idevent-distribution-01<=
/a><br class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-distributio=
n-01" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-distribu=
tion-01</a><br class=3D""><br class=3D"">Abstract:<br class=3D""> =
&nbsp;&nbsp;The specification defines how a subscriber to a feed of =
security<br class=3D""> &nbsp;&nbsp;events (SETs) may query for, =
subscribe and receive SETs from a<br class=3D""> &nbsp;&nbsp;security =
event feed. &nbsp;The specification defines a single mandatory-<br =
class=3D""> &nbsp;&nbsp;to-implement method using HTTP Post to deliver =
events to registered<br class=3D""> &nbsp;&nbsp;subscribers and a =
registry for new methods.<br class=3D""><br class=3D""><br class=3D""><br =
class=3D""><br class=3D"">Please note that it may take a couple of =
minutes from the time of submission<br class=3D"">until the htmlized =
version and diff are available at <a href=3D"http://tools.ietf.org" =
class=3D"">tools.ietf.org</a>.<br class=3D""><br class=3D"">The IETF =
Secretariat<br class=3D""><br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_4755B4CE-2298-43E4-B7C4-F507A973F110--


From nobody Thu Sep 29 15:39:11 2016
Return-Path: <phil.hunt@oracle.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E58F12B1F8; Thu, 29 Sep 2016 15:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.517
X-Spam-Level: 
X-Spam-Status: No, score=-6.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ez2qaTrDbRbw; Thu, 29 Sep 2016 15:39:04 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C2E112B0C5; Thu, 29 Sep 2016 15:39:04 -0700 (PDT)
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u8TMd3a5021471 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 29 Sep 2016 22:39:03 GMT
Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u8TMd2EM028273 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 29 Sep 2016 22:39:03 GMT
Received: from abhmp0015.oracle.com (abhmp0015.oracle.com [141.146.116.21]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id u8TMd2T1024226; Thu, 29 Sep 2016 22:39:02 GMT
Received: from [10.0.1.5] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 29 Sep 2016 15:39:01 -0700
From: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_983829E5-A634-42FA-9DFB-93F2A87A15B9"
Message-Id: <C9108E07-1DE7-4439-852B-48513269951B@oracle.com>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Date: Thu, 29 Sep 2016 15:39:00 -0700
References: <147518764595.18469.13842294313586215202.idtracker@ietfa.amsl.com>
To: id-event@ietf.org
X-Mailer: Apple Mail (2.3124)
X-Source-IP: aserv0021.oracle.com [141.146.126.233]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/f7vXciScrOFwRQyFN-GTOl5LRW8>
Cc: "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
Subject: [Id-event] Fwd: New Version Notification for draft-hunt-idevent-token-06.txt
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2016 22:39:06 -0000

--Apple-Mail=_983829E5-A634-42FA-9DFB-93F2A87A15B9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

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 =E2=80=9Cidempotency=E2=80=9D as this is =
not really the correct usage of the word. =20

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)

My gut feeling on sequencing (when needed) is most likely resolved by =
specs that profile SET Tokes by adding sequencing claim or defining =
=E2=80=9Ctxn=E2=80=9D 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=E2=80=99=
s not to say I haven=E2=80=99t overlooked a =E2=80=9Cduh=E2=80=9D simple =
solution.=20

This draft should be a good starting place for the SEC Event WG proposed =
charter.

Thanks,
=20
Phil

@independentid
www.independentid.com =
<http://www.independentid.com/>phil.hunt@oracle.com =
<mailto:phil.hunt@oracle.com>





> Begin forwarded message:
>=20
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-hunt-idevent-token-06.txt
> Date: September 29, 2016 at 3:20:45 PM PDT
> To: "Michael B. Jones" <mbj@microsoft.com>, "William Denniss" =
<wdenniss@google.com>, "Phil Hunt" <phil.hunt@yahoo.com>, "Morteza =
Ansari" <morteza.ansari@cisco.com>, "Michael Jones" <mbj@microsoft.com>
>=20
>=20
> A new version of I-D, draft-hunt-idevent-token-06.txt
> has been successfully submitted by Phil Hunt and posted to the
> IETF repository.
>=20
> Name:		draft-hunt-idevent-token
> Revision:	06
> Title:		Security Event Token (SET)
> Document date:	2016-09-29
> Group:		Individual Submission
> Pages:		19
> URL:            =
https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-06.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-hunt-idevent-token/
> Htmlized:       =
https://tools.ietf.org/html/draft-hunt-idevent-token-06
> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-token-06
>=20
> Abstract:
>   This specification defines the Security Event token, which may be
>   distributed via a protocol such as HTTP.  The Security Event Token
>   (SET) specification profiles the JSON Web Token (JWT) and may be
>   optionally signed and/or encrypted.  A SET describes a statement of
>   fact that may be shared by an event publisher with event =
subscribers.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20


--Apple-Mail=_983829E5-A634-42FA-9DFB-93F2A87A15B9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">This is a minor update to the SET Token draft. &nbsp;Based on =
the mailing list feedback, I made some revisions to the text on =
transactions and sequencing. &nbsp;I dropped the term =E2=80=9Cidempotency=
=E2=80=9D as this is not really the correct usage of the word. =
&nbsp;<div class=3D""><br class=3D""></div><div class=3D"">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. =
&nbsp;So while commands may be repeated achieving the same result, the =
sequence of different commands is critical. 8)</div><div class=3D""><br =
class=3D""></div><div class=3D"">My gut feeling on sequencing (when =
needed) is most likely resolved by specs that profile SET Tokes by =
adding sequencing claim or defining =E2=80=9Ctxn=E2=80=9D 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. &nbsp;That=E2=80=99s not to say I haven=E2=80=99t =
overlooked a =E2=80=9Cduh=E2=80=9D simple solution.&nbsp;<br =
class=3D""><div class=3D""><br class=3D""></div><div class=3D"">This =
draft should be a good starting place for the SEC Event WG proposed =
charter.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks,</div><div class=3D"">&nbsp;</div><div class=3D""><div =
class=3D"">
<div style=3D"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=3D""><div style=3D"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=3D""><div class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; line-height: normal; border-spacing: =
0px;"><div class=3D"" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div class=3D""><div =
class=3D""><div class=3D"">Phil</div><div class=3D""><br =
class=3D""></div><div class=3D"">@independentid</div><div class=3D""><a =
href=3D"http://www.independentid.com" =
class=3D"">www.independentid.com</a></div></div></div></div></span><a =
href=3D"mailto:phil.hunt@oracle.com" class=3D"" style=3D"orphans: 2; =
widows: 2;">phil.hunt@oracle.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>

<div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a =
href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">New Version =
Notification for draft-hunt-idevent-token-06.txt</b><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">September 29, 2016 at 3:20:45 =
PM PDT<br class=3D""></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">"Michael B. Jones" &lt;<a =
href=3D"mailto:mbj@microsoft.com" class=3D"">mbj@microsoft.com</a>&gt;, =
"William Denniss" &lt;<a href=3D"mailto:wdenniss@google.com" =
class=3D"">wdenniss@google.com</a>&gt;, "Phil Hunt" &lt;<a =
href=3D"mailto:phil.hunt@yahoo.com" =
class=3D"">phil.hunt@yahoo.com</a>&gt;, "Morteza Ansari" &lt;<a =
href=3D"mailto:morteza.ansari@cisco.com" =
class=3D"">morteza.ansari@cisco.com</a>&gt;, "Michael Jones" &lt;<a =
href=3D"mailto:mbj@microsoft.com" class=3D"">mbj@microsoft.com</a>&gt;<br =
class=3D""></span></div><br class=3D""><div class=3D""><div class=3D""><br=
 class=3D"">A new version of I-D, draft-hunt-idevent-token-06.txt<br =
class=3D"">has been successfully submitted by Phil Hunt and posted to =
the<br class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span=
 class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-hunt-idevent-token<br class=3D"">Revision:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>06<br =
class=3D"">Title:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Security Event Token (SET)<br class=3D"">Document date:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>2016-09-29<br class=3D"">Group:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Individual Submission<br =
class=3D"">Pages:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>19<br class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-06.t=
xt" =
class=3D"">https://www.ietf.org/internet-drafts/draft-hunt-idevent-token-0=
6.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-hunt-idevent-token/" =
class=3D"">https://datatracker.ietf.org/doc/draft-hunt-idevent-token/</a><=
br class=3D"">Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-hunt-idevent-token-06" =
class=3D"">https://tools.ietf.org/html/draft-hunt-idevent-token-06</a><br =
class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-token-06" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-token-06=
</a><br class=3D""><br class=3D"">Abstract:<br class=3D""> =
&nbsp;&nbsp;This specification defines the Security Event token, which =
may be<br class=3D""> &nbsp;&nbsp;distributed via a protocol such as =
HTTP. &nbsp;The Security Event Token<br class=3D""> &nbsp;&nbsp;(SET) =
specification profiles the JSON Web Token (JWT) and may be<br class=3D""> =
&nbsp;&nbsp;optionally signed and/or encrypted. &nbsp;A SET describes a =
statement of<br class=3D""> &nbsp;&nbsp;fact that may be shared by an =
event publisher with event subscribers.<br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D"">Please note that it may take a =
couple of minutes from the time of submission<br class=3D"">until the =
htmlized version and diff are available at <a =
href=3D"http://tools.ietf.org" class=3D"">tools.ietf.org</a>.<br =
class=3D""><br class=3D"">The IETF Secretariat<br class=3D""><br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_983829E5-A634-42FA-9DFB-93F2A87A15B9--


From nobody Thu Sep 29 17:15:31 2016
Return-Path: <alanhkarp@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30DBE12B208; Thu, 29 Sep 2016 17:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q1T9M9xA-uiz; Thu, 29 Sep 2016 17:15:26 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 749F112B09C; Thu, 29 Sep 2016 17:15:26 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id t83so112395855oie.3; Thu, 29 Sep 2016 17:15:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4h2ESaZFbkP+yrGG1SIi5duGJ44AGaxTBCtRj0Sy3Ts=; b=k6VmmEotroexKsyICdqHuf0zvVXzCnb3t6hqGUeHCGFS6AT0AsHkn3DlkuZJf+1sko Poa20GdMGOUkQXJxVK1Izk3abOE0Uq0+NmzY9grRTmS4CAugk7gFRr8x60wzWnF1a3+W 5A719bPIDu0we1oihxIuNuxqjmZzjTuakvoZapo2eZEypWcf5hjqSswFcNfs7XhLMZpT cMupcHrZIjtgkA19wMQKdof/05DrVVLccopTWNf4qtxMGhkAqXedOn4mRSGGS0xy0T4+ 390Z2QnemJiCUfWS4NvnyOynE5vX2YihCyyUXobtEeEL3e98DvJc/CnaThBGfqPKaznd reCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4h2ESaZFbkP+yrGG1SIi5duGJ44AGaxTBCtRj0Sy3Ts=; b=VC++6AuqrqGvarrHIC9xC4u0CxWcGy8s8HJPa/oQABW3xOF3gjV17TxUO3Qp7FX8XZ mHlZECo5/Lh+DemBx1h/HBzmopRYSBJBFBN9OycvOZdHZZzDsJxvEQVF2WyGjSA16SCc Tf2805VaEIqhFkKfG0OjQuAHLzoRLOqWUGWhdLoMtZMBnGX/N6s4CuRoRO5hTNwKg28n wKweol9NlyZBzLn4kxmSCzmYdGXNruLu1L/FFg8MxEShusySssqb4ZpooGc2g8trur/l e9c+7VKxEEMDXzp641QebOrzpoIzEjAEaYpOvLR4ZTy23vQscgBLQxrbGCO/t4GBv2Bt QKSg==
X-Gm-Message-State: AA6/9RlwrB40a8Cc4FJaL7hXzEMCsBYZiWBpXAXxkfXD7IXt0EdPLgw6AVreSUD1bvFgMDuj4I1Etx2pXfJtPw==
X-Received: by 10.157.6.46 with SMTP id 43mr2794914otn.33.1475194525874; Thu, 29 Sep 2016 17:15:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.142.39 with HTTP; Thu, 29 Sep 2016 17:15:25 -0700 (PDT)
In-Reply-To: <C9108E07-1DE7-4439-852B-48513269951B@oracle.com>
References: <147518764595.18469.13842294313586215202.idtracker@ietfa.amsl.com> <C9108E07-1DE7-4439-852B-48513269951B@oracle.com>
From: Alan Karp <alanhkarp@gmail.com>
Date: Thu, 29 Sep 2016 17:15:25 -0700
Message-ID: <CANpA1Z1yreWPrKN-j0iWLG17_dhVejiWNrqYP6MqW3jxLeJNXA@mail.gmail.com>
To: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary=94eb2c09b6c4b08047053dae7dd0
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/vFOMqh3yYRRf90Bes1EEbDpRqQM>
Cc: "scim@ietf.org WG" <scim@ietf.org>, "openid-specs-ab@lists.openid.net Ab" <openid-specs-ab@lists.openid.net>, id-event@ietf.org, openid-specs-risc@lists.openid.net
Subject: Re: [Id-event] Fwd: New Version Notification for draft-hunt-idevent-token-06.txt
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2016 00:15:28 -0000

--94eb2c09b6c4b08047053dae7dd0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Phil Hunt <phil.hunt@oracle.com> wrote:

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=E2=80=99s not to say I haven=E2=80=99t overlooked a =E2=80=9Cd=
uh=E2=80=9D simple solution.


Having worked with distributed systems for more years than I care to admit,
I doubt that you overlooked a "duh" solution.

--------------
Alan Karp

--94eb2c09b6c4b08047053dae7dd0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Phil Hunt=C2=A0<span dir=3D"ltr">&lt;<a href=3D"mailto:phi=
l.hunt@oracle.com" target=3D"_blank">phil.hunt@oracle.com</a>&gt;</span>=C2=
=A0wrote:<br><div class=3D"gmail_extra"><br clear=3D"all"></div><blockquote=
 style=3D"margin:0 0 0 40px;border:none;padding:0px"><div class=3D"gmail_ex=
tra"><div><div class=3D"gmail_signature">For example, in a distributed syst=
em, the way events are delivered to a Feed Publishing Service might enable =
the Feed Publisher to guarantee order.=C2=A0 That=E2=80=99s not to say I ha=
ven=E2=80=99t overlooked a =E2=80=9Cduh=E2=80=9D simple solution.=C2=A0</di=
v></div></div></blockquote><div class=3D"gmail_extra"><div><div class=3D"gm=
ail_signature"><br></div><div class=3D"gmail_signature">Having worked with =
distributed systems for more years than I care to admit, I doubt that you o=
verlooked a &quot;duh&quot; solution. =C2=A0</div><div class=3D"gmail_signa=
ture"><br>--------------<br>Alan Karp</div></div><br></div></div>

--94eb2c09b6c4b08047053dae7dd0--

