From nobody Tue Nov 1 14:37:06 2016 Return-Path: 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 C0B4F129A0F for ; Tue, 1 Nov 2016 14:37:03 -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 64BSFqmSAVFf for ; Tue, 1 Nov 2016 14:37:02 -0700 (PDT) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::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 294EB129A1B for ; Tue, 1 Nov 2016 14:37:02 -0700 (PDT) Received: by mail-wm0-x232.google.com with SMTP id a197so103167970wmd.0 for ; Tue, 01 Nov 2016 14:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:mime-version:subject:message-id:date:to; bh=l2Zz6nqY82/O7YLYKg1cmjA99PvJZuR1wWSGeg6xNDU=; b=B7eD3aAaxP7zlcaPh/VHdDeqDLgPFa1ZPoHZEK3vlSpj3YPG4Y7cCnfpwRFL7I5RAX Qw0k/tsOveXRZmAOh0CHhOpkYq7Yp8f/3MRKasvVoLkE3YzbH2+U1ztaJ1CbX2NA5lIn 36HPpqoYjPAATtxBZndzUBbdWWAerS0WjOjPGxBAYQFm5RNqGOj89nmCJ+NeS7ZZlGwh NOsPuQdujzm6tz5MZth25PesYVGeTJP2C8XRpRdu0Xi3jWJ3LbJ//7Jkf8A0M/MGQOlM OqH8CFeeJN9tzHK+NwGPJYUXOd9FuFfg+WgaLpAvKCAAlcPVlvAqtq63L9Kca8yPJCHJ KQhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=l2Zz6nqY82/O7YLYKg1cmjA99PvJZuR1wWSGeg6xNDU=; b=CHIDw7CzAa5X90w6JhdMAMOxOm6UMJ7vYShbQjUd/qTYhf2YgBmdUJl+6N9quGtzwS Rel3DeaksczfqIt4LwfNmknCw1cODRgpmZ4o4S28kIpu/pKsFv4QMmWGOw232qhskZva jdMdhq41Az3vX64HMN/EDcYqMsot48rY9rKv+7XXw/VWbN6L9qih6OhfEhTHUeeOfBfG oPrp9WMCRGX+L4lsF07IbTCmvk3ZN3p21EpMgQpdjE0uMJ8J7HjT1lw4ojsCJQNQLjGB IXW3cGhRtOMAeK9s6+7aafxEVBzgIih88CiirHoxnqyr51r6mzlHejvSs8wkYPNJ1Mah ZxkQ== X-Gm-Message-State: ABUngvd3RgVYMzvt7nkaHW4cHTMyZ/Y6qE6W1R/QS5I7QROn1tHw7Hyx8Mj2W4t8sPaO6Q== X-Received: by 10.194.99.69 with SMTP id eo5mr120727wjb.138.1478036220286; Tue, 01 Nov 2016 14:37:00 -0700 (PDT) Received: from [192.168.1.13] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id r1sm37712489wjc.43.2016.11.01.14.36.59 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Nov 2016 14:36:59 -0700 (PDT) From: Yoav Nir Content-Type: multipart/alternative; boundary="Apple-Mail=_40A91A6C-FA26-41B6-8098-36B654087737" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Message-Id: <4000ADE0-6B49-4C10-B0DB-AABA2877F4B0@gmail.com> Date: Tue, 1 Nov 2016 23:36:57 +0200 To: id-event@ietf.org X-Mailer: Apple Mail (2.3251) Archived-At: Subject: [Id-event] Preliminary Agenda Uploaded 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2016 21:37:04 -0000 --Apple-Mail=_40A91A6C-FA26-41B6-8098-36B654087737 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi all https://www.ietf.org/proceedings/97/agenda/agenda-97-secevent-00.txt = If I missed or forgotten something, please let me know Yoav= --Apple-Mail=_40A91A6C-FA26-41B6-8098-36B654087737 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii Hi all


If I missed or forgotten something, please let me know

Yoav
--Apple-Mail=_40A91A6C-FA26-41B6-8098-36B654087737-- From nobody Thu Nov 3 05:38:45 2016 Return-Path: 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 D1396129535 for ; Thu, 3 Nov 2016 05:38:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.697 X-Spam-Level: X-Spam-Status: No, score=-5.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, 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 Difm1fBT8Qgl for ; Thu, 3 Nov 2016 05:38:42 -0700 (PDT) Received: from dmz-mailsec-scanner-3.mit.edu (dmz-mailsec-scanner-3.mit.edu [18.9.25.14]) (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 3F3031293F2 for ; Thu, 3 Nov 2016 05:38:42 -0700 (PDT) X-AuditID: 1209190e-d3fff700000004ab-a1-581b2fd027a4 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 3F.A1.01195.0DF2B185; Thu, 3 Nov 2016 08:38:41 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id uA3CcdnQ027484; Thu, 3 Nov 2016 08:38:39 -0400 Received: from [192.168.128.57] (static-96-237-195-53.bstnma.fios.verizon.net [96.237.195.53]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id uA3Ccbnj022934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 3 Nov 2016 08:38:39 -0400 To: Yoav Nir , id-event@ietf.org References: <4000ADE0-6B49-4C10-B0DB-AABA2877F4B0@gmail.com> From: Justin Richer Message-ID: Date: Thu, 3 Nov 2016 08:38:30 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <4000ADE0-6B49-4C10-B0DB-AABA2877F4B0@gmail.com> Content-Type: multipart/alternative; boundary="------------0285C0135B8554AB8444D712" X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGIsWRmVeSWpSXmKPExsUixG6nrntRXzrC4N1GXouOBd1MFkuPfWBy YPLYOesuu8eSJT+ZApiiuGxSUnMyy1KL9O0SuDI2vZ7LXLBbuKJ78Xr2Bsar/F2MnBwSAiYS Z1Z+Zexi5OIQEmhjknj8fTorhLOBUeLmmhtsEM4tJompm9+xgLQICxhLTH/8hhXEFhEwlfj8 8RdYXEjARuLozS9gcTYBVYnpa1qYQGxeASuJB8fus4HYLAIqEtMvLAerFxWIkbj+7BEbRI2g xMmZT4DiHBycArYSzbPYQExmgTCJmZu8JzDyzUJSNAshAxJmBqq/M3c3M4QtL7H97RwoW1di 0bYV7DDx5q2zmRcwsq1ilE3JrdLNTczMKU5N1i1OTszLSy3SNdbLzSzRS00p3cQICl5OSb4d jJMavA8xCnAwKvHwZvyQjBBiTSwrrsw9xCjJwaQkyvtGUzpCiC8pP6UyI7E4I76oNCe1+BCj BAezkgivoh5QjjclsbIqtSgfJiXNwaIkzvvf7Wu4kEB6YklqdmpqQWoRTFaGg0NJgvccSKNg UWp6akVaZk4JQpqJgxNkOA/QcHZ9kOHFBYm5xZnpEPlTjIpS4rwndYASAiCJjNI8uF5Qckl4 e9j0FaM40CvCEO08wMQE1/0KaDAT0GDzJAmQwSWJCCmpBsakn0YH31f+CT6xYw3bNd18+699 B/2Z2NJLpMNOhU9nXbI/0dv1A2PzJkuNK9+ZfYuv2u5zEOzNeL/sdcAxpduHpXOeSF67dLo2 3fGhTP4DPqPo1cua7nDxn02XWTJ147SkLddm/lFLnu+z75DB8660b4f+7Q8zef7oBwu/6Hut 9M7W7d2WGs+VWIozEg21mIuKEwE3ZCP4CQMAAA== Archived-At: Subject: Re: [Id-event] Preliminary Agenda Uploaded 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2016 12:38:44 -0000 This is a multi-part message in MIME format. --------------0285C0135B8554AB8444D712 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit I'd like a couple minutes to talk about the consent work that we're looking at using this format for. I don't anticipate it will take long. -- Justin On 11/1/2016 5:36 PM, Yoav Nir wrote: > Hi all > > https://www.ietf.org/proceedings/97/agenda/agenda-97-secevent-00.txt > > If I missed or forgotten something, please let me know > > Yoav > > > _______________________________________________ > Id-event mailing list > Id-event@ietf.org > https://www.ietf.org/mailman/listinfo/id-event --------------0285C0135B8554AB8444D712 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit

I'd like a couple minutes to talk about the consent work that we're looking at using this format for. I don't anticipate it will take long.

 -- Justin


On 11/1/2016 5:36 PM, Yoav Nir wrote:
Hi all


If I missed or forgotten something, please let me know

Yoav


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

--------------0285C0135B8554AB8444D712-- From nobody Thu Nov 3 10:10:44 2016 Return-Path: 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 433BF12955D for ; Thu, 3 Nov 2016 10:10:43 -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 Y8VDc1vILze3 for ; Thu, 3 Nov 2016 10:10:41 -0700 (PDT) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 549AE128E18 for ; Thu, 3 Nov 2016 10:10:41 -0700 (PDT) Received: by mail-wm0-x234.google.com with SMTP id n67so114539576wme.1 for ; Thu, 03 Nov 2016 10:10:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=FZ/Chz54TU191XaQfH+j6YFWCDFGOIiGiLP4MI/hvbs=; b=PkF3BdtRs+LFyjG9PUrRNoDm3vNUlzkHTdiaZtYzVv1LjXQR0wpPFJdUOqEe+lsgw9 FQYv5HmYEZ9vetIs5h5037jIXBR8zhoLRe/dN/0SVTFtZCZctFP8eWxjdIWqCxo9Itv4 LwXWrNqnFy2qe6JLZ5q1a2nB9sctvu8uS1dYFkdmf2TXNNaN0D7KI11pkr72Q6i3UUM+ pdiHVi/z1g5JqtFgHT5vR8/Z8ej1V5gBtutecgq3JBsWDfPPXJ9TXQ+55KAAzrKcWMyh xmOY80lih2M76Gif4X86/oNPxnhqHpSZ3jZXMnW6UflS/oJo50CkWPZ6WrhJTmgHoPfj mcfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=FZ/Chz54TU191XaQfH+j6YFWCDFGOIiGiLP4MI/hvbs=; b=PHU7ww7gF4p9DDiSLxIAIdHgLgBtjiR/xxjCHCvccjbpYqsXDWWRGJnvV2wYjCMhDx 3QcyFxDZ6LB0wBzw74ttYyPDkc1UZujzjsWyoy34t25Ae7tz9hTjNv368azl+gbUBvFw 6dgrHz+iksJx/rKhmW284yPMkqy+aHatPNjb7u/Av+TUTyRSh04+MEXDXEVVfkKEkhxR Lb5JeJnJzjcli0u4BCSQWMCJLmrls9u4Epv1CvyJF7aDcxZnRZ97wWoIFPYpi2PnGr60 Pa+lcqPPQmQ/M69kbnggBL6s8LqsH0fOeSD+vkYME2V+BRbmrO7em48gvuFi/eIrXzQs OMAA== X-Gm-Message-State: ABUngveeKyE5H0ieS3vplaL8urX/Ht9Uso05iebnpbQDuLvLhy4e4a91qhTDI8rDXZpt3g== X-Received: by 10.28.113.13 with SMTP id m13mr10332799wmc.39.1478193037256; Thu, 03 Nov 2016 10:10:37 -0700 (PDT) Received: from [192.168.137.54] ([176.13.225.174]) by smtp.gmail.com with ESMTPSA id cl10sm1188865wjb.4.2016.11.03.10.10.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Nov 2016 10:10:36 -0700 (PDT) From: Yoav Nir Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_AC53F3C1-326F-4C1E-A76E-CA66D219EE8B" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Date: Thu, 3 Nov 2016 19:10:34 +0200 In-Reply-To: To: Justin Richer References: <4000ADE0-6B49-4C10-B0DB-AABA2877F4B0@gmail.com> X-Mailer: Apple Mail (2.3251) Archived-At: Cc: id-event@ietf.org Subject: Re: [Id-event] Preliminary Agenda Uploaded 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2016 17:10:43 -0000 --Apple-Mail=_AC53F3C1-326F-4C1E-A76E-CA66D219EE8B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 As you can see in the agenda, we=E2=80=99re pretty pressed for time. = There is a little buffer in the end, and I hope we can make use of that. Yoav > On 3 Nov 2016, at 14:38, Justin Richer wrote: >=20 > I'd like a couple minutes to talk about the consent work that we're = looking at using this format for. I don't anticipate it will take long. > -- Justin >=20 > On 11/1/2016 5:36 PM, Yoav Nir wrote: >> Hi all >>=20 >> https://www.ietf.org/proceedings/97/agenda/agenda-97-secevent-00.txt = >>=20 >> If I missed or forgotten something, please let me know >>=20 >> Yoav >>=20 >>=20 >> _______________________________________________ >> Id-event mailing list >> Id-event@ietf.org >> https://www.ietf.org/mailman/listinfo/id-event = >=20 --Apple-Mail=_AC53F3C1-326F-4C1E-A76E-CA66D219EE8B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 As you can see in the agenda, we=E2=80=99re pretty pressed = for time. There is a little buffer in the end, and I hope we can make = use of that.

Yoav

On 3 Nov 2016, at 14:38, Justin = Richer <jricher@mit.edu> wrote:

=20 =20

I'd = like a couple minutes to talk about the consent work that we're looking at using this format for. I don't anticipate it will take long.

 -- Justin


On 11/1/2016 5:36 PM, Yoav Nir = wrote:
Hi all

https://www.ietf.org/proceedings/97/agenda/agenda-97-secevent-0= 0.txt

If I missed or forgotten something, please let me know

Yoav


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


= --Apple-Mail=_AC53F3C1-326F-4C1E-A76E-CA66D219EE8B-- From nobody Thu Nov 3 10:24:06 2016 Return-Path: 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 28F93128E18 for ; Thu, 3 Nov 2016 10:24:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.697 X-Spam-Level: X-Spam-Status: No, score=-5.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, 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 TP8IHYNfkeqV for ; Thu, 3 Nov 2016 10:24:03 -0700 (PDT) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (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 EB1AD1294D1 for ; Thu, 3 Nov 2016 10:24:02 -0700 (PDT) X-AuditID: 12074423-763ff70000003b49-72-581b72b1b198 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 59.F7.15177.1B27B185; Thu, 3 Nov 2016 13:24:02 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id uA3HO1UQ018135; Thu, 3 Nov 2016 13:24:01 -0400 Received: from artemisia.richer.local (static-96-237-195-53.bstnma.fios.verizon.net [96.237.195.53]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id uA3HNx0I015762 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Nov 2016 13:24:00 -0400 Content-Type: multipart/alternative; boundary="Apple-Mail=_9CEAABA4-E6AD-4C2B-B1A1-9DF4B724DB34" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Justin Richer In-Reply-To: Date: Thu, 3 Nov 2016 13:23:59 -0400 Message-Id: <3AF59253-BB72-46A1-B56F-5F308258E573@mit.edu> References: <4000ADE0-6B49-4C10-B0DB-AABA2877F4B0@gmail.com> To: Yoav Nir X-Mailer: Apple Mail (2.3124) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmleLIzCtJLcpLzFFi42IRYrdT191UJB1hMG0ns0XHgm4mi6XHPjA5 MHnsnHWX3WPJkp9MAUxRXDYpqTmZZalF+nYJXBkXF71iLviqUrH8xCGmBsZF8l2MnBwSAiYS O+9+Zu9i5OIQEmhjklg+4T0ThLOBUeLblNOsIFVCAg+YJG6czQOxmQUSJPZs2cQIYvMK6Els Wv+WCcQWFjCWmP74DVg9m4CqxPQ1LUBxDg5OAVuJY2fDQMIsAioSzRNmsUKMEZWY8mgCC8QY K4mpa9rYIVbNYZS4ubscxBYRUJI4fOUrM8ShshJPTi5imcDIPwvJFbOQXAER15ZYtvA1M4St KbG/ezkLpriGROe3iawLGNlWMcqm5Fbp5iZm5hSnJusWJyfm5aUW6Zrp5WaW6KWmlG5iBIe1 i/IOxpd93ocYBTgYlXh4Z/hJRwixJpYVV+YeYpTkYFIS5V0cAxTiS8pPqcxILM6ILyrNSS0+ xCjBwawkwvs4HyjHm5JYWZValA+TkuZgURLn/e/2NVxIID2xJDU7NbUgtQgmK8PBoSTBKwKM XyHBotT01Iq0zJwShDQTByfIcB6g4W6FIMOLCxJzizPTIfKnGBWlxHknFwAlBEASGaV5cL2g tJPw9rDpK0ZxoFeEeUNA2nmAKQuu+xXQYCagweZJEiCDSxIRUlINjBERlzZIWFVPsui4dsTB s1ZMgSEsXHv2i3jL9tJIlm2e68qfXPl3vv99ilf6z3MHAhm3pIjefl5Zxnk49UVkjXnnhbN3 7100expyMHftkldbj07n8LaeJbaXOzEtwD1PbZrM7HSVf9t6dWa+l9TtumO57VW/+t1LvlUR LGv/chc3tP1c9KzWQ4mlOCPRUIu5qDgRAAVXA2MWAwAA Archived-At: Cc: id-event@ietf.org Subject: Re: [Id-event] Preliminary Agenda Uploaded 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2016 17:24:05 -0000 --Apple-Mail=_9CEAABA4-E6AD-4C2B-B1A1-9DF4B724DB34 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 That=E2=80=99s fair, but this was one of the motivating use cases along = side of logout and RISC. =E2=80=94 Justin > On Nov 3, 2016, at 1:10 PM, Yoav Nir wrote: >=20 > As you can see in the agenda, we=E2=80=99re pretty pressed for time. = There is a little buffer in the end, and I hope we can make use of that. >=20 > Yoav >=20 >> On 3 Nov 2016, at 14:38, Justin Richer > wrote: >>=20 >> I'd like a couple minutes to talk about the consent work that we're = looking at using this format for. I don't anticipate it will take long. >> -- Justin >>=20 >> On 11/1/2016 5:36 PM, Yoav Nir wrote: >>> Hi all >>>=20 >>> https://www.ietf.org/proceedings/97/agenda/agenda-97-secevent-00.txt = >>>=20 >>> If I missed or forgotten something, please let me know >>>=20 >>> Yoav >>>=20 >>>=20 >>> _______________________________________________ >>> Id-event mailing list >>> Id-event@ietf.org >>> https://www.ietf.org/mailman/listinfo/id-event = >>=20 >=20 --Apple-Mail=_9CEAABA4-E6AD-4C2B-B1A1-9DF4B724DB34 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 That=E2=80=99s fair, but this was one of the motivating use = cases along side of logout and RISC.

 =E2=80=94 Justin


On = Nov 3, 2016, at 1:10 PM, Yoav Nir <ynir.ietf@gmail.com>= wrote:

As you can see = in the agenda, we=E2=80=99re pretty pressed for time. There is a little = buffer in the end, and I hope we can make use of that.

Yoav

On 3 Nov 2016, at 14:38, Justin Richer <jricher@mit.edu> = wrote:

=20 =20 =20

I'd = like a couple minutes to talk about the consent work that we're looking at using this format for. I don't anticipate it will take long.

 -- Justin


On 11/1/2016 5:36 PM, Yoav Nir = wrote:
=20 Hi all

https://www.ietf.org/proceedings/97/agenda/agenda-97-secevent-0= 0.txt

If I missed or forgotten something, please let me know

Yoav


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



= --Apple-Mail=_9CEAABA4-E6AD-4C2B-B1A1-9DF4B724DB34-- From nobody Thu Nov 3 10:30:50 2016 Return-Path: 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 7EAF5129AAE for ; Thu, 3 Nov 2016 10:30:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.698 X-Spam-Level: X-Spam-Status: No, score=-5.698 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.497, 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 kaonJu3VANFF for ; Thu, 3 Nov 2016 10:30:41 -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 3D6B1129AA6 for ; Thu, 3 Nov 2016 10:30:38 -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 uA3HUaOX008335 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 3 Nov 2016 17:30:36 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 uA3HUZ5v027170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 3 Nov 2016 17:30:36 GMT Received: from abhmp0001.oracle.com (abhmp0001.oracle.com [141.146.116.7]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id uA3HUXLU007962; Thu, 3 Nov 2016 17:30:34 GMT Received: from [10.0.1.5] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 03 Nov 2016 10:30:33 -0700 Content-Type: multipart/alternative; boundary="Apple-Mail=_9D85C26C-395A-4EDB-92BE-8BFD60209174" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Phil Hunt In-Reply-To: Date: Thu, 3 Nov 2016 10:30:32 -0700 Message-Id: <53180319-A2C7-47C7-97F7-32098890D0BF@oracle.com> References: <4000ADE0-6B49-4C10-B0DB-AABA2877F4B0@gmail.com> To: Yoav Nir X-Mailer: Apple Mail (2.3124) X-Source-IP: aserv0021.oracle.com [141.146.126.233] Archived-At: Cc: id-event@ietf.org, Justin Richer Subject: Re: [Id-event] Preliminary Agenda Uploaded 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2016 17:30:49 -0000 --Apple-Mail=_9D85C26C-395A-4EDB-92BE-8BFD60209174 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Apologies Justin. My bad. I wanted to get a cross-section of uses to = act as use-cases. HEART would have been a good one too. These are all interesting to understand in discussing SET as they all = contribute some slightly different requirements: * Logout - A simple protocol signalling event from issuer/OP to relying = parties * RISC - Analytical events shared peer-to-peer. * SCIM - Dealing with provisioning events between providers where user = state is unequal * HEART - Tracking consent in a distributed system In the interest of time, we can limit the amount of detailed discussion = on the proposed drafts and focus on common understanding of the cases. However my hope is to determine if the current proposed drafts are ready = for adoption. If not, what changes the group would like to see before = adoption? The SET token draft is fairly close, and according to our = charter timeline we need to get that going. I note that on the SET token draft Justin had proposed some changes to = payloads improve parsing, I would like to keep that discussion going on = the list. I=E2=80=99m neutral on the final format, but we should = probably have some consensus before attempting to amend the draft = (either before or after adoption). Phil @independentid www.independentid.com = phil.hunt@oracle.com = > On Nov 3, 2016, at 10:10 AM, Yoav Nir wrote: >=20 > As you can see in the agenda, we=E2=80=99re pretty pressed for time. = There is a little buffer in the end, and I hope we can make use of that. >=20 > Yoav >=20 >> On 3 Nov 2016, at 14:38, Justin Richer > wrote: >>=20 >> I'd like a couple minutes to talk about the consent work that we're = looking at using this format for. I don't anticipate it will take long. >> -- Justin >>=20 >> On 11/1/2016 5:36 PM, Yoav Nir wrote: >>> Hi all >>>=20 >>> https://www.ietf.org/proceedings/97/agenda/agenda-97-secevent-00.txt = >>>=20 >>> If I missed or forgotten something, please let me know >>>=20 >>> Yoav >>>=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=_9D85C26C-395A-4EDB-92BE-8BFD60209174 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Apologies Justin. My bad.  I wanted to get a = cross-section of uses to act as use-cases. HEART would have been a good = one too.

These are = all interesting to understand in discussing SET as they all contribute = some slightly different requirements:
* =  Logout - A simple protocol signalling event from issuer/OP to = relying parties
*  RISC - Analytical events = shared peer-to-peer.
*  SCIM - Dealing with = provisioning events between providers where user state is = unequal
*  HEART - Tracking consent in a = distributed system

In the interest of time, we can limit the amount of detailed = discussion on the proposed drafts and focus on common understanding of = the cases.

However my hope is to determine if the current proposed = drafts are ready for adoption. If not, what changes the group would like = to see before adoption? The SET token draft is fairly close, and = according to our charter timeline we need to get that going.

I note that on the SET = token draft Justin had proposed some changes to payloads improve = parsing, I would like to keep that discussion going on the list. I=E2=80=99= m neutral on the final format, but we should probably have some = consensus before attempting to amend the draft (either before or after = adoption).




On Nov 3, 2016, at 10:10 AM, Yoav Nir <ynir.ietf@gmail.com>= wrote:

As you can see = in the agenda, we=E2=80=99re pretty pressed for time. There is a little = buffer in the end, and I hope we can make use of that.

Yoav

On 3 Nov 2016, at 14:38, Justin Richer <jricher@mit.edu> = wrote:

=20 =20

I'd = like a couple minutes to talk about the consent work that we're looking at using this format for. I don't anticipate it will take long.

 -- Justin


On 11/1/2016 5:36 PM, Yoav Nir = wrote:
Hi all

https://www.ietf.org/proceedings/97/agenda/agenda-97-secevent-0= 0.txt

If I missed or forgotten something, please let me know

Yoav


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


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

= --Apple-Mail=_9D85C26C-395A-4EDB-92BE-8BFD60209174-- From nobody Fri Nov 4 05:43:02 2016 Return-Path: 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 245C8129447 for ; Fri, 4 Nov 2016 05:43:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.717 X-Spam-Level: X-Spam-Status: No, score=-5.717 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.497, 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 zstAGD0079zz for ; Fri, 4 Nov 2016 05:42:59 -0700 (PDT) Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) (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 1D4B812940C for ; Fri, 4 Nov 2016 05:42:59 -0700 (PDT) X-AuditID: 12074422-6bfff70000003e97-b1-581c82511d40 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 0A.21.16023.1528C185; Fri, 4 Nov 2016 08:42:58 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id uA4Cgv2W001598; Fri, 4 Nov 2016 08:42:57 -0400 Received: from [192.168.128.57] (static-96-237-195-53.bstnma.fios.verizon.net [96.237.195.53]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id uA4Cgt3u004175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 4 Nov 2016 08:42:56 -0400 To: Phil Hunt , Yoav Nir References: <4000ADE0-6B49-4C10-B0DB-AABA2877F4B0@gmail.com> <53180319-A2C7-47C7-97F7-32098890D0BF@oracle.com> From: Justin Richer Message-ID: <99687485-7043-b742-55dd-6f6f5354fc3c@mit.edu> Date: Fri, 4 Nov 2016 08:42:46 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <53180319-A2C7-47C7-97F7-32098890D0BF@oracle.com> Content-Type: multipart/alternative; boundary="------------D1383B32F2A12F687EBAD914" X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplleLIzCtJLcpLzFFi42IR4hTV1g1qkokw+HmEw6JjQTeTxYL5jewW S499YHJg9tg56y67x5IlP5k8Pj69xRLAHMVlk5Kak1mWWqRvl8CVMefRJOaCV7EVe/Z+YG1g XG/fxcjJISFgIvFo6gvWLkYuDiGBNiaJLb83MoEkhAQ2MErMmyMBkbjFJHGs/TczSEJYwFhi +uM3rCC2iICLxJXWbWwQRVcYJX6dXQPWzSwgKjHl0QQWEJtNQFVi+poWoDgHB6+AlcSdD7kg YRYBFYmbN14zgtiiAjES1589YgOxeQUEJU7OfALWyilgJ/Gp9QALxMgwiUU9r9gmMPLPQlI2 C0kKwjaTmLf5ITOELS/RvHU2kM0BZKtJLGtVQhZewMi2ilE2JbdKNzcxM6c4NVm3ODkxLy+1 SNdULzezRC81pXQTIyjU2V2UdjBO/Od1iFGAg1GJh3eGn3SEEGtiWXFl7iFGSQ4mJVHe0/Yy EUJ8SfkplRmJxRnxRaU5qcWHGCU4mJVEeOsagHK8KYmVValF+TApaQ4WJXFeBvev4UIC6Ykl qdmpqQWpRTBZGQ4OJQle30agRsGi1PTUirTMnBKENBMHJ8hwHqDhhSA1vMUFibnFmekQ+VOM ilLivHYgCQGQREZpHlwvKBUlvD1s+opRHOgVYd5ykCoeYBqD634FNJgJaLBbCNjgkkSElFQD o8QS5u3dU/w1JN9JnhG5EnXeMrMtrXPK7SU2AX2prnOXXq2Wjoi8tvHt4fP8zvHh71zyCsVC rSLljv66t/r7gSefSpqCK819VmgZfbibmFS86L7qPu1bBsscTp0Jcph6N/TnwaYGwf2XPohF aTy3Y1ow9eOSTHfGKo18rUMeXZfOTpmbYsKurcRSnJFoqMVcVJwIAL0Z2xsgAwAA Archived-At: Cc: id-event@ietf.org Subject: Re: [Id-event] Preliminary Agenda Uploaded 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2016 12:43:01 -0000 This is a multi-part message in MIME format. --------------D1383B32F2A12F687EBAD914 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit +1 on the format discussion. I was assuming that would at least be mentioned in the discussion of the current drafts. On 11/3/2016 1:30 PM, Phil Hunt wrote: > Apologies Justin. My bad. I wanted to get a cross-section of uses to > act as use-cases. HEART would have been a good one too. > > These are all interesting to understand in discussing SET as they all > contribute some slightly different requirements: > * Logout - A simple protocol signalling event from issuer/OP to > relying parties > * RISC - Analytical events shared peer-to-peer. > * SCIM - Dealing with provisioning events between providers where > user state is unequal > * HEART - Tracking consent in a distributed system > > In the interest of time, we can limit the amount of detailed > discussion on the proposed drafts and focus on common understanding of > the cases. > > However my hope is to determine if the current proposed drafts are > ready for adoption. If not, what changes the group would like to see > before adoption? The SET token draft is fairly close, and according to > our charter timeline we need to get that going. > > I note that on the SET token draft Justin had proposed some changes to > payloads improve parsing, I would like to keep that discussion going > on the list. I’m neutral on the final format, but we should probably > have some consensus before attempting to amend the draft (either > before or after adoption). > > Phil > > @independentid > www.independentid.com > phil.hunt@oracle.com > > > > > >> On Nov 3, 2016, at 10:10 AM, Yoav Nir > > wrote: >> >> As you can see in the agenda, we’re pretty pressed for time. There is >> a little buffer in the end, and I hope we can make use of that. >> >> Yoav >> >>> On 3 Nov 2016, at 14:38, Justin Richer >> > wrote: >>> >>> I'd like a couple minutes to talk about the consent work that we're >>> looking at using this format for. I don't anticipate it will take long. >>> >>> -- Justin >>> >>> >>> On 11/1/2016 5:36 PM, Yoav Nir wrote: >>>> Hi all >>>> >>>> https://www.ietf.org/proceedings/97/agenda/agenda-97-secevent-00.txt >>>> >>>> If I missed or forgotten something, please let me know >>>> >>>> Yoav >>>> >>>> >>>> _______________________________________________ >>>> 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 > --------------D1383B32F2A12F687EBAD914 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

+1 on the format discussion. I was assuming that would at least be mentioned in the discussion of the current drafts.


On 11/3/2016 1:30 PM, Phil Hunt wrote:
Apologies Justin. My bad.  I wanted to get a cross-section of uses to act as use-cases. HEART would have been a good one too.

These are all interesting to understand in discussing SET as they all contribute some slightly different requirements:
*  Logout - A simple protocol signalling event from issuer/OP to relying parties
*  RISC - Analytical events shared peer-to-peer.
*  SCIM - Dealing with provisioning events between providers where user state is unequal
*  HEART - Tracking consent in a distributed system

In the interest of time, we can limit the amount of detailed discussion on the proposed drafts and focus on common understanding of the cases.

However my hope is to determine if the current proposed drafts are ready for adoption. If not, what changes the group would like to see before adoption? The SET token draft is fairly close, and according to our charter timeline we need to get that going.

I note that on the SET token draft Justin had proposed some changes to payloads improve parsing, I would like to keep that discussion going on the list. I’m neutral on the final format, but we should probably have some consensus before attempting to amend the draft (either before or after adoption).


On Nov 3, 2016, at 10:10 AM, Yoav Nir <ynir.ietf@gmail.com> wrote:

As you can see in the agenda, we’re pretty pressed for time. There is a little buffer in the end, and I hope we can make use of that.

Yoav

On 3 Nov 2016, at 14:38, Justin Richer <jricher@mit.edu> wrote:

I'd like a couple minutes to talk about the consent work that we're looking at using this format for. I don't anticipate it will take long.

 -- Justin


On 11/1/2016 5:36 PM, Yoav Nir wrote:
Hi all


If I missed or forgotten something, please let me know

Yoav


_______________________________________________
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


--------------D1383B32F2A12F687EBAD914-- From nobody Tue Nov 8 15:31:12 2016 Return-Path: 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 D979C129664 for ; Tue, 8 Nov 2016 15:31:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.698 X-Spam-Level: X-Spam-Status: No, score=-5.698 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.497, 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 z5OEEVhMUCUC for ; Tue, 8 Nov 2016 15:31:10 -0800 (PST) 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 066791296A4 for ; Tue, 8 Nov 2016 15:31:09 -0800 (PST) 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 uA8NV8pl021943 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 8 Nov 2016 23:31:09 GMT Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0022.oracle.com (8.14.4/8.13.8) with ESMTP id uA8NV8QE013637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 8 Nov 2016 23:31:08 GMT Received: from abhmp0016.oracle.com (abhmp0016.oracle.com [141.146.116.22]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id uA8NV7cV017989 for ; Tue, 8 Nov 2016 23:31:08 GMT Received: from [10.0.1.5] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 08 Nov 2016 15:31:07 -0800 From: Phil Hunt Content-Type: multipart/alternative; boundary="Apple-Mail=_F7C41BD5-3D38-4717-86A7-0689CF508F54" Message-Id: Date: Tue, 8 Nov 2016 15:31:06 -0800 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: aserv0022.oracle.com [141.146.126.234] Archived-At: Subject: [Id-event] Informal working sessions 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 23:31:12 -0000 --Apple-Mail=_F7C41BD5-3D38-4717-86A7-0689CF508F54 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 We are currently scheduled next week in Seoul for our session on Wed Nov = 16 at 11:10AM Seoul time. Based on some requests I got earlier this week I requested an informal = meeting room for about 15 on Monday - 13:00 to 15:30 Thursday - 13:00 to 15:20 If we don=E2=80=99t manage to get a room, we=E2=80=99ll look to find = somewhere in the hotel or a local restaurant to hang out. Stay tuned. All this discussion may seem a bit wide open for this first meeting. = However, I think we want to do this to ultimately focus in on: * What are the key common issues that need to be in the core specs * What do the core specs need to do (or not do) vs. what do profiling = specs define The outcome of these discussions will be shared on the id-event list to = support the ongoing consensus building efforts. As agenda, a number of people have indicated interest in: * Feed definition and how to manage the content of a feed (e.g. the RISC = subscription case) E.g. how can a subscriber indicate it is interested in receiving = events about a specific subject (such as in RISC or SCIM) * Extension of SCIM Feed management to non JWT formats (e.g. TAXII/STIX, = access logs, etc - note presumes those other formats have their own = transmission methods) * How important is verification and feed status polling? * Can events be used to handle provisioning updates in FastFed IDP to = SaaS provider cases? * Inter-domain event exchange vs. OP to RP event exchange are they the = same or different (e.g. such as RISC) * JWT event payload optimization options (as proposed by Justin) * Are there other important distribution models (e.g. RISC is = bi-directional, HEART?)? Other topics? Phil @independentid www.independentid.com = phil.hunt@oracle.com = --Apple-Mail=_F7C41BD5-3D38-4717-86A7-0689CF508F54 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 We are currently scheduled next week in Seoul for our session = on Wed Nov 16 at 11:10AM Seoul time.

Based on some requests I got earlier = this week I requested an informal meeting room for about 15 on

Monday - 13:00 to = 15:30
Thursday - 13:00 to 15:20

If we don=E2=80=99t = manage to get a room, we=E2=80=99ll look to find somewhere in the hotel = or a local restaurant to hang out. Stay tuned.

All this discussion may = seem a bit wide open for this first meeting. However, I think we want to = do this to ultimately focus in on:
*  What are = the key common issues that need to be in the core specs
*  What do the core specs need to do (or not do) =  vs. what do profiling specs define

The outcome of these discussions will = be shared on the id-event list to support the ongoing consensus building = efforts.

As agenda, a number of people have indicated interest = in:

* Feed = definition and how to manage the content of a feed (e.g. the RISC = subscription case)
   E.g. how can a = subscriber indicate it is interested in receiving events about a = specific subject (such as in RISC or SCIM)
* = Extension of SCIM Feed management to non JWT formats (e.g. TAXII/STIX, = access logs, etc - note presumes those other formats have their own = transmission methods)
* How important is = verification and feed status polling?
* Can events = be used to handle provisioning updates in FastFed IDP to SaaS provider = cases?
* Inter-domain event exchange vs.  OP = to RP event exchange are they the same or different (e.g. such as = RISC)
* JWT event payload optimization options (as = proposed by Justin)
* Are there other important = distribution models (e.g. RISC is bi-directional, =  HEART?)?

Other topics?




= --Apple-Mail=_F7C41BD5-3D38-4717-86A7-0689CF508F54-- From nobody Tue Nov 8 16:18:28 2016 Return-Path: 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 983A2129501 for ; Tue, 8 Nov 2016 16:18:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.017 X-Spam-Level: X-Spam-Status: No, score=-16.017 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.497, 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 uIHQ4xTC6FMq for ; Tue, 8 Nov 2016 16:18:23 -0800 (PST) Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D9BC129532 for ; Tue, 8 Nov 2016 16:18:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8513; q=dns/txt; s=iport; t=1478650703; x=1479860303; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=pylzgkyS+SuwfAhFVx50mTJDK9WZDPxOvFBSl2NGrTk=; b=m0m+Avb5dE3Tpp9dm7Fl31gd31rPE+ZoRvdJHVK8Z7aGTuxs10B99fj+ rOxRzL+7qwnJnKPurZ4SZji/IjoTO07SoXKN1O54rEghDMKlr8VLcWGBx ZmrEn8+3EV7n5E05GVPnolzhLt5K0EvnVcrdE0J5j5ICXcgYxkFGDpEEF 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BzAQDpaiJY/5RdJa1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgnM8AQEBAQEfWH8HjTWXBo85hRqCCCWFfwKCDT8UAQIBAQEBAQEBYii?= =?us-ascii?q?EYQEBAQRJQAIBCBEDAQIOGgcyFAkIAgQBEohctEyLSgEBAQEBAQQBAQEBAQEBA?= =?us-ascii?q?R+GPoRXhGiFQAWPFIsbAZBHkBSNMIQFAR43ehuFD3KGLIEMAQEB?= X-IronPort-AV: E=Sophos;i="5.31,612,1473120000"; d="scan'208,217";a="345387140" Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Nov 2016 00:18:22 +0000 Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id uA90IMNa009856 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 9 Nov 2016 00:18:22 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; Tue, 8 Nov 2016 18:18:21 -0600 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; Tue, 8 Nov 2016 18:18:21 -0600 From: "Morteza Ansari (moransar)" To: Phil Hunt , "id-event@ietf.org" Thread-Topic: [Id-event] Informal working sessions Thread-Index: AQHSOhg9JS1fHeUnwEGqhePjBZMryaDPp9UA Date: Wed, 9 Nov 2016 00:18:21 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.6.9.160926 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.155.40.10] Content-Type: multipart/alternative; boundary="_000_D447AA855192Amoransarciscocom_" MIME-Version: 1.0 Archived-At: Subject: Re: [Id-event] Informal working sessions 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 00:18:27 -0000 --_000_D447AA855192Amoransarciscocom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable If you guys have a phone in the room, I will join the conversation remotely= (or I can provide a WX for the meeting). Cheers, Morteza From: Id-event = > on behalf of Phil Hunt = > Date: Tuesday, November 8, 2016 at 3:31 PM To: "id-event@ietf.org" > Subject: [Id-event] Informal working sessions We are currently scheduled next week in Seoul for our session on Wed Nov 16= at 11:10AM Seoul time. Based on some requests I got earlier this week I requested an informal meet= ing room for about 15 on Monday - 13:00 to 15:30 Thursday - 13:00 to 15:20 If we don't manage to get a room, we'll look to find somewhere in the hotel= or a local restaurant to hang out. Stay tuned. All this discussion may seem a bit wide open for this first meeting. Howeve= r, I think we want to do this to ultimately focus in on: * What are the key common issues that need to be in the core specs * What do the core specs need to do (or not do) vs. what do profiling spe= cs define The outcome of these discussions will be shared on the id-event list to sup= port the ongoing consensus building efforts. As agenda, a number of people have indicated interest in: * Feed definition and how to manage the content of a feed (e.g. the RISC su= bscription case) E.g. how can a subscriber indicate it is interested in receiving events = about a specific subject (such as in RISC or SCIM) * Extension of SCIM Feed management to non JWT formats (e.g. TAXII/STIX, ac= cess logs, etc - note presumes those other formats have their own transmiss= ion methods) * How important is verification and feed status polling? * Can events be used to handle provisioning updates in FastFed IDP to SaaS = provider cases? * Inter-domain event exchange vs. OP to RP event exchange are they the sam= e or different (e.g. such as RISC) * JWT event payload optimization options (as proposed by Justin) * Are there other important distribution models (e.g. RISC is bi-directiona= l, HEART?)? Other topics? Phil @independentid www.independentid.com phil.hunt@oracle.com --_000_D447AA855192Amoransarciscocom_ Content-Type: text/html; charset="iso-8859-1" Content-ID: <316DD1E37319AA4A8BA670B2210859CD@emea.cisco.com> Content-Transfer-Encoding: quoted-printable
If you guys have a phone in the room, I will join the conversation rem= otely (or I can provide a WX for the meeting).


Cheers,
Morteza

From: Id-event <id-event-bounces@ietf.org> on behalf of= Phil Hunt <phil.hunt@oracle.com= >
Date: Tuesday, November 8, 2016 at = 3:31 PM
To: "id-event@ietf.org" <id-event@ietf.org>
Subject: [Id-event] Informal workin= g sessions

We are currently scheduled next week in Seoul for our session on Wed Nov 16= at 11:10AM Seoul time.

Based on some requests I got earlier this week I requested = an informal meeting room for about 15 on

Monday - 13:00 to 15:30
Thursday - 13:00 to 15:20

If we don’t manage to get a room, we’ll look to= find somewhere in the hotel or a local restaurant to hang out. Stay tuned.=

All this discussion may seem a bit wide open for this first= meeting. However, I think we want to do this to ultimately focus in on:
*  What are the key common issues that need to be in t= he core specs
*  What do the core specs need to do (or not do)  = ;vs. what do profiling specs define

The outcome of these discussions will be shared on the id-e= vent list to support the ongoing consensus building efforts.

As agenda, a number of people have indicated interest in:

* Feed definition and how to manage the content of a feed (= e.g. the RISC subscription case)
   E.g. how can a subscriber indicate it is inter= ested in receiving events about a specific subject (such as in RISC or SCIM= )
* Extension of SCIM Feed management to non JWT formats (e.g= . TAXII/STIX, access logs, etc - note presumes those other formats have the= ir own transmission methods)
* How important is verification and feed status polling?
* Can events be used to handle provisioning updates in Fast= Fed IDP to SaaS provider cases?
* Inter-domain event exchange vs.  OP to RP event exch= ange are they the same or different (e.g. such as RISC)
* JWT event payload optimization options (as proposed by Ju= stin)
* Are there other important distribution models (e.g. RISC = is bi-directional,  HEART?)?

Other topics?

Phil

@independentid
www.ind= ependentid.com
phil.hunt@oracle.com





--_000_D447AA855192Amoransarciscocom_-- From nobody Tue Nov 8 16:27:36 2016 Return-Path: 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 EEEEC129610 for ; Tue, 8 Nov 2016 16:27:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.697 X-Spam-Level: X-Spam-Status: No, score=-5.697 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.497, 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 o3YC9_yI6QQK for ; Tue, 8 Nov 2016 16:27:33 -0800 (PST) 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 3B6EB129513 for ; Tue, 8 Nov 2016 16:27:33 -0800 (PST) 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 uA90RVeY018197 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 9 Nov 2016 00:27:31 GMT Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0022.oracle.com (8.14.4/8.13.8) with ESMTP id uA90RVhN029056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 9 Nov 2016 00:27:31 GMT Received: from abhmp0006.oracle.com (abhmp0006.oracle.com [141.146.116.12]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id uA90RUOs013524; Wed, 9 Nov 2016 00:27:31 GMT Received: from [10.0.1.4] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 08 Nov 2016 16:27:30 -0800 Content-Type: multipart/alternative; boundary=Apple-Mail-877144BC-8BA0-4723-BD98-DFB7F033A38F Mime-Version: 1.0 (1.0) From: "Phil Hunt (IDM)" X-Mailer: iPhone Mail (14B100) In-Reply-To: Date: Tue, 8 Nov 2016 16:27:28 -0800 Content-Transfer-Encoding: 7bit Message-Id: References: To: "Morteza Ansari (moransar)" X-Source-IP: aserv0022.oracle.com [141.146.126.234] Archived-At: Cc: "id-event@ietf.org" Subject: Re: [Id-event] Informal working sessions 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 00:27:35 -0000 --Apple-Mail-877144BC-8BA0-4723-BD98-DFB7F033A38F Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Not sure if we'll have services but we can certainly fire up wx, or somethin= g.=20 Phil > On Nov 8, 2016, at 4:18 PM, Morteza Ansari (moransar) = wrote: >=20 > If you guys have a phone in the room, I will join the conversation remotel= y (or I can provide a WX for the meeting). >=20 >=20 > Cheers, > Morteza >=20 > From: Id-event on behalf of Phil Hunt > Date: Tuesday, November 8, 2016 at 3:31 PM > To: "id-event@ietf.org" > Subject: [Id-event] Informal working sessions >=20 > We are currently scheduled next week in Seoul for our session on Wed Nov 1= 6 at 11:10AM Seoul time. >=20 > Based on some requests I got earlier this week I requested an informal mee= ting room for about 15 on >=20 > Monday - 13:00 to 15:30 > Thursday - 13:00 to 15:20 >=20 > If we don=E2=80=99t manage to get a room, we=E2=80=99ll look to find somew= here in the hotel or a local restaurant to hang out. Stay tuned. >=20 > All this discussion may seem a bit wide open for this first meeting. Howev= er, I think we want to do this to ultimately focus in on: > * What are the key common issues that need to be in the core specs > * What do the core specs need to do (or not do) vs. what do profiling sp= ecs define >=20 > The outcome of these discussions will be shared on the id-event list to su= pport the ongoing consensus building efforts. >=20 > As agenda, a number of people have indicated interest in: >=20 > * Feed definition and how to manage the content of a feed (e.g. the RISC s= ubscription case) > E.g. how can a subscriber indicate it is interested in receiving events= about a specific subject (such as in RISC or SCIM) > * Extension of SCIM Feed management to non JWT formats (e.g. TAXII/STIX, a= ccess logs, etc - note presumes those other formats have their own transmiss= ion methods) > * How important is verification and feed status polling? > * Can events be used to handle provisioning updates in FastFed IDP to SaaS= provider cases? > * Inter-domain event exchange vs. OP to RP event exchange are they the sa= me or different (e.g. such as RISC) > * JWT event payload optimization options (as proposed by Justin) > * Are there other important distribution models (e.g. RISC is bi-direction= al, HEART?)? >=20 > Other topics? >=20 > Phil >=20 > @independentid > www.independentid.com > phil.hunt@oracle.com >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > Id-event mailing list > Id-event@ietf.org > https://www.ietf.org/mailman/listinfo/id-event --Apple-Mail-877144BC-8BA0-4723-BD98-DFB7F033A38F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Not sure if we'll have services but we= can certainly fire up wx, or something. 

Phil

On N= ov 8, 2016, at 4:18 PM, Morteza Ansari (moransar) <moransar@cisco.com> wrote:

If you guys have a phone in the room, I will join the conversation remo= tely (or I can provide a WX for the meeting).


Cheers,
Morteza

From: Id-event <id-event-bounces@ietf.org> on behalf of P= hil Hunt <phil.hunt@oracle.com>
Date: Tuesday, November 8, 2016 at 3= :31 PM
To: "id-event@ietf.org" <id-eve= nt@ietf.org>
Subject: [Id-event] Informal working= sessions

We are currently scheduled next week in Seoul for our session on Wed Nov 16 a= t 11:10AM Seoul time.

Based on some requests I got earlier this week I requested a= n informal meeting room for about 15 on

Monday - 13:00 to 15:30
Thursday - 13:00 to 15:20

If we don=E2=80=99t manage to get a room, we=E2=80=99ll look= to find somewhere in the hotel or a local restaurant to hang out. Stay tune= d.

All this discussion may seem a bit wide open for this first m= eeting. However, I think we want to do this to ultimately focus in on:
=
*  What are the key common issues that need to be in th= e core specs
*  What do the core specs need to do (or not do)  = vs. what do profiling specs define

The outcome of these discussions will be shared on the id-ev= ent list to support the ongoing consensus building efforts.

As agenda, a number of people have indicated interest in:

* Feed definition and how to manage the content of a feed (e= .g. the RISC subscription case)
   E.g. how can a subscriber indicate it is intere= sted in receiving events about a specific subject (such as in RISC or SCIM)<= /div>
* Extension of SCIM Feed management to non JWT formats (e.g.= TAXII/STIX, access logs, etc - note presumes those other formats have their= own transmission methods)
* How important is verification and feed status polling?
* Can events be used to handle provisioning updates in FastFe= d IDP to SaaS provider cases?
* Inter-domain event exchange vs.  OP to RP event excha= nge are they the same or different (e.g. such as RISC)
* JWT event payload optimization options (as proposed by Jus= tin)
* Are there other important distribution models (e.g. RISC i= s bi-directional,  HEART?)?

Other topics?

Phil

@independentid
www.inde= pendentid.com
phil.hunt@oracle.com





____________________= ___________________________
Id-event mailing list
= Id-event@ietf.org
<= span>https://www.= ietf.org/mailman/listinfo/id-event
<= /html>= --Apple-Mail-877144BC-8BA0-4723-BD98-DFB7F033A38F-- From nobody Fri Nov 11 20:05:01 2016 Return-Path: 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 E0B3712955A; Fri, 11 Nov 2016 20:04:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.002 X-Spam-Level: X-Spam-Status: No, score=-2.002 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_H2=-0.001, 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 gqMaPO2rX8ct; Fri, 11 Nov 2016 20:04:56 -0800 (PST) Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0118.outbound.protection.outlook.com [104.47.40.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A50B11293EE; Fri, 11 Nov 2016 20:04:56 -0800 (PST) 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=rLYa3K2+1fA4JUki2yJ9e9ufBk2vX5QINeaFKA0aRsU=; b=d4u0DP0TtMvOrHFXFTLDfdAIGwe1mzuY1jBCuQ9Q1AwACtU5GcG5hUHPmUapj8sPhvrgU0HWeL0212neleMh2QsFmRae+vqHdk01FY3ybRJ+k8J2gR96buPBrVQL3aJa5JdtpKzBb2z4PLDLRIJn+4sfougow9q+mHXxcAAshIU= Received: from BN3PR03MB2355.namprd03.prod.outlook.com (10.166.74.150) by BN3PR03MB2353.namprd03.prod.outlook.com (10.166.74.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.707.6; Sat, 12 Nov 2016 04:04:43 +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.0707.013; Sat, 12 Nov 2016 04:04:43 +0000 From: Mike Jones To: Phil Hunt , "id-event@ietf.org" Thread-Topic: [scim] Fwd: New Version Notification for draft-hunt-idevent-token-06.txt Thread-Index: AdI8md1yqAtFwtLyRmKmSyShi4kPow== Date: Sat, 12 Nov 2016 04:04:43 +0000 Message-ID: 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.139] x-microsoft-exchange-diagnostics: 1; BN3PR03MB2353; 7:pe3gHjonneoSOha/8gUMcdFOkMVxgsWZFiBIbnI1/8KxtUD1OTFq6/bc0Vv0vFVm3Q8NZbUmi7b+9Vtam87+7E3uxkLKv8yLsjsyhyP4BLQ0ZPcjeyOXIuXx38I7nd8XL3cGYkgMX5y3ArlxAeMswzvJKQhL/hj6lVmf4t/g/YDNP1LDoT6ib/Jed+ml4LoqNWGwskGxg5u3z0FIMdoglnkbHHqnIl1DoZEZmZoOd6GCC7glvWhvCTIBNQm6FfKszM0DW+RT68ka/NgwjVgt/8JYT7GcY/VdmlQTiKhkdF3vddoJGDWZJQnDdVzC765ol6GVHsYzvQTFbtS+vMjzX9oMO846i4uVdf9xl4BBFzNVwJpj8Eo0/BuTlBsZ2zN3 x-ms-office365-filtering-correlation-id: af40bcbd-143f-4df9-814e-08d40ab108aa x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:BN3PR03MB2353; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(120809045254105)(192374486261705)(211936372134217)(95692535739014)(21748063052155)(146099531331640)(201166117486090); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6060229)(6045074)(6040176)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(61426038)(61427038)(6046074)(6061226); SRVR:BN3PR03MB2353; BCL:0; PCL:0; RULEID:; SRVR:BN3PR03MB2353; x-forefront-prvs: 01244308DF x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(377454003)(189002)(199003)(51444003)(377424004)(7906003)(4326007)(87936001)(10710500007)(74316002)(2900100001)(14971765001)(1680700002)(54356999)(68736007)(105586002)(99286002)(50986999)(19609705001)(16601075003)(7846002)(7736002)(2906002)(102836003)(122556002)(6116002)(86362001)(86612001)(106356001)(790700001)(3846002)(66066001)(76576001)(229853002)(2501003)(92566002)(33656002)(10290500002)(8676002)(101416001)(189998001)(5005710100001)(230783001)(97736004)(9686002)(586003)(8936002)(7696004)(3280700002)(81156014)(81166006)(5001770100001)(3660700001)(8990500004)(10090500001)(5660300001)(77096005)(7110500001)(2420400007)(15650500001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR03MB2353; 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_BN3PR03MB23553C80B757C75672449838F5BA0BN3PR03MB2355namp_" MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Nov 2016 04:04:43.4972 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR03MB2353 Archived-At: Cc: "scim@ietf.org WG" , "openid-specs-ab@lists.openid.net Ab" , "openid-specs-risc@lists.openid.net" Subject: Re: [Id-event] [scim] 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2016 04:05:00 -0000 --_000_BN3PR03MB23553C80B757C75672449838F5BA0BN3PR03MB2355namp_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SSBqdXN0IHJldmlld2VkIHRoZSBjaGFuZ2VzIGluIGRyYWZ0LWh1bnQtaWRldmVudC10b2tlbi0w NiBhbmQsIGZvciB0aGUgcmVjb3JkLCBJ4oCZbSBmaW5lIHdpdGggdGhlbS4NCg0KICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIC0tIE1pa2UNCg0K RnJvbTogc2NpbSBbbWFpbHRvOnNjaW0tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFBo aWwgSHVudA0KU2VudDogVGh1cnNkYXksIFNlcHRlbWJlciAyOSwgMjAxNiAzOjM5IFBNDQpUbzog aWQtZXZlbnRAaWV0Zi5vcmcNCkNjOiBzY2ltQGlldGYub3JnIFdHIDxzY2ltQGlldGYub3JnPjsg b3BlbmlkLXNwZWNzLWFiQGxpc3RzLm9wZW5pZC5uZXQgQWIgPG9wZW5pZC1zcGVjcy1hYkBsaXN0 cy5vcGVuaWQubmV0Pjsgb3BlbmlkLXNwZWNzLXJpc2NAbGlzdHMub3BlbmlkLm5ldA0KU3ViamVj dDogW3NjaW1dIEZ3ZDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1odW50LWlk ZXZlbnQtdG9rZW4tMDYudHh0DQoNClRoaXMgaXMgYSBtaW5vciB1cGRhdGUgdG8gdGhlIFNFVCBU b2tlbiBkcmFmdC4gIEJhc2VkIG9uIHRoZSBtYWlsaW5nIGxpc3QgZmVlZGJhY2ssIEkgbWFkZSBz b21lIHJldmlzaW9ucyB0byB0aGUgdGV4dCBvbiB0cmFuc2FjdGlvbnMgYW5kIHNlcXVlbmNpbmcu ICBJIGRyb3BwZWQgdGhlIHRlcm0g4oCcaWRlbXBvdGVuY3nigJ0gYXMgdGhpcyBpcyBub3QgcmVh bGx5IHRoZSBjb3JyZWN0IHVzYWdlIG9mIHRoZSB3b3JkLg0KDQpUaGUgaXNzdWUgSSB3YXMgdHJ5 aW5nIHRvIGdldCBhdCB3YXMgd2hldGhlciBTRVRzIGNhbiBiZSBkZWxpdmVyZWQgaW4gYW55IHNl cXVlbmNlIG9yIHdoZXRoZXIgdGhlcmUgc2VxdWVuY2UgaXMgY3JpdGljYWwuIEZvciBleGFtcGxl IGluIGFuIElkZW1wb3RlbnQgc2VydmljZSwgb25lIGNhbm5vdCBtb2RpZnkgYSByZXNvdXJjZSB0 aGF0IGhhcyBub3QgeWV0IGJlZW4gY3JlYXRlZC4gIFNvIHdoaWxlIGNvbW1hbmRzIG1heSBiZSBy ZXBlYXRlZCBhY2hpZXZpbmcgdGhlIHNhbWUgcmVzdWx0LCB0aGUgc2VxdWVuY2Ugb2YgZGlmZmVy ZW50IGNvbW1hbmRzIGlzIGNyaXRpY2FsLiA4KQ0KDQpNeSBndXQgZmVlbGluZyBvbiBzZXF1ZW5j aW5nICh3aGVuIG5lZWRlZCkgaXMgbW9zdCBsaWtlbHkgcmVzb2x2ZWQgYnkgc3BlY3MgdGhhdCBw cm9maWxlIFNFVCBUb2tlcyBieSBhZGRpbmcgc2VxdWVuY2luZyBjbGFpbSBvciBkZWZpbmluZyDi gJx0eG7igJ0gZm9yIHRoZSBwdXJwb3NlLiBUaGVyZSBtYXkgYmUgc29tZSBkZWxpdmVyeSBtZXRo b2RzIHRoYXQgY2FuIHByb3ZpZGUgc2VxdWVuY2luZywgYnV0IEkgdGhpbmsgdGhhdCBoYXMgbW9y ZSB0byBkbyB3aXRoIGRlcGxveW1lbnQgYXJjaGl0ZWN0dXJlIHJhdGhlciB0aGFuIHByb3RvY29s LiBGb3IgZXhhbXBsZSwgaW4gYSBkaXN0cmlidXRlZCBzeXN0ZW0sIHRoZSB3YXkgZXZlbnRzIGFy ZSBkZWxpdmVyZWQgdG8gYSBGZWVkIFB1Ymxpc2hpbmcgU2VydmljZSBtaWdodCBlbmFibGUgdGhl IEZlZWQgUHVibGlzaGVyIHRvIGd1YXJhbnRlZSBvcmRlci4gIFRoYXTigJlzIG5vdCB0byBzYXkg SSBoYXZlbuKAmXQgb3Zlcmxvb2tlZCBhIOKAnGR1aOKAnSBzaW1wbGUgc29sdXRpb24uDQoNClRo aXMgZHJhZnQgc2hvdWxkIGJlIGEgZ29vZCBzdGFydGluZyBwbGFjZSBmb3IgdGhlIFNFQyBFdmVu dCBXRyBwcm9wb3NlZCBjaGFydGVyLg0KDQpUaGFua3MsDQoNClBoaWwNCg0KQGluZGVwZW5kZW50 aWQNCnd3dy5pbmRlcGVuZGVudGlkLmNvbTxodHRwOi8vd3d3LmluZGVwZW5kZW50aWQuY29tPg0K cGhpbC5odW50QG9yYWNsZS5jb208bWFpbHRvOnBoaWwuaHVudEBvcmFjbGUuY29tPg0KDQoNCg0K DQoNCkJlZ2luIGZvcndhcmRlZCBtZXNzYWdlOg0KDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0 Zi5vcmc8bWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZz4NClN1YmplY3Q6IE5ldyBWZXJz aW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtaHVudC1pZGV2ZW50LXRva2VuLTA2LnR4dA0KRGF0 ZTogU2VwdGVtYmVyIDI5LCAyMDE2IGF0IDM6MjA6NDUgUE0gUERUDQpUbzogIk1pY2hhZWwgQi4g Sm9uZXMiIDxtYmpAbWljcm9zb2Z0LmNvbTxtYWlsdG86bWJqQG1pY3Jvc29mdC5jb20+PiwgIldp bGxpYW0gRGVubmlzcyIgPHdkZW5uaXNzQGdvb2dsZS5jb208bWFpbHRvOndkZW5uaXNzQGdvb2ds ZS5jb20+PiwgIlBoaWwgSHVudCIgPHBoaWwuaHVudEB5YWhvby5jb208bWFpbHRvOnBoaWwuaHVu dEB5YWhvby5jb20+PiwgIk1vcnRlemEgQW5zYXJpIiA8bW9ydGV6YS5hbnNhcmlAY2lzY28uY29t PG1haWx0bzptb3J0ZXphLmFuc2FyaUBjaXNjby5jb20+PiwgIk1pY2hhZWwgSm9uZXMiIDxtYmpA bWljcm9zb2Z0LmNvbTxtYWlsdG86bWJqQG1pY3Jvc29mdC5jb20+Pg0KDQoNCkEgbmV3IHZlcnNp b24gb2YgSS1ELCBkcmFmdC1odW50LWlkZXZlbnQtdG9rZW4tMDYudHh0DQpoYXMgYmVlbiBzdWNj ZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFBoaWwgSHVudCBhbmQgcG9zdGVkIHRvIHRoZQ0KSUVURiBy ZXBvc2l0b3J5Lg0KDQpOYW1lOiAgICAgICAgICAgICBkcmFmdC1odW50LWlkZXZlbnQtdG9rZW4N ClJldmlzaW9uOiAgICAgICAgIDA2DQpUaXRsZTogICAgICAgICAgICAgICBTZWN1cml0eSBFdmVu dCBUb2tlbiAoU0VUKQ0KRG9jdW1lbnQgZGF0ZTogICAgICAgICAgIDIwMTYtMDktMjkNCkdyb3Vw OiAgICAgICAgICAgICBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NClBhZ2VzOiAgICAgICAgICAgICAg MTkNClVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMv ZHJhZnQtaHVudC1pZGV2ZW50LXRva2VuLTA2LnR4dA0KU3RhdHVzOiAgICAgICAgIGh0dHBzOi8v ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWh1bnQtaWRldmVudC10b2tlbi8NCkh0bWxp emVkOiAgICAgICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaHVudC1pZGV2ZW50 LXRva2VuLTA2DQpEaWZmOiAgICAgICAgICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91 cmwyPWRyYWZ0LWh1bnQtaWRldmVudC10b2tlbi0wNg0KDQpBYnN0cmFjdDoNCiAgVGhpcyBzcGVj aWZpY2F0aW9uIGRlZmluZXMgdGhlIFNlY3VyaXR5IEV2ZW50IHRva2VuLCB3aGljaCBtYXkgYmUN CiAgZGlzdHJpYnV0ZWQgdmlhIGEgcHJvdG9jb2wgc3VjaCBhcyBIVFRQLiAgVGhlIFNlY3VyaXR5 IEV2ZW50IFRva2VuDQogIChTRVQpIHNwZWNpZmljYXRpb24gcHJvZmlsZXMgdGhlIEpTT04gV2Vi IFRva2VuIChKV1QpIGFuZCBtYXkgYmUNCiAgb3B0aW9uYWxseSBzaWduZWQgYW5kL29yIGVuY3J5 cHRlZC4gIEEgU0VUIGRlc2NyaWJlcyBhIHN0YXRlbWVudCBvZg0KICBmYWN0IHRoYXQgbWF5IGJl IHNoYXJlZCBieSBhbiBldmVudCBwdWJsaXNoZXIgd2l0aCBldmVudCBzdWJzY3JpYmVycy4NCg0K DQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZy b20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5k IGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZzxodHRwOi8vdG9vbHMuaWV0Zi5v cmc+Lg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQo= --_000_BN3PR03MB23553C80B757C75672449838F5BA0BN3PR03MB2355namp_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6 SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN Cgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAz IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAx NSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFs LCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90 dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3 IFJvbWFuIixzZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1w cmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0K YTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0 eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1z b25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1l Om1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGlu Ow0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250 LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnNw YW4uYXBwbGUtc3R5bGUtc3Bhbg0KCXttc28tc3R5bGUtbmFtZTphcHBsZS1zdHlsZS1zcGFuO30N CnNwYW4uYXBwbGUtdGFiLXNwYW4NCgl7bXNvLXN0eWxlLW5hbWU6YXBwbGUtdGFiLXNwYW47fQ0K c3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9u dC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzAwMjA2MDt9DQouTXNvQ2hw RGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0 O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4w aW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0 aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZh dWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwh LS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86 aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFb ZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9 InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1h bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy aSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMwMDIwNjAiPkkganVzdCByZXZpZXdlZCB0aGUgY2hh bmdlcyBpbiBkcmFmdC1odW50LWlkZXZlbnQtdG9rZW4tMDYgYW5kLCBmb3IgdGhlIHJlY29yZCwg SeKAmW0gZmluZSB3aXRoIHRoZW0uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7 Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMwMDIwNjAiPjxvOnA+Jm5ic3A7PC9vOnA+ PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6 MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj MDAyMDYwIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgLS0gTWlrZTxv OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIG5hbWU9Il9NYWls RW5kQ29tcG9zZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1 b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMwMDIwNjAiPjxvOnA+Jm5ic3A7PC9v OnA+PC9zcGFuPjwvYT48L3A+DQo8c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsRW5kQ29t cG9zZSI+PC9zcGFuPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6 c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5 OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0 eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu cy1zZXJpZiI+IHNjaW0gW21haWx0bzpzY2ltLWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhh bGYgT2YgPC9iPlBoaWwgSHVudDxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgU2VwdGVtYmVy IDI5LCAyMDE2IDM6MzkgUE08YnI+DQo8Yj5Ubzo8L2I+IGlkLWV2ZW50QGlldGYub3JnPGJyPg0K PGI+Q2M6PC9iPiBzY2ltQGlldGYub3JnIFdHICZsdDtzY2ltQGlldGYub3JnJmd0Ozsgb3Blbmlk LXNwZWNzLWFiQGxpc3RzLm9wZW5pZC5uZXQgQWIgJmx0O29wZW5pZC1zcGVjcy1hYkBsaXN0cy5v cGVuaWQubmV0Jmd0Ozsgb3BlbmlkLXNwZWNzLXJpc2NAbGlzdHMub3BlbmlkLm5ldDxicj4NCjxi PlN1YmplY3Q6PC9iPiBbc2NpbV0gRndkOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRy YWZ0LWh1bnQtaWRldmVudC10b2tlbi0wNi50eHQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp dj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8 cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIGlzIGEgbWlub3IgdXBkYXRlIHRvIHRoZSBTRVQgVG9r ZW4gZHJhZnQuICZuYnNwO0Jhc2VkIG9uIHRoZSBtYWlsaW5nIGxpc3QgZmVlZGJhY2ssIEkgbWFk ZSBzb21lIHJldmlzaW9ucyB0byB0aGUgdGV4dCBvbiB0cmFuc2FjdGlvbnMgYW5kIHNlcXVlbmNp bmcuICZuYnNwO0kgZHJvcHBlZCB0aGUgdGVybSDigJxpZGVtcG90ZW5jeeKAnSBhcyB0aGlzIGlz IG5vdCByZWFsbHkgdGhlIGNvcnJlY3QgdXNhZ2Ugb2YgdGhlIHdvcmQuDQogJm5ic3A7PG86cD48 L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48 L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgaXNzdWUgSSB3YXMg dHJ5aW5nIHRvIGdldCBhdCB3YXMgd2hldGhlciBTRVRzIGNhbiBiZSBkZWxpdmVyZWQgaW4gYW55 IHNlcXVlbmNlIG9yIHdoZXRoZXIgdGhlcmUgc2VxdWVuY2UgaXMgY3JpdGljYWwuIEZvciBleGFt cGxlIGluIGFuIElkZW1wb3RlbnQgc2VydmljZSwgb25lIGNhbm5vdCBtb2RpZnkgYSByZXNvdXJj ZSB0aGF0IGhhcyBub3QgeWV0IGJlZW4gY3JlYXRlZC4gJm5ic3A7U28gd2hpbGUgY29tbWFuZHMN CiBtYXkgYmUgcmVwZWF0ZWQgYWNoaWV2aW5nIHRoZSBzYW1lIHJlc3VsdCwgdGhlIHNlcXVlbmNl IG9mIGRpZmZlcmVudCBjb21tYW5kcyBpcyBjcml0aWNhbC4gOCk8bzpwPjwvbzpwPjwvcD4NCjwv ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TXkgZ3V0IGZlZWxpbmcgb24gc2Vx dWVuY2luZyAod2hlbiBuZWVkZWQpIGlzIG1vc3QgbGlrZWx5IHJlc29sdmVkIGJ5IHNwZWNzIHRo YXQgcHJvZmlsZSBTRVQgVG9rZXMgYnkgYWRkaW5nIHNlcXVlbmNpbmcgY2xhaW0gb3IgZGVmaW5p bmcg4oCcdHhu4oCdIGZvciB0aGUgcHVycG9zZS4gVGhlcmUgbWF5IGJlIHNvbWUgZGVsaXZlcnkg bWV0aG9kcyB0aGF0IGNhbiBwcm92aWRlIHNlcXVlbmNpbmcsIGJ1dCBJIHRoaW5rDQogdGhhdCBo YXMgbW9yZSB0byBkbyB3aXRoIGRlcGxveW1lbnQgYXJjaGl0ZWN0dXJlIHJhdGhlciB0aGFuIHBy b3RvY29sLiBGb3IgZXhhbXBsZSwgaW4gYSBkaXN0cmlidXRlZCBzeXN0ZW0sIHRoZSB3YXkgZXZl bnRzIGFyZSBkZWxpdmVyZWQgdG8gYSBGZWVkIFB1Ymxpc2hpbmcgU2VydmljZSBtaWdodCBlbmFi bGUgdGhlIEZlZWQgUHVibGlzaGVyIHRvIGd1YXJhbnRlZSBvcmRlci4gJm5ic3A7VGhhdOKAmXMg bm90IHRvIHNheSBJIGhhdmVu4oCZdCBvdmVybG9va2VkDQogYSDigJxkdWjigJ0gc2ltcGxlIHNv bHV0aW9uLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h bCI+VGhpcyBkcmFmdCBzaG91bGQgYmUgYSBnb29kIHN0YXJ0aW5nIHBsYWNlIGZvciB0aGUgU0VD IEV2ZW50IFdHIHByb3Bvc2VkIGNoYXJ0ZXIuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+ DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+ DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4N CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPlBo aWw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y bWFsIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xv cjpibGFjayI+QGluZGVwZW5kZW50aWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxhIGhy ZWY9Imh0dHA6Ly93d3cuaW5kZXBlbmRlbnRpZC5jb20iPnd3dy5pbmRlcGVuZGVudGlkLmNvbTwv YT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PGEgaHJlZj0i bWFpbHRvOnBoaWwuaHVudEBvcmFjbGUuY29tIj5waGlsLmh1bnRAb3JhY2xlLmNvbTwvYT48bzpw PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48 c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwv ZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6Ymxh Y2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05v cm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4N CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4NCjxvOnA+PC9v OnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRv bTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QmVnaW4gZm9yd2FyZGVkIG1l c3NhZ2U6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+ Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0 eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTog PC9zcGFuPg0KPC9iPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVv dDssc2Fucy1zZXJpZiI+PGEgaHJlZj0ibWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyI+ aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnPC9hPjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2 Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LWZhbWls eTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+U3ViamVjdDogTmV3IFZlcnNpb24g Tm90aWZpY2F0aW9uIGZvciBkcmFmdC1odW50LWlkZXZlbnQtdG9rZW4tMDYudHh0PC9zcGFuPjwv Yj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxi PjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJp ZiI+RGF0ZTogPC9zcGFuPg0KPC9iPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2 ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+U2VwdGVtYmVyIDI5LCAyMDE2IGF0IDM6MjA6NDUgUE0g UERUPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v cm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90Oyxz YW5zLXNlcmlmIj5UbzogPC9zcGFuPg0KPC9iPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVv dDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+JnF1b3Q7TWljaGFlbCBCLiBKb25lcyZxdW90 OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1iakBtaWNyb3NvZnQuY29tIj5tYmpAbWljcm9zb2Z0LmNv bTwvYT4mZ3Q7LCAmcXVvdDtXaWxsaWFtIERlbm5pc3MmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0 bzp3ZGVubmlzc0Bnb29nbGUuY29tIj53ZGVubmlzc0Bnb29nbGUuY29tPC9hPiZndDssICZxdW90 O1BoaWwgSHVudCZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnBoaWwuaHVudEB5YWhvby5jb20i PnBoaWwuaHVudEB5YWhvby5jb208L2E+Jmd0OywNCiAmcXVvdDtNb3J0ZXphIEFuc2FyaSZxdW90 OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1vcnRlemEuYW5zYXJpQGNpc2NvLmNvbSI+bW9ydGV6YS5h bnNhcmlAY2lzY28uY29tPC9hPiZndDssICZxdW90O01pY2hhZWwgSm9uZXMmcXVvdDsgJmx0Ozxh IGhyZWY9Im1haWx0bzptYmpAbWljcm9zb2Z0LmNvbSI+bWJqQG1pY3Jvc29mdC5jb208L2E+Jmd0 Ozwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86 cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0 eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PGJyPg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRy YWZ0LWh1bnQtaWRldmVudC10b2tlbi0wNi50eHQ8YnI+DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkg c3VibWl0dGVkIGJ5IFBoaWwgSHVudCBhbmQgcG9zdGVkIHRvIHRoZTxicj4NCklFVEYgcmVwb3Np dG9yeS48YnI+DQo8YnI+DQpOYW1lOjxzcGFuIGNsYXNzPSJhcHBsZS10YWItc3BhbiI+Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7Jm5ic3A7IDwvc3Bhbj5kcmFmdC1odW50LWlkZXZlbnQtdG9rZW48YnI+DQpSZXZpc2lvbjo8 c3BhbiBjbGFzcz0iYXBwbGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+MDY8YnI+DQpUaXRsZTo8c3BhbiBjbGFzcz0iYXBw bGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+U2VjdXJpdHkg RXZlbnQgVG9rZW4gKFNFVCk8YnI+DQpEb2N1bWVudCBkYXRlOjxzcGFuIGNsYXNzPSJhcHBsZS10 YWItc3BhbiI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7IDwvc3Bhbj4yMDE2LTA5LTI5PGJyPg0KR3JvdXA6PHNwYW4gY2xhc3M9ImFw cGxlLXRhYi1zcGFuIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPC9zcGFuPkluZGl2aWR1YWwgU3VibWlzc2lv bjxicj4NClBhZ2VzOjxzcGFuIGNsYXNzPSJhcHBsZS10YWItc3BhbiI+Jm5ic3A7Jm5ic3A7Jm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7IDwvc3Bhbj4xOTxicj4NClVSTDogJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly93d3cu aWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWh1bnQtaWRldmVudC10b2tlbi0wNi50eHQi Pmh0dHBzOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1odW50LWlkZXZlbnQt dG9rZW4tMDYudHh0PC9hPjxicj4NClN0YXR1czogJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9y Zy9kb2MvZHJhZnQtaHVudC1pZGV2ZW50LXRva2VuLyI+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRm Lm9yZy9kb2MvZHJhZnQtaHVudC1pZGV2ZW50LXRva2VuLzwvYT48YnI+DQpIdG1saXplZDogJm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly90b29scy5p ZXRmLm9yZy9odG1sL2RyYWZ0LWh1bnQtaWRldmVudC10b2tlbi0wNiI+aHR0cHM6Ly90b29scy5p ZXRmLm9yZy9odG1sL2RyYWZ0LWh1bnQtaWRldmVudC10b2tlbi0wNjwvYT48YnI+DQpEaWZmOiAm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDs8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaHVudC1p ZGV2ZW50LXRva2VuLTA2Ij5odHRwczovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQt aHVudC1pZGV2ZW50LXRva2VuLTA2PC9hPjxicj4NCjxicj4NCkFic3RyYWN0Ojxicj4NCiZuYnNw OyZuYnNwO1RoaXMgc3BlY2lmaWNhdGlvbiBkZWZpbmVzIHRoZSBTZWN1cml0eSBFdmVudCB0b2tl biwgd2hpY2ggbWF5IGJlPGJyPg0KJm5ic3A7Jm5ic3A7ZGlzdHJpYnV0ZWQgdmlhIGEgcHJvdG9j b2wgc3VjaCBhcyBIVFRQLiAmbmJzcDtUaGUgU2VjdXJpdHkgRXZlbnQgVG9rZW48YnI+DQombmJz cDsmbmJzcDsoU0VUKSBzcGVjaWZpY2F0aW9uIHByb2ZpbGVzIHRoZSBKU09OIFdlYiBUb2tlbiAo SldUKSBhbmQgbWF5IGJlPGJyPg0KJm5ic3A7Jm5ic3A7b3B0aW9uYWxseSBzaWduZWQgYW5kL29y IGVuY3J5cHRlZC4gJm5ic3A7QSBTRVQgZGVzY3JpYmVzIGEgc3RhdGVtZW50IG9mPGJyPg0KJm5i c3A7Jm5ic3A7ZmFjdCB0aGF0IG1heSBiZSBzaGFyZWQgYnkgYW4gZXZlbnQgcHVibGlzaGVyIHdp dGggZXZlbnQgc3Vic2NyaWJlcnMuPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KUGxlYXNl IG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUg b2Ygc3VibWlzc2lvbjxicj4NCnVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFy ZSBhdmFpbGFibGUgYXQgPGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnIj4NCnRvb2xzLmll dGYub3JnPC9hPi48YnI+DQo8YnI+DQpUaGUgSUVURiBTZWNyZXRhcmlhdDxvOnA+PC9vOnA+PC9w Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05v cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jv ZHk+DQo8L2h0bWw+DQo= --_000_BN3PR03MB23553C80B757C75672449838F5BA0BN3PR03MB2355namp_-- From nobody Sun Nov 13 16:00:01 2016 Return-Path: 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 EA1A712969A for ; Sun, 13 Nov 2016 15:59:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.699 X-Spam-Level: X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.497, 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 s6h4EQTSuyKx for ; Sun, 13 Nov 2016 15:59:59 -0800 (PST) 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 0537212968B for ; Sun, 13 Nov 2016 15:59:58 -0800 (PST) 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 uADNxwMD007651 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sun, 13 Nov 2016 23:59:58 GMT Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserv0022.oracle.com (8.14.4/8.13.8) with ESMTP id uADNxvTA027541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sun, 13 Nov 2016 23:59:58 GMT Received: from abhmp0019.oracle.com (abhmp0019.oracle.com [141.146.116.25]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id uADNxvtU005233 for ; Sun, 13 Nov 2016 23:59:57 GMT Received: from [31.133.137.184] (/31.133.137.184) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 13 Nov 2016 15:59:57 -0800 From: "Phil Hunt (IDM)" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Mon, 14 Nov 2016 08:59:54 +0900 Message-Id: <71BE6E1B-FA12-48F9-9AD6-23FC7ACB9F91@oracle.com> To: id-event@ietf.org X-Mailer: iPhone Mail (14B100) X-Source-IP: aserv0022.oracle.com [141.146.126.234] Archived-At: Subject: [Id-event] Informal working 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2016 00:00:00 -0000 I have booked Studio 7 from 1 till 3 this afternoon (in Seoul) for those who= would like to discuss use cases and draft details.=20 Note the official wg meeting is still Wednesday.=20 Phil= From nobody Sun Nov 13 16:52:36 2016 Return-Path: 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 A5E361293FC for ; Sun, 13 Nov 2016 16:52:34 -0800 (PST) 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, 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 KkIsigAjpD7t for ; Sun, 13 Nov 2016 16:52:33 -0800 (PST) Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::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 1C3111295F0 for ; Sun, 13 Nov 2016 16:52:33 -0800 (PST) Received: by mail-pg0-x22e.google.com with SMTP id x23so44182938pgx.1 for ; Sun, 13 Nov 2016 16:52:33 -0800 (PST) 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=78gVwe0cMCdnSwcxom28JJTRMSHqIKSpd9Uurs5FgVI=; b=nYztwMSz6Y1t+5n5Wh+QvLlwd0RzZVlDFP6efIAzp8BAgMmEWM5AnvrLNQK2u3ybVL 70Le2R6bJ+nnOOiHdmRZ1mHnlF4BiLfc+nYO0TYOety0N/mZGUS8SE7C6/NYIfu35xQ3 ZNTf3CUfrLhTvawmiATJbwFzHunZ0s6Qd7VwUqeLbca+qD0tvPrWmMwpwqsF5VWsxr89 BWVa3oCEd3Ol6w4P10lG5IRu3DojSw/J+NGOCuZvjr8ASR6OKxC3SSfRjMBoCI4MTMgM oxhQNj2DLPINNyW5KGBPJoMCN08p+StNpnvVGg+eDXCrYogZrI4MTG8SbYNeUYwSTRJV vCtg== 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=78gVwe0cMCdnSwcxom28JJTRMSHqIKSpd9Uurs5FgVI=; b=Dxjbtal2iTkT1U5lJke0aJUUAt4T5HQFh4wADVURTd28siXqsYB92a1IJmvLqGTu+W YXMKmOvj7UEHq6flA2ceh/JP36YUI/ETeSNhZwnI3g+S6s0QohXK72q6asxGDrtOqYUn 6R9BFmyii1GPJ/u9bO/SCOKWvq2GLck/XMA/pArtSVv4PjwDPZ1QR9iUW5fl0TvL6OIK CP6jwDlBzzobmJekoR4Dr7IxT1JItg4EisY2zJEkGNDIrw6/PP5NSmKyrHOcW6t6XNm5 WgmTx5LH9Kuw9cIUGCvY7h0wuSOm+ZbNybO4ABAt8lpUsjp01ozrm2U0tlUAq3s5sGBB lY1g== X-Gm-Message-State: ABUngvfWE8n8MUaug8AuDBP2/xqbU5rIUfFUK6mCo7rpzrbaXI/oWSeU0vHIQPmmR6XCfg== X-Received: by 10.98.130.1 with SMTP id w1mr30458102pfd.35.1479084752693; Sun, 13 Nov 2016 16:52:32 -0800 (PST) Received: from t2001067c03700128d1eb21313db5b045.v6.meeting.ietf.org ([2001:67c:370:128:d1eb:2131:3db5:b045]) by smtp.gmail.com with ESMTPSA id t21sm6378730pfa.1.2016.11.13.16.52.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 13 Nov 2016 16:52:32 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) From: Yoav Nir In-Reply-To: <71BE6E1B-FA12-48F9-9AD6-23FC7ACB9F91@oracle.com> Date: Mon, 14 Nov 2016 09:52:29 +0900 Content-Transfer-Encoding: quoted-printable Message-Id: References: <71BE6E1B-FA12-48F9-9AD6-23FC7ACB9F91@oracle.com> To: "Phil Hunt (IDM)" X-Mailer: Apple Mail (2.3251) Archived-At: Cc: id-event@ietf.org Subject: Re: [Id-event] Informal working 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2016 00:52:34 -0000 Thanks, Phil [with chair hat on] To clarify, this is not an official working group meeting. This is more = like a side meeting or a design team meeting. IOW the proponents of a = draft are meeting to work on their draft.=20 As always, decisions are made on the mailing list - not in side meetings = and not even in regularly scheduled meetings. That said, any activity that advances the work of the group is welcome, = especially if that happens in IETF week. So anyone who wants to join in, = more power to you. I=E2=80=99ll have to miss it personally. Thanks Yoav > On 14 Nov 2016, at 8:59, Phil Hunt (IDM) wrote: >=20 > I have booked Studio 7 from 1 till 3 this afternoon (in Seoul) for = those who would like to discuss use cases and draft details.=20 >=20 > Note the official wg meeting is still Wednesday.=20 >=20 > Phil > _______________________________________________ > Id-event mailing list > Id-event@ietf.org > https://www.ietf.org/mailman/listinfo/id-event From nobody Sun Nov 13 22:41:02 2016 Return-Path: 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 AE0AB129420 for ; Sun, 13 Nov 2016 22:41:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.698 X-Spam-Level: X-Spam-Status: No, score=-5.698 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.497, 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 s9BQTLn5MvLt for ; Sun, 13 Nov 2016 22:40:59 -0800 (PST) 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 3FAEE129459 for ; Sun, 13 Nov 2016 22:40:59 -0800 (PST) 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 uAE6ewJt000382 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 14 Nov 2016 06:40:58 GMT Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0022.oracle.com (8.14.4/8.13.8) with ESMTP id uAE6ewAL022552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 14 Nov 2016 06:40:58 GMT Received: from abhmp0017.oracle.com (abhmp0017.oracle.com [141.146.116.23]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id uAE6eu7x016182 for ; Mon, 14 Nov 2016 06:40:57 GMT Received: from [10.0.1.2] (/31.133.150.74) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 13 Nov 2016 22:40:55 -0800 From: Phil Hunt Content-Type: multipart/alternative; boundary="Apple-Mail=_48763B9E-7D20-40F0-8856-316BF646BBCD" Message-Id: <64B92F5D-4730-4BC1-9AA3-CFD956F71627@oracle.com> Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Date: Mon, 14 Nov 2016 15:40:53 +0900 References: <71BE6E1B-FA12-48F9-9AD6-23FC7ACB9F91@oracle.com> To: id-event@ietf.org In-Reply-To: X-Mailer: Apple Mail (2.3124) X-Source-IP: aserv0022.oracle.com [141.146.126.234] Archived-At: Subject: Re: [Id-event] Informal working 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2016 06:41:02 -0000 --Apple-Mail=_48763B9E-7D20-40F0-8856-316BF646BBCD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Just a quick summary of today=E2=80=99s meeting highlights from my = perspective. I think we made some good progress and it will = shape/organize thoughts for Wednesday. There is interest in having further informal discussion tomorrow morning = at 9AM-10AM in Studio 7. This meeting will likely focus on talking more = about event control plane and the need for feeds and subscriptions (see = below). The following is a summary of some of the conclusions I took away from = the meeting. Apologies I did not take minutes so this doesn=E2=80=99t = really include who said what etc. Subscription Management. In today=E2=80=99s meeting we spent a lot of time discussing the use = case for the management portion of the distribution spec. At first = there was wide disagreement on the need but we eventually all realized = that any eventing system needs a control plane. So, in the current specification, the subscription metadata is = accessible and updatable using SCIM as the control plane. A subscriber = can interrogate the control plan by calling to the publisher=E2=80=99s = SCIM endpoint. Meanwhile, the pubsub relationship is the data plane and it flows in the = reverse direction towards the subscriber. We discussed how a subscriber can interrogate SCIM to find out the = current subscription status and to do functions like pause a = subscription, initiate a verification ping, or shut a subscription off. There was less agreement that subscribers would use SCIM CREATE and = DELETE to create and cancel subscriptions over time. Many felt this = would be handled out of band. Type of Subscriptions to Manage There was interest in expanding scope of event subscriptions beyond SET = (JWT) tokens to include things like SAML events, or STIX/TAXII events. = The feeling was why not. While the distribution spec will use SETs as = examples, we can soften the language to allow for any event message = which would be dictated by mime-type (e.g. application/jwt). Sequencing There seemed to be consensus that sequencing does not need to be in the = core spec, but that we should include considerations to inform profiling = specs that using timestamps for sequencing is not advisable. Feeds vs. Subscriptions There is some interest (but no informal conclusions) in merging Feeds = and Subscriptions as a single object. There is currently not much = interest in having a feed catalogue to help subscribers discover = available Feeds. If we were to merge this stuff, it would mean adding = the events attribute to the subscription metadata. Other Delivery Methods Some are interested in defining a polling method. It=E2=80=99s not clear = whether this should go in the initial spec. Version 00 of the = distribution draft had it but it was pulled to align with the charter. SET JSON Optimization We discussed Justin=E2=80=99s optimization. The issue is what format is = best for events that have no =E2=80=9Cpayload=E2=80=9D attributes. There = were 3 possible alternatives that could be used. Version 1 (null): =E2=80=9Cevents=E2=80=9D:[=E2=80=9Csome:event:uri=E2=80=9D:null] We don=E2=80=99t like because it suggests that =E2=80=9Csome:event:uri=E2=80= =9D is NOT being asserted. Version 2: (true): =E2=80=9Cevents=E2=80=9D:[=E2=80=9Csome:event:uri=E2=80=9D:true] Might be confusing because it is a boolean value instead of a json = object. Parsers have to check what data type is present in thev value. Version 3 (empty object): =E2=80=9Cevents=E2=80=9D:[=E2=80=9Csome:event:uri=E2=80=9D:{}] This seems to be the informal favourite. It is also less characters = than null or true. It also means that the event value always has a json = object attached. Justin also pointed out that we should forbid repeated event values = within the events attribute as they may not be valid JSON or might cause = confusion.=20 Drafts Plan We discussed how adoption might work going forward. The SET spec seems = straight forward and can go ahead as planned in the charter. Given the above, we probably want to keep talking about distribution and = management/control plane. Should these be separate specifications? As = editor, my comment was that the delivery methods might depend on a lot = of metadata. I agreed I would take a look at whether we can pull this = apart fairly easily. Thanks everyone for the great discussion! Phil @independentid www.independentid.com = phil.hunt@oracle.com = > On Nov 14, 2016, at 9:52 AM, Yoav Nir wrote: >=20 > Thanks, Phil >=20 > [with chair hat on] >=20 > To clarify, this is not an official working group meeting. This is = more like a side meeting or a design team meeting. IOW the proponents of = a draft are meeting to work on their draft.=20 >=20 > As always, decisions are made on the mailing list - not in side = meetings and not even in regularly scheduled meetings. >=20 > That said, any activity that advances the work of the group is = welcome, especially if that happens in IETF week. So anyone who wants to = join in, more power to you. I=E2=80=99ll have to miss it personally. >=20 > Thanks >=20 > Yoav >=20 >> On 14 Nov 2016, at 8:59, Phil Hunt (IDM) = wrote: >>=20 >> I have booked Studio 7 from 1 till 3 this afternoon (in Seoul) for = those who would like to discuss use cases and draft details.=20 >>=20 >> Note the official wg meeting is still Wednesday.=20 >>=20 >> Phil >> _______________________________________________ >> Id-event mailing list >> Id-event@ietf.org >> https://www.ietf.org/mailman/listinfo/id-event >=20 --Apple-Mail=_48763B9E-7D20-40F0-8856-316BF646BBCD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Just a quick summary of today=E2=80=99s meeting highlights = from my perspective.  I think we made some good progress and it = will shape/organize thoughts for Wednesday.

There is interest in having further = informal discussion tomorrow morning at 9AM-10AM in Studio 7.  This = meeting will likely focus on talking more about event control plane and = the need for feeds and subscriptions (see below).
The following is a summary of some of = the conclusions I took away from the meeting. Apologies I did not take = minutes so this doesn=E2=80=99t really include who said what = etc.

Subscription Management.
In = today=E2=80=99s meeting we spent a lot of time discussing the use case = for the management portion of the distribution spec.  At first = there was wide disagreement on the need but we eventually all realized = that any eventing system needs a control plane.

So, in the current specification, the = subscription metadata is accessible and updatable using SCIM as the = control plane.  A subscriber can interrogate the control plan by = calling to the publisher=E2=80=99s SCIM endpoint.
Meanwhile, the pubsub relationship is = the data plane and it flows in the reverse direction towards the = subscriber.

We = discussed how a subscriber can interrogate SCIM to find out the current = subscription status and to do functions like pause a subscription, = initiate a verification ping, or shut a subscription off.

There was less agreement = that subscribers would use SCIM CREATE and DELETE to create and cancel = subscriptions over time. Many felt this would be handled out of = band.

Type of Subscriptions to Manage

There was interest in expanding scope = of event subscriptions beyond SET (JWT) tokens to include things like = SAML events, or STIX/TAXII events. The feeling was why not.  While = the distribution spec will use SETs as examples, we can soften the = language to allow for any event message which would be dictated by = mime-type (e.g. application/jwt).

Sequencing

There seemed to be = consensus that sequencing does not need to be in the core spec, but that = we should include considerations to inform profiling specs that using = timestamps for sequencing is not advisable.

Feeds vs. = Subscriptions

There is some interest (but no informal conclusions) in = merging Feeds and Subscriptions as a single object. There is currently = not much interest in having a feed catalogue to help subscribers = discover available Feeds.  If we were to merge this stuff, it would = mean adding the events attribute to the subscription metadata.

Other = Delivery Methods

Some are interested in defining a polling method. It=E2=80=99s = not clear whether this should go in the initial spec.  Version 00 = of the distribution draft had it but it was pulled to align with the = charter.

SET JSON Optimization

We discussed Justin=E2=80=99s = optimization. The issue is what format is best for events that have no = =E2=80=9Cpayload=E2=80=9D attributes. There were 3 possible alternatives = that could be used.

Version 1 (null):

=E2=80=9Cevents=E2=80=9D:[=E2=80=9Csome:event:uri=E2=80=9D:null= ]

We don=E2=80=99= t like because it suggests that =E2=80=9Csome:event:uri=E2=80=9D is NOT = being asserted.

Version 2: (true):

=E2=80=9Cevents=E2=80=9D:[=E2=80=9Csome:event:uri=E2=80=9D:true= ]

Might be = confusing because it is a boolean value instead of a json object. =  Parsers have to check what data type is present in thev = value.

Version = 3 (empty object):

=E2=80=9Cevents=E2=80=9D:[=E2=80=9Csome:event:uri=E2=80=9D:{}]<= /div>

This seems to be the informal favourite.  It is also = less characters than null or true.  It also means that the event = value always has a json object attached.

Justin also pointed out that we should = forbid repeated event values within the events attribute as they may not = be valid JSON or might cause confusion. 

Drafts Plan
We discussed how adoption might work going forward. The SET = spec seems straight forward and can go ahead as planned in the = charter.

Given = the above, we probably want to keep talking about distribution and = management/control plane. Should these be separate specifications? =  As editor, my comment was that the delivery methods might depend = on a lot of metadata.  I agreed I would take a look at whether we = can pull this apart fairly easily.

Thanks everyone for the great = discussion!

Phil

@independentid
www.independentid.com
phil.hunt@oracle.com





On Nov 14, 2016, at 9:52 AM, Yoav Nir <ynir.ietf@gmail.com>= wrote:

Thanks, Phil

[with chair hat = on]

To clarify, this is not an official = working group meeting. This is more like a side meeting or a design team = meeting. IOW the proponents of a draft are meeting to work on their = draft.

As always, decisions are made on = the mailing list - not in side meetings and not even in regularly = scheduled meetings.

That said, any activity = that advances the work of the group is welcome, especially if that = happens in IETF week. So anyone who wants to join in, more power to you. = I=E2=80=99ll have to miss it personally.

Thanks

Yoav

On 14 Nov 2016, at 8:59, = Phil Hunt (IDM) <phil.hunt@oracle.com> wrote:

I have booked Studio 7 from 1 till 3 this afternoon (in = Seoul) for those who would like to discuss use cases and draft details. =

Note the official wg meeting is still = Wednesday.

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


= --Apple-Mail=_48763B9E-7D20-40F0-8856-316BF646BBCD-- From nobody Mon Nov 14 16:23:40 2016 Return-Path: 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 BB4E5129479 for ; Mon, 14 Nov 2016 16:23:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.697 X-Spam-Level: X-Spam-Status: No, score=-5.697 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.497, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 4fAXFgpHHCJd for ; Mon, 14 Nov 2016 16:23:37 -0800 (PST) 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 79EF5129431 for ; Mon, 14 Nov 2016 16:23:37 -0800 (PST) Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id uAF0NaYU025490 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 15 Nov 2016 00:23:36 GMT Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id uAF0NaAV028176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 15 Nov 2016 00:23: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 uAF0NYnn014920 for ; Tue, 15 Nov 2016 00:23:35 GMT Received: from dhcp-896a.meeting.ietf.org (/31.133.138.106) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 14 Nov 2016 16:23:34 -0800 From: Phil Hunt Content-Type: multipart/alternative; boundary="Apple-Mail=_EC6E1A49-9A35-469F-B8CA-5D14AAF9E38E" Message-Id: Date: Tue, 15 Nov 2016 09:23:32 +0900 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: Subject: [Id-event] Feed / subscription discussion meeting happening now 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2016 00:23:39 -0000 --Apple-Mail=_EC6E1A49-9A35-469F-B8CA-5D14AAF9E38E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii For those that are around the Conrad, we are in Studio 7 talking about = feeds/subscriptions until 10 or so. Phil @independentid www.independentid.com = phil.hunt@oracle.com = --Apple-Mail=_EC6E1A49-9A35-469F-B8CA-5D14AAF9E38E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii For those that are around the Conrad, we are in Studio 7 = talking about feeds/subscriptions until 10 or so.




= --Apple-Mail=_EC6E1A49-9A35-469F-B8CA-5D14AAF9E38E-- From nobody Mon Nov 14 20:41:48 2016 Return-Path: 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 51E4B129501 for ; Mon, 14 Nov 2016 20:41:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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, 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 VVZFhqU2l4Hi for ; Mon, 14 Nov 2016 20:41:46 -0800 (PST) Received: from mail-pg0-x22d.google.com (mail-pg0-x22d.google.com [IPv6:2607:f8b0:400e:c05::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 E3EED1293EE for ; Mon, 14 Nov 2016 20:41:45 -0800 (PST) Received: by mail-pg0-x22d.google.com with SMTP id f188so61917098pgc.3 for ; Mon, 14 Nov 2016 20:41:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:mime-version:subject:message-id:date:to; bh=WeCFNuo6sxW0riiN3WsQmW/p74lPzsGJhydlr6Mz3iw=; b=oTULPIhBLJa2PPwEfVrKXirhbrm9CbrdEX7vkqezsdUHFAbGcNx5xxzWeZHlm1EhNJ m9Upc78DoIoYKiCv1z5rHMohI0AyIju90h02DAxyKrXJ6U4JyMbT53TbHo0CJ3TnVTE/ Nz+LDKZI6Ttse1162E1NOI1/8zUeGRVaoUpkWZOHuCxq5egnDGs9c7rCpPWUcQJXdMAD EeUA5RjsvkFV4+jB9t0AB+Qc/DrKvZbgBhcec6nSefyfHhgMhJXOAshx48QsOzJwMKfx yF6amzPwFPehLLm2sCCx/aT3Fl1CBzfGpTavty0rr4mG5kgLORECpUAfRdR+eV4yQCXW aFtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=WeCFNuo6sxW0riiN3WsQmW/p74lPzsGJhydlr6Mz3iw=; b=hGahNe7tT9Z+4II6a8RQrUWcw1xFTxAk9CGYJFmSY0RsgJsjLpRTfoEx3wBdn+8IGj v+OdHgVX4ivK4dXIgsarDwLmG9gQQeKXNa7mDwqwOadLulrX5JWbfMT5pfmiekjzHaa/ Ahx+2xK6JdAgavJLk/E3qV9lgM5B5loHRbmlpXkBX6NFhYImnk+QbWjkpEe+Ued9FE9J DrGxT1+8XPwpFlozpXBe++v8mzgsf3mjjARaoBW42TG94xDnFV/fpwH3gHGlx4ROCjlp bR5l86oMHASksoEfQUI79ZfVOBxIh2cIOTvjXtq8YLhXSHLI0OILk239o28ikxhJ3MPP DQbw== X-Gm-Message-State: ABUngvfL7q1wX2WfgUo2IFcL7sJxVl+978Gc/Ai3iw6Hf/ClBm0RjQWJk8DvPieY1UmxGA== X-Received: by 10.99.103.198 with SMTP id b189mr75410959pgc.81.1479184905304; Mon, 14 Nov 2016 20:41:45 -0800 (PST) Received: from t2001067c03700128401ff44bdf28fc46.v6.meeting.ietf.org ([2001:67c:370:128:401f:f44b:df28:fc46]) by smtp.gmail.com with ESMTPSA id yc7sm38823661pab.24.2016.11.14.20.41.44 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Nov 2016 20:41:44 -0800 (PST) From: Yoav Nir Content-Type: multipart/alternative; boundary="Apple-Mail=_C2907DCC-8D25-4587-BB24-B368308D6836" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Message-Id: Date: Tue, 15 Nov 2016 13:41:39 +0900 To: id-event@ietf.org X-Mailer: Apple Mail (2.3251) Archived-At: Subject: [Id-event] Slides uploaded, minute taker and Jabber relay 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2016 04:41:47 -0000 --Apple-Mail=_C2907DCC-8D25-4587-BB24-B368308D6836 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi all. I=E2=80=99ve just uploaded the slides for tomorrow=E2=80=99s session. = Get them here: = https://datatracker.ietf.org/meeting/97/materials#secevent = Also, we need a minute taker and a jabber relay. Preferably not people = who are also presenting. Please contact me if you=E2=80=99d like to = volunteer Thanks Yoav Nir (as acting chair)= --Apple-Mail=_C2907DCC-8D25-4587-BB24-B368308D6836 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi all.

I=E2=80=99ve just uploaded the slides for tomorrow=E2=80=99s = session. Get them here: https://datatracker.ietf.org/meeting/97/materials#secevent<= /div>

Also, we need = a minute taker and a jabber relay.  Preferably not people who are = also presenting. Please contact me if you=E2=80=99d like to = volunteer

Thanks

Yoav Nir
(as acting = chair)
= --Apple-Mail=_C2907DCC-8D25-4587-BB24-B368308D6836-- From nobody Mon Nov 14 21:42:52 2016 Return-Path: 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 E28A1129542 for ; Mon, 14 Nov 2016 21:42:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.699 X-Spam-Level: X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=unavailable 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 K7kILRBd_2sq for ; Mon, 14 Nov 2016 21:42:50 -0800 (PST) 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 A62C612954A for ; Mon, 14 Nov 2016 21:34:55 -0800 (PST) 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 uAF5Ypwj014078 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 Nov 2016 05:34:52 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 uAF5YpZx004963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 Nov 2016 05:34:51 GMT Received: from abhmp0003.oracle.com (abhmp0003.oracle.com [141.146.116.9]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id uAF5Yntb015619; Tue, 15 Nov 2016 05:34:50 GMT Received: from [10.0.1.3] (/31.133.150.74) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 14 Nov 2016 21:34:49 -0800 From: "Phil Hunt (IDM)" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Tue, 15 Nov 2016 14:34:46 +0900 Message-Id: <73751460-70B3-44C1-B293-8881CABAF538@oracle.com> To: id-event@ietf.org X-Mailer: iPhone Mail (14B100) X-Source-IP: aserv0021.oracle.com [141.146.126.233] Archived-At: Cc: Tony Nadalin , Dick Hardt , Marius Scurtescu Subject: [Id-event] Wed morning session on pubsub data model 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2016 05:42:51 -0000 We decided today to keep talking about the publish/subscribe data model and t= he process for controlling and managing event streams.=20 We plan to meet tomorrow at 9 in studio 7 again.=20 This is in addition to tomorrows formal meeting.=20 All are welcome.=20 Phil= From nobody Tue Nov 15 16:59:47 2016 Return-Path: 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 EA14A1293D8 for ; Tue, 15 Nov 2016 16:59:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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, 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 DNVIWT9T63Tq for ; Tue, 15 Nov 2016 16:59:44 -0800 (PST) Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e: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 A1E61126CD8 for ; Tue, 15 Nov 2016 16:59:44 -0800 (PST) Received: by mail-pg0-x22c.google.com with SMTP id x23so69787869pgx.1 for ; Tue, 15 Nov 2016 16:59:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=60J0JVqBll/rrszngHO2XoilYcUiUa0zu0T3MSwFdTM=; b=oL7dkIdEbTkq/HWEeywzjbWR4tH9rWhl54ncUxg1gibaiIZHI1J3axgDZ7aRwekwAB B2XZw8vTG9XVkWu4Rl/5eUk4mci3uYF/3OiRWLI/c38+xJZpHLXMbPdpnPsPn/9a24uT qJXPMIu7fmQzUUzzCk7NdrSyLGoDvBlvxST0gjxJaZ1UXBPxXPZAEpFrMnf9HD+Fj5gg G8wj/NlI1A1Qy/cG5SIiCVlH/1ZGfDbi4EOTIw+yvB1DHRqV8IXeQq9nMX0H9nzskvnJ OsalW4Zk6XI7tl2lFz9WQkGskYedR+VdSjR/ktF/5rckt0tPUFMHRpUd7bowB7GaSLOO pzOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=60J0JVqBll/rrszngHO2XoilYcUiUa0zu0T3MSwFdTM=; b=VKryVsu7pNnbHdDBSkvzeqhxY256LRMpFijE3pwJbf8K+a4SHJ9GNiPSe8+Ty6BhAK 7EcqHpMk+ciMPp5aWWgIxpK78w5WU7pkWhJb+DBDhEtnqdFWpRK5q1s7ZxeUt8tRne6t oDq3YCV3Kl6YoeUZiSonbsR7NjgR4PCEgd6J8/JRWYAuVhOKKBj2w2Xvnnylam2eoHPt 8VVoU6uiNEWr4B3uOuf3pWhG0h+4b7qKyFaYAPgS1Fahw5cr44lqn3yfab4gSxSc19HI mvyF8BNXtTs3nqTBXVlGER48isoW6wsrrEoWT/b5SdDjnuoZCX1rXB6tGjEpzaKpxF6h zj3Q== X-Gm-Message-State: ABUngvf4oYAXf1olCPeE2wQItd8FGqfTrxy10PBfIbyOPkp0cT/0OCucDyHkPxLAGvIVkQ== X-Received: by 10.99.60.69 with SMTP id i5mr2088578pgn.158.1479257984112; Tue, 15 Nov 2016 16:59:44 -0800 (PST) Received: from t2001067c03700128b0cd002daee86f00.v6.meeting.ietf.org (t2001067c03700128b0cd002daee86f00.v6.meeting.ietf.org. [2001:67c:370:128:b0cd:2d:aee8:6f00]) by smtp.gmail.com with ESMTPSA id a22sm46804101pfg.7.2016.11.15.16.59.42 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Nov 2016 16:59:43 -0800 (PST) From: Yoav Nir Content-Type: multipart/alternative; boundary="Apple-Mail=_A0D6A633-94FC-4ADC-9AB6-3FE5F7121FC8" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Date: Wed, 16 Nov 2016 09:59:39 +0900 References: To: id-event@ietf.org In-Reply-To: Message-Id: <443134EA-2A6C-42B5-A13F-CE40A21A02F5@gmail.com> X-Mailer: Apple Mail (2.3251) Archived-At: Subject: Re: [Id-event] Slides uploaded, minute taker and Jabber relay 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2016 00:59:46 -0000 --Apple-Mail=_A0D6A633-94FC-4ADC-9AB6-3FE5F7121FC8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Reminder: I am still looking for Jabber scribe and Minute taker. Please volunteer. Yoav > On 15 Nov 2016, at 13:41, Yoav Nir wrote: >=20 > Hi all. >=20 > I=E2=80=99ve just uploaded the slides for tomorrow=E2=80=99s session. = Get them here: = https://datatracker.ietf.org/meeting/97/materials#secevent = >=20 > Also, we need a minute taker and a jabber relay. Preferably not = people who are also presenting. Please contact me if you=E2=80=99d like = to volunteer >=20 > Thanks >=20 > Yoav Nir > (as acting chair) --Apple-Mail=_A0D6A633-94FC-4ADC-9AB6-3FE5F7121FC8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Reminder: I am still looking for Jabber scribe and Minute = taker.

Please = volunteer.

Yoav

On 15 Nov 2016, at 13:41, Yoav = Nir <ynir.ietf@gmail.com> wrote:

Hi all.

I=E2=80=99ve just = uploaded the slides for tomorrow=E2=80=99s session. Get them = here: https://datatracker.ietf.org/meeting/97/materials#secevent<= /div>

Also, we need = a minute taker and a jabber relay.  Preferably not people who are = also presenting. Please contact me if you=E2=80=99d like to = volunteer

Thanks

Yoav Nir
(as acting = chair)

= --Apple-Mail=_A0D6A633-94FC-4ADC-9AB6-3FE5F7121FC8-- From nobody Tue Nov 15 19:58:49 2016 Return-Path: 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 12E941294F7 for ; Tue, 15 Nov 2016 19:58:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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, 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 HNC2gT_TyEgw for ; Tue, 15 Nov 2016 19:58:46 -0800 (PST) Received: from mail-pg0-x242.google.com (mail-pg0-x242.google.com [IPv6:2607:f8b0:400e:c05::242]) (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 4790A129431 for ; Tue, 15 Nov 2016 19:58:46 -0800 (PST) Received: by mail-pg0-x242.google.com with SMTP id p66so13492045pga.2 for ; Tue, 15 Nov 2016 19:58:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:mime-version:subject:message-id:date:to; bh=5T3oi0yQObAOqIokJ+G6Ns9oU81auMMph/wC4qydEAY=; b=uGHXLu7RhJQUCEY7ebdCpm0u7TCSnGtNSrQeO4wv8hg80z0AyRi+zFj6SMeyTpr8kT r6f3JiZ98R+7o9YvCf1a3LtOsD2lu9YE7AdTK8DL89pkTbXVjYFx9qNem7lgd3a1Mpzv 7VZM6PR4GoYVti9t/kP4PzRun6UeGreeXZPs3xFsI28f1KoMoh1QI14Gr7mbcIxLjyTi 2s5HuJ9BKOjJivh4H/OB0u5xR1Pq+zlYVpiROgn4LfeHBDrzoftl20AQc81ttrsqndpT qGg08xvjkmRI/YLkwiwdBcxsS1LkEqHL6YS5K3TkDW1CasG7JvQELUaoPQxkKtBmMPwh R9nA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=5T3oi0yQObAOqIokJ+G6Ns9oU81auMMph/wC4qydEAY=; b=lLbKv4tk5ODRnsltd1nArziO6tX0mWmu8QMWOSvOjP7DgAnIl30M08bygdKcZsperY bk3Q/iL2AGH8KeAhDbQfbTuOujvhQJ7Qj5BackJEPp6WZcVEl4+0axLpcLwopjEUsoQc 2vvLAQTghrZ+P++l7+NnbsMqW5gisNjhODLje3P1sdd02jMu+QccEvppMr5j4glrTj5d xqMij6wwArKcqqyMTPjVrWNPLAumRjS1r9vSi+d5expj2BJg0KplwjDwBPIV6q1ZHMDr xWEeV0+rGWUUnmhw3xvSQM3lepG5K8k2Nj4m0toEBxeE9MGycgFVcp+/uzTZqvFzK0sn GBLQ== X-Gm-Message-State: ABUngvfpX8w/RmUUVZt1YnxldYX3QdsofpaUJ9h3cDOopiJUEKYVEZtQmu+/3gey3AuVrA== X-Received: by 10.98.15.206 with SMTP id 75mr1592908pfp.105.1479268725551; Tue, 15 Nov 2016 19:58:45 -0800 (PST) Received: from t2001067c03700128ac67fa2b472bc1c2.v6.meeting.ietf.org ([2001:67c:370:128:ac67:fa2b:472b:c1c2]) by smtp.gmail.com with ESMTPSA id 89sm42593234pfi.70.2016.11.15.19.58.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Nov 2016 19:58:44 -0800 (PST) From: Yoav Nir Content-Type: multipart/alternative; boundary="Apple-Mail=_1D12613C-23FD-4E98-9CB7-CD41AE8C992F" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Message-Id: <2ACCC970-D108-4847-9B4E-D627A2F85C4C@gmail.com> Date: Wed, 16 Nov 2016 12:58:39 +0900 To: id-event@ietf.org X-Mailer: Apple Mail (2.3251) Archived-At: Subject: [Id-event] Raw minutes of today's session 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2016 03:58:48 -0000 --Apple-Mail=_1D12613C-23FD-4E98-9CB7-CD41AE8C992F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Thanks again to Stefan Winter for taking minutes. A dump from Etherpad = is below. I will post more official minutes later on. Yoav IETF97: Minutes of the secevent session =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Note Well, Preliminaries Agenda Bashing: Agenda accepted Chair recapped history of working group formation, current WG status Handful of people read the WG drafts prior to the meeting Presentations: =20 RISC: (presenter presented slide deck as uploaded to meeting = materials) no comments from the audience OIDC Back-Channel Logout...: (presenter presented slide deck as uploaded to meeting = materials) Justin Richer Placement of Issuer and Subject in the tokens. Makes sense = here (IdP is generating the logout message itself), but needs to be = generalised for cases where third party sends events. Complex topic, = needs offline discussion. Security Events Draft Proposals: Background: SCIM events - good for single-master events, but not = multi-master work going on on multi-master synchronisation SCIM shut down - so need a new place to continue work set of events was similar to what RISC presentation had Idea: there are multiple approaches to the same problem - can = this be reconciled into a core protocol? (presenter presented slide deck as uploaded to meeting = materials) SET Distribution HTTP POST, which needs to be parsed and checked = before returning OK (On slide "Drafts") Kathleen Moriarty: in early stage, so let's consider broad set of options: what = about XMPP Grid? Has pub/sub support, more than ten=20 vendors doing it. XMPP Grid works bidirectionally, and = supports multitude of data formats. Nancy Cam-Winget: confirmed XMPP details. Needs secevents to clarify what their = requirements re bilateralness are, but should be a good match. (continuing to remainder of slide deck) Kathleen Moriarty: on STIX/TAXII. STIX is huge effort, might end up using sth like this. = TAXII some kind of transport, maybe too complex/bloated; keep hearing that it doesn't work. STIX and this work = can co-exist; no need to merge into STIX. Ben ... : "verify" operation: what is the scope? Scope is limited to verify that = parsing of the events works, and map to an account; not about verifying the account itself (i.e. not checking = existence of an email address property etc.) Remote Comment: EMpty HTTP 202 response means "OK"? Shouldn't there be a JSON object = inside? John Bradley: subject to WG discussion. Personally in favour of an empty message. Conclusion: Will be put into draft; can be changed during WG process at = any time. John Bradley: Should claims be in the object? Does subject have to be in the object? Subject at top-level, mostly for legacy reasons. Issue can be discussed = on the list. Conclusions from Chair: no humming, as too few people have read drafts. Please read drafts. Discussions should please happen on-list. There was some criticism on existence of the WG. Bob: great place for /Identity/ security events. It is difficult to = follow discussions as an outsider. Data models for the work here would = be very useful to assess applicability in other areas (e.g. IoT). Kathleen Moriarty: probably just a naming problem: wg "security events" may suggest = larger scope. WG names not very important in the long run. Yaron Sheffer: how about a use case document? Could shed light on the lingering = privacy issues. Kathleen Moriarty: request for more/new working group chairs. Justin Richer: driving force and main use case: transaction approval (not only re = identity, also "release medical record" type). William Denniss: JWT is a IETF specification, so this use of it also inside process. --Apple-Mail=_1D12613C-23FD-4E98-9CB7-CD41AE8C992F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Thanks again to Stefan Winter for taking minutes.  A = dump from Etherpad is below.

I will post more official minutes later on.

Yoav


IETF97: Minutes of the secevent = session
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Note Well, Preliminaries

Agenda Bashing: Agenda accepted

Chair recapped history of working group formation, = current WG status
Handful of people read the WG drafts prior to the = meeting

Presentations:
    
    RISC:
        = (presenter presented slide deck as uploaded to meeting = materials)
        no = comments from the audience

    OIDC Back-Channel = Logout...:
        = (presenter presented slide deck as uploaded to meeting = materials)
        Justin = Richer
          Placement = of Issuer and Subject in the tokens. Makes sense here (IdP is generating = the logout message itself), but needs to be generalised for cases where = third party sends events. Complex topic, needs offline = discussion.

    Security Events Draft = Proposals:
        = Background:
  •         SCIM = events - good for single-master events, but not = multi-master
  •         work = going on on multi-master synchronisation
  •         SCIM = shut down - so need a new place to continue = work
  •         set of = events was similar to what RISC presentation = had
  •         Idea: = there are multiple approaches to the same problem - can this be = reconciled into a core protocol?
        = (presenter presented slide deck as uploaded to meeting = materials)
        SET = Distribution HTTP POST, which needs to be parsed and checked before = returning OK
        (On = slide "Drafts")
        Kathleen = Moriarty:
          in early = stage, so let's consider broad set of options: what about XMPP Grid? Has = pub/sub support, more than ten 
          vendors = doing it. XMPP Grid works bidirectionally, and supports multitude of = data formats.
  • Nancy Cam-Winget:
  • confirmed XMPP details. Needs secevents to clarify = what their requirements re bilateralness are, but should be a good = match.
  • (continuing to remainder of slide = deck)
  • Kathleen Moriarty:
  •   on STIX/TAXII. STIX is huge effort, might = end up using sth like this. TAXII some kind of transport, maybe = too
  •   complex/bloated; keep hearing that it = doesn't work. STIX and this work can co-exist; no need to merge into = STIX.
  • Ben ... :
  •   "verify" operation: what is the scope? Scope = is limited to verify that parsing of the events works, and map to = an
  •   account; not about verifying the account = itself (i.e. not checking existence of an email address property = etc.)
  • Remote Comment:
  •   EMpty HTTP 202 response means "OK"? = Shouldn't there be a JSON object inside?
  • John Bradley:
  •   subject to WG discussion. Personally in = favour of an empty message.
  • Conclusion: Will be put into draft; can be changed = during WG process at any time.
  • John Bradley:
  •   Should claims be in the object? Does subject = have to be in the object?
  • Subject at top-level, mostly for legacy reasons. = Issue can be discussed on the list.
Conclusions from Chair:
    no humming, as too few people = have read drafts. Please read drafts.
    Discussions should please happen = on-list.
    There was some criticism on = existence of the WG.
    Bob:
        great = place for /Identity/ security events. It is difficult to follow = discussions as an outsider. Data models for the work here would be very = useful to assess applicability in other areas (e.g. = IoT).
  •   Kathleen = Moriarty:
  •   probably just a naming problem: wg "security = events" may suggest larger scope. WG names not very important in the = long run.
  • Yaron Sheffer:
  •   how about a use case document? Could shed = light on the lingering privacy issues.
  • Kathleen Moriarty:
  •   request for more/new working group = chairs.
  • Justin Richer:
  •   driving force and main use case: transaction = approval (not only re identity, also "release medical record" = type).
  • William Denniss:
  •   JWT is a IETF specification, so this use of = it also inside process.
= --Apple-Mail=_1D12613C-23FD-4E98-9CB7-CD41AE8C992F-- From nobody Thu Nov 17 22:25:56 2016 Return-Path: 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 6E1D11296C8; Thu, 17 Nov 2016 22:25:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.698 X-Spam-Level: X-Spam-Status: No, score=-5.698 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.497, 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 6vBglRpgEFUP; Thu, 17 Nov 2016 22:25:52 -0800 (PST) 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 A17A5129497; Thu, 17 Nov 2016 22:25:52 -0800 (PST) Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id uAI6Pm7q032504 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 18 Nov 2016 06:25:48 GMT Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id uAI6Pm6x023371 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 18 Nov 2016 06:25:48 GMT Received: from abhmp0017.oracle.com (abhmp0017.oracle.com [141.146.116.23]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id uAI6Plcn021197; Fri, 18 Nov 2016 06:25:47 GMT Received: from [10.56.16.123] (/116.84.110.2) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 17 Nov 2016 22:25:47 -0800 From: Phil Hunt Content-Type: multipart/alternative; boundary="Apple-Mail=_AFAC2864-6AB2-4922-B18C-F84832CF6BA7" Date: Fri, 18 Nov 2016 15:25:42 +0900 Message-Id: <8CCC780F-E02B-4BC7-B4EF-7743F088FD05@oracle.com> 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: Cc: Tony Nadalin , Marius Scurtescu , Nancy Cam-Winget , Dick Hardt , "scim@ietf.org WG" , PRATEEK MISHRA , openid-specs-risc@lists.openid.net, Morteza Ansari Subject: [Id-event] Follow-up from IETF97 - XMPP Grid 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2016 06:25:54 -0000 --Apple-Mail=_AFAC2864-6AB2-4922-B18C-F84832CF6BA7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Note: cross-posted to IdEvents, SCIM, and OpenID RISC mailing lists. At the end of the Sec Events meeting, Nancy Cam-Winget mentioned the = XMPP-Grid draft which is about to go WGLC. See: https://datatracker.ietf.org/doc/draft-ietf-mile-xmpp-grid/ = I have taken a look and my initial impression is we should look at it: 1. Bi-directional signalling. A few use-cases (e.g. RISC) have = indicated a need to enable bi-directional flow. While HTTP post is = simple, it would involve managing two separate connections. It may be = possible XMPP-Grid turns out to be logistically simpler? 2. Firewall issues (e.g. cloud-to-enterprise). XMPP could be a good way = to avoid needing =E2=80=9Cpolling=E2=80=9D solutions such as HTTP GET = when it is inconvenient to open access for an HTTP POST. This may be of = great interest to the SCIM Synchronization work that some are = considering. 3. Fan-out distribution: It could potentially handle publishing to = multiple receivers simultaneously. This is particularly useful in cases = where multiple data centers or server clusters need to receive the = events. For example, in OpenID Connect logout, the ability to notify = all members of a Single-sign-on audience for ID Tokens. 4. It supports multiple data formats (e.g. not just JWTs) 5. There is a control-plane in XMPP-grid that may also prove useful for = some or all of our requirements. 6. While it seems more complex, it can provide simplification overall. = Thought over-kill for one-way pub-sub, XMPP-Grid might be more of a = universal solution for all cases. Recalling Kathleen=E2=80=99s comments = about TAXII, this could be one way to avoid connection-itus and = brokering. While this may seem like a very positive review on my part, I do suspect = that many will find this over-kill.=20 ACTION REQUESTED: I=E2=80=99d like to get a feel from the Sec Events community about this = idea. Would you like to see this idea explored further on the list? A. Does this look like something we should consider? What additional = capabilities do you see XMPP Grid bringing? B. If you see this as unnecessary, what would be your concerns? ps. I=E2=80=99m working on the other action items and hope to post a new = SEC Token draft early next week. Thanks for a great kick-off meeting! Phil @independentid www.independentid.com = phil.hunt@oracle.com = --Apple-Mail=_AFAC2864-6AB2-4922-B18C-F84832CF6BA7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Note: cross-posted to IdEvents, SCIM, and = OpenID RISC mailing lists.

At = the end of the Sec Events meeting, Nancy Cam-Winget mentioned the = XMPP-Grid draft which is about to go WGLC. See:
  https://datatracker.ietf.org/doc/draft-ietf-mile-xmpp-grid/=

I have taken = a look and my initial impression is we should look at it:

1. Bi-directional = signalling.  A few use-cases (e.g. RISC) have indicated a need to = enable bi-directional flow. While HTTP post is simple, it would involve = managing two separate connections. It may be possible XMPP-Grid turns = out to be logistically simpler?

2. Firewall issues (e.g. = cloud-to-enterprise). XMPP could be a good way to avoid needing = =E2=80=9Cpolling=E2=80=9D solutions such as HTTP GET when it is = inconvenient to open access for an HTTP POST.  This may be of great = interest to the SCIM Synchronization work that some are = considering.

3. = Fan-out distribution: It could potentially handle publishing to multiple = receivers simultaneously. This is particularly useful in cases where = multiple data centers or server clusters need to receive the events. =  For example, in OpenID Connect logout, the ability to notify all = members of a Single-sign-on audience for ID Tokens.

4. It supports multiple = data formats (e.g. not just JWTs)

5. There is a control-plane in = XMPP-grid that may also prove useful for some or all of our = requirements.

6.= While it seems more complex, it can provide simplification overall. = Thought over-kill for one-way pub-sub, XMPP-Grid might be more of a = universal solution for all cases. Recalling Kathleen=E2=80=99s comments = about TAXII, this could be one way to avoid connection-itus and = brokering.

While= this may seem like a very positive review on my part, I do suspect that = many will find this over-kill. 

ACTION REQUESTED:
I=E2=80=99d like to get a feel from the Sec Events community = about this idea. Would you like to see this idea explored further on the = list?

A. =  Does this look like something we should consider?  What = additional capabilities do you see XMPP Grid bringing?

B.  If you see this = as unnecessary, what would be your concerns?

ps. I=E2=80=99m working on the other = action items and hope to post a new SEC Token draft early next = week.

Thanks = for a great kick-off meeting!




= --Apple-Mail=_AFAC2864-6AB2-4922-B18C-F84832CF6BA7-- From nobody Sat Nov 19 11:36:03 2016 Return-Path: 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 EB9DB129471 for ; Sat, 19 Nov 2016 11:36:01 -0800 (PST) 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_H4=-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 w8mHhV4P7ovS for ; Sat, 19 Nov 2016 11:35:59 -0800 (PST) Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0102.outbound.protection.outlook.com [104.47.42.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF920129576 for ; Sat, 19 Nov 2016 11:35:59 -0800 (PST) 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=oIpUAA7XXe56nuYxmWLYJgYU93bB0b32zwuFoCqm07I=; b=FJoeVLzMbpJ2AhMWPrm1i1aRwc5IfYs77et8V6+7V+jsGBUwWjJKJZWHLVvSBBZj8TLe3iv6foUTcd/4Q4nG2DESz/Y2lhDiFR0yk4lhtoakPSHcvVzh23Kp07HuEc2SQbOXxSRKcOeiZqhjipzZzcl2qIuBuB28F9swoY4BE7U= Received: from BN3PR03MB2355.namprd03.prod.outlook.com (10.166.74.150) by BN3PR03MB2353.namprd03.prod.outlook.com (10.166.74.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.721.10; Sat, 19 Nov 2016 19:35:55 +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.0721.017; Sat, 19 Nov 2016 19:35:55 +0000 From: Mike Jones To: "id-event@ietf.org" Thread-Topic: MILE XMPP Grid doc Thread-Index: AdJCm2TswR2E3iriRXiA26xuLdSHnw== Date: Sat, 19 Nov 2016 19:35:55 +0000 Message-ID: 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.133] x-microsoft-exchange-diagnostics: 1; BN3PR03MB2353; 7:qUmF1ijYTtOQJilWqXx7Ss1jr1Z0FP3rxRsQcpwKfdRRsFuOXmC/6GspqJbQ2D6557l8ljYpogVSovsjH8ORnFYxC+woQPdMNO6wb3Be9K/bFEWWdvnBMxkfUOWYjl7hbkGFDhG6AuxXaYiv01zfUSJ3E+eYGKf2R0o2YbBV5BVZO+41DI5gVhFs7yYovBNukeDTxo3d9sspLa9j28YMN1uaPC0J7KJMOI983tLVGFYXVGXe8WLMw5oQAI0qKRTbnqyJdPvNW9vqNd3P1ghoD27wvodn2fsKAVKn52ewypihUQ48pm2oQW9I7OkBStMBv+S7WtuoeSSD3QlE4Kz9Qz5cY66twJkHLDcuShXEj61fuziQs7InacyB1qY5Yeo5 x-ms-office365-filtering-correlation-id: c6424c44-3f1f-4437-4eb6-08d410b347af x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:BN3PR03MB2353; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(192374486261705)(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040307)(6060326)(6045199)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026)(61426038)(61427038)(6061324)(6046074)(6041248)(6042181); SRVR:BN3PR03MB2353; BCL:0; PCL:0; RULEID:; SRVR:BN3PR03MB2353; x-forefront-prvs: 0131D22242 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(199003)(189002)(2351001)(6916009)(74316002)(105586002)(106356001)(122556002)(5660300001)(9686002)(81166006)(81156014)(7696004)(8676002)(110136003)(87936001)(38730400001)(606004)(7736002)(7846002)(2501003)(86612001)(6506003)(3280700002)(2906002)(3660700001)(5630700001)(102836003)(790700001)(3846002)(86362001)(33656002)(6116002)(5640700001)(7906003)(2900100001)(77096005)(92566002)(5005710100001)(10090500001)(99286002)(189998001)(3480700004)(76576001)(450100001)(8936002)(66066001)(68736007)(50986999)(101416001)(97736004)(8990500004)(10290500002)(54356999)(107886002)(217873001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR03MB2353; H:BN3PR03MB2355.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX: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_BN3PR03MB2355040B043EC496C3491B15F5B30BN3PR03MB2355namp_" MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Nov 2016 19:35:55.1201 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR03MB2353 Archived-At: Subject: [Id-event] MILE XMPP Grid doc 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2016 19:36:02 -0000 --_000_BN3PR03MB2355040B043EC496C3491B15F5B30BN3PR03MB2355namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I attended the Managed Incident Lightweight Exchange (mile) working group o= n Friday. At it, the "XMPP Protocol Extensions for Use with IODEF" https:/= /tools.ietf.org/html/draft-ietf-mile-xmpp-grid-01 draft was presented. Thi= s is the transport that Kathleen Moriarty suggested during our working grou= p meeting that SecEvent consider to transport SETs. The abstract of the sp= ecification is: This document describes the extensions made to Extensible Messaging and Presence Protocol (XMPP) [RFC6120]that enables the use of XMPP as a transport protocol for collecting and distributing any security telemetry information between and among network platforms, endpoints, and most any network connected device. Specifically, this document will focus on how these extensions can be used to transport the Incident Object Description Exchange Format (IODEF) information. It would be good if people gave it a read - both for SecEvent's purposes an= d to provide feedback to MILE. -- Mike --_000_BN3PR03MB2355040B043EC496C3491B15F5B30BN3PR03MB2355namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I attended the Managed Incident Lightweight Exchange= (mile) working group on Friday.  At it, the “XMPP Protocol Exte= nsions for Use with IODEF” https:= //tools.ietf.org/html/draft-ietf-mile-xmpp-grid-01 draft was presented.=   This is the transport that Kathleen Moriarty suggested during our wo= rking group meeting that SecEvent consider to transport SETs.  The abstract of the specification is:<= /p>

 

   This document describes the extensions = made to Extensible Messaging

   and Presence Protocol (XMPP) [RFC6120]t= hat enables the use of XMPP as

   a transport protocol for collecting and= distributing any security

   telemetry information between and among= network platforms, endpoints,

   and most any network connected device.&= nbsp; Specifically, this document

   will focus on how these extensions can = be used to transport the

   Incident Object Description Exchange Fo= rmat (IODEF) information.

 

It would be good if people gave it a read – bo= th for SecEvent’s purposes and to provide feedback to MILE.

 

        &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;        -- Mike

 

--_000_BN3PR03MB2355040B043EC496C3491B15F5B30BN3PR03MB2355namp_-- From nobody Sun Nov 20 14:01:00 2016 Return-Path: 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 02566128874 for ; Sun, 20 Nov 2016 14:00:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.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 feKZ_Rq6qdD7 for ; Sun, 20 Nov 2016 14:00:52 -0800 (PST) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::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 289361294B6 for ; Sun, 20 Nov 2016 14:00:52 -0800 (PST) Received: by mail-wm0-x229.google.com with SMTP id f82so115741121wmf.1 for ; Sun, 20 Nov 2016 14:00:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=fpWSA93klp+Bxo/vpDy+thuMlRIpI/WhLt7O5yIrOUY=; b=mEbHnhBN9BnLX4heepEIhdUq0J+tye5/3zPWDo2jHWaNuMzSd9UUM+mUcTrzkjxOA6 q1Y1aHi9igusHTnoGwmti5Q3mXZUT87VZVlSSfeQmOT77RN/FXZZqdplaetlHTm8aqip 8NFFCumyXr5PzFD2PTkovWT/s+/HAnyT51MCW3xJ/Z1KwfkX/fo4OeEWfo8lwLGQVDA3 QNa4TUTwx3+DrLHnS/a6V4I1EWVTuCgZqJgQ9hHP9GoRfEVvz//7orxZVJQbyEI2gh6R /D6HU1VP6yvAYKENfjnWvLeob50b4AXud0dkSPk5OehH0ixsVErUHPI7jnWev+AiJx45 cIDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=fpWSA93klp+Bxo/vpDy+thuMlRIpI/WhLt7O5yIrOUY=; b=JFPEJiOe4Da2yH8lSYZyvAVdgAX9I1lNU2IAlcI0CWLEmc/Helmr8IUoO5migtLP5R 6JNE08DdEVevAp60bAkVdsePaZwt+YbRmHpq1GBkmf4RIeqiA2993o0JmHrNyhd8PQjG kqO2vJa8YT++FbtkVyfW2dFWKFRsfCS72vCepdrnNhmdhx+rVI/xg7U7TBxeVaZNlzZ4 2Tca/2U+ESqZ2YF8957pExpfF0LHLDt3Qvb+5ycBaAgCfVut9pczVVZze7feMgctO5Tc ZOECTjHDPbyrznqdrVsi7o3n0wSH/arqKJj3MzcpDPar8aO7QQ/qrwIiNCna11AyRLuq g8Ug== X-Gm-Message-State: AKaTC01hOmHrrqZuXx2gZZKi4OaSqoS+Fc/EF6nKKH/jDtrjW55pKCZFwBtGkI47zyTWnw== X-Received: by 10.46.77.92 with SMTP id a89mr6139454ljb.28.1479679250364; Sun, 20 Nov 2016 14:00:50 -0800 (PST) Received: from [10.0.0.101] (tb62-102-145-131.cust.teknikbyran.com. [62.102.145.131]) by smtp.gmail.com with ESMTPSA id g84sm4769843ljg.31.2016.11.20.14.00.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 20 Nov 2016 14:00:47 -0800 (PST) To: scim@ietf.org, id-event@ietf.org References: <8CCC780F-E02B-4BC7-B4EF-7743F088FD05@oracle.com> From: Leif Johansson Message-ID: <5e3bb755-515f-e632-9252-36b6823f0762@mnt.se> Date: Sun, 20 Nov 2016 23:00:47 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <8CCC780F-E02B-4BC7-B4EF-7743F088FD05@oracle.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [Id-event] [scim] Follow-up from IETF97 - XMPP Grid 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 22:00:55 -0000 On 2016-11-18 07:25, Phil Hunt wrote: > Note: cross-posted to IdEvents, SCIM, and OpenID RISC mailing lists. > > At the end of the Sec Events meeting, Nancy Cam-Winget mentioned the > XMPP-Grid draft which is about to go WGLC. See: > https://datatracker.ietf.org/doc/draft-ietf-mile-xmpp-grid/ > > I have taken a look and my initial impression is we should look at it: > > 1. Bi-directional signalling. A few use-cases (e.g. RISC) have > indicated a need to enable bi-directional flow. While HTTP post is > simple, it would involve managing two separate connections. It may be > possible XMPP-Grid turns out to be logistically simpler? > > 2. Firewall issues (e.g. cloud-to-enterprise). XMPP could be a good way > to avoid needing “polling” solutions such as HTTP GET when it is > inconvenient to open access for an HTTP POST. This may be of great > interest to the SCIM Synchronization work that some are considering. > > 3. Fan-out distribution: It could potentially handle publishing to > multiple receivers simultaneously. This is particularly useful in cases > where multiple data centers or server clusters need to receive the > events. For example, in OpenID Connect logout, the ability to notify > all members of a Single-sign-on audience for ID Tokens. > > 4. It supports multiple data formats (e.g. not just JWTs) > > 5. There is a control-plane in XMPP-grid that may also prove useful for > some or all of our requirements. > > 6. While it seems more complex, it can provide simplification overall. > Thought over-kill for one-way pub-sub, XMPP-Grid might be more of a > universal solution for all cases. Recalling Kathleen’s comments about > TAXII, this could be one way to avoid connection-itus and brokering. > > While this may seem like a very positive review on my part, I do suspect > that many will find this over-kill. > > ACTION REQUESTED: > I’d like to get a feel from the Sec Events community about this idea. > Would you like to see this idea explored further on the list? > > A. Does this look like something we should consider? What additional > capabilities do you see XMPP Grid bringing? > > B. If you see this as unnecessary, what would be your concerns? > > ps. I’m working on the other action items and hope to post a new SEC > Token draft early next week. > > Thanks for a great kick-off meeting! > > Phil > > @independentid > www.independentid.com > phil.hunt@oracle.com > > > > > > > > _______________________________________________ > scim mailing list > scim@ietf.org > https://www.ietf.org/mailman/listinfo/scim > In an earlier life (about 10 years ago) I built and deployed (what is now called) "chat ops" based on XMPP pubsub - very similar in requirements to what we're talking about here. XMPP is quite nice once you get it deployed but building and maintaining scalable xmpp pubsub infrastructure can be a bit more than many organizations is able to deal with. I guess that part will be up to Dick :-) Cheers Leif From nobody Mon Nov 21 10:54:25 2016 Return-Path: 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 7F2F9129B43 for ; Mon, 21 Nov 2016 10:54:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.398 X-Spam-Level: X-Spam-Status: No, score=-3.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497, 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 3blfPtPyjKdI for ; Mon, 21 Nov 2016 10:54:22 -0800 (PST) Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1394B129B42 for ; Mon, 21 Nov 2016 10:54:22 -0800 (PST) Received: from hebrews (24.21.96.37) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 21 Nov 2016 11:11:57 -0800 From: Jim Schaad To: Date: Mon, 21 Nov 2016 10:54:14 -0800 Message-ID: <073a01d24428$a9415f20$fbc41d60$@augustcellars.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AdJEJMf9OC8EdlzQQUaN+yFcnsyYMw== X-Originating-IP: [24.21.96.37] Archived-At: Cc: id-event@ietf.org Subject: [Id-event] draft-hunt-idevent-token -06 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 18:54:23 -0000 Somebody mentioned this group to me last week at the F2F meeting in the context of work being done in a different group. I therefore did a fast read on this draft and there are two issues that I want to highlight as being of major concern to me. 1. Section 3.5 gives advice on how to distinguish a SET from a JWT. While I think that building on the JWT infrastructure can make sense, the use of random rules to try and do distinguishing between different types does not make any sense to me. I would feel much more comfortable with a single fixed way of being able to distinguish between them. It seems to me to make far more sense to use either the typ or ctyp fields in the header to make this distinction. One could either do 'typ'='SET' or 'typ=JWT' and ctyp='SET' and it would be totally unambiguous. 2. The way that qualifiers are setup in this document looks to be a potential registration nightmare. The fact that any qualifier might have data stated as a claim means that people might want to use a registered value rather than a full url to make the message shorter. This is even more significant if one is looking at moving the world of CWT at some point in the future. It makes more sense to me to say that the event array has a string as the first element and then the subsequent elements be objects which describe the qualifiers. Thus you might get: "events":[ "urn:ietf:params:scim:event:passwordReset", {"name":"https://example.com/scim/event/passwordResetExt", "resetAttempts":5 } ] One can then play games with what goes into the name field to shorten things if one wishes. For example the above could be "./passwordResetExt" if the qualifier is defined by the URN as opposed to being defined locally by example.com. Jim From nobody Mon Nov 21 11:36:21 2016 Return-Path: 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 232E8129430 for ; Mon, 21 Nov 2016 11:36:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.698 X-Spam-Level: X-Spam-Status: No, score=-5.698 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.497, 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 EFgrjbH47AHA for ; Mon, 21 Nov 2016 11:36:18 -0800 (PST) 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 296CF129781 for ; Mon, 21 Nov 2016 11:36:18 -0800 (PST) Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id uALJaAdQ030460 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 21 Nov 2016 19:36:10 GMT Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id uALJa8su000322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 21 Nov 2016 19:36:09 GMT Received: from abhmp0010.oracle.com (abhmp0010.oracle.com [141.146.116.16]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id uALJa5Vb016156; Mon, 21 Nov 2016 19:36:06 GMT Received: from [192.168.1.26] (/174.7.250.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 21 Nov 2016 11:36:05 -0800 Content-Type: multipart/alternative; boundary="Apple-Mail=_D45304B9-3ADC-48D3-BB24-88D3880CE34A" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Phil Hunt In-Reply-To: <073a01d24428$a9415f20$fbc41d60$@augustcellars.com> Date: Mon, 21 Nov 2016 11:36:03 -0800 Message-Id: References: <073a01d24428$a9415f20$fbc41d60$@augustcellars.com> To: Jim Schaad X-Mailer: Apple Mail (2.3124) X-Source-IP: userv0022.oracle.com [156.151.31.74] Archived-At: Cc: draft-hunt-idevent-token@tools.ietf.org, id-event@ietf.org Subject: Re: [Id-event] draft-hunt-idevent-token -06 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 19:36:20 -0000 --Apple-Mail=_D45304B9-3ADC-48D3-BB24-88D3880CE34A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Jim, Thanks for the feedback! Comments inline below. =20 Phil @independentid www.independentid.com = phil.hunt@oracle.com = > On Nov 21, 2016, at 10:54 AM, Jim Schaad = wrote: >=20 > Somebody mentioned this group to me last week at the F2F meeting in = the > context of work being done in a different group. I therefore did a = fast > read on this draft and there are two issues that I want to highlight = as > being of major concern to me. >=20 > 1. Section 3.5 gives advice on how to distinguish a SET from a JWT. = While > I think that building on the JWT infrastructure can make sense, the = use of > random rules to try and do distinguishing between different types does = not > make any sense to me. I would feel much more comfortable with a = single > fixed way of being able to distinguish between them. It seems to me = to make > far more sense to use either the typ or ctyp fields in the header to = make > this distinction. One could either do 'typ'=3D'SET' or 'typ=3DJWT' = and > ctyp=3D'SET' and it would be totally unambiguous. This was discussed at some length. See: https://www.ietf.org/mail-archive/web/id-event/current/msg00001.html = >=20 > 2. The way that qualifiers are setup in this document looks to be a > potential registration nightmare. The fact that any qualifier might = have > data stated as a claim means that people might want to use a = registered > value rather than a full url to make the message shorter. This is = even more > significant if one is looking at moving the world of CWT at some point = in > the future. Early on the authors discussed requiring events to be registered with = IANA, in part to potentially reconcile duplicate events. There was a feeling that events may be negotiated between specific = parties or used internally. So in draft 01, we switched from URNs to = URIs for the value of events. The group should feel free to re-open this discussion if there is a = preference to register events. I note that just because the spec might = say events should be registered doesn=E2=80=99t have to mean that = internal uses are registered to work in reality. >=20 > It makes more sense to me to say that the event array has a string as = the > first element and then the subsequent elements be objects which = describe the > qualifiers. Thus you might get: >=20 > "events":[ > "urn:ietf:params:scim:event:passwordReset", > {"name":"https://example.com/scim/event/passwordResetExt", > "resetAttempts":5 > } > ] During the IETF97 SECEVENTS meeting, it was proposed to actually do = this. I=E2=80=99m amending the proposed draft (version 07) now. We also discussed this informally and a summary is available here where = a number of alternatives were proposed (the formal session preferred = version 3: https://www.ietf.org/mail-archive/web/id-event/current/msg00273.html >=20 > One can then play games with what goes into the name field to shorten = things > if one wishes. For example the above could be "./passwordResetExt" if = the > qualifier is defined by the URN as opposed to being defined locally by > example.com. =20 >=20 > Jim >=20 >=20 > _______________________________________________ > Id-event mailing list > Id-event@ietf.org > https://www.ietf.org/mailman/listinfo/id-event --Apple-Mail=_D45304B9-3ADC-48D3-BB24-88D3880CE34A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Jim,

Thanks= for the feedback! Comments inline below.  




On Nov 21, 2016, at 10:54 AM, Jim Schaad <ietf@augustcellars.com> wrote:

Somebody mentioned this group to me last week at the F2F = meeting in the
context of work being done in a different = group.  I therefore did a fast
read on this draft and = there are two issues that I want to highlight as
being of = major concern to me.

1.  Section 3.5 = gives advice on how to distinguish a SET from a JWT.  While
I think that building on the JWT infrastructure can make = sense, the use of
random rules to try and do = distinguishing between different types does not
make any = sense to me.  I would feel much more comfortable with a single
fixed way of being able to distinguish between them.  It = seems to me to make
far more sense to use either the typ = or ctyp fields in the header to make
this distinction. =  One could either do 'typ'=3D'SET' or 'typ=3DJWT' and
ctyp=3D'SET' and it would be totally unambiguous.

This was = discussed at some length.  See:


2.  The = way that qualifiers are setup in this document looks to be a
potential registration nightmare.   The fact that = any qualifier might have
data stated as a claim means that = people might want to use a registered
value rather than a = full url to make the message shorter.  This is even more
significant if one is looking at moving the world of CWT at = some point in
the future.

Early on = the authors discussed requiring events to be registered with IANA, in = part to potentially reconcile duplicate events.

There was a feeling that events may be negotiated = between specific parties or used internally. So in draft 01, we switched = from URNs to URIs for the value of events.

The group should feel free to re-open this = discussion if there is a preference to register events.  I note = that just because the spec might say events should be registered = doesn=E2=80=99t have to mean that internal uses are registered to work = in reality.


It makes more = sense to me to say that the event array has a string as the
first element and then the subsequent elements be objects = which describe the
qualifiers.  Thus you might = get:

"events":[
=    "urn:ietf:params:scim:event:passwordReset",
   {"name":"https://example.com/scim/event/passwordResetExt",
    "resetAttempts":5
=    }
]

During the IETF97 SECEVENTS meeting, it was proposed to = actually do this. I=E2=80=99m amending the proposed draft (version 07) = now.

We also discussed this = informally and a summary is available here where a number of = alternatives were proposed (the formal session preferred version = 3:


One can then = play games with what goes into the name field to shorten things
if one wishes.  For example the above could be = "./passwordResetExt" if the
qualifier is defined by the = URN as opposed to being defined locally by
example.com.  


Jim


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

= --Apple-Mail=_D45304B9-3ADC-48D3-BB24-88D3880CE34A-- From nobody Tue Nov 22 00:49:11 2016 Return-Path: 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 F3418129771 for ; Tue, 22 Nov 2016 00:49:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.397 X-Spam-Level: X-Spam-Status: No, score=-3.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.497, 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 c3xxbMUcyxru for ; Tue, 22 Nov 2016 00:49:07 -0800 (PST) Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E86D129759 for ; Tue, 22 Nov 2016 00:49:07 -0800 (PST) Received: from hebrews (24.21.96.37) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 22 Nov 2016 01:06:41 -0800 From: Jim Schaad To: 'Phil Hunt' References: <073a01d24428$a9415f20$fbc41d60$@augustcellars.com> In-Reply-To: Date: Tue, 22 Nov 2016 00:48:58 -0800 Message-ID: <07e901d2449d$459f0790$d0dd16b0$@augustcellars.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_07EA_01D2445A.377E3890" X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AQD813kelBGIAfUAENMYvb1OBT80CQFxZ/CvooQAE6A= X-Originating-IP: [24.21.96.37] Archived-At: Cc: draft-hunt-idevent-token@tools.ietf.org, id-event@ietf.org Subject: Re: [Id-event] draft-hunt-idevent-token -06 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 08:49:10 -0000 ------=_NextPart_000_07EA_01D2445A.377E3890 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable =20 =20 From: Phil Hunt [mailto:phil.hunt@oracle.com]=20 Sent: Monday, November 21, 2016 11:36 AM To: Jim Schaad Cc: draft-hunt-idevent-token@tools.ietf.org; id-event@ietf.org Subject: Re: [Id-event] draft-hunt-idevent-token -06 =20 Jim, =20 Thanks for the feedback! Comments inline below. =20 =20 Phil =20 @independentid www.independentid.com =20 phil.hunt@oracle.com =20 =20 =20 =20 =20 On Nov 21, 2016, at 10:54 AM, Jim Schaad > wrote: =20 Somebody mentioned this group to me last week at the F2F meeting in the context of work being done in a different group. I therefore did a fast read on this draft and there are two issues that I want to highlight as being of major concern to me. 1. Section 3.5 gives advice on how to distinguish a SET from a JWT. = While I think that building on the JWT infrastructure can make sense, the use = of random rules to try and do distinguishing between different types does = not make any sense to me. I would feel much more comfortable with a single fixed way of being able to distinguish between them. It seems to me to = make far more sense to use either the typ or ctyp fields in the header to = make this distinction. One could either do 'typ'=3D'SET' or 'typ=3DJWT' and ctyp=3D'SET' and it would be totally unambiguous. =20 This was discussed at some length. See: https://www.ietf.org/mail-archive/web/id-event/current/msg00001.html =20 2. The way that qualifiers are setup in this document looks to be a potential registration nightmare. The fact that any qualifier might = have data stated as a claim means that people might want to use a registered value rather than a full url to make the message shorter. This is even = more significant if one is looking at moving the world of CWT at some point = in the future. =20 Early on the authors discussed requiring events to be registered with = IANA, in part to potentially reconcile duplicate events. =20 There was a feeling that events may be negotiated between specific = parties or used internally. So in draft 01, we switched from URNs to = URIs for the value of events. =20 The group should feel free to re-open this discussion if there is a = preference to register events. I note that just because the spec might = say events should be registered doesn=E2=80=99t have to mean that = internal uses are registered to work in reality. =20 [JLS] Please note that my issue had nothing to do with the event itself, = but with qualifiers. (I also note that events are URNs so your sentence = above may be reversed.) =20 Jim =20 It makes more sense to me to say that the event array has a string as = the first element and then the subsequent elements be objects which describe = the qualifiers. Thus you might get: "events":[ "urn:ietf:params:scim:event:passwordReset", {"name":"https://example.com/scim/event/passwordResetExt", "resetAttempts":5 } ] =20 During the IETF97 SECEVENTS meeting, it was proposed to actually do = this. I=E2=80=99m amending the proposed draft (version 07) now. =20 We also discussed this informally and a summary is available here where = a number of alternatives were proposed (the formal session preferred = version 3: https://www.ietf.org/mail-archive/web/id-event/current/msg00273.html =20 One can then play games with what goes into the name field to shorten = things if one wishes. For example the above could be "./passwordResetExt" if = the qualifier is defined by the URN as opposed to being defined locally by example.com . =20 =20 Jim _______________________________________________ Id-event mailing list Id-event@ietf.org =20 https://www.ietf.org/mailman/listinfo/id-event =20 ------=_NextPart_000_07EA_01D2445A.377E3890 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

 

 

From:<= /b> = Phil Hunt [mailto:phil.hunt@oracle.com]
Sent: Monday, = November 21, 2016 11:36 AM
To: Jim Schaad = <ietf@augustcellars.com>
Cc: = draft-hunt-idevent-token@tools.ietf.org; = id-event@ietf.org
Subject: Re: [Id-event] = draft-hunt-idevent-token -06

 

Jim,

 

Thanks for the feedback! Comments inline below. =  

 

Phil

 

@independentid

phil.hunt@oracle.com<= /span>

 

 

 

 

On Nov 21, 2016, at 10:54 AM, Jim Schaad <ietf@augustcellars.com> = wrote:

 

Somebody mentioned this group to me last week at the = F2F meeting in the
context of work being done in a different group. =  I therefore did a fast
read on this draft and there are two = issues that I want to highlight as
being of major concern to = me.

1.  Section 3.5 gives advice on how to distinguish a SET = from a JWT.  While
I think that building on the JWT = infrastructure can make sense, the use of
random rules to try and do = distinguishing between different types does not
make any sense to me. =  I would feel much more comfortable with a single
fixed way of = being able to distinguish between them.  It seems to me to = make
far more sense to use either the typ or ctyp fields in the = header to make
this distinction.  One could either do = 'typ'=3D'SET' or 'typ=3DJWT' and
ctyp=3D'SET' and it would be totally = unambiguous.

 

This = was discussed at some length.  See:

 


2.  The way that qualifiers are setup in this = document looks to be a
potential registration nightmare. =   The fact that any qualifier might have
data stated as a = claim means that people might want to use a registered
value rather = than a full url to make the message shorter.  This is even = more
significant if one is looking at moving the world of CWT at some = point in
the future.

 

Early = on the authors discussed requiring events to be registered with IANA, in = part to potentially reconcile duplicate = events.

 

There was a feeling that events may be negotiated = between specific parties or used internally. So in draft 01, we switched = from URNs to URIs for the value of events.

 

The group should feel free to re-open this discussion = if there is a preference to register events.  I note that just = because the spec might say events should be registered doesn=E2=80=99t = have to mean that internal uses are registered to work in = reality.

 

[JLS] Please = note that my issue had nothing to do with the event itself, but with = qualifiers.=C2=A0 (I also note that events are URNs so your sentence = above may be reversed.)

 

Jim

 




It makes more sense to me to say that the event = array has a string as the
first element and then the subsequent = elements be objects which describe the
qualifiers.  Thus you = might = get:

"events":[
   "urn:ietf:para= ms:scim:event:passwordReset",
   {"name"= :"https://example.= com/scim/event/passwordResetExt",
    &qu= ot;resetAttempts":5
   }
]

=

 

During = the IETF97 SECEVENTS meeting, it was proposed to actually do this. = I=E2=80=99m amending the proposed draft (version 07) = now.

 

We also discussed this informally and a summary is = available here where a number of alternatives were proposed (the formal = session preferred version 3:

 


One can then play games with what goes into the = name field to shorten things
if one wishes.  For example the = above could be "./passwordResetExt" if the
qualifier is = defined by the URN as opposed to being defined locally by
example.com. =  

 


Jim


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

=

 

------=_NextPart_000_07EA_01D2445A.377E3890-- From nobody Tue Nov 22 11:38:04 2016 Return-Path: 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 27189129439; Sat, 19 Nov 2016 18:57:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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, 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 4InaFu3-PcjN; Sat, 19 Nov 2016 18:57:23 -0800 (PST) Received: from mail-qk0-x243.google.com (mail-qk0-x243.google.com [IPv6:2607:f8b0:400d:c09::243]) (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 7D11C129400; Sat, 19 Nov 2016 18:57:23 -0800 (PST) Received: by mail-qk0-x243.google.com with SMTP id x190so40254895qkb.0; Sat, 19 Nov 2016 18:57:22 -0800 (PST) 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=CWSehZvtntAoKaixo2qax5lbhSmIooyg9TK8OKOFEhQ=; b=ELqPbwigj2KiKqSBOMm8yjhSmO3rQ5F2fKDwo7/Vu2eh2M9zYiIJ0YC5bkNX+rhdRK wEvLWXVvEPxL0CkYHaISO0i/kPVpPHMg+PkTRQH+bxjm3WOqhjF0bNQY/KwODnRbN9Yy 0gdQPZLzm1BwdK6onG2UAN+hiHDGA8UCm7lYXVsdko6N1fUtfle8XRbDj3m/lawS486Q cb/Ed0IcNrlh1NaE004yyV/ySXwlymFk10xtl2szVFQEvGUI07xmZ27fjGOsRIT/V3bf EiojuAztkahNVD353KbfeBT4mJ4EWwn/rOJvsshGfMS0Dzfysl6dcItS0odiMfiGTMBc rShg== 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=CWSehZvtntAoKaixo2qax5lbhSmIooyg9TK8OKOFEhQ=; b=Zmcy81tmpAz0CveH/9RThH9eSW50nGKN3LaQ33DRnlb5rg7A60NyxWVoxngVhCmjEy CTxQGTzvjqFXd6cELJGH0QCP4M/QeG3g+SSineB/VHYcLe1AEtA9cwyf/yRa+PI0U0iw NrJdMfztlSAkRqld7JNes2IvJtN9/es1C8D08IfgPdVdY7L4Tq1l2CEDM0CMc8fL2qxw wN+pwQzp5Z4NCpitNHjztHB2Ilg9MUfJMYNEVxSAP3DmHdgRocStjwtYIIpo/tStlxsp fOy6jfMetPkrSm1jgShqbf7RZ3U62i3o6Zv4fngtftpkP+27ZNFp9IRotuo+S6kPa1X/ MZnw== X-Gm-Message-State: AKaTC02pxZaZT4vYYXZ2DHdWIiN6a51ChxNsm7MXHGNYTWVPZ9EAd7/AH6kqt1dB/GV4Z7IOc0a6gjYr2/SfKA== X-Received: by 10.55.102.83 with SMTP id a80mr5345961qkc.292.1479610641902; Sat, 19 Nov 2016 18:57:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.50.161 with HTTP; Sat, 19 Nov 2016 18:57:01 -0800 (PST) In-Reply-To: <8CCC780F-E02B-4BC7-B4EF-7743F088FD05@oracle.com> References: <8CCC780F-E02B-4BC7-B4EF-7743F088FD05@oracle.com> From: Dick Hardt Date: Sun, 20 Nov 2016 11:57:01 +0900 Message-ID: To: Phil Hunt Content-Type: multipart/alternative; boundary=94eb2c058662b773230541b2b21b Archived-At: X-Mailman-Approved-At: Tue, 22 Nov 2016 11:38:03 -0800 Cc: Tony Nadalin , Marius Scurtescu , Nancy Cam-Winget , Dick Hardt , Morteza Ansari , "scim@ietf.org WG" , PRATEEK MISHRA , openid-specs-risc@lists.openid.net, id-event@ietf.org Subject: Re: [Id-event] Follow-up from IETF97 - XMPP Grid 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 02:57:26 -0000 --94eb2c058662b773230541b2b21b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hey Phil Thanks for taking a look at XMPP Grid and writing up a summary. - This draft is dated October, 2016. I worry about building distribution on something that is that fresh. - The model seems to be somewhat oriented to user participation. - Our use at Amazon is restricted to sending security events ONLY to the IdP for a user. We do not want any security events to be re-broadcast or be inspected by any other parties. - Authentication is based on certificates. It is not clear how authorization is managed on who is able to see events. Other comments inserted inline. On Fri, Nov 18, 2016 at 3:25 PM, Phil Hunt wrote: > Note: cross-posted to IdEvents, SCIM, and OpenID RISC mailing lists. > > At the end of the Sec Events meeting, Nancy Cam-Winget mentioned the > XMPP-Grid draft which is about to go WGLC. See: > https://datatracker.ietf.org/doc/draft-ietf-mile-xmpp-grid/ > > I have taken a look and my initial impression is we should look at it: > > 1. Bi-directional signalling. A few use-cases (e.g. RISC) have indicated > a need to enable bi-directional flow. While HTTP post is simple, it would > involve managing two separate connections. It may be possible XMPP-Grid > turns out to be logistically simpler? > It actually seems more complicated. Having an end point where we receive messages and a separate mechanism to send messages is a proven model that works well for us. > > 2. Firewall issues (e.g. cloud-to-enterprise). XMPP could be a good way t= o > avoid needing =E2=80=9Cpolling=E2=80=9D solutions such as HTTP GET when i= t is inconvenient > to open access for an HTTP POST. This may be of great interest to the SC= IM > Synchronization work that some are considering. > I don't anticipate any firewall issues. > > 3. Fan-out distribution: It could potentially handle publishing to > multiple receivers simultaneously. This is particularly useful in cases > where multiple data centers or server clusters need to receive the events= . > For example, in OpenID Connect logout, the ability to notify all members = of > a Single-sign-on audience for ID Tokens. > > We don't anticipate having any fan out ourselves. > 4. It supports multiple data formats (e.g. not just JWTs) > HTTPS supports multiple data formats as well. :) > > 5. There is a control-plane in XMPP-grid that may also prove useful for > some or all of our requirements. > Maybe. > > 6. While it seems more complex, it can provide simplification overall. > Thought over-kill for one-way pub-sub, XMPP-Grid might be more of a > universal solution for all cases. Recalling Kathleen=E2=80=99s comments a= bout > TAXII, this could be one way to avoid connection-itus and brokering. > If XMPP-Grid was proven, then maybe. But it is not. > > While this may seem like a very positive review on my part, I do suspect > that many will find this over-kill. > > ACTION REQUESTED: > I=E2=80=99d like to get a feel from the Sec Events community about this i= dea. > Would you like to see this idea explored further on the list? > > A. Does this look like something we should consider? What additional > capabilities do you see XMPP Grid bringing? > No, none. > > B. If you see this as unnecessary, what would be your concerns? > Yes, see above. > > ps. I=E2=80=99m working on the other action items and hope to post a new = SEC Token > draft early next week. > > Thanks for a great kick-off meeting! > > 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 > > --=20 Subscribe to the HARDTWARE mail list to learn about projects I am working on! --94eb2c058662b773230541b2b21b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

H= ey Phil

<= span>=C2=A0

T= hanks for taking a look at XMPP Grid and writing up a summary.


- T= his draft is dated October, 2016. I worry about building distribution on so= mething that is that fresh.

- The model seems to be somewhat orien= ted to user participation.=C2=A0

- Our use at Amazon is restricted= to sending security events ONLY to the IdP for a user. We do not want any = security events to be re-broadcast or be inspected by any other parties.

- Authentication is based on certificates. It is not clear how autho= rization is managed on who is able to see events.


<= p class=3D"MsoNormal">Ot= her comments inserted inline.


On Fri, Nov 18, 2= 016 at 3:25 PM, Phil Hunt <phil.hunt@oracle.com> wrote:
N= ote: cross-posted to IdEvents, SCIM, and OpenID RISC mailing lists.

At the end of the Sec Events meeting,=C2=A0Nancy Cam-Winget me= ntioned the XMPP-Grid draft which is about to go WGLC. See:

I have taken a look and my initia= l impression is we should look at it:

1. Bi-direct= ional signalling.=C2=A0 A few use-cases (e.g. RISC) have indicated a need t= o enable bi-directional flow. While HTTP post is simple, it would involve m= anaging two separate connections. It may be possible XMPP-Grid turns out to= be logistically simpler?

It ac= tually seems more complicated.

Having an end point= where we receive messages and a separate mechanism to send messages is a p= roven model that works well for us.
=C2=A0

2. Fi= rewall issues (e.g. cloud-to-enterprise). XMPP could be a good way to avoid= needing =E2=80=9Cpolling=E2=80=9D solutions such as HTTP GET when it is in= convenient to open access for an HTTP POST.=C2=A0 This may be of great inte= rest to the SCIM Synchronization work that some are considering.

I don't anticipate any firewall issue= s.
=C2=A0

3. Fan-out distribution: It could pote= ntially handle publishing to multiple receivers simultaneously. This is par= ticularly useful in cases where multiple data centers or server clusters ne= ed to receive the events.=C2=A0 For example, in OpenID Connect logout, the = ability to notify all members of a Single-sign-on audience for ID Tokens.


We don't anti= cipate having any fan out ourselves.=C2=A0

=C2=A0<= /div>
4. It supports multiple data formats (e.g. not just JWTs)

HTTPS supports multiple data format= s as well. :)
=C2=A0

5. There is a control-plane= in XMPP-grid that may also prove useful for some or all of our requirement= s.

Maybe.=C2=A0
=C2= =A0

6. While it seems more complex, it can provide simplif= ication overall. Thought over-kill for one-way pub-sub, XMPP-Grid might be = more of a universal solution for all cases. Recalling Kathleen=E2=80=99s co= mments about TAXII, this could be one way to avoid connection-itus and brok= ering.

If XMPP-Grid was proven,= then maybe. But it is not.
=C2=A0

While this ma= y seem like a very positive review on my part, I do suspect that many will = find this over-kill.=C2=A0

ACTION REQUESTED:
=
I=E2=80=99d like to get a feel from the Sec Events community about thi= s idea. Would you like to see this idea explored further on the list?
=

A.=C2=A0 Does this look like something we should consid= er?=C2=A0 What additional capabilities do you see XMPP Grid bringing?
=

No, none.
=C2=A0

B.=C2=A0 If you see this as unnecessary, what would be your concern= s?

Yes, see above.
= =C2=A0

ps. I=E2=80=99m working on the other action items a= nd hope to post a new SEC Token draft early next week.

=
Thanks for a great kick-off meeting!



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




--
=
Subscribe to the HARDTWARE mail list to learn abou= t projects I am working on!
--94eb2c058662b773230541b2b21b-- From nobody Wed Nov 23 16:06:21 2016 Return-Path: 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 A2EDC1294A5; Wed, 23 Nov 2016 16:06:16 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.38.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147994597666.389.8703249248942730964.idtracker@ietfa.amsl.com> Date: Wed, 23 Nov 2016 16:06:16 -0800 Archived-At: Cc: id-event@ietf.org Subject: [Id-event] I-D Action: draft-hunt-idevent-token-07.txt 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 00:06:16 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Security Events of the IETF. Title : Security Event Token (SET) Authors : Phil Hunt William Denniss Morteza Ansari Michael B. Jones Filename : draft-hunt-idevent-token-07.txt Pages : 19 Date : 2016-11-23 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-hunt-idevent-token/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-hunt-idevent-token-07 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-hunt-idevent-token-07 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Nov 23 16:14:44 2016 Return-Path: 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 320EC1295DA for ; Wed, 23 Nov 2016 16:14:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.698 X-Spam-Level: X-Spam-Status: No, score=-5.698 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.497, 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 XqslpTWSEe5n for ; Wed, 23 Nov 2016 16:14:40 -0800 (PST) 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 AC0C0129600 for ; Wed, 23 Nov 2016 16:14:36 -0800 (PST) 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 uAO0EYnf031196 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 24 Nov 2016 00:14:35 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 uAO0EY75012056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 24 Nov 2016 00:14:34 GMT Received: from abhmp0014.oracle.com (abhmp0014.oracle.com [141.146.116.20]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id uAO0EXDI005508 for ; Thu, 24 Nov 2016 00:14:34 GMT Received: from [10.0.1.30] (/24.86.208.48) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 23 Nov 2016 16:14:32 -0800 From: Phil Hunt Content-Type: multipart/alternative; boundary="Apple-Mail=_9BDD6FA1-16DC-4D96-8C70-9B6BCFB4FF44" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Date: Wed, 23 Nov 2016 16:14:31 -0800 References: <147994597666.389.8703249248942730964.idtracker@ietfa.amsl.com> To: id-event@ietf.org In-Reply-To: <147994597666.389.8703249248942730964.idtracker@ietfa.amsl.com> X-Mailer: Apple Mail (2.3124) X-Source-IP: aserv0022.oracle.com [141.146.126.234] Archived-At: Subject: Re: [Id-event] I-D Action: draft-hunt-idevent-token-07.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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 00:14:42 -0000 --Apple-Mail=_9BDD6FA1-16DC-4D96-8C70-9B6BCFB4FF44 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 As discussed at the IETF97 meeting in Seoul, this revision includes the = new JSON structure optimization for the events =E2=80=9Cpayload=E2=80=9D = information to improve parsing. The draft also includes some minor non-normative edits to normalize = terminology with JWT terminology (thanks Mike). *I believe this draft is now ready for consideration for adoption as a = working group draft.* Thanks and Happy US Thanksgiving! Phil @independentid www.independentid.com = phil.hunt@oracle.com = > On Nov 23, 2016, at 4:06 PM, internet-drafts@ietf.org wrote: >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Security Events of the IETF. >=20 > Title : Security Event Token (SET) > Authors : Phil Hunt > William Denniss > Morteza Ansari > Michael B. Jones > Filename : draft-hunt-idevent-token-07.txt > Pages : 19 > Date : 2016-11-23 >=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 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-hunt-idevent-token/ >=20 > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-hunt-idevent-token-07 >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-token-07 >=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 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Id-event mailing list > Id-event@ietf.org > https://www.ietf.org/mailman/listinfo/id-event --Apple-Mail=_9BDD6FA1-16DC-4D96-8C70-9B6BCFB4FF44 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 As discussed at the IETF97 meeting in Seoul, this revision = includes the new JSON structure optimization for the events = =E2=80=9Cpayload=E2=80=9D information to improve parsing.

The draft also includes = some minor non-normative edits to normalize terminology with JWT = terminology (thanks Mike).

*I believe this draft is now ready for consideration for = adoption as a working group draft.*

Thanks and Happy US = Thanksgiving!




On Nov 23, 2016, at 4:06 PM, internet-drafts@ietf.org wrote:


A New Internet-Draft is available from the on-line = Internet-Drafts directories.
This draft is a work item of = the Security Events of the IETF.

=        Title =           : Security = Event Token (SET)
=        Authors =         : Phil Hunt
= =             &n= bsp;           &nbs= p;William Denniss
=             &n= bsp;           &nbs= p;Morteza Ansari
=             &n= bsp;           &nbs= p;Michael B. Jones
Filename =        : = draft-hunt-idevent-token-07.txt
Pages =           : 19
= Date =            : = 2016-11-23

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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-hunt-idevent-token/<= br class=3D"">
There's also a htmlized version available = at:
https://tools.ietf.org/html/draft-hunt-idevent-token-07

A diff from the previous version is available = at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-hunt-idevent-token-07=


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.

Internet-Drafts are also available by = anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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

= --Apple-Mail=_9BDD6FA1-16DC-4D96-8C70-9B6BCFB4FF44-- From nobody Wed Nov 23 19:59:12 2016 Return-Path: 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 EE8AA126D73 for ; Wed, 23 Nov 2016 19:59:09 -0800 (PST) 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 NkxziJUCUMAU for ; Wed, 23 Nov 2016 19:59:07 -0800 (PST) Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0099.outbound.protection.outlook.com [104.47.40.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 335CF12953B for ; Wed, 23 Nov 2016 19:59:07 -0800 (PST) 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=Ejfdb9PipJuwxbCCVPFUB6JK4aJVBpYEzOK4uLpJc+I=; b=b5qbrTTaMaYEQjx0Y1uvXvli1l4F0KP6iy0HeoIABeZKZttCj49+H+qNMMmOv+GfbhFiaB7N48qiSCqSz0Lfj+zwvfQtcaf4oMjeB7W4dzsP1eLZ1OaOnMZHR3zsxyEeMRb5ZTHnfQVib7aIaiOHjvlsyfvjE1wKpDL4wu57eNU= Received: from BN3PR03MB2355.namprd03.prod.outlook.com (10.166.74.150) by BN3PR03MB2353.namprd03.prod.outlook.com (10.166.74.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.734.8; Thu, 24 Nov 2016 03:59:04 +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.0734.014; Thu, 24 Nov 2016 03:59:05 +0000 From: Mike Jones To: Phil Hunt , "id-event@ietf.org" Thread-Topic: [Id-event] I-D Action: draft-hunt-idevent-token-07.txt Thread-Index: AQHSRea0iquujeVS4UW1W0i4WXU27KDnQ6aAgAA+TQA= Date: Thu, 24 Nov 2016 03:59:04 +0000 Message-ID: References: <147994597666.389.8703249248942730964.idtracker@ietfa.amsl.com> In-Reply-To: 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: [50.47.80.137] x-microsoft-exchange-diagnostics: 1; BN3PR03MB2353; 7:EZnnPvOqmeqk4N3ws7M6szpiunXq658P8ZRzvkCKmo+yv2CScVMc5s2dq6bW5VGR2OVEasNkvLEvJEr3l3KKi03Iv//wQtps91roNiLp09xYdCuYeT+pmv0LTcIws4+IJu100KmaTvqdHBl9YwOiWXru/boJWHGmt0fHCZcIOAZS2ltUG/HrVBF9W6FBiCPnuYv7frz/HLtPoZKSUWs4j03HIaFPvS7uhTbcl2kq1LUxm7uZRphIY9fvJ2NYAFu9eOj30OFXvVg9Nai/L93E5xUwXuyAzryz1hebpayFoHbFervKzDY1R8i67wh/Wldxz/0aYXcF4KtvLQXpe1aJhgTC0iotBO4Ns6++00Vn3pz6L1bWJCvFvqt7kNdzGeGh x-ms-office365-filtering-correlation-id: 50603a84-8792-4144-51e3-08d4141e3bc6 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:BN3PR03MB2353; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(120809045254105)(192374486261705)(31418570063057)(21748063052155)(146099531331640); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6045199)(6040307)(6060326)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(61426038)(61427038)(6046074)(6041248)(6061324)(6047074)(6042181)(6072148); SRVR:BN3PR03MB2353; BCL:0; PCL:0; RULEID:; SRVR:BN3PR03MB2353; x-forefront-prvs: 0136C1DDA4 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(209900001)(24454002)(377424004)(69234005)(377454003)(199003)(189002)(86612001)(7736002)(8990500004)(74316002)(7696004)(19609705001)(7906003)(8936002)(3280700002)(3660700001)(9686002)(10290500002)(5005710100001)(33656002)(86362001)(7846002)(68736007)(66066001)(230783001)(16601075003)(2906002)(105586002)(38730400001)(3846002)(2950100002)(102836003)(76576001)(6116002)(122556002)(101416001)(790700001)(2900100001)(92566002)(189998001)(1680700002)(2501003)(4001150100001)(97736004)(107886002)(606004)(5001770100001)(81156014)(77096005)(106116001)(50986999)(106356001)(76176999)(54356999)(6506003)(10090500001)(229853002)(81166006)(8676002)(99286002)(5660300001)(6606295002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR03MB2353; H:BN3PR03MB2355.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX: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_BN3PR03MB235508A0DE8B01B6F4337FE9F5B60BN3PR03MB2355namp_" MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Nov 2016 03:59:04.8257 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR03MB2353 Archived-At: Subject: Re: [Id-event] I-D Action: draft-hunt-idevent-token-07.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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 03:59:10 -0000 --_000_BN3PR03MB235508A0DE8B01B6F4337FE9F5B60BN3PR03MB2355namp_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 RllJLCBJIGJsb2dnZWQgYWJvdXQgdGhpcyBhdCBodHRwOi8vc2VsZi1pc3N1ZWQuaW5mby8/cD0x NjIwIGFuZCBhcyBAc2VsZmlzc3VlZDxodHRwczovL3R3aXR0ZXIuY29tL3NlbGZpc3N1ZWQ+LiAg VGhlIGJsb2cgcG9zdCB3YXMgaW50ZW5kZWQgdG8gcHJvdmlkZSBhbiBpbnRyb2R1Y3Rpb24gdG8g U0VUcyB0byB0aG9zZSB3aG8gbWF5IG5vdCBoYXZlIGJlZW4gcHJldmlvdXNseSBmb2xsb3dpbmcg dGhlIHdvcmsuDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAtLSBNaWtlDQoNCkZyb206IElkLWV2ZW50IFttYWlsdG86aWQtZXZlbnQtYm91 bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFBoaWwgSHVudA0KU2VudDogV2VkbmVzZGF5LCBO b3ZlbWJlciAyMywgMjAxNiA0OjE1IFBNDQpUbzogaWQtZXZlbnRAaWV0Zi5vcmcNClN1YmplY3Q6 IFJlOiBbSWQtZXZlbnRdIEktRCBBY3Rpb246IGRyYWZ0LWh1bnQtaWRldmVudC10b2tlbi0wNy50 eHQNCg0KQXMgZGlzY3Vzc2VkIGF0IHRoZSBJRVRGOTcgbWVldGluZyBpbiBTZW91bCwgdGhpcyBy ZXZpc2lvbiBpbmNsdWRlcyB0aGUgbmV3IEpTT04gc3RydWN0dXJlIG9wdGltaXphdGlvbiBmb3Ig dGhlIGV2ZW50cyDigJxwYXlsb2Fk4oCdIGluZm9ybWF0aW9uIHRvIGltcHJvdmUgcGFyc2luZy4N Cg0KVGhlIGRyYWZ0IGFsc28gaW5jbHVkZXMgc29tZSBtaW5vciBub24tbm9ybWF0aXZlIGVkaXRz IHRvIG5vcm1hbGl6ZSB0ZXJtaW5vbG9neSB3aXRoIEpXVCB0ZXJtaW5vbG9neSAodGhhbmtzIE1p a2UpLg0KDQoqSSBiZWxpZXZlIHRoaXMgZHJhZnQgaXMgbm93IHJlYWR5IGZvciBjb25zaWRlcmF0 aW9uIGZvciBhZG9wdGlvbiBhcyBhIHdvcmtpbmcgZ3JvdXAgZHJhZnQuKg0KDQpUaGFua3MgYW5k IEhhcHB5IFVTIFRoYW5rc2dpdmluZyENCg0KUGhpbA0KDQpAaW5kZXBlbmRlbnRpZA0Kd3d3Lmlu ZGVwZW5kZW50aWQuY29tPGh0dHA6Ly93d3cuaW5kZXBlbmRlbnRpZC5jb20+DQpwaGlsLmh1bnRA b3JhY2xlLmNvbTxtYWlsdG86cGhpbC5odW50QG9yYWNsZS5jb20+DQoNCg0KDQoNCk9uIE5vdiAy MywgMjAxNiwgYXQgNDowNiBQTSwgaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnPG1haWx0bzppbnRl cm5ldC1kcmFmdHNAaWV0Zi5vcmc+IHdyb3RlOg0KDQoNCkEgTmV3IEludGVybmV0LURyYWZ0IGlz IGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy4N ClRoaXMgZHJhZnQgaXMgYSB3b3JrIGl0ZW0gb2YgdGhlIFNlY3VyaXR5IEV2ZW50cyBvZiB0aGUg SUVURi4NCg0KICAgICAgIFRpdGxlICAgICAgICAgICA6IFNlY3VyaXR5IEV2ZW50IFRva2VuIChT RVQpDQogICAgICAgQXV0aG9ycyAgICAgICAgIDogUGhpbCBIdW50DQogICAgICAgICAgICAgICAg ICAgICAgICAgV2lsbGlhbSBEZW5uaXNzDQogICAgICAgICAgICAgICAgICAgICAgICAgTW9ydGV6 YSBBbnNhcmkNCiAgICAgICAgICAgICAgICAgICAgICAgICBNaWNoYWVsIEIuIEpvbmVzDQogICAg ICAgICAgICAgIEZpbGVuYW1lICAgICAgICA6IGRyYWZ0LWh1bnQtaWRldmVudC10b2tlbi0wNy50 eHQNCiAgICAgICAgICAgICAgUGFnZXMgICAgICAgICAgIDogMTkNCiAgICAgICAgICAgICAgRGF0 ZSAgICAgICAgICAgIDogMjAxNi0xMS0yMw0KDQpBYnN0cmFjdDoNCiAgVGhpcyBzcGVjaWZpY2F0 aW9uIGRlZmluZXMgdGhlIFNlY3VyaXR5IEV2ZW50IFRva2VuLCB3aGljaCBtYXkgYmUNCiAgZGlz dHJpYnV0ZWQgdmlhIGEgcHJvdG9jb2wgc3VjaCBhcyBIVFRQLiAgVGhlIFNlY3VyaXR5IEV2ZW50 IFRva2VuDQogIChTRVQpIHNwZWNpZmljYXRpb24gcHJvZmlsZXMgdGhlIEpTT04gV2ViIFRva2Vu IChKV1QpIGFuZCBtYXkgYmUNCiAgb3B0aW9uYWxseSBzaWduZWQgYW5kL29yIGVuY3J5cHRlZC4g IEEgU0VUIGRlc2NyaWJlcyBhIHN0YXRlbWVudCBvZg0KICBmYWN0IHRoYXQgbWF5IGJlIHNoYXJl ZCBieSBhbiBldmVudCBwdWJsaXNoZXIgd2l0aCBldmVudCBzdWJzY3JpYmVycy4NCg0KDQpUaGUg SUVURiBkYXRhdHJhY2tlciBzdGF0dXMgcGFnZSBmb3IgdGhpcyBkcmFmdCBpczoNCmh0dHBzOi8v ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWh1bnQtaWRldmVudC10b2tlbi8NCg0KVGhl cmUncyBhbHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6DQpodHRwczovL3Rvb2xz LmlldGYub3JnL2h0bWwvZHJhZnQtaHVudC1pZGV2ZW50LXRva2VuLTA3DQoNCkEgZGlmZiBmcm9t IHRoZSBwcmV2aW91cyB2ZXJzaW9uIGlzIGF2YWlsYWJsZSBhdDoNCmh0dHBzOi8vd3d3LmlldGYu b3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1odW50LWlkZXZlbnQtdG9rZW4tMDcNCg0KDQpQbGVhc2Ug bm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBv ZiBzdWJtaXNzaW9uDQp1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZh aWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KDQpJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZh aWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQpmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQt ZHJhZnRzLw0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Xw0KSWQtZXZlbnQgbWFpbGluZyBsaXN0DQpJZC1ldmVudEBpZXRmLm9yZzxtYWlsdG86SWQtZXZl bnRAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lkLWV2 ZW50DQoNCg== --_000_BN3PR03MB235508A0DE8B01B6F4337FE9F5B60BN3PR03MB2355namp_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6 IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv cjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1z b0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJw bGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25v cm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28t bWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90 dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uYXBwbGUtc3R5bGUtc3Bhbg0K CXttc28tc3R5bGUtbmFtZTphcHBsZS1zdHlsZS1zcGFuO30NCnNwYW4uYXBwbGUtdGFiLXNwYW4N Cgl7bXNvLXN0eWxlLW5hbWU6YXBwbGUtdGFiLXNwYW47fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7 bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNh bnMtc2VyaWY7DQoJY29sb3I6IzAwMjA2MDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUt dHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9u MQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47 fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwh LS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3Bp ZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1s Pg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRh dGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8 Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNz PSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9y OiMwMDIwNjAiPkZZSSwgSSBibG9nZ2VkIGFib3V0IHRoaXMgYXQgPGEgaHJlZj0iaHR0cDovL3Nl bGYtaXNzdWVkLmluZm8vP3A9MTYyMCI+DQpodHRwOi8vc2VsZi1pc3N1ZWQuaW5mby8/cD0xNjIw PC9hPiBhbmQgYXMgPGEgaHJlZj0iaHR0cHM6Ly90d2l0dGVyLmNvbS9zZWxmaXNzdWVkIj4NCkBz ZWxmaXNzdWVkPC9hPi4mbmJzcDsgVGhlIGJsb2cgcG9zdCB3YXMgaW50ZW5kZWQgdG8gcHJvdmlk ZSBhbiBpbnRyb2R1Y3Rpb24gdG8gU0VUcyB0byB0aG9zZSB3aG8gbWF5IG5vdCBoYXZlIGJlZW4g cHJldmlvdXNseSBmb2xsb3dpbmcgdGhlIHdvcmsuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMwMDIwNjAiPjxvOnA+Jm5ic3A7 PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xv cjojMDAyMDYwIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgLS0gTWlr ZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIG5hbWU9Il9N YWlsRW5kQ29tcG9zZSI+PHNwYW4gc3R5bGU9ImNvbG9yOiMwMDIwNjAiPjxvOnA+Jm5ic3A7PC9v OnA+PC9zcGFuPjwvYT48L3A+DQo8c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsRW5kQ29t cG9zZSI+PC9zcGFuPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6 c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBJZC1ldmVudCBbbWFpbHRvOmlkLWV2ZW50LWJvdW5j ZXNAaWV0Zi5vcmddIDxiPg0KT24gQmVoYWxmIE9mIDwvYj5QaGlsIEh1bnQ8YnI+DQo8Yj5TZW50 OjwvYj4gV2VkbmVzZGF5LCBOb3ZlbWJlciAyMywgMjAxNiA0OjE1IFBNPGJyPg0KPGI+VG86PC9i PiBpZC1ldmVudEBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW0lkLWV2ZW50XSBJ LUQgQWN0aW9uOiBkcmFmdC1odW50LWlkZXZlbnQtdG9rZW4tMDcudHh0PG86cD48L286cD48L3A+ DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48 L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BcyBkaXNjdXNzZWQgYXQgdGhlIElFVEY5NyBtZWV0 aW5nIGluIFNlb3VsLCB0aGlzIHJldmlzaW9uIGluY2x1ZGVzIHRoZSBuZXcgSlNPTiBzdHJ1Y3R1 cmUgb3B0aW1pemF0aW9uIGZvciB0aGUgZXZlbnRzIOKAnHBheWxvYWTigJ0gaW5mb3JtYXRpb24g dG8gaW1wcm92ZSBwYXJzaW5nLjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z b05vcm1hbCI+VGhlIGRyYWZ0IGFsc28gaW5jbHVkZXMgc29tZSBtaW5vciBub24tbm9ybWF0aXZl IGVkaXRzIHRvIG5vcm1hbGl6ZSB0ZXJtaW5vbG9neSB3aXRoIEpXVCB0ZXJtaW5vbG9neSAodGhh bmtzIE1pa2UpLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv Tm9ybWFsIj4qSSBiZWxpZXZlIHRoaXMgZHJhZnQgaXMgbm93IHJlYWR5IGZvciBjb25zaWRlcmF0 aW9uIGZvciBhZG9wdGlvbiBhcyBhIHdvcmtpbmcgZ3JvdXAgZHJhZnQuKjxvOnA+PC9vOnA+PC9w Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48 L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MgYW5kIEhhcHB5 IFVTIFRoYW5rc2dpdmluZyE8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4N CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+UGhpbDxvOnA+PC9vOnA+PC9zcGFuPjwv cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xv cjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5AaW5kZXBlbmRlbnRp ZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt YWwiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PGEgaHJlZj0iaHR0cDovL3d3dy5pbmRlcGVu ZGVudGlkLmNvbSI+d3d3LmluZGVwZW5kZW50aWQuY29tPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwv cD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+ PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48YSBocmVmPSJtYWlsdG86cGhpbC5odW50QG9yYWNs ZS5jb20iPnBoaWwuaHVudEBvcmFjbGUuY29tPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFj ayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48 L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJv dHRvbToxMi4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0i bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0i TXNvTm9ybWFsIj5PbiBOb3YgMjMsIDIwMTYsIGF0IDQ6MDYgUE0sIDxhIGhyZWY9Im1haWx0bzpp bnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmciPg0KaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnPC9hPiB3 cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m bmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4N CkEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVy bmV0LURyYWZ0cyBkaXJlY3Rvcmllcy48YnI+DQpUaGlzIGRyYWZ0IGlzIGEgd29yayBpdGVtIG9m IHRoZSBTZWN1cml0eSBFdmVudHMgb2YgdGhlIElFVEYuPGJyPg0KPGJyPg0KJm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7VGl0bGUgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7OiBTZWN1cml0eSBFdmVudCBU b2tlbiAoU0VUKTxicj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw O0F1dGhvcnMgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 OiBQaGlsIEh1bnQ8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtXaWxs aWFtIERlbm5pc3M8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtNb3J0 ZXphIEFuc2FyaTxicj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO01pY2hh ZWwgQi4gSm9uZXM8YnI+DQo8c3BhbiBjbGFzcz0iYXBwbGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyA8L3NwYW4+RmlsZW5hbWUgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7OiBkcmFmdC1odW50LWlkZXZlbnQtdG9rZW4tMDcudHh0PGJyPg0KPHNwYW4g Y2xhc3M9ImFwcGxlLXRhYi1zcGFuIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPC9zcGFuPlBhZ2Vz ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOzogMTk8YnI+DQo8c3BhbiBjbGFzcz0iYXBwbGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyA8L3NwYW4+RGF0ZSAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDs6IDIwMTYtMTEtMjM8YnI+DQo8YnI+DQpBYnN0 cmFjdDo8YnI+DQombmJzcDsmbmJzcDtUaGlzIHNwZWNpZmljYXRpb24gZGVmaW5lcyB0aGUgU2Vj dXJpdHkgRXZlbnQgVG9rZW4sIHdoaWNoIG1heSBiZTxicj4NCiZuYnNwOyZuYnNwO2Rpc3RyaWJ1 dGVkIHZpYSBhIHByb3RvY29sIHN1Y2ggYXMgSFRUUC4gJm5ic3A7VGhlIFNlY3VyaXR5IEV2ZW50 IFRva2VuPGJyPg0KJm5ic3A7Jm5ic3A7KFNFVCkgc3BlY2lmaWNhdGlvbiBwcm9maWxlcyB0aGUg SlNPTiBXZWIgVG9rZW4gKEpXVCkgYW5kIG1heSBiZTxicj4NCiZuYnNwOyZuYnNwO29wdGlvbmFs bHkgc2lnbmVkIGFuZC9vciBlbmNyeXB0ZWQuICZuYnNwO0EgU0VUIGRlc2NyaWJlcyBhIHN0YXRl bWVudCBvZjxicj4NCiZuYnNwOyZuYnNwO2ZhY3QgdGhhdCBtYXkgYmUgc2hhcmVkIGJ5IGFuIGV2 ZW50IHB1Ymxpc2hlciB3aXRoIGV2ZW50IHN1YnNjcmliZXJzLjxicj4NCjxicj4NCjxicj4NClRo ZSBJRVRGIGRhdGF0cmFja2VyIHN0YXR1cyBwYWdlIGZvciB0aGlzIGRyYWZ0IGlzOjxicj4NCjxh IGhyZWY9Imh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWh1bnQtaWRldmVu dC10b2tlbi8iPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWh1bnQtaWRl dmVudC10b2tlbi88L2E+PGJyPg0KPGJyPg0KVGhlcmUncyBhbHNvIGEgaHRtbGl6ZWQgdmVyc2lv biBhdmFpbGFibGUgYXQ6PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s L2RyYWZ0LWh1bnQtaWRldmVudC10b2tlbi0wNyI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s L2RyYWZ0LWh1bnQtaWRldmVudC10b2tlbi0wNzwvYT48YnI+DQo8YnI+DQpBIGRpZmYgZnJvbSB0 aGUgcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUgYXQ6PGJyPg0KPGEgaHJlZj0iaHR0cHM6 Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWh1bnQtaWRldmVudC10b2tlbi0wNyI+ aHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWh1bnQtaWRldmVudC10b2tl bi0wNzwvYT48YnI+DQo8YnI+DQo8YnI+DQpQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEg Y291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uPGJyPg0KdW50aWwg dGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRm Lm9yZy48YnI+DQo8YnI+DQpJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFu b255bW91cyBGVFAgYXQ6PGJyPg0KPGEgaHJlZj0iZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0 LWRyYWZ0cy8iPmZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvPC9hPjxicj4NCjxi cj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0K SWQtZXZlbnQgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOklkLWV2ZW50QGlldGYu b3JnIj5JZC1ldmVudEBpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRm Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lkLWV2ZW50Ij5odHRwczovL3d3dy5pZXRmLm9yZy9tYWls bWFuL2xpc3RpbmZvL2lkLWV2ZW50PC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N CjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8 L286cD48L3A+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg== --_000_BN3PR03MB235508A0DE8B01B6F4337FE9F5B60BN3PR03MB2355namp_--