
From nobody Tue Dec  1 06:52:36 2020
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F38E3A1450 for <id-event@ietfa.amsl.com>; Tue,  1 Dec 2020 06:52:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 2w0Xipz_PxRJ for <id-event@ietfa.amsl.com>; Tue,  1 Dec 2020 06:52:25 -0800 (PST)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 AAE653A1394 for <id-event@ietf.org>; Tue,  1 Dec 2020 06:52:09 -0800 (PST)
Received: by mail-ed1-x52e.google.com with SMTP id r5so249696eda.12 for <id-event@ietf.org>; Tue, 01 Dec 2020 06:52:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=user-agent:date:subject:from:to:message-id:thread-topic :mime-version:content-transfer-encoding; bh=zUYcXTvtqV1qntt8W/xUUhoqltfMRwRa/ktsYzceoKc=; b=N6q82FlmGiiSzH+N7FSR+7Mno02VK3Kh+5THE2ubpc+VmO1B4dR0I06bjs+bsS9OsC 5XObWvCRSK5wwEQFcIy2Av7fdR+I3swzkx5jeeiRZlda4qNZabtjcSwIB2MJ23WEpkiK wuPT7XpDKfNZK7VIBWktQYFmPWUW9FRU8uGbX3QN2I2pRbkU4VcUXiaLhbTpbNwU9fFi Ym9dbynQc0tQTY7NcjoHvWYOmSOrW9j6Ay4iasbE/QXScajRZL+Doi/wXFZrYEm5VX3i UI/wReOuZ1YkuL383e1yL7oaZjxDxFebQUE3Z8PIttQAOatPBtfDOaTkawlM3qhUlmQ5 XzKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:mime-version:content-transfer-encoding; bh=zUYcXTvtqV1qntt8W/xUUhoqltfMRwRa/ktsYzceoKc=; b=MA6h7n6BWxiPu4d+F2ivXrazWm3xS6seuXlWWEYUxIuRnxKpjfMxsT+kKwAQAWbXbu hA2vAA/0Rb1EggAUmUnJMctwYj6r5QNTXanNqs+tWfKStoc7Gu94ecuC4nI9mxhCIvdW ITfDTj2JrQWIrelg3UB6d624qvHFWDFckb5KALxGYXDEZUsrs39Omsc6neWV9/9fmF0p tsMmp8RjIqygd5cEfUW0KvCBwM9GUDIGcR4wj01KtyEOEQunwzEDHzzvSlFXDzDuHUIc 24i9BdeZlI2MCfiPmGaoEYOR2oi+ZUclrNYxbvK7j1vWX7lFQRVTvCUGu/iEnqYEJI93 NAIA==
X-Gm-Message-State: AOAM530VkDnPGKF+sV+LtCsulhoX6Es2W3Rrc7f/7bbLiEhYy1TUtqvE rP7LkQ+RRM5NXVog17dV5YRrcehGLa1NFg==
X-Google-Smtp-Source: ABdhPJxUCeapRTvrAKwKOWXEg4sbiErNPxgOxKuljZmXDjAo5f9+/cXv5HZE31YkRirhirjTsW68fA==
X-Received: by 2002:a05:6402:22e1:: with SMTP id dn1mr3375778edb.142.1606834327771;  Tue, 01 Dec 2020 06:52:07 -0800 (PST)
Received: from [172.26.49.35] (pub-corp-42-8.intuit.com. [91.102.42.8]) by smtp.gmail.com with ESMTPSA id 22sm935831ejx.115.2020.12.01.06.52.06 for <id-event@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Dec 2020 06:52:07 -0800 (PST)
User-Agent: Microsoft-MacOutlook/16.43.20110804
Date: Tue, 01 Dec 2020 16:52:05 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: SecEvent <id-event@ietf.org>
Message-ID: <C6223D8A-5875-4301-ACC3-CA768B57BCDA@gmail.com>
Thread-Topic: Delivery RFCs just published
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/S6m4BKRzVyxvOIRiR4wIDblmGYo>
Subject: [Id-event] Delivery RFCs just published
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2020 14:52:35 -0000

Hi Everyone,

RFC 8935 (https://datatracker.ietf.org/doc/rfc8935/) and RFC 8936 (https://=
datatracker.ietf.org/doc/rfc8936/) were published earlier today. In addition=
 to the baseline SET format, these are the two main working group deliverabl=
es: push and poll delivery of identity events over HTTP. I am very happy to =
see us hit this milestone and I=E2=80=99d like to thank the authors of both specif=
ications:

=E2=80=A2 Annabelle Backman
=E2=80=A2 Michael Jones
=E2=80=A2 Marius Scurtescu
=E2=80=A2 Morteza Ansari
=E2=80=A2 Anthony Nadalin

Regards,
	Yaron



From nobody Wed Dec  2 11:58:14 2020
Return-Path: <dick.hardt@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C83613A1543 for <id-event@ietfa.amsl.com>; Wed,  2 Dec 2020 11:58:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 SVLjy4RH_qLF for <id-event@ietfa.amsl.com>; Wed,  2 Dec 2020 11:58:09 -0800 (PST)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 C5F5A3A1541 for <id-event@ietf.org>; Wed,  2 Dec 2020 11:58:08 -0800 (PST)
Received: by mail-lf1-x12a.google.com with SMTP id l11so6729361lfg.0 for <id-event@ietf.org>; Wed, 02 Dec 2020 11:58:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=M5y0MQ68Vx+mwgoeADtX1PX94eiaVb3wQSkTQogUDc0=; b=f55n0U7ZLhEr9m1tjiCJQH2n5ewBStEBYfx4Ncu2w+kTSS3YBDx0XKOJeKdco34yjL 0pCrJCGxkC1W+3owStC3UMevCD+FYbEbBy/fBBJy3GkU+X3a0IHBudMIrDThiepNW081 A1dRWkzX0YeNhgA47Lfmn/2Ugv66MZTlspsuoou5Ey2NZaYiEJcX1OB38dTUxXl0W7FH ZACEXNISp+VCZ6uH6RR8cwTxEyQ8FFRUgULXfppni+yUjV0sWHKc1ekawwn6LX4D8wVR e9WwRJFEE/I3GYKwGaj7sIYHjAXDtkZSnGpvgPERXYn3vWC/Da1cluKpg/Ly/irrn86M iNng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=M5y0MQ68Vx+mwgoeADtX1PX94eiaVb3wQSkTQogUDc0=; b=KBJgVPu60nKNi66Uzbeah9bLl8sF8LDiUSf6+4/M7VW2FIvfCZ4AhSYbtRS0MJAMOU QaJUB1QbuA9qYVuPtfmbknkb1/Sf0+1+w1LxelPOxOy4Xuv8jbk3FyNJKsu9pDPXM0YP CzuiOoAByeyP8ck75tzmadQdC+gzhtLuDVs0h0l76lr9BHh3HgAIqz61j+QIgObzgUhs HHhd199BHwbiFNV7WkhmU51EY5/evqdE53f+UkSc6MMU6wN5XgyWMsZH5Fl/AFzU3dBD 3Ni0gSV6AeUMc00gI0JpFAdkMJr+jUlbdLKwgPZUL0XiLQqcoZRVkUVlnxvtLefOf7DT 2TtQ==
X-Gm-Message-State: AOAM533Iq3ntdC/KiYtUo9d0nS59bzFDXzvFnLADVRuj/p9/wHD5Sb34 XjIW1mkJrDl3V4IG8vVAng+AhJ8JxmRyWxfg0Fg=
X-Google-Smtp-Source: ABdhPJzo4IuYxpu1pauw9VQ2kLj9OZrMrJVhihBZd1unZ85t58jLw5Hqlk781mYI8mKsAGSEUzrd/k4NOV9UYZXbNPA=
X-Received: by 2002:a19:6e4c:: with SMTP id q12mr1865598lfk.162.1606939085210;  Wed, 02 Dec 2020 11:58:05 -0800 (PST)
MIME-Version: 1.0
References: <CAMCkG5u5YjqNrQu=Uth7F=QPvAy9-BwBCoQcMXd=ihMFjcHcmw@mail.gmail.com> <33AA53B6-D6E1-498C-AC47-470ABB558BDB@mit.edu> <CAMCkG5u6dVe7qKLfXhiesUNan2VwvRUFXxppzUnpT=7HQ7W_3A@mail.gmail.com> <947809F3-7C03-478F-B3A5-A483E9426375@gmail.com> <CAMCkG5t=rJKOskyRvcg5g0sV4Lf7U1zq_VTLwTHQKtbG6L=FSg@mail.gmail.com> <CAMCkG5u2sVALP38cAhDnvfXsORSxPe-LeZ0ignsUQBzwgr1U-Q@mail.gmail.com> <CAMCkG5v251jTkQqpXUzRsq68ZQZ3YzUo1zwYUeDbn0hTypqLOA@mail.gmail.com>
In-Reply-To: <CAMCkG5v251jTkQqpXUzRsq68ZQZ3YzUo1zwYUeDbn0hTypqLOA@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Wed, 2 Dec 2020 11:57:29 -0800
Message-ID: <CAD9ie-vv=3G_3hEbvpUB4b8-csCkcP-0KzUay6vL6gZE=isj5A@mail.gmail.com>
To: Atul Tulshibagwale <atultulshi=40google.com@dmarc.ietf.org>, SecEvent <id-event@ietf.org>,  "Richard Backman, Annabelle" <richanna=40amazon.com@dmarc.ietf.org>
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000598d0505b580a9a9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/VF12EJ7MAJrxXMoEaMmAlVqhqVg>
Subject: Re: [Id-event] Draft-06 issue re: subject principal grouping
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2020 19:58:12 -0000

--000000000000598d0505b580a9a9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Annabelle / Atul

Has the SPAG issue been resolved?  Would be great to get resolution and
consensus so we can propose a last call again for this draft.

/Dick
=E1=90=A7

On Wed, Nov 25, 2020 at 9:05 AM Atul Tulshibagwale <atultulshi=3D
40google.com@dmarc.ietf.org> wrote:

> Pinging this topic as discussed in the CAEP call yesterday.
>
> On Tue, Oct 13, 2020 at 11:44 AM Atul Tulshibagwale <atultulshi@google.co=
m>
> wrote:
>
>> Annabelle,
>>
>> Could you please provide an update on whether this change (any of the tw=
o
>> proposed options) is possible in this Subject Identifiers specification?
>> The work in the OpenID SSE WG cannot proceed without this clarification.
>>
>> Thanks,
>> Atul
>>
>> On Fri, Oct 2, 2020 at 4:13 PM Atul Tulshibagwale <atultulshi@google.com=
>
>> wrote:
>>
>>> Hi Yaron,
>>>
>>> I agree that SPAGs would typically need to be understood by the
>>> transmitter and receiver. However this claim need not be present in eve=
ry
>>> subject identifier, since it may not apply in many cases. Ignoring a SP=
AG
>>> value may still be OK if, say, the receiver is a single tenanted receiv=
er
>>> and the SPAG in the subject identifier is a tenant identifier. Also, no=
te
>>> that SPAGs do not necessarily only identify tenants; they may identify
>>> other subject principal groupings such as OUs, groups, etc.
>>>
>>> In general, specifications that use the Subject Identifiers
>>> specification could add claims that may have additional semantics relat=
ing
>>> to the interpretation of those claims. The Subject Identifiers
>>> specification could leave the interpretation of the additional claims o=
pen.
>>>
>>> I believe SPAGs is going to be a common enough use case, so it should b=
e
>>> included in the Subject Identifiers specification as such. But I'm OK w=
ith
>>> defining the SPAG claim in the SSE specification, if we have a way for =
the
>>> Subject Identifiers specification to allow the addition of such a claim=
 to
>>> any subject identifier.
>>>
>>> Thanks,
>>> Atul
>>>
>>> PS: There has been some discussion in the OpenID SSE WG about multiple
>>> event streams versus using SPAGs to identify different subject grouping=
s
>>> within the same stream. A good venue to discuss this is the
>>> openid-specs-risc@openid.net mailing list, and now is a good time to
>>> bring this up. The present work is captured in the SSE profile
>>> <https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profile=
-2_0.txt>
>>> draft spec (the one you referred to in your email was the RISC profile,
>>> which could be replaced with this SSE profile spec when it's ready).
>>>
>>>
>>> On Fri, Oct 2, 2020 at 8:26 AM Yaron Sheffer <yaronf.ietf@gmail.com>
>>> wrote:
>>>
>>>> Hi Justin, Atul,
>>>>
>>>> I think this may be a reasonable way to extend the solution.
>>>>
>>>> But I have a problem with Atul=E2=80=99s example below: the SPAG attri=
bute that
>>>> he=E2=80=99s proposing defines a scope (a.k.a. namespace) for the subj=
ect ID. I
>>>> don=E2=80=99t think the receiver can act correctly on the event *unles=
s* it
>>>> understands the tenant ID. So this is not a benign extension that can =
be
>>>> ignored by a receiver with no consequence.
>>>>
>>>> The SecEvent mechanism to distinguish multiple tenants is not to embed
>>>> the tenant=E2=80=99s identity in the event, rather it is to use separa=
te event
>>>> streams. In fact, this is enabled by the OpenID SSE document [1] which
>>>> defines a profile of this solution: =E2=80=9CUsing path components ena=
bles
>>>> supporting multiple issuers per host. This is required in some multi-t=
enant
>>>> hosting configurations.=E2=80=9D
>>>>
>>>> Thanks,
>>>>         Yaron
>>>>
>>>> [1]
>>>> https://openid.net/specs/openid-risc-profile-1_0-ID1.html#rfc.section.=
3.2.1
>>>>
>>>> From: Id-event <id-event-bounces@ietf.org> on behalf of Atul
>>>> Tulshibagwale <atultulshi=3D40google.com@dmarc.ietf.org>
>>>> Date: Thursday, October 1, 2020 at 19:02
>>>> To: Justin Richer <jricher@mit.edu>
>>>> Cc: SecEvent <id-event@ietf.org>
>>>> Subject: Re: [Id-event] Draft-06 issue re: subject principal grouping
>>>>
>>>> Hi Justin,
>>>> Agree with the theme of the language proposed in your email. I'd like
>>>> to propose something similar, like:
>>>>
>>>> "Each subject_type may define required fields. Subject identifiers MUS=
T
>>>> include all fields required by the subject_type, but MAY contain other
>>>> fields, either defined as optional fields within this Subject Identifi=
ers
>>>> specification or elsewhere. A receiver MUST ignore fields in a Subject
>>>> Identifier that it does not understand."
>>>>
>>>> Atul
>>>>
>>>>
>>>> On Wed, Sep 30, 2020 at 1:51 PM Justin Richer <mailto:jricher@mit.edu>
>>>> wrote:
>>>> Atul,
>>>>
>>>> I raised this in my review as well. I think the goal of the restrictio=
n
>>>> was to make the subject identifier objects compact and easily processe=
d
>>>> without getting a bunch of arbitrary stuff strung onto them, but I thi=
nk
>>>> the MUST NOT might go too far toward that.
>>>>
>>>>
>>>> I would like to see the requirement relaxed but also have guidance as
>>>> to how and when to add additional members to the object. Maybe the
>>>> subject_type field determines the REQUIRED fields and their semantics,=
 but
>>>> extensions MAY add new fields? And that a receiver MUST ignore fields =
they
>>>> don=E2=80=99t understand?
>>>>
>>>>
>>>>
>>>>  =E2=80=94 Justin
>>>>
>>>>
>>>> On Sep 29, 2020, at 8:28 PM, Atul Tulshibagwale <mailto:atultulshi=3D
>>>> 40google.com@dmarc.ietf.org> wrote:
>>>>
>>>> Hi Annabelle,
>>>> After reviewing the
>>>> https://github.com/richanna/secevent/blob/master/draft-ietf-secevent-s=
ubject-identifiers.txt
>>>> (document dated Sep 04), there's one issue that I feel needs to be
>>>> addressed:
>>>>
>>>> The sentence on line 246 ("A Subject Identifier MUST NOT contain any
>>>> members...") has the consequence that if we need to add claims in a
>>>> specific subject identifier type (e.g. email), then we will need to de=
fine
>>>> new subject identifier types.
>>>>
>>>> As discussed earlier, I am interested in adding a "Subject Principal
>>>> Administrative Grouping" or SPAG as a property of any subject identifi=
er.
>>>> This is important because the same principal may appear in different
>>>> administrative groupings, and without the disambiguation, it will be
>>>> impossible to figure out which SPAG the event that includes a subject
>>>> identifier applies to.
>>>>
>>>> For example, if the user "mailto:a@b.com" is present in two tenants of
>>>> a service that acts as a SSE Receiver. Say the tenant names in which t=
his
>>>> user occurs is "http://B.com" and "http://C.com". This can happen if
>>>> "mailto:a@b.com" is an employee of the tenant http://B.com, but is on
>>>> a contract for a project that is run by the tenant "http://C.com".
>>>>
>>>> If the event received only has the subject:
>>>> "subject" : {
>>>>   "subject_type" : "email",
>>>>   "email" : "mailto:a@b.com"
>>>> }
>>>>
>>>> Then it will be impossible for the receiver to determine whether the
>>>> event applies to the tenant http://B.com or http://C.com. If on the
>>>> other hand, an optional claim "spag_id" is added, then the subject loo=
ks
>>>> like:
>>>>
>>>> "subject" : {
>>>>   "subject_type" : "email",
>>>>   "email" : "mailto:a@b.com",
>>>>   "spag_id" : "http://B.com"
>>>> }
>>>>
>>>> This disambiguates the particular grouping that the event applies to.
>>>>
>>>> So, I feel there are at least two ways of addressing this concern:
>>>> 1. Include SPAGs as a concept in the Subject Identifiers spec and allo=
w
>>>> a "spag_id" claim in any subject identifier
>>>> 2. Drop the requirement on line 246, and allow subject identifiers to
>>>> have additional claims, which may be defined elsewhere.
>>>> Thanks,
>>>> Atul
>>>>
>>>> _______________________________________________
>>>> Id-event mailing list
>>>> mailto:Id-event@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/id-event
>>>>
>>>> _______________________________________________ Id-event mailing list
>>>> Id-event@ietf.org https://www.ietf.org/mailman/listinfo/id-event
>>>>
>>>>
>>>> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>

--000000000000598d0505b580a9a9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Annabelle / Atul<div><br></div><div>Has the SPAG issue bee=
n=C2=A0resolved?=C2=A0 Would be great to get resolution and consensus so we=
 can propose a last call again for this draft.</div><div><br></div><div>/Di=
ck</div></div><div hspace=3D"streak-pt-mark" style=3D"max-height:1px"><img =
alt=3D"" style=3D"width:0px;max-height:0px;overflow:hidden" src=3D"https://=
mailfoogae.appspot.com/t?sender=3DaZGljay5oYXJkdEBnbWFpbC5jb20%3D&amp;type=
=3Dzerocontent&amp;guid=3Dc798286b-c826-4082-ab1b-ace668e914a1"><font color=
=3D"#ffffff" size=3D"1">=E1=90=A7</font></div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Nov 25, 2020 at 9:05 AM Atu=
l Tulshibagwale &lt;atultulshi=3D<a href=3D"mailto:40google.com@dmarc.ietf.=
org">40google.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr">Pinging this topic as dis=
cussed in the CAEP call yesterday.</div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 13, 2020 at 11:44 AM Atul Tul=
shibagwale &lt;<a href=3D"mailto:atultulshi@google.com" target=3D"_blank">a=
tultulshi@google.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr">Annabelle,<div><br><div>Could you plea=
se provide an update on whether this change (any of the two proposed option=
s) is possible in this Subject Identifiers specification? The work in the O=
penID SSE WG cannot proceed without this clarification.</div><div><br></div=
><div>Thanks,</div><div>Atul</div></div></div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 2, 2020 at 4:13 PM Atul=
 Tulshibagwale &lt;<a href=3D"mailto:atultulshi@google.com" target=3D"_blan=
k">atultulshi@google.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr">Hi=C2=A0Yaron,<div><br></div><div>=
I agree that SPAGs would typically need to be understood by the transmitter=
 and receiver. However this claim need not be present in every subject iden=
tifier, since it may not apply in many=C2=A0cases. Ignoring a SPAG value ma=
y still be OK if, say, the receiver is a single tenanted receiver and the S=
PAG in the subject identifier is a tenant identifier. Also,=C2=A0note that =
SPAGs do not necessarily only identify tenants; they may identify other sub=
ject principal groupings such as OUs, groups, etc.</div><div><br></div><div=
>In general, specifications that use the Subject Identifiers specification =
could add claims that may have additional semantics relating to the interpr=
etation of those claims. The Subject Identifiers specification could leave =
the interpretation of the additional claims open.</div><div><br></div><div>=
I believe SPAGs is going to be a common enough use case, so it should be in=
cluded in the Subject Identifiers specification as such. But I&#39;m OK wit=
h defining the SPAG claim in the SSE specification, if we have a way for th=
e Subject Identifiers specification to allow the addition of such a claim t=
o any subject identifier.</div><div><br></div><div>Thanks,</div><div>Atul</=
div><div><br></div><div>PS: There has been some discussion in the OpenID SS=
E WG about multiple event streams versus using SPAGs to identify different =
subject groupings within the same stream. A good venue to discuss this is t=
he <a href=3D"mailto:openid-specs-risc@openid.net" target=3D"_blank">openid=
-specs-risc@openid.net</a> mailing list, and now is a good time to bring th=
is up. The present work is captured in the <a href=3D"https://bitbucket.org=
/openid/risc/src/caep-draft-01/openid-sse-profile-2_0.txt" target=3D"_blank=
">SSE profile</a> draft spec (the one you referred to in your email was the=
 RISC profile, which could be replaced with this SSE profile spec when it&#=
39;s ready). </div><div><br></div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 2, 2020 at 8:26 AM Yaron Shef=
fer &lt;<a href=3D"mailto:yaronf.ietf@gmail.com" target=3D"_blank">yaronf.i=
etf@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">Hi Justin, Atul,<br>
<br>
I think this may be a reasonable way to extend the solution.<br>
<br>
But I have a problem with Atul=E2=80=99s example below: the SPAG attribute =
that he=E2=80=99s proposing defines a scope (a.k.a. namespace) for the subj=
ect ID. I don=E2=80=99t think the receiver can act correctly on the event *=
unless* it understands the tenant ID. So this is not a benign extension tha=
t can be ignored by a receiver with no consequence.<br>
<br>
The SecEvent mechanism to distinguish multiple tenants is not to embed the =
tenant=E2=80=99s identity in the event, rather it is to use separate event =
streams. In fact, this is enabled by the OpenID SSE document [1] which defi=
nes a profile of this solution: =E2=80=9CUsing path components enables supp=
orting multiple issuers per host. This is required in some multi-tenant hos=
ting configurations.=E2=80=9D<br>
<br>
Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Yaron<br>
<br>
[1] <a href=3D"https://openid.net/specs/openid-risc-profile-1_0-ID1.html#rf=
c.section.3.2.1" rel=3D"noreferrer" target=3D"_blank">https://openid.net/sp=
ecs/openid-risc-profile-1_0-ID1.html#rfc.section.3.2.1</a><br>
<br>
From: Id-event &lt;<a href=3D"mailto:id-event-bounces@ietf.org" target=3D"_=
blank">id-event-bounces@ietf.org</a>&gt; on behalf of Atul Tulshibagwale &l=
t;atultulshi=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_bl=
ank">40google.com@dmarc.ietf.org</a>&gt;<br>
Date: Thursday, October 1, 2020 at 19:02<br>
To: Justin Richer &lt;<a href=3D"mailto:jricher@mit.edu" target=3D"_blank">=
jricher@mit.edu</a>&gt;<br>
Cc: SecEvent &lt;<a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-=
event@ietf.org</a>&gt;<br>
Subject: Re: [Id-event] Draft-06 issue re: subject principal grouping<br>
<br>
Hi Justin,<br>
Agree with the theme of the language proposed in your email. I&#39;d like t=
o propose something similar, like:<br>
<br>
&quot;Each subject_type may define required fields. Subject identifiers MUS=
T include all fields required by the subject_type, but MAY contain other fi=
elds,=C2=A0either defined as optional fields within this Subject Identifier=
s specification or elsewhere. A receiver MUST ignore fields in a Subject Id=
entifier that it does not understand.&quot;<br>
<br>
Atul<br>
<br>
<br>
On Wed, Sep 30, 2020 at 1:51 PM Justin Richer &lt;mailto:<a href=3D"mailto:=
jricher@mit.edu" target=3D"_blank">jricher@mit.edu</a>&gt; wrote:<br>
Atul,<br>
<br>
I raised this in my review as well. I think the goal of the restriction was=
 to make the subject identifier objects compact and easily processed withou=
t getting a bunch of arbitrary stuff strung onto them, but I think the MUST=
 NOT might go too far toward that.<br>
<br>
<br>
I would like to see the requirement relaxed but also have guidance as to ho=
w and when to add additional members to the object. Maybe the subject_type =
field determines the REQUIRED fields and their semantics, but extensions MA=
Y add new fields? And that a receiver MUST ignore fields they don=E2=80=99t=
 understand?=C2=A0<br>
<br>
<br>
<br>
=C2=A0=E2=80=94 Justin<br>
<br>
<br>
On Sep 29, 2020, at 8:28 PM, Atul Tulshibagwale &lt;mailto:<a href=3D"mailt=
o:atultulshi" target=3D"_blank">atultulshi</a>=3D<a href=3D"mailto:40google=
.com@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt; =
wrote:<br>
<br>
Hi Annabelle,<br>
After reviewing the <a href=3D"https://github.com/richanna/secevent/blob/ma=
ster/draft-ietf-secevent-subject-identifiers.txt" rel=3D"noreferrer" target=
=3D"_blank">https://github.com/richanna/secevent/blob/master/draft-ietf-sec=
event-subject-identifiers.txt</a> (document dated Sep 04), there&#39;s one =
issue that I feel needs=C2=A0to be addressed:<br>
<br>
The sentence=C2=A0on line=C2=A0246 (&quot;A Subject Identifier MUST NOT con=
tain any members...&quot;) has the consequence that if we need to add claim=
s in a specific subject identifier type (e.g. email), then we will need to =
define new subject identifier types.<br>
<br>
As discussed earlier, I am interested in adding a &quot;Subject Principal A=
dministrative Grouping&quot; or SPAG as a property of any subject identifie=
r. This is important because the same principal may appear in different adm=
inistrative groupings, and without the disambiguation, it will be impossibl=
e to figure out which SPAG the event that includes a subject identifier app=
lies to.<br>
<br>
For example, if the user &quot;mailto:<a href=3D"mailto:a@b.com" target=3D"=
_blank">a@b.com</a>&quot; is present in two tenants of a service that acts =
as a SSE Receiver. Say the tenant names in which this user occurs is &quot;=
<a href=3D"http://B.com" rel=3D"noreferrer" target=3D"_blank">http://B.com<=
/a>&quot; and &quot;<a href=3D"http://C.com" rel=3D"noreferrer" target=3D"_=
blank">http://C.com</a>&quot;. This can happen if &quot;mailto:<a href=3D"m=
ailto:a@b.com" target=3D"_blank">a@b.com</a>&quot; is an employee of the te=
nant <a href=3D"http://B.com" rel=3D"noreferrer" target=3D"_blank">http://B=
.com</a>, but is on a contract for a project that is run by the tenant &quo=
t;<a href=3D"http://C.com" rel=3D"noreferrer" target=3D"_blank">http://C.co=
m</a>&quot;.<br>
<br>
If the event received only has the subject:<br>
&quot;subject&quot; : {<br>
=C2=A0 &quot;subject_type&quot; : &quot;email&quot;,<br>
=C2=A0 &quot;email&quot; : &quot;mailto:<a href=3D"mailto:a@b.com" target=
=3D"_blank">a@b.com</a>&quot;<br>
}<br>
<br>
Then it will be impossible for the receiver to determine whether the event =
applies to the tenant <a href=3D"http://B.com" rel=3D"noreferrer" target=3D=
"_blank">http://B.com</a> or <a href=3D"http://C.com" rel=3D"noreferrer" ta=
rget=3D"_blank">http://C.com</a>. If on the other hand, an optional claim &=
quot;spag_id&quot; is added, then the subject looks like:<br>
<br>
&quot;subject&quot; : {<br>
=C2=A0 &quot;subject_type&quot; : &quot;email&quot;,<br>
=C2=A0 &quot;email&quot; : &quot;mailto:<a href=3D"mailto:a@b.com" target=
=3D"_blank">a@b.com</a>&quot;,<br>
=C2=A0 &quot;spag_id&quot; : &quot;<a href=3D"http://B.com" rel=3D"noreferr=
er" target=3D"_blank">http://B.com</a>&quot;<br>
}<br>
<br>
This disambiguates the particular grouping that the event applies to.<br>
<br>
So, I feel there are at least two ways of addressing this concern:<br>
1. Include SPAGs as a concept in the Subject Identifiers spec and allow a &=
quot;spag_id&quot; claim in any subject identifier<br>
2. Drop the requirement on line 246, and allow subject identifiers to have =
additional claims, which may be defined elsewhere.<br>
Thanks,<br>
Atul<br>
<br>
_______________________________________________<br>
Id-event mailing list<br>
mailto:<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf=
.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
<br>
_______________________________________________ Id-event mailing list <a hr=
ef=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a> <a =
href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a> <br>
<br>
<br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>

--000000000000598d0505b580a9a9--


From nobody Wed Dec  2 16:14:08 2020
Return-Path: <atultulshi@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E717B3A1645 for <id-event@ietfa.amsl.com>; Wed,  2 Dec 2020 16:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.598
X-Spam-Level: 
X-Spam-Status: No, score=-17.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LTrWPnUy5so2 for <id-event@ietfa.amsl.com>; Wed,  2 Dec 2020 16:14:05 -0800 (PST)
Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (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 7ABF03A1643 for <id-event@ietf.org>; Wed,  2 Dec 2020 16:14:05 -0800 (PST)
Received: by mail-yb1-xb2c.google.com with SMTP id t33so413680ybd.0 for <id-event@ietf.org>; Wed, 02 Dec 2020 16:14:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YzEh8cnJzx+EleHw8e5EKhpaY5KYCxPYXZcUjvTXk30=; b=u/Y8z53qXGq5SP9C7jLCUjX+TA6gdH5lq0VhEKX3wfvMHuwm6OAQ7ouJhDwowQvDRM xWtqVvXKsHPy7YCtojELsfmitpBBga7rN5K0C6ie1R6rG7KxzJRY2l5k9GirnfrpBCEy bPdIxmTwSy9nOCmCHGsv0qbtJU7lpZRz9C0RD6+p1IRyB4gNRKUHWKcGUqx6SRRny9o6 aRk5VDm2tQcic78PsUjCm89Yp/A7biJtCF375NgfvUWyUfqBTCAI97708pmBouZBfMb9 JlqRpBtW9z4/CB4ZpXyiGyclv0zO/keHF0j0Svo/Y3wKHpL7f/Io/iXb31CGRQOE5RTM U5QQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YzEh8cnJzx+EleHw8e5EKhpaY5KYCxPYXZcUjvTXk30=; b=qwQhWlPivhya34Mj05y3S0owWuo6lzzX8ohE4m1nZR3sRF2juw3wOSbGWWguppxPEz KRIPQEE+frfVBPc7xmtK94GkbcyurQNsaq9rZl8wKYs9B34x5ifKYYKXkqaS6bjbXEqI tYNGOmQteiD18OIi95mLnk/EGX8UHvPRmnP1YtBvO8IGYhJIi1u5nXfiwkLSXpF2JU9C qobY7Jtjbb9e9B1up+gJyW8xHPO4hoOge22m2cblXSU+bKgdbFlGAWLCxx2mAel8h5wi QTZNp9k9I190UR14A6bRQbOM4bgxxcDivuHC4f7Qb+GnX4Z9zcBWRnE949/Wxm1mt01x uRQQ==
X-Gm-Message-State: AOAM532bryIe+u8Y02SvL3Kpy6rj9ab8hT5cDbFI67cpnxawaKUaTyHj cmXRmhE3ytNxb8EybqKg1GZptJdkaRhzwaUsrJR4Rg==
X-Google-Smtp-Source: ABdhPJzZJMvpwPhaoJ1jSOiB+bzke1j0KNQ3ljZaVuSzBpy7IcdUCKsz/WHlXcugI1QqWk4tSC3xrz/Yzp2TQAhpADw=
X-Received: by 2002:a25:cd48:: with SMTP id d69mr905944ybf.465.1606954444365;  Wed, 02 Dec 2020 16:14:04 -0800 (PST)
MIME-Version: 1.0
References: <CAMCkG5u5YjqNrQu=Uth7F=QPvAy9-BwBCoQcMXd=ihMFjcHcmw@mail.gmail.com> <33AA53B6-D6E1-498C-AC47-470ABB558BDB@mit.edu> <CAMCkG5u6dVe7qKLfXhiesUNan2VwvRUFXxppzUnpT=7HQ7W_3A@mail.gmail.com> <947809F3-7C03-478F-B3A5-A483E9426375@gmail.com> <CAMCkG5t=rJKOskyRvcg5g0sV4Lf7U1zq_VTLwTHQKtbG6L=FSg@mail.gmail.com> <CAMCkG5u2sVALP38cAhDnvfXsORSxPe-LeZ0ignsUQBzwgr1U-Q@mail.gmail.com> <CAMCkG5v251jTkQqpXUzRsq68ZQZ3YzUo1zwYUeDbn0hTypqLOA@mail.gmail.com> <CAD9ie-vv=3G_3hEbvpUB4b8-csCkcP-0KzUay6vL6gZE=isj5A@mail.gmail.com>
In-Reply-To: <CAD9ie-vv=3G_3hEbvpUB4b8-csCkcP-0KzUay6vL6gZE=isj5A@mail.gmail.com>
From: Atul Tulshibagwale <atultulshi@google.com>
Date: Wed, 2 Dec 2020 16:13:52 -0800
Message-ID: <CAMCkG5sUuLHHO36+jTtMerdT=p3ASBUgq89QPwr0OadiH_SvVA@mail.gmail.com>
To: Dick Hardt <dick.hardt@gmail.com>
Cc: Atul Tulshibagwale <atultulshi=40google.com@dmarc.ietf.org>, SecEvent <id-event@ietf.org>,  "Richard Backman, Annabelle" <richanna=40amazon.com@dmarc.ietf.org>,  Yaron Sheffer <yaronf.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000d401d905b5843c50"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/c9A3-eVmPj7JMarakjvM0chR8F0>
Subject: Re: [Id-event] Draft-06 issue re: subject principal grouping
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2020 00:14:08 -0000

--000000000000d401d905b5843c50
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Dick,

Just a quick clarification: My request above is to allow attributes that
are not defined in specific subject_type descriptions in the SecEvents
Subject Identifiers specification to be allowed to be added by other
specifications that use it. The SPAG attribute is only an example of such
an addition that we are interested in for the OpenID Shared Signals and
Events WG.

Atul

On Wed, Dec 2, 2020 at 11:58 AM Dick Hardt <dick.hardt@gmail.com> wrote:

> Annabelle / Atul
>
> Has the SPAG issue been resolved?  Would be great to get resolution and
> consensus so we can propose a last call again for this draft.
>
> /Dick
> =E1=90=A7
>
> On Wed, Nov 25, 2020 at 9:05 AM Atul Tulshibagwale <atultulshi=3D
> 40google.com@dmarc.ietf.org> wrote:
>
>> Pinging this topic as discussed in the CAEP call yesterday.
>>
>> On Tue, Oct 13, 2020 at 11:44 AM Atul Tulshibagwale <
>> atultulshi@google.com> wrote:
>>
>>> Annabelle,
>>>
>>> Could you please provide an update on whether this change (any of the
>>> two proposed options) is possible in this Subject Identifiers
>>> specification? The work in the OpenID SSE WG cannot proceed without thi=
s
>>> clarification.
>>>
>>> Thanks,
>>> Atul
>>>
>>> On Fri, Oct 2, 2020 at 4:13 PM Atul Tulshibagwale <atultulshi@google.co=
m>
>>> wrote:
>>>
>>>> Hi Yaron,
>>>>
>>>> I agree that SPAGs would typically need to be understood by the
>>>> transmitter and receiver. However this claim need not be present in ev=
ery
>>>> subject identifier, since it may not apply in many cases. Ignoring a S=
PAG
>>>> value may still be OK if, say, the receiver is a single tenanted recei=
ver
>>>> and the SPAG in the subject identifier is a tenant identifier. Also, n=
ote
>>>> that SPAGs do not necessarily only identify tenants; they may identify
>>>> other subject principal groupings such as OUs, groups, etc.
>>>>
>>>> In general, specifications that use the Subject Identifiers
>>>> specification could add claims that may have additional semantics rela=
ting
>>>> to the interpretation of those claims. The Subject Identifiers
>>>> specification could leave the interpretation of the additional claims =
open.
>>>>
>>>> I believe SPAGs is going to be a common enough use case, so it should
>>>> be included in the Subject Identifiers specification as such. But I'm =
OK
>>>> with defining the SPAG claim in the SSE specification, if we have a wa=
y for
>>>> the Subject Identifiers specification to allow the addition of such a =
claim
>>>> to any subject identifier.
>>>>
>>>> Thanks,
>>>> Atul
>>>>
>>>> PS: There has been some discussion in the OpenID SSE WG about multiple
>>>> event streams versus using SPAGs to identify different subject groupin=
gs
>>>> within the same stream. A good venue to discuss this is the
>>>> openid-specs-risc@openid.net mailing list, and now is a good time to
>>>> bring this up. The present work is captured in the SSE profile
>>>> <https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profil=
e-2_0.txt>
>>>> draft spec (the one you referred to in your email was the RISC profile=
,
>>>> which could be replaced with this SSE profile spec when it's ready).
>>>>
>>>>
>>>> On Fri, Oct 2, 2020 at 8:26 AM Yaron Sheffer <yaronf.ietf@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Justin, Atul,
>>>>>
>>>>> I think this may be a reasonable way to extend the solution.
>>>>>
>>>>> But I have a problem with Atul=E2=80=99s example below: the SPAG attr=
ibute
>>>>> that he=E2=80=99s proposing defines a scope (a.k.a. namespace) for th=
e subject ID.
>>>>> I don=E2=80=99t think the receiver can act correctly on the event *un=
less* it
>>>>> understands the tenant ID. So this is not a benign extension that can=
 be
>>>>> ignored by a receiver with no consequence.
>>>>>
>>>>> The SecEvent mechanism to distinguish multiple tenants is not to embe=
d
>>>>> the tenant=E2=80=99s identity in the event, rather it is to use separ=
ate event
>>>>> streams. In fact, this is enabled by the OpenID SSE document [1] whic=
h
>>>>> defines a profile of this solution: =E2=80=9CUsing path components en=
ables
>>>>> supporting multiple issuers per host. This is required in some multi-=
tenant
>>>>> hosting configurations.=E2=80=9D
>>>>>
>>>>> Thanks,
>>>>>         Yaron
>>>>>
>>>>> [1]
>>>>> https://openid.net/specs/openid-risc-profile-1_0-ID1.html#rfc.section=
.3.2.1
>>>>>
>>>>> From: Id-event <id-event-bounces@ietf.org> on behalf of Atul
>>>>> Tulshibagwale <atultulshi=3D40google.com@dmarc.ietf.org>
>>>>> Date: Thursday, October 1, 2020 at 19:02
>>>>> To: Justin Richer <jricher@mit.edu>
>>>>> Cc: SecEvent <id-event@ietf.org>
>>>>> Subject: Re: [Id-event] Draft-06 issue re: subject principal grouping
>>>>>
>>>>> Hi Justin,
>>>>> Agree with the theme of the language proposed in your email. I'd like
>>>>> to propose something similar, like:
>>>>>
>>>>> "Each subject_type may define required fields. Subject identifiers
>>>>> MUST include all fields required by the subject_type, but MAY contain=
 other
>>>>> fields, either defined as optional fields within this Subject Identif=
iers
>>>>> specification or elsewhere. A receiver MUST ignore fields in a Subjec=
t
>>>>> Identifier that it does not understand."
>>>>>
>>>>> Atul
>>>>>
>>>>>
>>>>> On Wed, Sep 30, 2020 at 1:51 PM Justin Richer <mailto:jricher@mit.edu=
>
>>>>> wrote:
>>>>> Atul,
>>>>>
>>>>> I raised this in my review as well. I think the goal of the
>>>>> restriction was to make the subject identifier objects compact and ea=
sily
>>>>> processed without getting a bunch of arbitrary stuff strung onto them=
, but
>>>>> I think the MUST NOT might go too far toward that.
>>>>>
>>>>>
>>>>> I would like to see the requirement relaxed but also have guidance as
>>>>> to how and when to add additional members to the object. Maybe the
>>>>> subject_type field determines the REQUIRED fields and their semantics=
, but
>>>>> extensions MAY add new fields? And that a receiver MUST ignore fields=
 they
>>>>> don=E2=80=99t understand?
>>>>>
>>>>>
>>>>>
>>>>>  =E2=80=94 Justin
>>>>>
>>>>>
>>>>> On Sep 29, 2020, at 8:28 PM, Atul Tulshibagwale <mailto:atultulshi=3D
>>>>> 40google.com@dmarc.ietf.org> wrote:
>>>>>
>>>>> Hi Annabelle,
>>>>> After reviewing the
>>>>> https://github.com/richanna/secevent/blob/master/draft-ietf-secevent-=
subject-identifiers.txt
>>>>> (document dated Sep 04), there's one issue that I feel needs to be
>>>>> addressed:
>>>>>
>>>>> The sentence on line 246 ("A Subject Identifier MUST NOT contain any
>>>>> members...") has the consequence that if we need to add claims in a
>>>>> specific subject identifier type (e.g. email), then we will need to d=
efine
>>>>> new subject identifier types.
>>>>>
>>>>> As discussed earlier, I am interested in adding a "Subject Principal
>>>>> Administrative Grouping" or SPAG as a property of any subject identif=
ier.
>>>>> This is important because the same principal may appear in different
>>>>> administrative groupings, and without the disambiguation, it will be
>>>>> impossible to figure out which SPAG the event that includes a subject
>>>>> identifier applies to.
>>>>>
>>>>> For example, if the user "mailto:a@b.com" is present in two tenants
>>>>> of a service that acts as a SSE Receiver. Say the tenant names in whi=
ch
>>>>> this user occurs is "http://B.com" and "http://C.com". This can
>>>>> happen if "mailto:a@b.com" is an employee of the tenant http://B.com,
>>>>> but is on a contract for a project that is run by the tenant "
>>>>> http://C.com".
>>>>>
>>>>> If the event received only has the subject:
>>>>> "subject" : {
>>>>>   "subject_type" : "email",
>>>>>   "email" : "mailto:a@b.com"
>>>>> }
>>>>>
>>>>> Then it will be impossible for the receiver to determine whether the
>>>>> event applies to the tenant http://B.com or http://C.com. If on the
>>>>> other hand, an optional claim "spag_id" is added, then the subject lo=
oks
>>>>> like:
>>>>>
>>>>> "subject" : {
>>>>>   "subject_type" : "email",
>>>>>   "email" : "mailto:a@b.com",
>>>>>   "spag_id" : "http://B.com"
>>>>> }
>>>>>
>>>>> This disambiguates the particular grouping that the event applies to.
>>>>>
>>>>> So, I feel there are at least two ways of addressing this concern:
>>>>> 1. Include SPAGs as a concept in the Subject Identifiers spec and
>>>>> allow a "spag_id" claim in any subject identifier
>>>>> 2. Drop the requirement on line 246, and allow subject identifiers to
>>>>> have additional claims, which may be defined elsewhere.
>>>>> Thanks,
>>>>> Atul
>>>>>
>>>>> _______________________________________________
>>>>> Id-event mailing list
>>>>> mailto:Id-event@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/id-event
>>>>>
>>>>> _______________________________________________ Id-event mailing list
>>>>> Id-event@ietf.org https://www.ietf.org/mailman/listinfo/id-event
>>>>>
>>>>>
>>>>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>

--000000000000d401d905b5843c50
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Dick,<div><br><div>Just a quick clarification: My reque=
st above is to allow attributes that are not defined in specific subject_ty=
pe descriptions in the SecEvents Subject Identifiers specification to be al=
lowed to be added by other specifications that use it. The SPAG attribute i=
s only an example of such an addition that we are interested in for the Ope=
nID Shared Signals and Events WG.</div><div><br></div><div>Atul</div></div>=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Wed, Dec 2, 2020 at 11:58 AM Dick Hardt &lt;<a href=3D"mailto:dick.hardt=
@gmail.com">dick.hardt@gmail.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr">Annabelle / Atul<div><br>=
</div><div>Has the SPAG issue been=C2=A0resolved?=C2=A0 Would be great to g=
et resolution and consensus so we can propose a last call again for this dr=
aft.</div><div><br></div><div>/Dick</div></div><div hspace=3D"streak-pt-mar=
k" style=3D"max-height:1px"><img alt=3D"" style=3D"width: 0px; max-height: =
0px; overflow: hidden;" src=3D"https://mailfoogae.appspot.com/t?sender=3DaZ=
Gljay5oYXJkdEBnbWFpbC5jb20%3D&amp;type=3Dzerocontent&amp;guid=3Dc798286b-c8=
26-4082-ab1b-ace668e914a1"><font color=3D"#ffffff" size=3D"1">=E1=90=A7</fo=
nt></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_att=
r">On Wed, Nov 25, 2020 at 9:05 AM Atul Tulshibagwale &lt;atultulshi=3D<a h=
ref=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank">40google.com@d=
marc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div dir=3D"ltr">Pinging this topic as discussed in the CAEP c=
all yesterday.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Tue, Oct 13, 2020 at 11:44 AM Atul Tulshibagwale &lt;<a =
href=3D"mailto:atultulshi@google.com" target=3D"_blank">atultulshi@google.c=
om</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><div dir=3D"ltr">Annabelle,<div><br><div>Could you please provide an upda=
te on whether this change (any of the two proposed options) is possible in =
this Subject Identifiers specification? The work in the OpenID SSE WG canno=
t proceed without this clarification.</div><div><br></div><div>Thanks,</div=
><div>Atul</div></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr"=
 class=3D"gmail_attr">On Fri, Oct 2, 2020 at 4:13 PM Atul Tulshibagwale &lt=
;<a href=3D"mailto:atultulshi@google.com" target=3D"_blank">atultulshi@goog=
le.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><div dir=3D"ltr">Hi=C2=A0Yaron,<div><br></div><div>I agree that SPAGs=
 would typically need to be understood by the transmitter and receiver. How=
ever this claim need not be present in every subject identifier, since it m=
ay not apply in many=C2=A0cases. Ignoring a SPAG value may still be OK if, =
say, the receiver is a single tenanted receiver and the SPAG in the subject=
 identifier is a tenant identifier. Also,=C2=A0note that SPAGs do not neces=
sarily only identify tenants; they may identify other subject principal gro=
upings such as OUs, groups, etc.</div><div><br></div><div>In general, speci=
fications that use the Subject Identifiers specification could add claims t=
hat may have additional semantics relating to the interpretation of those c=
laims. The Subject Identifiers specification could leave the interpretation=
 of the additional claims open.</div><div><br></div><div>I believe SPAGs is=
 going to be a common enough use case, so it should be included in the Subj=
ect Identifiers specification as such. But I&#39;m OK with defining the SPA=
G claim in the SSE specification, if we have a way for the Subject Identifi=
ers specification to allow the addition of such a claim to any subject iden=
tifier.</div><div><br></div><div>Thanks,</div><div>Atul</div><div><br></div=
><div>PS: There has been some discussion in the OpenID SSE WG about multipl=
e event streams versus using SPAGs to identify different subject groupings =
within the same stream. A good venue to discuss this is the <a href=3D"mail=
to:openid-specs-risc@openid.net" target=3D"_blank">openid-specs-risc@openid=
.net</a> mailing list, and now is a good time to bring this up. The present=
 work is captured in the <a href=3D"https://bitbucket.org/openid/risc/src/c=
aep-draft-01/openid-sse-profile-2_0.txt" target=3D"_blank">SSE profile</a> =
draft spec (the one you referred to in your email was the RISC profile, whi=
ch could be replaced with this SSE profile spec when it&#39;s ready). </div=
><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Fri, Oct 2, 2020 at 8:26 AM Yaron Sheffer &lt;<a href=3D=
"mailto:yaronf.ietf@gmail.com" target=3D"_blank">yaronf.ietf@gmail.com</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Ju=
stin, Atul,<br>
<br>
I think this may be a reasonable way to extend the solution.<br>
<br>
But I have a problem with Atul=E2=80=99s example below: the SPAG attribute =
that he=E2=80=99s proposing defines a scope (a.k.a. namespace) for the subj=
ect ID. I don=E2=80=99t think the receiver can act correctly on the event *=
unless* it understands the tenant ID. So this is not a benign extension tha=
t can be ignored by a receiver with no consequence.<br>
<br>
The SecEvent mechanism to distinguish multiple tenants is not to embed the =
tenant=E2=80=99s identity in the event, rather it is to use separate event =
streams. In fact, this is enabled by the OpenID SSE document [1] which defi=
nes a profile of this solution: =E2=80=9CUsing path components enables supp=
orting multiple issuers per host. This is required in some multi-tenant hos=
ting configurations.=E2=80=9D<br>
<br>
Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Yaron<br>
<br>
[1] <a href=3D"https://openid.net/specs/openid-risc-profile-1_0-ID1.html#rf=
c.section.3.2.1" rel=3D"noreferrer" target=3D"_blank">https://openid.net/sp=
ecs/openid-risc-profile-1_0-ID1.html#rfc.section.3.2.1</a><br>
<br>
From: Id-event &lt;<a href=3D"mailto:id-event-bounces@ietf.org" target=3D"_=
blank">id-event-bounces@ietf.org</a>&gt; on behalf of Atul Tulshibagwale &l=
t;atultulshi=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_bl=
ank">40google.com@dmarc.ietf.org</a>&gt;<br>
Date: Thursday, October 1, 2020 at 19:02<br>
To: Justin Richer &lt;<a href=3D"mailto:jricher@mit.edu" target=3D"_blank">=
jricher@mit.edu</a>&gt;<br>
Cc: SecEvent &lt;<a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-=
event@ietf.org</a>&gt;<br>
Subject: Re: [Id-event] Draft-06 issue re: subject principal grouping<br>
<br>
Hi Justin,<br>
Agree with the theme of the language proposed in your email. I&#39;d like t=
o propose something similar, like:<br>
<br>
&quot;Each subject_type may define required fields. Subject identifiers MUS=
T include all fields required by the subject_type, but MAY contain other fi=
elds,=C2=A0either defined as optional fields within this Subject Identifier=
s specification or elsewhere. A receiver MUST ignore fields in a Subject Id=
entifier that it does not understand.&quot;<br>
<br>
Atul<br>
<br>
<br>
On Wed, Sep 30, 2020 at 1:51 PM Justin Richer &lt;mailto:<a href=3D"mailto:=
jricher@mit.edu" target=3D"_blank">jricher@mit.edu</a>&gt; wrote:<br>
Atul,<br>
<br>
I raised this in my review as well. I think the goal of the restriction was=
 to make the subject identifier objects compact and easily processed withou=
t getting a bunch of arbitrary stuff strung onto them, but I think the MUST=
 NOT might go too far toward that.<br>
<br>
<br>
I would like to see the requirement relaxed but also have guidance as to ho=
w and when to add additional members to the object. Maybe the subject_type =
field determines the REQUIRED fields and their semantics, but extensions MA=
Y add new fields? And that a receiver MUST ignore fields they don=E2=80=99t=
 understand?=C2=A0<br>
<br>
<br>
<br>
=C2=A0=E2=80=94 Justin<br>
<br>
<br>
On Sep 29, 2020, at 8:28 PM, Atul Tulshibagwale &lt;mailto:<a href=3D"mailt=
o:atultulshi" target=3D"_blank">atultulshi</a>=3D<a href=3D"mailto:40google=
.com@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt; =
wrote:<br>
<br>
Hi Annabelle,<br>
After reviewing the <a href=3D"https://github.com/richanna/secevent/blob/ma=
ster/draft-ietf-secevent-subject-identifiers.txt" rel=3D"noreferrer" target=
=3D"_blank">https://github.com/richanna/secevent/blob/master/draft-ietf-sec=
event-subject-identifiers.txt</a> (document dated Sep 04), there&#39;s one =
issue that I feel needs=C2=A0to be addressed:<br>
<br>
The sentence=C2=A0on line=C2=A0246 (&quot;A Subject Identifier MUST NOT con=
tain any members...&quot;) has the consequence that if we need to add claim=
s in a specific subject identifier type (e.g. email), then we will need to =
define new subject identifier types.<br>
<br>
As discussed earlier, I am interested in adding a &quot;Subject Principal A=
dministrative Grouping&quot; or SPAG as a property of any subject identifie=
r. This is important because the same principal may appear in different adm=
inistrative groupings, and without the disambiguation, it will be impossibl=
e to figure out which SPAG the event that includes a subject identifier app=
lies to.<br>
<br>
For example, if the user &quot;mailto:<a href=3D"mailto:a@b.com" target=3D"=
_blank">a@b.com</a>&quot; is present in two tenants of a service that acts =
as a SSE Receiver. Say the tenant names in which this user occurs is &quot;=
<a href=3D"http://B.com" rel=3D"noreferrer" target=3D"_blank">http://B.com<=
/a>&quot; and &quot;<a href=3D"http://C.com" rel=3D"noreferrer" target=3D"_=
blank">http://C.com</a>&quot;. This can happen if &quot;mailto:<a href=3D"m=
ailto:a@b.com" target=3D"_blank">a@b.com</a>&quot; is an employee of the te=
nant <a href=3D"http://B.com" rel=3D"noreferrer" target=3D"_blank">http://B=
.com</a>, but is on a contract for a project that is run by the tenant &quo=
t;<a href=3D"http://C.com" rel=3D"noreferrer" target=3D"_blank">http://C.co=
m</a>&quot;.<br>
<br>
If the event received only has the subject:<br>
&quot;subject&quot; : {<br>
=C2=A0 &quot;subject_type&quot; : &quot;email&quot;,<br>
=C2=A0 &quot;email&quot; : &quot;mailto:<a href=3D"mailto:a@b.com" target=
=3D"_blank">a@b.com</a>&quot;<br>
}<br>
<br>
Then it will be impossible for the receiver to determine whether the event =
applies to the tenant <a href=3D"http://B.com" rel=3D"noreferrer" target=3D=
"_blank">http://B.com</a> or <a href=3D"http://C.com" rel=3D"noreferrer" ta=
rget=3D"_blank">http://C.com</a>. If on the other hand, an optional claim &=
quot;spag_id&quot; is added, then the subject looks like:<br>
<br>
&quot;subject&quot; : {<br>
=C2=A0 &quot;subject_type&quot; : &quot;email&quot;,<br>
=C2=A0 &quot;email&quot; : &quot;mailto:<a href=3D"mailto:a@b.com" target=
=3D"_blank">a@b.com</a>&quot;,<br>
=C2=A0 &quot;spag_id&quot; : &quot;<a href=3D"http://B.com" rel=3D"noreferr=
er" target=3D"_blank">http://B.com</a>&quot;<br>
}<br>
<br>
This disambiguates the particular grouping that the event applies to.<br>
<br>
So, I feel there are at least two ways of addressing this concern:<br>
1. Include SPAGs as a concept in the Subject Identifiers spec and allow a &=
quot;spag_id&quot; claim in any subject identifier<br>
2. Drop the requirement on line 246, and allow subject identifiers to have =
additional claims, which may be defined elsewhere.<br>
Thanks,<br>
Atul<br>
<br>
_______________________________________________<br>
Id-event mailing list<br>
mailto:<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf=
.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
<br>
_______________________________________________ Id-event mailing list <a hr=
ef=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a> <a =
href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a> <br>
<br>
<br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>

--000000000000d401d905b5843c50--


From nobody Wed Dec  2 16:45:22 2020
Return-Path: <dick.hardt@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A51AF3A0115 for <id-event@ietfa.amsl.com>; Wed,  2 Dec 2020 16:45:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 gckUy63t4bJA for <id-event@ietfa.amsl.com>; Wed,  2 Dec 2020 16:45:12 -0800 (PST)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 75CBA3A0846 for <id-event@ietf.org>; Wed,  2 Dec 2020 16:45:09 -0800 (PST)
Received: by mail-lf1-x129.google.com with SMTP id d20so174784lfe.11 for <id-event@ietf.org>; Wed, 02 Dec 2020 16:45:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WTFjR+h8kcF5Lj/hKIFFEWIyGk/qqtGVa1YbaPYgEpM=; b=i3Zw44XhjZC/odntH8aq66QB8BFVmW2lmtzYe2XOnC38FlL1+4FwCc1oqiNeI154DF s73CK76xmmC4Ww2pHnZnbFHr0kMZiHjw/1O+Si06Gjb7FaBQICyxbx65VWn3mgLNEFcA 5AGYvf+wpc5J6jhoPRE1KA9ZarSVVfokHHhFoBPf6S1QDsEyUZd5UrAnA+OfCRAOc5ak RBBLWhE5v1xV9v//X5qmo46f3Ss0V08B6fKm1JHnYiwFA+yNaoFO3R8VVm01km4lOPDf CCRaQ8BhD4/vxT3TjpJDhjBrC0Aj7zzI7xz6W6L6xthGg7Ke2IjY3frUDk64yCkHqrve lF3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WTFjR+h8kcF5Lj/hKIFFEWIyGk/qqtGVa1YbaPYgEpM=; b=rSeOQnohoK9Il6TDKQWZv4b0AmSn3UN4RqSRmXMPJ/wRhrWoaslsg3zYduRlsx6Mt0 Aw+FZll/R+DQ/cbQ4mqQq+unx6rveQLnt3Czb2bKABz+7p+Uswj3zWMmcq+gbzYimb54 PwK2tq2T3sg/XWUYhOr2n3DXxBWsMqx/Xvwpzk3EuBbMObrYCMVUuhtICgnOqOLLB5IL zQP+qaDJvo8pnyX52OKIwCQO5nuzIFDxWVgRqYa6ppRjUUyaJX4EgSxW7G9Z6oTEiudQ wxIqxqmaQDfcBHWXXNiqgaZRyqrcQbVtJ4BJjbszQJVnxPKjGxqdSmP9e88C29orLo2A dm5A==
X-Gm-Message-State: AOAM533R3is83e/rV126vptQCC2LMfbReS5fW4RMXR0OuigN9AudJHRW PQ6qz6eM6pgoK8Xgatsy3/DOAVOnu+6v8pohEWU=
X-Google-Smtp-Source: ABdhPJwm4d6u4OlNe+mxLPtrJ/JDi7WKQ7EEZrCG1OUGsnMOLtdaWClu2OTe4zzwXT5GAsH+U8KDQnRsOhPv+l70iBI=
X-Received: by 2002:a19:88a:: with SMTP id 132mr305710lfi.316.1606956307384; Wed, 02 Dec 2020 16:45:07 -0800 (PST)
MIME-Version: 1.0
References: <CAMCkG5u5YjqNrQu=Uth7F=QPvAy9-BwBCoQcMXd=ihMFjcHcmw@mail.gmail.com> <33AA53B6-D6E1-498C-AC47-470ABB558BDB@mit.edu> <CAMCkG5u6dVe7qKLfXhiesUNan2VwvRUFXxppzUnpT=7HQ7W_3A@mail.gmail.com> <947809F3-7C03-478F-B3A5-A483E9426375@gmail.com> <CAMCkG5t=rJKOskyRvcg5g0sV4Lf7U1zq_VTLwTHQKtbG6L=FSg@mail.gmail.com> <CAMCkG5u2sVALP38cAhDnvfXsORSxPe-LeZ0ignsUQBzwgr1U-Q@mail.gmail.com> <CAMCkG5v251jTkQqpXUzRsq68ZQZ3YzUo1zwYUeDbn0hTypqLOA@mail.gmail.com> <CAD9ie-vv=3G_3hEbvpUB4b8-csCkcP-0KzUay6vL6gZE=isj5A@mail.gmail.com> <CAMCkG5sUuLHHO36+jTtMerdT=p3ASBUgq89QPwr0OadiH_SvVA@mail.gmail.com>
In-Reply-To: <CAMCkG5sUuLHHO36+jTtMerdT=p3ASBUgq89QPwr0OadiH_SvVA@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Wed, 2 Dec 2020 16:44:30 -0800
Message-ID: <CAD9ie-sjuoAAdVx3Anh340P7U2jM2yh7j+nzZzNBYO_4rp3igA@mail.gmail.com>
To: Atul Tulshibagwale <atultulshi@google.com>
Cc: Atul Tulshibagwale <atultulshi=40google.com@dmarc.ietf.org>, SecEvent <id-event@ietf.org>,  "Richard Backman, Annabelle" <richanna=40amazon.com@dmarc.ietf.org>,  Yaron Sheffer <yaronf.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000df0dfc05b584abb6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/Fqb8W5bqPuzqTEfvShtY80g-LgM>
Subject: Re: [Id-event] Draft-06 issue re: subject principal grouping
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2020 00:45:16 -0000

--000000000000df0dfc05b584abb6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Atul, would you mind starting a new thread that outlines the options for
the SPAG functionality, and elaborates on other additions that the OpenID
Shared Signals and Events WG is interested in? We can then dig into the
pros and cons and get closure.

/Dick
=E1=90=A7

On Wed, Dec 2, 2020 at 4:14 PM Atul Tulshibagwale <atultulshi@google.com>
wrote:

> Hi Dick,
>
> Just a quick clarification: My request above is to allow attributes that
> are not defined in specific subject_type descriptions in the SecEvents
> Subject Identifiers specification to be allowed to be added by other
> specifications that use it. The SPAG attribute is only an example of such
> an addition that we are interested in for the OpenID Shared Signals and
> Events WG.
>
> Atul
>
> On Wed, Dec 2, 2020 at 11:58 AM Dick Hardt <dick.hardt@gmail.com> wrote:
>
>> Annabelle / Atul
>>
>> Has the SPAG issue been resolved?  Would be great to get resolution and
>> consensus so we can propose a last call again for this draft.
>>
>> /Dick
>> =E1=90=A7
>>
>> On Wed, Nov 25, 2020 at 9:05 AM Atul Tulshibagwale <atultulshi=3D
>> 40google.com@dmarc.ietf.org> wrote:
>>
>>> Pinging this topic as discussed in the CAEP call yesterday.
>>>
>>> On Tue, Oct 13, 2020 at 11:44 AM Atul Tulshibagwale <
>>> atultulshi@google.com> wrote:
>>>
>>>> Annabelle,
>>>>
>>>> Could you please provide an update on whether this change (any of the
>>>> two proposed options) is possible in this Subject Identifiers
>>>> specification? The work in the OpenID SSE WG cannot proceed without th=
is
>>>> clarification.
>>>>
>>>> Thanks,
>>>> Atul
>>>>
>>>> On Fri, Oct 2, 2020 at 4:13 PM Atul Tulshibagwale <
>>>> atultulshi@google.com> wrote:
>>>>
>>>>> Hi Yaron,
>>>>>
>>>>> I agree that SPAGs would typically need to be understood by the
>>>>> transmitter and receiver. However this claim need not be present in e=
very
>>>>> subject identifier, since it may not apply in many cases. Ignoring a =
SPAG
>>>>> value may still be OK if, say, the receiver is a single tenanted rece=
iver
>>>>> and the SPAG in the subject identifier is a tenant identifier. Also, =
note
>>>>> that SPAGs do not necessarily only identify tenants; they may identif=
y
>>>>> other subject principal groupings such as OUs, groups, etc.
>>>>>
>>>>> In general, specifications that use the Subject Identifiers
>>>>> specification could add claims that may have additional semantics rel=
ating
>>>>> to the interpretation of those claims. The Subject Identifiers
>>>>> specification could leave the interpretation of the additional claims=
 open.
>>>>>
>>>>> I believe SPAGs is going to be a common enough use case, so it should
>>>>> be included in the Subject Identifiers specification as such. But I'm=
 OK
>>>>> with defining the SPAG claim in the SSE specification, if we have a w=
ay for
>>>>> the Subject Identifiers specification to allow the addition of such a=
 claim
>>>>> to any subject identifier.
>>>>>
>>>>> Thanks,
>>>>> Atul
>>>>>
>>>>> PS: There has been some discussion in the OpenID SSE WG about multipl=
e
>>>>> event streams versus using SPAGs to identify different subject groupi=
ngs
>>>>> within the same stream. A good venue to discuss this is the
>>>>> openid-specs-risc@openid.net mailing list, and now is a good time to
>>>>> bring this up. The present work is captured in the SSE profile
>>>>> <https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profi=
le-2_0.txt>
>>>>> draft spec (the one you referred to in your email was the RISC profil=
e,
>>>>> which could be replaced with this SSE profile spec when it's ready).
>>>>>
>>>>>
>>>>> On Fri, Oct 2, 2020 at 8:26 AM Yaron Sheffer <yaronf.ietf@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Justin, Atul,
>>>>>>
>>>>>> I think this may be a reasonable way to extend the solution.
>>>>>>
>>>>>> But I have a problem with Atul=E2=80=99s example below: the SPAG att=
ribute
>>>>>> that he=E2=80=99s proposing defines a scope (a.k.a. namespace) for t=
he subject ID.
>>>>>> I don=E2=80=99t think the receiver can act correctly on the event *u=
nless* it
>>>>>> understands the tenant ID. So this is not a benign extension that ca=
n be
>>>>>> ignored by a receiver with no consequence.
>>>>>>
>>>>>> The SecEvent mechanism to distinguish multiple tenants is not to
>>>>>> embed the tenant=E2=80=99s identity in the event, rather it is to us=
e separate
>>>>>> event streams. In fact, this is enabled by the OpenID SSE document [=
1]
>>>>>> which defines a profile of this solution: =E2=80=9CUsing path compon=
ents enables
>>>>>> supporting multiple issuers per host. This is required in some multi=
-tenant
>>>>>> hosting configurations.=E2=80=9D
>>>>>>
>>>>>> Thanks,
>>>>>>         Yaron
>>>>>>
>>>>>> [1]
>>>>>> https://openid.net/specs/openid-risc-profile-1_0-ID1.html#rfc.sectio=
n.3.2.1
>>>>>>
>>>>>> From: Id-event <id-event-bounces@ietf.org> on behalf of Atul
>>>>>> Tulshibagwale <atultulshi=3D40google.com@dmarc.ietf.org>
>>>>>> Date: Thursday, October 1, 2020 at 19:02
>>>>>> To: Justin Richer <jricher@mit.edu>
>>>>>> Cc: SecEvent <id-event@ietf.org>
>>>>>> Subject: Re: [Id-event] Draft-06 issue re: subject principal groupin=
g
>>>>>>
>>>>>> Hi Justin,
>>>>>> Agree with the theme of the language proposed in your email. I'd lik=
e
>>>>>> to propose something similar, like:
>>>>>>
>>>>>> "Each subject_type may define required fields. Subject identifiers
>>>>>> MUST include all fields required by the subject_type, but MAY contai=
n other
>>>>>> fields, either defined as optional fields within this Subject Identi=
fiers
>>>>>> specification or elsewhere. A receiver MUST ignore fields in a Subje=
ct
>>>>>> Identifier that it does not understand."
>>>>>>
>>>>>> Atul
>>>>>>
>>>>>>
>>>>>> On Wed, Sep 30, 2020 at 1:51 PM Justin Richer <mailto:jricher@mit.ed=
u>
>>>>>> wrote:
>>>>>> Atul,
>>>>>>
>>>>>> I raised this in my review as well. I think the goal of the
>>>>>> restriction was to make the subject identifier objects compact and e=
asily
>>>>>> processed without getting a bunch of arbitrary stuff strung onto the=
m, but
>>>>>> I think the MUST NOT might go too far toward that.
>>>>>>
>>>>>>
>>>>>> I would like to see the requirement relaxed but also have guidance a=
s
>>>>>> to how and when to add additional members to the object. Maybe the
>>>>>> subject_type field determines the REQUIRED fields and their semantic=
s, but
>>>>>> extensions MAY add new fields? And that a receiver MUST ignore field=
s they
>>>>>> don=E2=80=99t understand?
>>>>>>
>>>>>>
>>>>>>
>>>>>>  =E2=80=94 Justin
>>>>>>
>>>>>>
>>>>>> On Sep 29, 2020, at 8:28 PM, Atul Tulshibagwale <mailto:atultulshi=
=3D
>>>>>> 40google.com@dmarc.ietf.org> wrote:
>>>>>>
>>>>>> Hi Annabelle,
>>>>>> After reviewing the
>>>>>> https://github.com/richanna/secevent/blob/master/draft-ietf-secevent=
-subject-identifiers.txt
>>>>>> (document dated Sep 04), there's one issue that I feel needs to be
>>>>>> addressed:
>>>>>>
>>>>>> The sentence on line 246 ("A Subject Identifier MUST NOT contain any
>>>>>> members...") has the consequence that if we need to add claims in a
>>>>>> specific subject identifier type (e.g. email), then we will need to =
define
>>>>>> new subject identifier types.
>>>>>>
>>>>>> As discussed earlier, I am interested in adding a "Subject Principal
>>>>>> Administrative Grouping" or SPAG as a property of any subject identi=
fier.
>>>>>> This is important because the same principal may appear in different
>>>>>> administrative groupings, and without the disambiguation, it will be
>>>>>> impossible to figure out which SPAG the event that includes a subjec=
t
>>>>>> identifier applies to.
>>>>>>
>>>>>> For example, if the user "mailto:a@b.com" is present in two tenants
>>>>>> of a service that acts as a SSE Receiver. Say the tenant names in wh=
ich
>>>>>> this user occurs is "http://B.com" and "http://C.com". This can
>>>>>> happen if "mailto:a@b.com" is an employee of the tenant http://B.com=
,
>>>>>> but is on a contract for a project that is run by the tenant "
>>>>>> http://C.com".
>>>>>>
>>>>>> If the event received only has the subject:
>>>>>> "subject" : {
>>>>>>   "subject_type" : "email",
>>>>>>   "email" : "mailto:a@b.com"
>>>>>> }
>>>>>>
>>>>>> Then it will be impossible for the receiver to determine whether the
>>>>>> event applies to the tenant http://B.com or http://C.com. If on the
>>>>>> other hand, an optional claim "spag_id" is added, then the subject l=
ooks
>>>>>> like:
>>>>>>
>>>>>> "subject" : {
>>>>>>   "subject_type" : "email",
>>>>>>   "email" : "mailto:a@b.com",
>>>>>>   "spag_id" : "http://B.com"
>>>>>> }
>>>>>>
>>>>>> This disambiguates the particular grouping that the event applies to=
.
>>>>>>
>>>>>> So, I feel there are at least two ways of addressing this concern:
>>>>>> 1. Include SPAGs as a concept in the Subject Identifiers spec and
>>>>>> allow a "spag_id" claim in any subject identifier
>>>>>> 2. Drop the requirement on line 246, and allow subject identifiers t=
o
>>>>>> have additional claims, which may be defined elsewhere.
>>>>>> Thanks,
>>>>>> Atul
>>>>>>
>>>>>> _______________________________________________
>>>>>> Id-event mailing list
>>>>>> mailto:Id-event@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/id-event
>>>>>>
>>>>>> _______________________________________________ Id-event mailing lis=
t
>>>>>> Id-event@ietf.org https://www.ietf.org/mailman/listinfo/id-event
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
>>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>

--000000000000df0dfc05b584abb6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Atul, would you mind starting a new thread that outline=
s the options=C2=A0for the SPAG functionality, and elaborates on other addi=
tions that the OpenID Shared Signals and Events WG is interested in? We can=
 then dig into the pros and cons and get closure.<div><br></div><div>/Dick<=
/div></div><div hspace=3D"streak-pt-mark" style=3D"max-height:1px"><img alt=
=3D"" style=3D"width:0px;max-height:0px;overflow:hidden" src=3D"https://mai=
lfoogae.appspot.com/t?sender=3DaZGljay5oYXJkdEBnbWFpbC5jb20%3D&amp;type=3Dz=
erocontent&amp;guid=3Dffb5aa2b-8de1-46d3-a584-1957690c2b02"><font color=3D"=
#ffffff" size=3D"1">=E1=90=A7</font></div><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Wed, Dec 2, 2020 at 4:14 PM Atul Tul=
shibagwale &lt;<a href=3D"mailto:atultulshi@google.com">atultulshi@google.c=
om</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><div dir=3D"ltr">Hi Dick,<div><br><div>Just a quick clarification: My req=
uest above is to allow attributes that are not defined in specific subject_=
type descriptions in the SecEvents Subject Identifiers specification to be =
allowed to be added by other specifications that use it. The SPAG attribute=
 is only an example of such an addition that we are interested in for the O=
penID Shared Signals and Events WG.</div><div><br></div><div>Atul</div></di=
v></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr=
">On Wed, Dec 2, 2020 at 11:58 AM Dick Hardt &lt;<a href=3D"mailto:dick.har=
dt@gmail.com" target=3D"_blank">dick.hardt@gmail.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Annabe=
lle / Atul<div><br></div><div>Has the SPAG issue been=C2=A0resolved?=C2=A0 =
Would be great to get resolution and consensus so we can propose a last cal=
l again for this draft.</div><div><br></div><div>/Dick</div></div><div hspa=
ce=3D"streak-pt-mark" style=3D"max-height:1px"><img alt=3D"" style=3D"width=
: 0px; max-height: 0px; overflow: hidden;" src=3D"https://mailfoogae.appspo=
t.com/t?sender=3DaZGljay5oYXJkdEBnbWFpbC5jb20%3D&amp;type=3Dzerocontent&amp=
;guid=3Dc798286b-c826-4082-ab1b-ace668e914a1"><font color=3D"#ffffff" size=
=3D"1">=E1=90=A7</font></div><br><div class=3D"gmail_quote"><div dir=3D"ltr=
" class=3D"gmail_attr">On Wed, Nov 25, 2020 at 9:05 AM Atul Tulshibagwale &=
lt;atultulshi=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_b=
lank">40google.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr">Pinging this topic as dis=
cussed in the CAEP call yesterday.</div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 13, 2020 at 11:44 AM Atul Tul=
shibagwale &lt;<a href=3D"mailto:atultulshi@google.com" target=3D"_blank">a=
tultulshi@google.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr">Annabelle,<div><br><div>Could you plea=
se provide an update on whether this change (any of the two proposed option=
s) is possible in this Subject Identifiers specification? The work in the O=
penID SSE WG cannot proceed without this clarification.</div><div><br></div=
><div>Thanks,</div><div>Atul</div></div></div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 2, 2020 at 4:13 PM Atul=
 Tulshibagwale &lt;<a href=3D"mailto:atultulshi@google.com" target=3D"_blan=
k">atultulshi@google.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr">Hi=C2=A0Yaron,<div><br></div><div>=
I agree that SPAGs would typically need to be understood by the transmitter=
 and receiver. However this claim need not be present in every subject iden=
tifier, since it may not apply in many=C2=A0cases. Ignoring a SPAG value ma=
y still be OK if, say, the receiver is a single tenanted receiver and the S=
PAG in the subject identifier is a tenant identifier. Also,=C2=A0note that =
SPAGs do not necessarily only identify tenants; they may identify other sub=
ject principal groupings such as OUs, groups, etc.</div><div><br></div><div=
>In general, specifications that use the Subject Identifiers specification =
could add claims that may have additional semantics relating to the interpr=
etation of those claims. The Subject Identifiers specification could leave =
the interpretation of the additional claims open.</div><div><br></div><div>=
I believe SPAGs is going to be a common enough use case, so it should be in=
cluded in the Subject Identifiers specification as such. But I&#39;m OK wit=
h defining the SPAG claim in the SSE specification, if we have a way for th=
e Subject Identifiers specification to allow the addition of such a claim t=
o any subject identifier.</div><div><br></div><div>Thanks,</div><div>Atul</=
div><div><br></div><div>PS: There has been some discussion in the OpenID SS=
E WG about multiple event streams versus using SPAGs to identify different =
subject groupings within the same stream. A good venue to discuss this is t=
he <a href=3D"mailto:openid-specs-risc@openid.net" target=3D"_blank">openid=
-specs-risc@openid.net</a> mailing list, and now is a good time to bring th=
is up. The present work is captured in the <a href=3D"https://bitbucket.org=
/openid/risc/src/caep-draft-01/openid-sse-profile-2_0.txt" target=3D"_blank=
">SSE profile</a> draft spec (the one you referred to in your email was the=
 RISC profile, which could be replaced with this SSE profile spec when it&#=
39;s ready). </div><div><br></div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 2, 2020 at 8:26 AM Yaron Shef=
fer &lt;<a href=3D"mailto:yaronf.ietf@gmail.com" target=3D"_blank">yaronf.i=
etf@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">Hi Justin, Atul,<br>
<br>
I think this may be a reasonable way to extend the solution.<br>
<br>
But I have a problem with Atul=E2=80=99s example below: the SPAG attribute =
that he=E2=80=99s proposing defines a scope (a.k.a. namespace) for the subj=
ect ID. I don=E2=80=99t think the receiver can act correctly on the event *=
unless* it understands the tenant ID. So this is not a benign extension tha=
t can be ignored by a receiver with no consequence.<br>
<br>
The SecEvent mechanism to distinguish multiple tenants is not to embed the =
tenant=E2=80=99s identity in the event, rather it is to use separate event =
streams. In fact, this is enabled by the OpenID SSE document [1] which defi=
nes a profile of this solution: =E2=80=9CUsing path components enables supp=
orting multiple issuers per host. This is required in some multi-tenant hos=
ting configurations.=E2=80=9D<br>
<br>
Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Yaron<br>
<br>
[1] <a href=3D"https://openid.net/specs/openid-risc-profile-1_0-ID1.html#rf=
c.section.3.2.1" rel=3D"noreferrer" target=3D"_blank">https://openid.net/sp=
ecs/openid-risc-profile-1_0-ID1.html#rfc.section.3.2.1</a><br>
<br>
From: Id-event &lt;<a href=3D"mailto:id-event-bounces@ietf.org" target=3D"_=
blank">id-event-bounces@ietf.org</a>&gt; on behalf of Atul Tulshibagwale &l=
t;atultulshi=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_bl=
ank">40google.com@dmarc.ietf.org</a>&gt;<br>
Date: Thursday, October 1, 2020 at 19:02<br>
To: Justin Richer &lt;<a href=3D"mailto:jricher@mit.edu" target=3D"_blank">=
jricher@mit.edu</a>&gt;<br>
Cc: SecEvent &lt;<a href=3D"mailto:id-event@ietf.org" target=3D"_blank">id-=
event@ietf.org</a>&gt;<br>
Subject: Re: [Id-event] Draft-06 issue re: subject principal grouping<br>
<br>
Hi Justin,<br>
Agree with the theme of the language proposed in your email. I&#39;d like t=
o propose something similar, like:<br>
<br>
&quot;Each subject_type may define required fields. Subject identifiers MUS=
T include all fields required by the subject_type, but MAY contain other fi=
elds,=C2=A0either defined as optional fields within this Subject Identifier=
s specification or elsewhere. A receiver MUST ignore fields in a Subject Id=
entifier that it does not understand.&quot;<br>
<br>
Atul<br>
<br>
<br>
On Wed, Sep 30, 2020 at 1:51 PM Justin Richer &lt;mailto:<a href=3D"mailto:=
jricher@mit.edu" target=3D"_blank">jricher@mit.edu</a>&gt; wrote:<br>
Atul,<br>
<br>
I raised this in my review as well. I think the goal of the restriction was=
 to make the subject identifier objects compact and easily processed withou=
t getting a bunch of arbitrary stuff strung onto them, but I think the MUST=
 NOT might go too far toward that.<br>
<br>
<br>
I would like to see the requirement relaxed but also have guidance as to ho=
w and when to add additional members to the object. Maybe the subject_type =
field determines the REQUIRED fields and their semantics, but extensions MA=
Y add new fields? And that a receiver MUST ignore fields they don=E2=80=99t=
 understand?=C2=A0<br>
<br>
<br>
<br>
=C2=A0=E2=80=94 Justin<br>
<br>
<br>
On Sep 29, 2020, at 8:28 PM, Atul Tulshibagwale &lt;mailto:<a href=3D"mailt=
o:atultulshi" target=3D"_blank">atultulshi</a>=3D<a href=3D"mailto:40google=
.com@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt; =
wrote:<br>
<br>
Hi Annabelle,<br>
After reviewing the <a href=3D"https://github.com/richanna/secevent/blob/ma=
ster/draft-ietf-secevent-subject-identifiers.txt" rel=3D"noreferrer" target=
=3D"_blank">https://github.com/richanna/secevent/blob/master/draft-ietf-sec=
event-subject-identifiers.txt</a> (document dated Sep 04), there&#39;s one =
issue that I feel needs=C2=A0to be addressed:<br>
<br>
The sentence=C2=A0on line=C2=A0246 (&quot;A Subject Identifier MUST NOT con=
tain any members...&quot;) has the consequence that if we need to add claim=
s in a specific subject identifier type (e.g. email), then we will need to =
define new subject identifier types.<br>
<br>
As discussed earlier, I am interested in adding a &quot;Subject Principal A=
dministrative Grouping&quot; or SPAG as a property of any subject identifie=
r. This is important because the same principal may appear in different adm=
inistrative groupings, and without the disambiguation, it will be impossibl=
e to figure out which SPAG the event that includes a subject identifier app=
lies to.<br>
<br>
For example, if the user &quot;mailto:<a href=3D"mailto:a@b.com" target=3D"=
_blank">a@b.com</a>&quot; is present in two tenants of a service that acts =
as a SSE Receiver. Say the tenant names in which this user occurs is &quot;=
<a href=3D"http://B.com" rel=3D"noreferrer" target=3D"_blank">http://B.com<=
/a>&quot; and &quot;<a href=3D"http://C.com" rel=3D"noreferrer" target=3D"_=
blank">http://C.com</a>&quot;. This can happen if &quot;mailto:<a href=3D"m=
ailto:a@b.com" target=3D"_blank">a@b.com</a>&quot; is an employee of the te=
nant <a href=3D"http://B.com" rel=3D"noreferrer" target=3D"_blank">http://B=
.com</a>, but is on a contract for a project that is run by the tenant &quo=
t;<a href=3D"http://C.com" rel=3D"noreferrer" target=3D"_blank">http://C.co=
m</a>&quot;.<br>
<br>
If the event received only has the subject:<br>
&quot;subject&quot; : {<br>
=C2=A0 &quot;subject_type&quot; : &quot;email&quot;,<br>
=C2=A0 &quot;email&quot; : &quot;mailto:<a href=3D"mailto:a@b.com" target=
=3D"_blank">a@b.com</a>&quot;<br>
}<br>
<br>
Then it will be impossible for the receiver to determine whether the event =
applies to the tenant <a href=3D"http://B.com" rel=3D"noreferrer" target=3D=
"_blank">http://B.com</a> or <a href=3D"http://C.com" rel=3D"noreferrer" ta=
rget=3D"_blank">http://C.com</a>. If on the other hand, an optional claim &=
quot;spag_id&quot; is added, then the subject looks like:<br>
<br>
&quot;subject&quot; : {<br>
=C2=A0 &quot;subject_type&quot; : &quot;email&quot;,<br>
=C2=A0 &quot;email&quot; : &quot;mailto:<a href=3D"mailto:a@b.com" target=
=3D"_blank">a@b.com</a>&quot;,<br>
=C2=A0 &quot;spag_id&quot; : &quot;<a href=3D"http://B.com" rel=3D"noreferr=
er" target=3D"_blank">http://B.com</a>&quot;<br>
}<br>
<br>
This disambiguates the particular grouping that the event applies to.<br>
<br>
So, I feel there are at least two ways of addressing this concern:<br>
1. Include SPAGs as a concept in the Subject Identifiers spec and allow a &=
quot;spag_id&quot; claim in any subject identifier<br>
2. Drop the requirement on line 246, and allow subject identifiers to have =
additional claims, which may be defined elsewhere.<br>
Thanks,<br>
Atul<br>
<br>
_______________________________________________<br>
Id-event mailing list<br>
mailto:<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf=
.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
<br>
_______________________________________________ Id-event mailing list <a hr=
ef=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a> <a =
href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a> <br>
<br>
<br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>
</blockquote></div>

--000000000000df0dfc05b584abb6--


From nobody Thu Dec  3 15:03:56 2020
Return-Path: <atultulshi@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF283A0E8A for <id-event@ietfa.amsl.com>; Thu,  3 Dec 2020 15:03:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6wGJ2P40LO64 for <id-event@ietfa.amsl.com>; Thu,  3 Dec 2020 15:03:53 -0800 (PST)
Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (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 AA4F23A0E89 for <id-event@ietf.org>; Thu,  3 Dec 2020 15:03:53 -0800 (PST)
Received: by mail-yb1-xb36.google.com with SMTP id x17so3609177ybr.8 for <id-event@ietf.org>; Thu, 03 Dec 2020 15:03:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=L5UM2ushmuvClJuSyHHq1Wrs6VJWSZNvU4b0l6d6BFU=; b=dkd8AcAJS+OGWgu/kNLK5D9e7pk7OzVlbM6pY7PK3zO+6bWGPSpfqk+7WndD7J4XwJ 2T9zqQl00M5zObq3IJ1GtVOW/NKjvP8HLXuQZKLlXKVNgNXQqLdf5wR+mM+UyWmbPP0b rqWmVB0ctoLpJzFGCGk22b9Z4sTGyiTuKOZb8OruCLy+BKNw90R9HMg/Hj+Z522tq+xS xQWgbJZT5vp1KW6nZ3xdjuZkQpejAUGuFmQh4a8sfg6KzbLVd82fHJkda7GYr0ytbVTm V57+JDboP/7XTybdWmKxFS+94HXlHXJJFXDO3I4xQR3JYpifDqUHKuawmztOiOABb7LL Cvdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=L5UM2ushmuvClJuSyHHq1Wrs6VJWSZNvU4b0l6d6BFU=; b=gpFOrQ8eHwZb59cVHy8k9UK7eL4INdMz9YVxgsGp4bPmCs0aWo8z/jS8Z62JHtsj5o TpLWZ2XBDiM9zOvgGYvamm++7RyRpF622xRawirKCKJtO/tm4z0Q6EF11ETG5U7skET5 2y4tyYxod/hDVB/YuU3jtj1HLQDuCN+wh2Z38tGAr3FAbrAWu7OdhsgRbmVfRLrOYR5V g8ZtA7bhNthVvCt/Z1dNNdxQ2CxaYuiqpSyx+WACXIWzA6zBIcdl5GyBFDU69DBE7hRx TELx4SIHkPviqJ24+G/sUytwegjJY5hVpM3U1VswGDnuAxSvDHfO16pgEHpoLjigAZnx akog==
X-Gm-Message-State: AOAM532RQVJFTvPQ5jmK8/E2a9QBpgykbht8ncu0Gh15Aw40EtFxTelJ 0NR8CIPSHAY+r+gs2tWgDzrNwvTkE6SD5nrzErg809CrmF8YBA==
X-Google-Smtp-Source: ABdhPJzgso/1CkhCFi7K/gjmAxiKKtdqh70PfPLDm/v2cZ7nDuu186wUpqWk8P0up2kEq135ZP5cMGj3bRiEHAoNbBw=
X-Received: by 2002:a25:32c9:: with SMTP id y192mr2037319yby.211.1607036632260;  Thu, 03 Dec 2020 15:03:52 -0800 (PST)
MIME-Version: 1.0
From: Atul Tulshibagwale <atultulshi@google.com>
Date: Thu, 3 Dec 2020 15:03:41 -0800
Message-ID: <CAMCkG5vAnEyUeRjjRuyuk_mRQEXX2ZdZffGamzGg2+AzjMp9kQ@mail.gmail.com>
To: SecEvent <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009be2e305b5975f20"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/eYII2_xdATtYy4rM4WQC7w_QPzw>
Subject: [Id-event] Options regarding SPAGs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2020 23:03:56 -0000

--0000000000009be2e305b5975f20
Content-Type: text/plain; charset="UTF-8"

Hi all,
Based on Dick's request, I'd like to summarize the situation with SPAGs
here.

*Background*:
The present Subject Identifiers draft
<https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt>
forbids a subject identifier of a specific subject_type from having any
claims that are not described in the subject_type. This prevents
higher-level specs from proposing any additional claims to be included in
subject identifiers of subject types that are defined in the Subject
Identifier spec.

*SPAGs*:
Subject Principal Administrative Groupings or SPAGs are an addition to the
OpenID "Shared Signals and Events Profile of SETs"
<https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profile-2_0.txt>,
which is a revision of the "RISC Profile of SETs
<https://bitbucket.org/openid/risc/src/master/openid-risc-profile-1_0.txt>".
The present draft of the SecEvents Subject Identifiers spec is derived from
a section in this RISC Profile. The SSE Profile now refers to the SecEvents
Subject Identifiers draft.

SPAGs are required to address the following needs:

   1. Disambiguate a subject identifier if it belongs to more than one
   sub-organizations. For example, if the subject claim in an event is of the
   subject type "email", then a SPAG may be used to specify the
   sub-organization the specified email should be scoped down to. A dynamic
   organization may have the same email in multiple sub-organizations, and the
   event may apply to only one such sub organization.
   2. Provide a lighter weight mechanism to start and stop event streams
   for sub-organizations. These could be OUs or dynamic groups within an
   organization, or separate tenants in a multi-tenanted transmitter or
   receiver.

*Requirements from Subject Identifiers*:

   1. A SPAG may be specified as an additional attribute of a subject
   identifier with any subject type, in order to disambiguate and scope the
   event with that subject identifier.
   2. A SPAG may be a new subject type of its own when it is used in an
   event that specifies the starting or stopping of a stream.

*Options*:
The following options are possible to address this requirement.

   1. *Minimal Change to the present Subject Identifiers draft*: Remove the
   words "or not described" on line 247
   <https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt#L247>.
   This way a higher-level spec that needs to add additional attributes to all
   subject identifiers used in that spec can add them and specify the
   additional attributes' optional or required nature. In this option, SPAGs
   will be defined in the SSE profile spec.
   2. *Include SPAGs in the Subject Identifiers spec*: Include language for
   SPAGs proposed earlier in this list, so that:
      1. Subject Principals and SPAGs are defined in the Subject
      Identifiers spec
      2. An additional attribute named "spag_id" is added as an optional
      attribute of any subject_type.
      3. An additional subject_type "spag" is defined (this is used
      primarily for "control plane" events.)
   3. *Do both 1. and 2*: With this, we will address the issue that
   higher-level specs cannot insert additional attributes in predefined
   subject types, and define SPAGs within the Subject Identifiers spec.

Thanks,
Atul

--0000000000009be2e305b5975f20
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div>Based on Dick&#39;s request, I&#39;d like to s=
ummarize the situation with SPAGs here.</div><div><br></div><div><b>Backgro=
und</b>:</div><div>The present <a href=3D"https://github.com/richanna/secev=
ent/blob/1fd045d251ff3c6be9a500c6a78d895be3c6b2bf/draft-ietf-secevent-subje=
ct-identifiers.txt">Subject Identifiers draft</a> forbids a subject identif=
ier of a specific subject_type from having any claims that are not describe=
d in the subject_type. This prevents higher-level specs from proposing any =
additional claims to be included in subject identifiers of subject=C2=A0typ=
es that are defined in the Subject Identifier spec.</div><div>=C2=A0</div><=
div><b>SPAGs</b>:</div><div>Subject Principal Administrative Groupings or S=
PAGs are an addition to the OpenID &quot;<a href=3D"https://bitbucket.org/o=
penid/risc/src/caep-draft-01/openid-sse-profile-2_0.txt">Shared Signals and=
 Events Profile of SETs&quot;</a>, which is a revision of the &quot;<a href=
=3D"https://bitbucket.org/openid/risc/src/master/openid-risc-profile-1_0.tx=
t">RISC Profile of SETs</a>&quot;. The present draft of the SecEvents Subje=
ct Identifiers spec is derived from a section in this RISC Profile. The SSE=
 Profile now refers to the SecEvents Subject Identifiers draft.</div><div><=
br></div><div></div><div>SPAGs are required to address the following needs:=
</div><div><ol><li>Disambiguate a subject identifier if it belongs to more =
than one sub-organizations. For example, if the subject claim in an event i=
s of the subject type &quot;email&quot;, then a SPAG may be used to specify=
 the sub-organization the specified email should be scoped down to. A dynam=
ic organization may have the same email in multiple sub-organizations, and =
the event may apply to only one such sub organization.</li><li>Provide a li=
ghter weight mechanism to start and stop event streams for sub-organization=
s. These could be OUs or dynamic groups within an organization, or separate=
 tenants in a multi-tenanted transmitter or receiver.</li></ol><div><b>Requ=
irements from Subject Identifiers</b>:</div></div><div><ol><li>A SPAG may b=
e specified as an additional attribute of a subject identifier with any sub=
ject type, in order to disambiguate and scope the event with that subject i=
dentifier.</li><li>A SPAG may be a new subject type of its own when it is u=
sed in an event that specifies the starting or stopping of a stream.</li></=
ol><div><b>Options</b>:</div></div><div>The following options are possible =
to address this requirement.</div><div><ol><li><b>Minimal Change to the pre=
sent Subject Identifiers draft</b>: Remove the words &quot;or not described=
&quot; on <a href=3D"https://github.com/richanna/secevent/blob/1fd045d251ff=
3c6be9a500c6a78d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt#L2=
47">line 247</a>. This way a higher-level spec that needs to add additional=
 attributes to all subject identifiers used in that spec can add them and s=
pecify the additional attributes&#39; optional or required nature. In this =
option, SPAGs will be defined in the SSE profile spec.</li><li><b>Include S=
PAGs in the Subject Identifiers spec</b>: Include language for SPAGs propos=
ed earlier in this list, so that:</li><ol><li>Subject Principals and SPAGs =
are defined in the Subject Identifiers spec</li><li>An additional attribute=
 named &quot;spag_id&quot; is added as an optional attribute of any subject=
_type.</li><li>An additional subject_type &quot;spag&quot; is defined (this=
 is used primarily for &quot;control plane&quot; events.)</li></ol><li><b>D=
o both 1. and 2</b>: With this, we will address the issue that higher-level=
 specs cannot insert additional attributes in predefined subject types, and=
 define SPAGs within the Subject Identifiers spec.</li></ol><div>Thanks,</d=
iv></div><div>Atul</div><div><br></div><div></div></div>

--0000000000009be2e305b5975f20--


From nobody Thu Dec  3 17:42:55 2020
Return-Path: <dick.hardt@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 078043A1201 for <id-event@ietfa.amsl.com>; Thu,  3 Dec 2020 17:42:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 g-W22N6TrdiF for <id-event@ietfa.amsl.com>; Thu,  3 Dec 2020 17:42:50 -0800 (PST)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::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 D7B713A12B9 for <id-event@ietf.org>; Thu,  3 Dec 2020 17:42:32 -0800 (PST)
Received: by mail-lj1-x22c.google.com with SMTP id f24so4738519ljk.13 for <id-event@ietf.org>; Thu, 03 Dec 2020 17:42:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0EvihjWDRi3QPRGathiZRaMjv/BllKggGDfWQ9sfLJ0=; b=B6ondliQuQdw5okBny1+UYn5I4cmV2RRJbTtHG3Oble0KUqzhwu5dXGvmlAm8fpNs7 muFRjzpuJeG2jbyT9tKgWw/bumJBquPlwt+GE6oR/xZo7ZI1IPveMuLMwp+jSLQnCz+2 BDiFuPGBVE5IdeiYhEiIkU9lTMZE4upfFX8BSyYIuFo3lStcZR4sfJpuBMZBPFCoxoMu kTfPLtpLtbI5sHIARkrVnP2hx7MvnCDNyLQcwKKgxHqparuaxZOyb8EgbcLpbEnThrhA BpqqAX60HRXRHAwnWjbWfEMT16bj9+EWsWXBmr2ND6MwNgyQiHio57Los2ZEauR4pxuB eMLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0EvihjWDRi3QPRGathiZRaMjv/BllKggGDfWQ9sfLJ0=; b=TSPlBSyr2R19k0y6QysE+3I8w+SCTj6CjTwSbEVyhaxYMy0V3iFqrND1uNO8yc4gSW Fd+0ecgMa2aXp5JYqVCTiC5V+hv8JR0RUClXDESZi3D9goRPMnatviNNKUe+pXz3sqfY 2WQljWNf9te4/VRwXlVXa6YVU9VcOe6xwG3apKqgOoQA0oQgiEXL1775W+Fyfi8s5N5L 6i3IBvzNGSMT2PJTzZ4Purp704DZwcwiAFqEGsji7W/NhoLnZOQLB3aPWlg22/N0yPg5 a8Z7BPbqfjrHC/c0o6WN3y+08G9WunXUWa2djhQG/FGsL4L/9/W75foFU5auHOvyTykh PnVg==
X-Gm-Message-State: AOAM531ApbLMXrOAKVQqhPdOItuSuOaoUE8EbFNZ1LeOxwNA2gpBsx9L RbM4UJ1Z+0PHvO83OGiEwkw3NJoUrMs682e9X9eiQQWUHc5ZfA==
X-Google-Smtp-Source: ABdhPJzBK8uAmOlWheDKFzxpiJYf7z3bltZSjAKLMkC6Tf5oNB2y201MkEc4OnUANs0xRzjQvdG+p6ZpcqT5dBjMhoY=
X-Received: by 2002:a2e:b4d1:: with SMTP id r17mr2351712ljm.246.1607046150381;  Thu, 03 Dec 2020 17:42:30 -0800 (PST)
MIME-Version: 1.0
References: <CAMCkG5vAnEyUeRjjRuyuk_mRQEXX2ZdZffGamzGg2+AzjMp9kQ@mail.gmail.com>
In-Reply-To: <CAMCkG5vAnEyUeRjjRuyuk_mRQEXX2ZdZffGamzGg2+AzjMp9kQ@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Thu, 3 Dec 2020 17:41:54 -0800
Message-ID: <CAD9ie-tk53ztCTA8U2bNmaB9dd9x0bK6JNyN=kOU+=RJ8zEUCw@mail.gmail.com>
To: Atul Tulshibagwale <atultulshi=40google.com@dmarc.ietf.org>
Cc: SecEvent <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ee64d005b59996bf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/shtAEpu0enKojOcnszH3zqo4vQw>
Subject: Re: [Id-event] Options regarding SPAGs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Dec 2020 01:42:53 -0000

--000000000000ee64d005b59996bf
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I think there is also a fourth option:

4. a SPAG identifier can be placed in a separate top level object or top
level property

Atul: in the other thread, you mentioned that there were other additions
that the OpenID Shared Signals and Events WG is interested in. Would you
enumerate them as well so that we can address all potential issues?


=E1=90=A7

On Thu, Dec 3, 2020 at 3:04 PM Atul Tulshibagwale <atultulshi=3D
40google.com@dmarc.ietf.org> wrote:

> Hi all,
> Based on Dick's request, I'd like to summarize the situation with SPAGs
> here.
>
> *Background*:
> The present Subject Identifiers draft
> <https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d89=
5be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt>
> forbids a subject identifier of a specific subject_type from having any
> claims that are not described in the subject_type. This prevents
> higher-level specs from proposing any additional claims to be included in
> subject identifiers of subject types that are defined in the Subject
> Identifier spec.
>
> *SPAGs*:
> Subject Principal Administrative Groupings or SPAGs are an addition to th=
e
> OpenID "Shared Signals and Events Profile of SETs"
> <https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profile-2=
_0.txt>,
> which is a revision of the "RISC Profile of SETs
> <https://bitbucket.org/openid/risc/src/master/openid-risc-profile-1_0.txt=
>".
> The present draft of the SecEvents Subject Identifiers spec is derived fr=
om
> a section in this RISC Profile. The SSE Profile now refers to the SecEven=
ts
> Subject Identifiers draft.
>
> SPAGs are required to address the following needs:
>
>    1. Disambiguate a subject identifier if it belongs to more than one
>    sub-organizations. For example, if the subject claim in an event is of=
 the
>    subject type "email", then a SPAG may be used to specify the
>    sub-organization the specified email should be scoped down to. A dynam=
ic
>    organization may have the same email in multiple sub-organizations, an=
d the
>    event may apply to only one such sub organization.
>    2. Provide a lighter weight mechanism to start and stop event streams
>    for sub-organizations. These could be OUs or dynamic groups within an
>    organization, or separate tenants in a multi-tenanted transmitter or
>    receiver.
>
> *Requirements from Subject Identifiers*:
>
>    1. A SPAG may be specified as an additional attribute of a subject
>    identifier with any subject type, in order to disambiguate and scope t=
he
>    event with that subject identifier.
>    2. A SPAG may be a new subject type of its own when it is used in an
>    event that specifies the starting or stopping of a stream.
>
> *Options*:
> The following options are possible to address this requirement.
>
>    1. *Minimal Change to the present Subject Identifiers draft*: Remove
>    the words "or not described" on line 247
>    <https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78=
d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt#L247>.
>    This way a higher-level spec that needs to add additional attributes t=
o all
>    subject identifiers used in that spec can add them and specify the
>    additional attributes' optional or required nature. In this option, SP=
AGs
>    will be defined in the SSE profile spec.
>    2. *Include SPAGs in the Subject Identifiers spec*: Include language
>    for SPAGs proposed earlier in this list, so that:
>       1. Subject Principals and SPAGs are defined in the Subject
>       Identifiers spec
>       2. An additional attribute named "spag_id" is added as an optional
>       attribute of any subject_type.
>       3. An additional subject_type "spag" is defined (this is used
>       primarily for "control plane" events.)
>    3. *Do both 1. and 2*: With this, we will address the issue that
>    higher-level specs cannot insert additional attributes in predefined
>    subject types, and define SPAGs within the Subject Identifiers spec.
>
> Thanks,
> Atul
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>

--000000000000ee64d005b59996bf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think there is also a fourth option:<div><br></div><div>=
4. a SPAG identifier can be placed in a separate top level object or top le=
vel property</div><div><br></div><div>Atul: in the other thread, you mentio=
ned that there were other additions that the OpenID Shared Signals and Even=
ts WG is interested in. Would you enumerate them as well so that we can add=
ress all potential issues?</div><div><br></div><div><br></div></div><div hs=
pace=3D"streak-pt-mark" style=3D"max-height:1px"><img alt=3D"" style=3D"wid=
th:0px;max-height:0px;overflow:hidden" src=3D"https://mailfoogae.appspot.co=
m/t?sender=3DaZGljay5oYXJkdEBnbWFpbC5jb20%3D&amp;type=3Dzerocontent&amp;gui=
d=3D831b7283-e9f5-4dbd-a507-5c398074b254"><font color=3D"#ffffff" size=3D"1=
">=E1=90=A7</font></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Thu, Dec 3, 2020 at 3:04 PM Atul Tulshibagwale &lt;atu=
ltulshi=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank">=
40google.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div dir=3D"ltr">Hi all,<div>Based on Dick&#39;s=
 request, I&#39;d like to summarize the situation with SPAGs here.</div><di=
v><br></div><div><b>Background</b>:</div><div>The present <a href=3D"https:=
//github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d895be3c6b2b=
f/draft-ietf-secevent-subject-identifiers.txt" target=3D"_blank">Subject Id=
entifiers draft</a> forbids a subject identifier of a specific subject_type=
 from having any claims that are not described in the subject_type. This pr=
events higher-level specs from proposing any additional claims to be includ=
ed in subject identifiers of subject=C2=A0types that are defined in the Sub=
ject Identifier spec.</div><div>=C2=A0</div><div><b>SPAGs</b>:</div><div>Su=
bject Principal Administrative Groupings or SPAGs are an addition to the Op=
enID &quot;<a href=3D"https://bitbucket.org/openid/risc/src/caep-draft-01/o=
penid-sse-profile-2_0.txt" target=3D"_blank">Shared Signals and Events Prof=
ile of SETs&quot;</a>, which is a revision of the &quot;<a href=3D"https://=
bitbucket.org/openid/risc/src/master/openid-risc-profile-1_0.txt" target=3D=
"_blank">RISC Profile of SETs</a>&quot;. The present draft of the SecEvents=
 Subject Identifiers spec is derived from a section in this RISC Profile. T=
he SSE Profile now refers to the SecEvents Subject Identifiers draft.</div>=
<div><br></div><div></div><div>SPAGs are required to address the following =
needs:</div><div><ol><li>Disambiguate a subject identifier if it belongs to=
 more than one sub-organizations. For example, if the subject claim in an e=
vent is of the subject type &quot;email&quot;, then a SPAG may be used to s=
pecify the sub-organization the specified email should be scoped down to. A=
 dynamic organization may have the same email in multiple sub-organizations=
, and the event may apply to only one such sub organization.</li><li>Provid=
e a lighter weight mechanism to start and stop event streams for sub-organi=
zations. These could be OUs or dynamic groups within an organization, or se=
parate tenants in a multi-tenanted transmitter or receiver.</li></ol><div><=
b>Requirements from Subject Identifiers</b>:</div></div><div><ol><li>A SPAG=
 may be specified as an additional attribute of a subject identifier with a=
ny subject type, in order to disambiguate and scope the event with that sub=
ject identifier.</li><li>A SPAG may be a new subject type of its own when i=
t is used in an event that specifies the starting or stopping of a stream.<=
/li></ol><div><b>Options</b>:</div></div><div>The following options are pos=
sible to address this requirement.</div><div><ol><li><b>Minimal Change to t=
he present Subject Identifiers draft</b>: Remove the words &quot;or not des=
cribed&quot; on <a href=3D"https://github.com/richanna/secevent/blob/1fd045=
d251ff3c6be9a500c6a78d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.=
txt#L247" target=3D"_blank">line 247</a>. This way a higher-level spec that=
 needs to add additional attributes to all subject identifiers used in that=
 spec can add them and specify the additional attributes&#39; optional or r=
equired nature. In this option, SPAGs will be defined in the SSE profile sp=
ec.</li><li><b>Include SPAGs in the Subject Identifiers spec</b>: Include l=
anguage for SPAGs proposed earlier in this list, so that:</li><ol><li>Subje=
ct Principals and SPAGs are defined in the Subject Identifiers spec</li><li=
>An additional attribute named &quot;spag_id&quot; is added as an optional =
attribute of any subject_type.</li><li>An additional subject_type &quot;spa=
g&quot; is defined (this is used primarily for &quot;control plane&quot; ev=
ents.)</li></ol><li><b>Do both 1. and 2</b>: With this, we will address the=
 issue that higher-level specs cannot insert additional attributes in prede=
fined subject types, and define SPAGs within the Subject Identifiers spec.<=
/li></ol><div>Thanks,</div></div><div>Atul</div><div><br></div><div></div><=
/div>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>

--000000000000ee64d005b59996bf--


From nobody Fri Dec  4 16:41:07 2020
Return-Path: <atultulshi@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 089993A10A7 for <id-event@ietfa.amsl.com>; Fri,  4 Dec 2020 16:41:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.598
X-Spam-Level: 
X-Spam-Status: No, score=-17.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49V355x7GUqA for <id-event@ietfa.amsl.com>; Fri,  4 Dec 2020 16:41:02 -0800 (PST)
Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (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 ABA773A10A3 for <id-event@ietf.org>; Fri,  4 Dec 2020 16:41:02 -0800 (PST)
Received: by mail-yb1-xb2e.google.com with SMTP id g15so7114859ybq.6 for <id-event@ietf.org>; Fri, 04 Dec 2020 16:41:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kiLxxPgDaHrSoBMvTKa/qo2hbFG1KCllfRJyT08OdW4=; b=RkQy1iGUwu535yFjSgipW+ZZbWUajd9PzM08Vhz0lM3YBNZAhx2VG9zTqzCCYuRcTr l3N+F8xKJrx6b+miTQRO3diAvqgjti6lqpkiSuxlBDkUaAiVBMdrwWd4jtbAb+hmLRdW WHB41NGJGv3VzBF+A4VApTZI9YoKzHjC3fhOAN11QNT9fb1nwjQb86ERqA1uf7NGuci3 49g7o+CmfiYKjrqB27A1Pb2mG8bqtYYy1SpBhdm0SBBqvkg8vU2JBvaL1Gmr9EQEgIdh 21VYdVqkhyIFAUA3YuBNXEkOIFjkKqI7cB/dZUoEczRpd+Ghm8gRpiYJI/J7AfBP5kDh XfRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kiLxxPgDaHrSoBMvTKa/qo2hbFG1KCllfRJyT08OdW4=; b=PKyVJpcLXNVeDgs7vadojZ0+MLoNVNv20NDKtiKeB7d3fD1zF4sRrUIKZw39pZAY5E oeTgNXyY6NXXBlh8eK0JpnABoTDNlCoTXpxaTh+3IayGr8NW/gC738/6NJgrBcx2rG2k TAmDDpc7OtX2OSVDiTPB/4bLtDxJXfh4sAZTa2XMb0+ZoLWD4BHeDzLTbj7N7jKi2tNa SYQBosPOmFqJBXiftxu4FzUH+s4FL9eAj93d0A0IpnwgCoXVlfaPSgCTrtOZh7ueUmZk UJg7ndeRGuBr4LzVFFzt5+4AfGJ3exA7kvsylp5sdqtQV94TYYf4wFI0qwc5OygSdK0L 5rcA==
X-Gm-Message-State: AOAM531m1ewvgSLw/ihFtUgInY79DN2kqqPgiE5DfYJ4CzuG+MR3QLAa 1nM5fkkQgSwH/y/zlYXkpnC4z+91AEZQXXr8EDsOBw==
X-Google-Smtp-Source: ABdhPJwXLkWEDb8rEHXVew/kQ+LavsqHinIMdtwQkY9RaOu86frbEVtoRL8iWH+CmBpcnhXVhm3V+zEouFz9Rror6Vk=
X-Received: by 2002:a25:3808:: with SMTP id f8mr9113910yba.377.1607128861480;  Fri, 04 Dec 2020 16:41:01 -0800 (PST)
MIME-Version: 1.0
References: <CAMCkG5vAnEyUeRjjRuyuk_mRQEXX2ZdZffGamzGg2+AzjMp9kQ@mail.gmail.com> <CAD9ie-tk53ztCTA8U2bNmaB9dd9x0bK6JNyN=kOU+=RJ8zEUCw@mail.gmail.com>
In-Reply-To: <CAD9ie-tk53ztCTA8U2bNmaB9dd9x0bK6JNyN=kOU+=RJ8zEUCw@mail.gmail.com>
From: Atul Tulshibagwale <atultulshi@google.com>
Date: Fri, 4 Dec 2020 16:40:50 -0800
Message-ID: <CAMCkG5v3FTnNz878Fg85hV1vYpVo1QO=AF49yvDOacw9bLw-vQ@mail.gmail.com>
To: Dick Hardt <dick.hardt@gmail.com>
Cc: SecEvent <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e6083405b5acd8fe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/GX4ZLn0a1M2EBbRKdNDCdBs7_No>
Subject: Re: [Id-event] Options regarding SPAGs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Dec 2020 00:41:06 -0000

--000000000000e6083405b5acd8fe
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Dick,
#4 may not always be an option if the event has more than one subject claim
(e.g. for an event like "device transfer").

Regarding other additions:
*Subject Categories*:
Earlier, I had proposed that a subject identifier of any subject_type have
an optional common claim named "subject_category", which could identify the
type of subject principal the subject identifier refers to. However, since
the future of this request in the Subject Identifiers spec wasn't clear, we
decided to add a new "subject_type" in the SSE spec, called
"user-device-session". The SSE spec draft defines the algorithm to figure
out the category of the subject principal based on the content of this
subject identifier.

As a result of this new subject type definition in the SSE spec draft,
"subject_category" is no longer a requirement for the SSE work. However,
since the SSE spec is still being drafted, if the Subject Identifiers spec
has the ability to add a subject category claim to any subject_type, then
we can possibly change the SSE spec to make use of it.

*SAML Subject Type*:
I had proposed that a SAML subject type be introduced in the Subject
Identifiers. This will help us send and receive events relating to a
specific SAML-based federated session. I thought this would be a common
subject type of interest to the Subject Identifiers spec. However, we have
now added it as a subject type in the SSE draft spec. If the Subject
Identifiers draft were to include this, it would be very easy for us to
remove this from the SSE draft spec.

BTW a good way to look at all my proposed changes to the Subject
Identifiers draft is by reviewing my pull request here:
https://github.com/richanna/secevent/pull/1

Thanks,
Atul


On Thu, Dec 3, 2020 at 5:43 PM Dick Hardt <dick.hardt@gmail.com> wrote:

> I think there is also a fourth option:
>
> 4. a SPAG identifier can be placed in a separate top level object or top
> level property
>
> Atul: in the other thread, you mentioned that there were other additions
> that the OpenID Shared Signals and Events WG is interested in. Would you
> enumerate them as well so that we can address all potential issues?
>
>
> =E1=90=A7
>
> On Thu, Dec 3, 2020 at 3:04 PM Atul Tulshibagwale <atultulshi=3D
> 40google.com@dmarc.ietf.org> wrote:
>
>> Hi all,
>> Based on Dick's request, I'd like to summarize the situation with SPAGs
>> here.
>>
>> *Background*:
>> The present Subject Identifiers draft
>> <https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d8=
95be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt>
>> forbids a subject identifier of a specific subject_type from having any
>> claims that are not described in the subject_type. This prevents
>> higher-level specs from proposing any additional claims to be included i=
n
>> subject identifiers of subject types that are defined in the Subject
>> Identifier spec.
>>
>> *SPAGs*:
>> Subject Principal Administrative Groupings or SPAGs are an addition to
>> the OpenID "Shared Signals and Events Profile of SETs"
>> <https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profile-=
2_0.txt>,
>> which is a revision of the "RISC Profile of SETs
>> <https://bitbucket.org/openid/risc/src/master/openid-risc-profile-1_0.tx=
t>".
>> The present draft of the SecEvents Subject Identifiers spec is derived f=
rom
>> a section in this RISC Profile. The SSE Profile now refers to the SecEve=
nts
>> Subject Identifiers draft.
>>
>> SPAGs are required to address the following needs:
>>
>>    1. Disambiguate a subject identifier if it belongs to more than one
>>    sub-organizations. For example, if the subject claim in an event is o=
f the
>>    subject type "email", then a SPAG may be used to specify the
>>    sub-organization the specified email should be scoped down to. A dyna=
mic
>>    organization may have the same email in multiple sub-organizations, a=
nd the
>>    event may apply to only one such sub organization.
>>    2. Provide a lighter weight mechanism to start and stop event streams
>>    for sub-organizations. These could be OUs or dynamic groups within an
>>    organization, or separate tenants in a multi-tenanted transmitter or
>>    receiver.
>>
>> *Requirements from Subject Identifiers*:
>>
>>    1. A SPAG may be specified as an additional attribute of a subject
>>    identifier with any subject type, in order to disambiguate and scope =
the
>>    event with that subject identifier.
>>    2. A SPAG may be a new subject type of its own when it is used in an
>>    event that specifies the starting or stopping of a stream.
>>
>> *Options*:
>> The following options are possible to address this requirement.
>>
>>    1. *Minimal Change to the present Subject Identifiers draft*: Remove
>>    the words "or not described" on line 247
>>    <https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a7=
8d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt#L247>.
>>    This way a higher-level spec that needs to add additional attributes =
to all
>>    subject identifiers used in that spec can add them and specify the
>>    additional attributes' optional or required nature. In this option, S=
PAGs
>>    will be defined in the SSE profile spec.
>>    2. *Include SPAGs in the Subject Identifiers spec*: Include language
>>    for SPAGs proposed earlier in this list, so that:
>>       1. Subject Principals and SPAGs are defined in the Subject
>>       Identifiers spec
>>       2. An additional attribute named "spag_id" is added as an optional
>>       attribute of any subject_type.
>>       3. An additional subject_type "spag" is defined (this is used
>>       primarily for "control plane" events.)
>>    3. *Do both 1. and 2*: With this, we will address the issue that
>>    higher-level specs cannot insert additional attributes in predefined
>>    subject types, and define SPAGs within the Subject Identifiers spec.
>>
>> Thanks,
>> Atul
>>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org
>> https://www.ietf.org/mailman/listinfo/id-event
>>
>

--000000000000e6083405b5acd8fe
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Dick,<div>#4 may not always be an option if the event h=
as more than one subject claim (e.g. for an event like &quot;device transfe=
r&quot;).=C2=A0</div><div><br></div><div>Regarding other additions:</div><d=
iv><b>Subject Categories</b>:</div><div>Earlier, I had proposed that a subj=
ect identifier of any subject_type have an optional common claim named &quo=
t;subject_category&quot;, which could identify the type of subject principa=
l the subject identifier refers to. However, since the future of this reque=
st in the Subject Identifiers spec wasn&#39;t clear, we decided to add a ne=
w &quot;subject_type&quot; in the SSE spec, called &quot;user-device-sessio=
n&quot;. The SSE spec draft defines the algorithm to figure out the categor=
y of the subject principal based on the content of this subject identifier.=
</div><div><br></div><div>As a result of this new subject type definition i=
n the SSE spec draft, &quot;subject_category&quot; is no longer a requireme=
nt for the SSE work. However, since the SSE spec is still being drafted, if=
 the Subject Identifiers spec has the ability to add a subject category cla=
im to any subject_type, then we can possibly change the SSE spec to make us=
e of it.</div><div><br></div><div><b>SAML Subject Type</b>:</div><div>I had=
 proposed that a SAML subject type be introduced in the Subject Identifiers=
. This will help us send and receive events relating to a specific SAML-bas=
ed federated session. I thought this would be a common subject type of inte=
rest to the Subject Identifiers spec. However, we have now added it as a su=
bject type in the SSE draft spec. If the Subject Identifiers draft were to =
include this, it would be very easy for us to remove this from the SSE draf=
t spec.</div><div><br></div><div>BTW a good way to look at all my proposed=
=C2=A0changes to the Subject Identifiers draft is by reviewing my pull requ=
est here:=C2=A0<a href=3D"https://github.com/richanna/secevent/pull/1" targ=
et=3D"_blank">https://github.com/richanna/secevent/pull/1</a></div><div><br=
></div><div>Thanks,</div><div>Atul</div><div><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 3, 2020 =
at 5:43 PM Dick Hardt &lt;<a href=3D"mailto:dick.hardt@gmail.com" target=3D=
"_blank">dick.hardt@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr">I think there is also a fourt=
h option:<div><br></div><div>4. a SPAG identifier can be placed in a separa=
te top level object or top level property</div><div><br></div><div>Atul: in=
 the other thread, you mentioned that there were other additions that the O=
penID Shared Signals and Events WG is interested in. Would you enumerate th=
em as well so that we can address all potential issues?</div><div><br></div=
><div><br></div></div><div hspace=3D"streak-pt-mark" style=3D"max-height:1p=
x"><img alt=3D"" style=3D"width: 0px; max-height: 0px; overflow: hidden;" s=
rc=3D"https://mailfoogae.appspot.com/t?sender=3DaZGljay5oYXJkdEBnbWFpbC5jb2=
0%3D&amp;type=3Dzerocontent&amp;guid=3D831b7283-e9f5-4dbd-a507-5c398074b254=
"><font color=3D"#ffffff" size=3D"1">=E1=90=A7</font></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 3, 2020 =
at 3:04 PM Atul Tulshibagwale &lt;atultulshi=3D<a href=3D"mailto:40google.c=
om@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt; wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D=
"ltr">Hi all,<div>Based on Dick&#39;s request, I&#39;d like to summarize th=
e situation with SPAGs here.</div><div><br></div><div><b>Background</b>:</d=
iv><div>The present <a href=3D"https://github.com/richanna/secevent/blob/1f=
d045d251ff3c6be9a500c6a78d895be3c6b2bf/draft-ietf-secevent-subject-identifi=
ers.txt" target=3D"_blank">Subject Identifiers draft</a> forbids a subject =
identifier of a specific subject_type from having any claims that are not d=
escribed in the subject_type. This prevents higher-level specs from proposi=
ng any additional claims to be included in subject identifiers of subject=
=C2=A0types that are defined in the Subject Identifier spec.</div><div>=C2=
=A0</div><div><b>SPAGs</b>:</div><div>Subject Principal Administrative Grou=
pings or SPAGs are an addition to the OpenID &quot;<a href=3D"https://bitbu=
cket.org/openid/risc/src/caep-draft-01/openid-sse-profile-2_0.txt" target=
=3D"_blank">Shared Signals and Events Profile of SETs&quot;</a>, which is a=
 revision of the &quot;<a href=3D"https://bitbucket.org/openid/risc/src/mas=
ter/openid-risc-profile-1_0.txt" target=3D"_blank">RISC Profile of SETs</a>=
&quot;. The present draft of the SecEvents Subject Identifiers spec is deri=
ved from a section in this RISC Profile. The SSE Profile now refers to the =
SecEvents Subject Identifiers draft.</div><div><br></div><div></div><div>SP=
AGs are required to address the following needs:</div><div><ol><li>Disambig=
uate a subject identifier if it belongs to more than one sub-organizations.=
 For example, if the subject claim in an event is of the subject type &quot=
;email&quot;, then a SPAG may be used to specify the sub-organization the s=
pecified email should be scoped down to. A dynamic organization may have th=
e same email in multiple sub-organizations, and the event may apply to only=
 one such sub organization.</li><li>Provide a lighter weight mechanism to s=
tart and stop event streams for sub-organizations. These could be OUs or dy=
namic groups within an organization, or separate tenants in a multi-tenante=
d transmitter or receiver.</li></ol><div><b>Requirements from Subject Ident=
ifiers</b>:</div></div><div><ol><li>A SPAG may be specified as an additiona=
l attribute of a subject identifier with any subject type, in order to disa=
mbiguate and scope the event with that subject identifier.</li><li>A SPAG m=
ay be a new subject type of its own when it is used in an event that specif=
ies the starting or stopping of a stream.</li></ol><div><b>Options</b>:</di=
v></div><div>The following options are possible to address this requirement=
.</div><div><ol><li><b>Minimal Change to the present Subject Identifiers dr=
aft</b>: Remove the words &quot;or not described&quot; on <a href=3D"https:=
//github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d895be3c6b2b=
f/draft-ietf-secevent-subject-identifiers.txt#L247" target=3D"_blank">line =
247</a>. This way a higher-level spec that needs to add additional attribut=
es to all subject identifiers used in that spec can add them and specify th=
e additional attributes&#39; optional or required nature. In this option, S=
PAGs will be defined in the SSE profile spec.</li><li><b>Include SPAGs in t=
he Subject Identifiers spec</b>: Include language for SPAGs proposed earlie=
r in this list, so that:</li><ol><li>Subject Principals and SPAGs are defin=
ed in the Subject Identifiers spec</li><li>An additional attribute named &q=
uot;spag_id&quot; is added as an optional attribute of any subject_type.</l=
i><li>An additional subject_type &quot;spag&quot; is defined (this is used =
primarily for &quot;control plane&quot; events.)</li></ol><li><b>Do both 1.=
 and 2</b>: With this, we will address the issue that higher-level specs ca=
nnot insert additional attributes in predefined subject types, and define S=
PAGs within the Subject Identifiers spec.</li></ol><div>Thanks,</div></div>=
<div>Atul</div><div><br></div><div></div></div>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>
</blockquote></div>

--000000000000e6083405b5acd8fe--


From nobody Sat Dec  5 09:04:10 2020
Return-Path: <phil.hunt@independentid.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 882C43A08AF for <id-event@ietfa.amsl.com>; Sat,  5 Dec 2020 09:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level: 
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=independentid-com.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 X2EeeLQvcBzh for <id-event@ietfa.amsl.com>; Sat,  5 Dec 2020 09:04:07 -0800 (PST)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (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 D8C673A08A5 for <Id-event@ietf.org>; Sat,  5 Dec 2020 09:04:03 -0800 (PST)
Received: by mail-pg1-x529.google.com with SMTP id q3so5565362pgr.3 for <Id-event@ietf.org>; Sat, 05 Dec 2020 09:04:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=independentid-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=80Np0Madyl+d/s7RQWOAqPsJCfVe7BZAaRQqdh1HDTc=; b=EjUEP4ZNk9SuwspfFJa73cxWlV0IFRTRMSrMH6ney8dXK9G3vWEVhhT2oL0n1kF2o0 pw/rDm6GkPuEqlxzqhW7h1kQ10tQyhPeH3/ppmGkKn4zvBuBc2BmyXBQACr/AutiuJ1+ JXTKoCsuSJ7Px/jFtCjLkNRyyGYm3E5U/Omg6sjVgy6mu4RD7DRafWyAS550sngdy9tW c3oT66/RTKz1MnQV6Js56gKlUP92GMYqavaRX8HQlOCPqE4Ce2NWCuUmYb7xdyfYt1Bp Sss2WwV213EVuYCfUjPh0QD9w/pS75xe5y/G+aVXMT+bQncg9MR56zZj4v+I+OaQHTkg f24Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=80Np0Madyl+d/s7RQWOAqPsJCfVe7BZAaRQqdh1HDTc=; b=LtV9QeAhE1dpR58gbIA+tULZxb5bmYuR4DLv2e60BC2I16L+AxiJZ8byBAMZvf2oB2 muFAHEadGsGb9Xr0zTkfiJqXrJD0KNseAI2eocozGQ1RBOdALfTSfmHoUJ2wS56hibNN By1I7y+UL48q1SDgMqmRqR05p4W1tJxZDa8TxPNHtwKfpe3fZOGOiMbYgr4pCN1ak6Aq XGEgrmom3Tlwosr9vglZ4rAxxxwo945/5c/yPmDW1A/8rRsq2boNeVFK4ETwaewFqTvS nJMNXEFiAjTrIOgfbvYWGX85EEIluVOSIQzwntEGA3cqpyEGsnlAnELqjn4rnfsHuTBh wndw==
X-Gm-Message-State: AOAM530fZdM0nvY543I5D2ZbkSrXQClZ27J0KMdyDItUdtroA/xGXrXM 3Ha8NTf9QcMBR8VaQzM7g+2+1g==
X-Google-Smtp-Source: ABdhPJynBHc4m95VnN4e6az6QnqoKeO3NHjXtw0yyp+rRsGKHG2CZtnWx8Mh6OqCInZUYcPRMqDxBA==
X-Received: by 2002:a62:e50e:0:b029:19d:9fab:4 with SMTP id n14-20020a62e50e0000b029019d9fab0004mr9268789pff.0.1607187843014;  Sat, 05 Dec 2020 09:04:03 -0800 (PST)
Received: from [192.168.1.70] (d75-156-79-23.bchsia.telus.net. [75.156.79.23]) by smtp.gmail.com with ESMTPSA id w11sm9661221pfi.162.2020.12.05.09.04.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 05 Dec 2020 09:04:02 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-8F3FAFE8-6B2F-4DB3-ADDE-292CDBA16BAC
Content-Transfer-Encoding: 7bit
From: Phillip Hunt <phil.hunt@independentid.com>
Mime-Version: 1.0 (1.0)
Date: Sat, 5 Dec 2020 09:04:01 -0800
Message-Id: <6C154303-F3D3-45A5-9701-25FDF319E92E@independentid.com>
References: <CAMCkG5v3FTnNz878Fg85hV1vYpVo1QO=AF49yvDOacw9bLw-vQ@mail.gmail.com>
Cc: Dick Hardt <dick.hardt@gmail.com>, SecEvent <Id-event@ietf.org>
In-Reply-To: <CAMCkG5v3FTnNz878Fg85hV1vYpVo1QO=AF49yvDOacw9bLw-vQ@mail.gmail.com>
To: Atul Tulshibagwale <atultulshi=40google.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (18B92)
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/GDIJMH18mu2mzecK84jgfzL_WqI>
Subject: Re: [Id-event] Options regarding SPAGs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Dec 2020 17:04:10 -0000

--Apple-Mail-8F3FAFE8-6B2F-4DB3-ADDE-292CDBA16BAC
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

When we first started discussions around SET, one goal was to keep events si=
mple/atomic. If multiple subjects are effected by the same event, why not is=
sue multiple events and a =E2=80=9Ctxn=E2=80=9D value to indicate each SET i=
s part of the same parent event/transaction?

Creating compound events to express full context creates a lot of contextual=
 =E2=80=9Cbinding=E2=80=9D between sender and receiver.=20

I am not saying multiple subjects is always wrong. But this begins to feel l=
ike a lot of parsing complexity (affecting event parsing speed) on every mes=
sage rather than send a few more simple messages.  For example ksql can capt=
ure multiple events in a stream to learn that the same event for multiple su=
bjects is related if that needs to be known.=20

Phil

> On Dec 4, 2020, at 4:41 PM, Atul Tulshibagwale <atultulshi=3D40google.com@=
dmarc.ietf.org> wrote:
>=20
> =EF=BB=BF
> Hi Dick,
> #4 may not always be an option if the event has more than one subject clai=
m (e.g. for an event like "device transfer").=20
>=20
> Regarding other additions:
> Subject Categories:
> Earlier, I had proposed that a subject identifier of any subject_type have=
 an optional common claim named "subject_category", which could identify the=
 type of subject principal the subject identifier refers to. However, since t=
he future of this request in the Subject Identifiers spec wasn't clear, we d=
ecided to add a new "subject_type" in the SSE spec, called "user-device-sess=
ion". The SSE spec draft defines the algorithm to figure out the category of=
 the subject principal based on the content of this subject identifier.
>=20
> As a result of this new subject type definition in the SSE spec draft, "su=
bject_category" is no longer a requirement for the SSE work. However, since t=
he SSE spec is still being drafted, if the Subject Identifiers spec has the a=
bility to add a subject category claim to any subject_type, then we can poss=
ibly change the SSE spec to make use of it.
>=20
> SAML Subject Type:
> I had proposed that a SAML subject type be introduced in the Subject Ident=
ifiers. This will help us send and receive events relating to a specific SAM=
L-based federated session. I thought this would be a common subject type of i=
nterest to the Subject Identifiers spec. However, we have now added it as a s=
ubject type in the SSE draft spec. If the Subject Identifiers draft were to i=
nclude this, it would be very easy for us to remove this from the SSE draft s=
pec.
>=20
> BTW a good way to look at all my proposed changes to the Subject Identifie=
rs draft is by reviewing my pull request here: https://github.com/richanna/s=
ecevent/pull/1
>=20
> Thanks,
> Atul
>=20
>=20
>> On Thu, Dec 3, 2020 at 5:43 PM Dick Hardt <dick.hardt@gmail.com> wrote:
>> I think there is also a fourth option:
>>=20
>> 4. a SPAG identifier can be placed in a separate top level object or top l=
evel property
>>=20
>> Atul: in the other thread, you mentioned that there were other additions t=
hat the OpenID Shared Signals and Events WG is interested in. Would you enum=
erate them as well so that we can address all potential issues?
>>=20
>>=20
>> =E1=90=A7
>>=20
>>> On Thu, Dec 3, 2020 at 3:04 PM Atul Tulshibagwale <atultulshi=3D40google=
.com@dmarc.ietf.org> wrote:
>>> Hi all,
>>> Based on Dick's request, I'd like to summarize the situation with SPAGs h=
ere.
>>>=20
>>> Background:
>>> The present Subject Identifiers draft forbids a subject identifier of a s=
pecific subject_type from having any claims that are not described in the su=
bject_type. This prevents higher-level specs from proposing any additional c=
laims to be included in subject identifiers of subject types that are define=
d in the Subject Identifier spec.
>>> =20
>>> SPAGs:
>>> Subject Principal Administrative Groupings or SPAGs are an addition to t=
he OpenID "Shared Signals and Events Profile of SETs", which is a revision o=
f the "RISC Profile of SETs". The present draft of the SecEvents Subject Ide=
ntifiers spec is derived from a section in this RISC Profile. The SSE Profil=
e now refers to the SecEvents Subject Identifiers draft.
>>>=20
>>> SPAGs are required to address the following needs:
>>> Disambiguate a subject identifier if it belongs to more than one sub-org=
anizations. For example, if the subject claim in an event is of the subject t=
ype "email", then a SPAG may be used to specify the sub-organization the spe=
cified email should be scoped down to. A dynamic organization may have the s=
ame email in multiple sub-organizations, and the event may apply to only one=
 such sub organization.
>>> Provide a lighter weight mechanism to start and stop event streams for s=
ub-organizations. These could be OUs or dynamic groups within an organizatio=
n, or separate tenants in a multi-tenanted transmitter or receiver.
>>> Requirements from Subject Identifiers:
>>> A SPAG may be specified as an additional attribute of a subject identifi=
er with any subject type, in order to disambiguate and scope the event with t=
hat subject identifier.
>>> A SPAG may be a new subject type of its own when it is used in an event t=
hat specifies the starting or stopping of a stream.
>>> Options:
>>> The following options are possible to address this requirement.
>>> Minimal Change to the present Subject Identifiers draft: Remove the word=
s "or not described" on line 247. This way a higher-level spec that needs to=
 add additional attributes to all subject identifiers used in that spec can a=
dd them and specify the additional attributes' optional or required nature. I=
n this option, SPAGs will be defined in the SSE profile spec.
>>> Include SPAGs in the Subject Identifiers spec: Include language for SPAG=
s proposed earlier in this list, so that:
>>> Subject Principals and SPAGs are defined in the Subject Identifiers spec=

>>> An additional attribute named "spag_id" is added as an optional attribut=
e of any subject_type.
>>> An additional subject_type "spag" is defined (this is used primarily for=
 "control plane" events.)
>>> Do both 1. and 2: With this, we will address the issue that higher-level=
 specs cannot insert additional attributes in predefined subject types, and d=
efine SPAGs within the Subject Identifiers spec.
>>> Thanks,
>>> Atul
>>>=20
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event

--Apple-Mail-8F3FAFE8-6B2F-4DB3-ADDE-292CDBA16BAC
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">When we first started discussions around SE=
T, one goal was to keep events simple/atomic. If multiple subjects are effec=
ted by the same event, why not issue multiple events and a =E2=80=9Ctxn=E2=80=
=9D value to indicate each SET is part of the same parent event/transaction?=
<div><br></div><div>Creating compound events to express full context creates=
 a lot of contextual =E2=80=9Cbinding=E2=80=9D between sender and receiver.&=
nbsp;</div><div><br></div><div>I am not saying multiple subjects is always w=
rong. But this begins to feel like a lot of parsing complexity (affecting ev=
ent parsing speed) on every message rather than send a few more simple messa=
ges. &nbsp;For example ksql can capture multiple events in a stream to learn=
 that the same event for multiple subjects is related if that needs to be kn=
own.&nbsp;</div><div><br><div dir=3D"ltr">Phil</div><div dir=3D"ltr"><br><bl=
ockquote type=3D"cite">On Dec 4, 2020, at 4:41 PM, Atul Tulshibagwale &lt;at=
ultulshi=3D40google.com@dmarc.ietf.org&gt; wrote:<br><br></blockquote></div>=
<blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF<div dir=3D"ltr">Hi Dick=
,<div>#4 may not always be an option if the event has more than one subject c=
laim (e.g. for an event like "device transfer").&nbsp;</div><div><br></div><=
div>Regarding other additions:</div><div><b>Subject Categories</b>:</div><di=
v>Earlier, I had proposed that a subject identifier of any subject_type have=
 an optional common claim named "subject_category", which could identify the=
 type of subject principal the subject identifier refers to. However, since t=
he future of this request in the Subject Identifiers spec wasn't clear, we d=
ecided to add a new "subject_type" in the SSE spec, called "user-device-sess=
ion". The SSE spec draft defines the algorithm to figure out the category of=
 the subject principal based on the content of this subject identifier.</div=
><div><br></div><div>As a result of this new subject type definition in the S=
SE spec draft, "subject_category" is no longer a requirement for the SSE wor=
k. However, since the SSE spec is still being drafted, if the Subject Identi=
fiers spec has the ability to add a subject category claim to any subject_ty=
pe, then we can possibly change the SSE spec to make use of it.</div><div><b=
r></div><div><b>SAML Subject Type</b>:</div><div>I had proposed that a SAML s=
ubject type be introduced in the Subject Identifiers. This will help us send=
 and receive events relating to a specific SAML-based federated session. I t=
hought this would be a common subject type of interest to the Subject Identi=
fiers spec. However, we have now added it as a subject type in the SSE draft=
 spec. If the Subject Identifiers draft were to include this, it would be ve=
ry easy for us to remove this from the SSE draft spec.</div><div><br></div><=
div>BTW a good way to look at all my proposed&nbsp;changes to the Subject Id=
entifiers draft is by reviewing my pull request here:&nbsp;<a href=3D"https:=
//github.com/richanna/secevent/pull/1" target=3D"_blank">https://github.com/=
richanna/secevent/pull/1</a></div><div><br></div><div>Thanks,</div><div>Atul=
</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Thu, Dec 3, 2020 at 5:43 PM Dick Hardt &lt;<a href=3D=
"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.hardt@gmail.com</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D=
"ltr">I think there is also a fourth option:<div><br></div><div>4. a SPAG id=
entifier can be placed in a separate top level object or top level property<=
/div><div><br></div><div>Atul: in the other thread, you mentioned that there=
 were other additions that the OpenID Shared Signals and Events WG is intere=
sted in. Would you enumerate them as well so that we can address all potenti=
al issues?</div><div><br></div><div><br></div></div><div hspace=3D"streak-pt=
-mark" style=3D"max-height:1px"><img alt=3D"" style=3D"width: 0px; max-heigh=
t: 0px; overflow: hidden;" src=3D"https://mailfoogae.appspot.com/t?sender=3D=
aZGljay5oYXJkdEBnbWFpbC5jb20%3D&amp;type=3Dzerocontent&amp;guid=3D831b7283-e=
9f5-4dbd-a507-5c398074b254" data-unique-identifier=3D""><font color=3D"#ffff=
ff" size=3D"1">=E1=90=A7</font></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Thu, Dec 3, 2020 at 3:04 PM Atul Tulshibagw=
ale &lt;atultulshi=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D=
"_blank">40google.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi all,<div>Based on Dick=
's request, I'd like to summarize the situation with SPAGs here.</div><div><=
br></div><div><b>Background</b>:</div><div>The present <a href=3D"https://gi=
thub.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d895be3c6b2bf/dra=
ft-ietf-secevent-subject-identifiers.txt" target=3D"_blank">Subject Identifi=
ers draft</a> forbids a subject identifier of a specific subject_type from h=
aving any claims that are not described in the subject_type. This prevents h=
igher-level specs from proposing any additional claims to be included in sub=
ject identifiers of subject&nbsp;types that are defined in the Subject Ident=
ifier spec.</div><div>&nbsp;</div><div><b>SPAGs</b>:</div><div>Subject Princ=
ipal Administrative Groupings or SPAGs are an addition to the OpenID "<a hre=
f=3D"https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profile-=
2_0.txt" target=3D"_blank">Shared Signals and Events Profile of SETs"</a>, w=
hich is a revision of the "<a href=3D"https://bitbucket.org/openid/risc/src/=
master/openid-risc-profile-1_0.txt" target=3D"_blank">RISC Profile of SETs</=
a>". The present draft of the SecEvents Subject Identifiers spec is derived f=
rom a section in this RISC Profile. The SSE Profile now refers to the SecEve=
nts Subject Identifiers draft.</div><div><br></div><div></div><div>SPAGs are=
 required to address the following needs:</div><div><ol><li>Disambiguate a s=
ubject identifier if it belongs to more than one sub-organizations. For exam=
ple, if the subject claim in an event is of the subject type "email", then a=
 SPAG may be used to specify the sub-organization the specified email should=
 be scoped down to. A dynamic organization may have the same email in multip=
le sub-organizations, and the event may apply to only one such sub organizat=
ion.</li><li>Provide a lighter weight mechanism to start and stop event stre=
ams for sub-organizations. These could be OUs or dynamic groups within an or=
ganization, or separate tenants in a multi-tenanted transmitter or receiver.=
</li></ol><div><b>Requirements from Subject Identifiers</b>:</div></div><div=
><ol><li>A SPAG may be specified as an additional attribute of a subject ide=
ntifier with any subject type, in order to disambiguate and scope the event w=
ith that subject identifier.</li><li>A SPAG may be a new subject type of its=
 own when it is used in an event that specifies the starting or stopping of a=
 stream.</li></ol><div><b>Options</b>:</div></div><div>The following options=
 are possible to address this requirement.</div><div><ol><li><b>Minimal Chan=
ge to the present Subject Identifiers draft</b>: Remove the words "or not de=
scribed" on <a href=3D"https://github.com/richanna/secevent/blob/1fd045d251f=
f3c6be9a500c6a78d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt#L2=
47" target=3D"_blank">line 247</a>. This way a higher-level spec that needs t=
o add additional attributes to all subject identifiers used in that spec can=
 add them and specify the additional attributes' optional or required nature=
. In this option, SPAGs will be defined in the SSE profile spec.</li><li><b>=
Include SPAGs in the Subject Identifiers spec</b>: Include language for SPAG=
s proposed earlier in this list, so that:</li><ol><li>Subject Principals and=
 SPAGs are defined in the Subject Identifiers spec</li><li>An additional att=
ribute named "spag_id" is added as an optional attribute of any subject_type=
.</li><li>An additional subject_type "spag" is defined (this is used primari=
ly for "control plane" events.)</li></ol><li><b>Do both 1. and 2</b>: With t=
his, we will address the issue that higher-level specs cannot insert additio=
nal attributes in predefined subject types, and define SPAGs within the Subj=
ect Identifiers spec.</li></ol><div>Thanks,</div></div><div>Atul</div><div><=
br></div><div></div></div>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a>=
<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>
</blockquote></div>
<span>_______________________________________________</span><br><span>Id-eve=
nt mailing list</span><br><span>Id-event@ietf.org</span><br><span>https://ww=
w.ietf.org/mailman/listinfo/id-event</span><br></div></blockquote></div></bo=
dy></html>=

--Apple-Mail-8F3FAFE8-6B2F-4DB3-ADDE-292CDBA16BAC--


From nobody Mon Dec  7 13:22:07 2020
Return-Path: <atultulshi@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 759C93A0B25 for <id-event@ietfa.amsl.com>; Mon,  7 Dec 2020 13:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.598
X-Spam-Level: 
X-Spam-Status: No, score=-17.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yDPiLORJbLDN for <id-event@ietfa.amsl.com>; Mon,  7 Dec 2020 13:22:04 -0800 (PST)
Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (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 DF5DC3A0B22 for <Id-event@ietf.org>; Mon,  7 Dec 2020 13:22:03 -0800 (PST)
Received: by mail-yb1-xb2f.google.com with SMTP id w127so2690896ybw.8 for <Id-event@ietf.org>; Mon, 07 Dec 2020 13:22:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=X3GWSaCt1YEnKr2BKGTSOBXBv9jEjg2Kq1dSHE5xUBs=; b=NjoRZ1/Mpz3TT4EbT6nGHRXh7S/ldK+g60OiVCXqxjBzWA2ZjGxcF87zxkQ97Lbquo lhUoeHDxHFC9W0MswjAH21z3K/nOJ4eRzcSjM52/JhM/ciLQyVcjxDqoayW6zDArLKXe HBrJcA2h7nmD3/UJyaMeLRFg+fgTVpNeN5QsWNK2S0T/aT/dyJ4mYs0Y6FMh4Hi9xq1I cBXKyutE3W88vuIIJpzNKczwsGPavTIzdB8U2LTfytYfr4bTmg/dMqg45ImshsUP04pH g9BL6VMbpd8ZP+vvayVXL00JyRfE3iMzD/fKDGyoaAzVuhh1lpmg80CGWAsv95XghC7y 5cJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=X3GWSaCt1YEnKr2BKGTSOBXBv9jEjg2Kq1dSHE5xUBs=; b=Bt5XKxBFnO3heJ3aegg0f3SamVGqD20gPP/s/27BYWRTDi1oM1McT7fSGVORB3lQCT RWV6uY+lN57rpmb4tmRv+aiOtBlrdcIrplRWP9x+Kog7ZXG9xjfy3hsoDa1nZ9OWuqKZ NkW3Jk3z5KeWvLLbAdgW1yN8tjtfcr1tZB92HQU22uDzoS8AT9uTghEwLDvic5nMpCkI b92RKHEuvQyoFU9jN0Jil2d9jCAo4u4Ky0p5q9K5VZ7bZhQOMhfCPBQf1mpdU80TebtK gUXqLb+1i1kdpC5G3XuixGR6SWDYlShEmUMCfdrO9PAEqxuIK8hYvFKckyGnvyMDYKBK 5ypA==
X-Gm-Message-State: AOAM531Y2UvZwiIJjmbRJ2HvWUo1Y5vdWDLhJ2vRwaJM8pro8SkqZZ6Z jiDNRBkf5I9ago2Sv99ui4KOixIu2SEDrkfRXuA9AA==
X-Google-Smtp-Source: ABdhPJwhaKKVpbo/YsIjIPc+XEKt35qVRQVUw6CKWqgsD9WO/knIsvuLB0ICxs26f+OlLNH4iFHDOCNjmIxUmq4MNJY=
X-Received: by 2002:a25:cd48:: with SMTP id d69mr25452868ybf.465.1607376122547;  Mon, 07 Dec 2020 13:22:02 -0800 (PST)
MIME-Version: 1.0
References: <CAMCkG5v3FTnNz878Fg85hV1vYpVo1QO=AF49yvDOacw9bLw-vQ@mail.gmail.com> <6C154303-F3D3-45A5-9701-25FDF319E92E@independentid.com>
In-Reply-To: <6C154303-F3D3-45A5-9701-25FDF319E92E@independentid.com>
From: Atul Tulshibagwale <atultulshi@google.com>
Date: Mon, 7 Dec 2020 13:21:50 -0800
Message-ID: <CAMCkG5tObvekze6c_ie1iVo8CcAqAGx45MxjoLUvHF8og5cShg@mail.gmail.com>
To: Phillip Hunt <phil.hunt@independentid.com>
Cc: Atul Tulshibagwale <atultulshi=40google.com@dmarc.ietf.org>, SecEvent <Id-event@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000ce909505b5e66aa5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/s6p2dOXS89wFTDpnCQimVsfKTso>
Subject: Re: [Id-event] Options regarding SPAGs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2020 21:22:07 -0000

--000000000000ce909505b5e66aa5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Phillip,
Your suggestion makes sense, but I believe this is not something we have
considered in the SSE work. (Also, to be clear, the "device-transfer" is
not an event being considered in the current draft of SSE Event Types spec
either, but just something we have hypothesized about while considering
whether SPAGs belong in the event or in the subject identifier.)

So from a Subject Identifiers spec perspective, the alternative (i.e. #4 in
Dick's email) to not include a SPAG identifier as a claim in the Subject
Identifier is valid.

However since I believe it is a property of the subject principal rather
than of the event, I'd prefer it to be a claim in the Subject Identifier.

Separately, I'd also like to understand the issue of complexity of SETs:
The limitations placed by the spec; intended but not specified by the
authors; and what issues could result from creating more complex SETs.
Right now, one SSE event is designed to be a single SET. If we have to
create multiple SETs for some events, it will be a bit of additional spec
work (and possibly downstream implementation work).

Thanks,
Atul

On Sat, Dec 5, 2020 at 9:04 AM Phillip Hunt <phil.hunt@independentid.com>
wrote:

> When we first started discussions around SET, one goal was to keep events
> simple/atomic. If multiple subjects are effected by the same event, why n=
ot
> issue multiple events and a =E2=80=9Ctxn=E2=80=9D value to indicate each =
SET is part of the
> same parent event/transaction?
>
> Creating compound events to express full context creates a lot of
> contextual =E2=80=9Cbinding=E2=80=9D between sender and receiver.
>
> I am not saying multiple subjects is always wrong. But this begins to fee=
l
> like a lot of parsing complexity (affecting event parsing speed) on every
> message rather than send a few more simple messages.  For example ksql ca=
n
> capture multiple events in a stream to learn that the same event for
> multiple subjects is related if that needs to be known.
>
> Phil
>
> On Dec 4, 2020, at 4:41 PM, Atul Tulshibagwale <atultulshi=3D
> 40google.com@dmarc.ietf.org> wrote:
>
> =EF=BB=BF
> Hi Dick,
> #4 may not always be an option if the event has more than one subject
> claim (e.g. for an event like "device transfer").
>
> Regarding other additions:
> *Subject Categories*:
> Earlier, I had proposed that a subject identifier of any subject_type hav=
e
> an optional common claim named "subject_category", which could identify t=
he
> type of subject principal the subject identifier refers to. However, sinc=
e
> the future of this request in the Subject Identifiers spec wasn't clear, =
we
> decided to add a new "subject_type" in the SSE spec, called
> "user-device-session". The SSE spec draft defines the algorithm to figure
> out the category of the subject principal based on the content of this
> subject identifier.
>
> As a result of this new subject type definition in the SSE spec draft,
> "subject_category" is no longer a requirement for the SSE work. However,
> since the SSE spec is still being drafted, if the Subject Identifiers spe=
c
> has the ability to add a subject category claim to any subject_type, then
> we can possibly change the SSE spec to make use of it.
>
> *SAML Subject Type*:
> I had proposed that a SAML subject type be introduced in the Subject
> Identifiers. This will help us send and receive events relating to a
> specific SAML-based federated session. I thought this would be a common
> subject type of interest to the Subject Identifiers spec. However, we hav=
e
> now added it as a subject type in the SSE draft spec. If the Subject
> Identifiers draft were to include this, it would be very easy for us to
> remove this from the SSE draft spec.
>
> BTW a good way to look at all my proposed changes to the Subject
> Identifiers draft is by reviewing my pull request here:
> https://github.com/richanna/secevent/pull/1
>
> Thanks,
> Atul
>
>
> On Thu, Dec 3, 2020 at 5:43 PM Dick Hardt <dick.hardt@gmail.com> wrote:
>
>> I think there is also a fourth option:
>>
>> 4. a SPAG identifier can be placed in a separate top level object or top
>> level property
>>
>> Atul: in the other thread, you mentioned that there were other additions
>> that the OpenID Shared Signals and Events WG is interested in. Would you
>> enumerate them as well so that we can address all potential issues?
>>
>>
>> =E1=90=A7
>>
>> On Thu, Dec 3, 2020 at 3:04 PM Atul Tulshibagwale <atultulshi=3D
>> 40google.com@dmarc.ietf.org> wrote:
>>
>>> Hi all,
>>> Based on Dick's request, I'd like to summarize the situation with SPAGs
>>> here.
>>>
>>> *Background*:
>>> The present Subject Identifiers draft
>>> <https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d=
895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt>
>>> forbids a subject identifier of a specific subject_type from having any
>>> claims that are not described in the subject_type. This prevents
>>> higher-level specs from proposing any additional claims to be included =
in
>>> subject identifiers of subject types that are defined in the Subject
>>> Identifier spec.
>>>
>>> *SPAGs*:
>>> Subject Principal Administrative Groupings or SPAGs are an addition to
>>> the OpenID "Shared Signals and Events Profile of SETs"
>>> <https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profile=
-2_0.txt>,
>>> which is a revision of the "RISC Profile of SETs
>>> <https://bitbucket.org/openid/risc/src/master/openid-risc-profile-1_0.t=
xt>".
>>> The present draft of the SecEvents Subject Identifiers spec is derived =
from
>>> a section in this RISC Profile. The SSE Profile now refers to the SecEv=
ents
>>> Subject Identifiers draft.
>>>
>>> SPAGs are required to address the following needs:
>>>
>>>    1. Disambiguate a subject identifier if it belongs to more than one
>>>    sub-organizations. For example, if the subject claim in an event is =
of the
>>>    subject type "email", then a SPAG may be used to specify the
>>>    sub-organization the specified email should be scoped down to. A dyn=
amic
>>>    organization may have the same email in multiple sub-organizations, =
and the
>>>    event may apply to only one such sub organization.
>>>    2. Provide a lighter weight mechanism to start and stop event
>>>    streams for sub-organizations. These could be OUs or dynamic groups =
within
>>>    an organization, or separate tenants in a multi-tenanted transmitter=
 or
>>>    receiver.
>>>
>>> *Requirements from Subject Identifiers*:
>>>
>>>    1. A SPAG may be specified as an additional attribute of a subject
>>>    identifier with any subject type, in order to disambiguate and scope=
 the
>>>    event with that subject identifier.
>>>    2. A SPAG may be a new subject type of its own when it is used in an
>>>    event that specifies the starting or stopping of a stream.
>>>
>>> *Options*:
>>> The following options are possible to address this requirement.
>>>
>>>    1. *Minimal Change to the present Subject Identifiers draft*: Remove
>>>    the words "or not described" on line 247
>>>    <https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a=
78d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt#L247>.
>>>    This way a higher-level spec that needs to add additional attributes=
 to all
>>>    subject identifiers used in that spec can add them and specify the
>>>    additional attributes' optional or required nature. In this option, =
SPAGs
>>>    will be defined in the SSE profile spec.
>>>    2. *Include SPAGs in the Subject Identifiers spec*: Include language
>>>    for SPAGs proposed earlier in this list, so that:
>>>       1. Subject Principals and SPAGs are defined in the Subject
>>>       Identifiers spec
>>>       2. An additional attribute named "spag_id" is added as an
>>>       optional attribute of any subject_type.
>>>       3. An additional subject_type "spag" is defined (this is used
>>>       primarily for "control plane" events.)
>>>    3. *Do both 1. and 2*: With this, we will address the issue that
>>>    higher-level specs cannot insert additional attributes in predefined
>>>    subject types, and define SPAGs within the Subject Identifiers spec.
>>>
>>> Thanks,
>>> Atul
>>>
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
>>>
>> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>

--000000000000ce909505b5e66aa5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Phillip,<div>Your suggestion makes sense, but I believe=
 this is not something we have considered in the SSE work. (Also, to be cle=
ar, the &quot;device-transfer&quot; is not an event being considered in the=
 current draft of SSE Event Types spec either, but just something we have h=
ypothesized about while considering whether SPAGs belong in the event or in=
 the subject identifier.)</div><div><br></div><div>So from a Subject Identi=
fiers spec perspective, the alternative (i.e. #4 in Dick&#39;s email) to no=
t include a SPAG identifier as a claim in the Subject Identifier is valid.<=
/div><div><br></div><div>However since I believe it is a property of the su=
bject principal rather than of the event, I&#39;d prefer it to be a claim i=
n the Subject Identifier.</div><div><br></div><div>Separately, I&#39;d also=
 like to understand the issue of complexity of SETs: The limitations placed=
 by the spec; intended but not specified by the authors; and what issues co=
uld result from creating more complex SETs. Right now, one SSE event is des=
igned to be a single SET. If we have to create multiple SETs for some event=
s, it will be a bit of additional spec work (and possibly downstream implem=
entation work).</div><div><br></div><div>Thanks,</div><div>Atul</div></div>=
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat=
, Dec 5, 2020 at 9:04 AM Phillip Hunt &lt;<a href=3D"mailto:phil.hunt@indep=
endentid.com">phil.hunt@independentid.com</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">When we first st=
arted discussions around SET, one goal was to keep events simple/atomic. If=
 multiple subjects are effected by the same event, why not issue multiple e=
vents and a =E2=80=9Ctxn=E2=80=9D value to indicate each SET is part of the=
 same parent event/transaction?<div><br></div><div>Creating compound events=
 to express full context creates a lot of contextual =E2=80=9Cbinding=E2=80=
=9D between sender and receiver.=C2=A0</div><div><br></div><div>I am not sa=
ying multiple subjects is always wrong. But this begins to feel like a lot =
of parsing complexity (affecting event parsing speed) on every message rath=
er than send a few more simple messages.=C2=A0 For example ksql can capture=
 multiple events in a stream to learn that the same event for multiple subj=
ects is related if that needs to be known.=C2=A0</div><div><br><div dir=3D"=
ltr">Phil</div><div dir=3D"ltr"><br><blockquote type=3D"cite">On Dec 4, 202=
0, at 4:41 PM, Atul Tulshibagwale &lt;atultulshi=3D<a href=3D"mailto:40goog=
le.com@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt=
; wrote:<br><br></blockquote></div><blockquote type=3D"cite"><div dir=3D"lt=
r">=EF=BB=BF<div dir=3D"ltr">Hi Dick,<div>#4 may not always be an option if=
 the event has more than one subject claim (e.g. for an event like &quot;de=
vice transfer&quot;).=C2=A0</div><div><br></div><div>Regarding other additi=
ons:</div><div><b>Subject Categories</b>:</div><div>Earlier, I had proposed=
 that a subject identifier of any subject_type have an optional common clai=
m named &quot;subject_category&quot;, which could identify the type of subj=
ect principal the subject identifier refers to. However, since the future o=
f this request in the Subject Identifiers spec wasn&#39;t clear, we decided=
 to add a new &quot;subject_type&quot; in the SSE spec, called &quot;user-d=
evice-session&quot;. The SSE spec draft defines the algorithm to figure out=
 the category of the subject principal based on the content of this subject=
 identifier.</div><div><br></div><div>As a result of this new subject type =
definition in the SSE spec draft, &quot;subject_category&quot; is no longer=
 a requirement for the SSE work. However, since the SSE spec is still being=
 drafted, if the Subject Identifiers spec has the ability to add a subject =
category claim to any subject_type, then we can possibly change the SSE spe=
c to make use of it.</div><div><br></div><div><b>SAML Subject Type</b>:</di=
v><div>I had proposed that a SAML subject type be introduced in the Subject=
 Identifiers. This will help us send and receive events relating to a speci=
fic SAML-based federated session. I thought this would be a common subject =
type of interest to the Subject Identifiers spec. However, we have now adde=
d it as a subject type in the SSE draft spec. If the Subject Identifiers dr=
aft were to include this, it would be very easy for us to remove this from =
the SSE draft spec.</div><div><br></div><div>BTW a good way to look at all =
my proposed=C2=A0changes to the Subject Identifiers draft is by reviewing m=
y pull request here:=C2=A0<a href=3D"https://github.com/richanna/secevent/p=
ull/1" target=3D"_blank">https://github.com/richanna/secevent/pull/1</a></d=
iv><div><br></div><div>Thanks,</div><div>Atul</div><div><br></div></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, D=
ec 3, 2020 at 5:43 PM Dick Hardt &lt;<a href=3D"mailto:dick.hardt@gmail.com=
" target=3D"_blank">dick.hardt@gmail.com</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">I think there is a=
lso a fourth option:<div><br></div><div>4. a SPAG identifier can be placed =
in a separate top level object or top level property</div><div><br></div><d=
iv>Atul: in the other thread, you mentioned that there were other additions=
 that the OpenID Shared Signals and Events WG is interested in. Would you e=
numerate them as well so that we can address all potential issues?</div><di=
v><br></div><div><br></div></div><div hspace=3D"streak-pt-mark" style=3D"ma=
x-height:1px"><img alt=3D"" style=3D"width: 0px; max-height: 0px; overflow:=
 hidden;" src=3D"https://mailfoogae.appspot.com/t?sender=3DaZGljay5oYXJkdEB=
nbWFpbC5jb20%3D&amp;type=3Dzerocontent&amp;guid=3D831b7283-e9f5-4dbd-a507-5=
c398074b254"><font color=3D"#ffffff" size=3D"1">=E1=90=A7</font></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec=
 3, 2020 at 3:04 PM Atul Tulshibagwale &lt;atultulshi=3D<a href=3D"mailto:4=
0google.com@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr">Hi all,<div>Based on Dick&#39;s request, I&#39;d like to sum=
marize the situation with SPAGs here.</div><div><br></div><div><b>Backgroun=
d</b>:</div><div>The present <a href=3D"https://github.com/richanna/seceven=
t/blob/1fd045d251ff3c6be9a500c6a78d895be3c6b2bf/draft-ietf-secevent-subject=
-identifiers.txt" target=3D"_blank">Subject Identifiers draft</a> forbids a=
 subject identifier of a specific subject_type from having any claims that =
are not described in the subject_type. This prevents higher-level specs fro=
m proposing any additional claims to be included in subject identifiers of =
subject=C2=A0types that are defined in the Subject Identifier spec.</div><d=
iv>=C2=A0</div><div><b>SPAGs</b>:</div><div>Subject Principal Administrativ=
e Groupings or SPAGs are an addition to the OpenID &quot;<a href=3D"https:/=
/bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profile-2_0.txt" ta=
rget=3D"_blank">Shared Signals and Events Profile of SETs&quot;</a>, which =
is a revision of the &quot;<a href=3D"https://bitbucket.org/openid/risc/src=
/master/openid-risc-profile-1_0.txt" target=3D"_blank">RISC Profile of SETs=
</a>&quot;. The present draft of the SecEvents Subject Identifiers spec is =
derived from a section in this RISC Profile. The SSE Profile now refers to =
the SecEvents Subject Identifiers draft.</div><div><br></div><div></div><di=
v>SPAGs are required to address the following needs:</div><div><ol><li>Disa=
mbiguate a subject identifier if it belongs to more than one sub-organizati=
ons. For example, if the subject claim in an event is of the subject type &=
quot;email&quot;, then a SPAG may be used to specify the sub-organization t=
he specified email should be scoped down to. A dynamic organization may hav=
e the same email in multiple sub-organizations, and the event may apply to =
only one such sub organization.</li><li>Provide a lighter weight mechanism =
to start and stop event streams for sub-organizations. These could be OUs o=
r dynamic groups within an organization, or separate tenants in a multi-ten=
anted transmitter or receiver.</li></ol><div><b>Requirements from Subject I=
dentifiers</b>:</div></div><div><ol><li>A SPAG may be specified as an addit=
ional attribute of a subject identifier with any subject type, in order to =
disambiguate and scope the event with that subject identifier.</li><li>A SP=
AG may be a new subject type of its own when it is used in an event that sp=
ecifies the starting or stopping of a stream.</li></ol><div><b>Options</b>:=
</div></div><div>The following options are possible to address this require=
ment.</div><div><ol><li><b>Minimal Change to the present Subject Identifier=
s draft</b>: Remove the words &quot;or not described&quot; on <a href=3D"ht=
tps://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d895be3c=
6b2bf/draft-ietf-secevent-subject-identifiers.txt#L247" target=3D"_blank">l=
ine 247</a>. This way a higher-level spec that needs to add additional attr=
ibutes to all subject identifiers used in that spec can add them and specif=
y the additional attributes&#39; optional or required nature. In this optio=
n, SPAGs will be defined in the SSE profile spec.</li><li><b>Include SPAGs =
in the Subject Identifiers spec</b>: Include language for SPAGs proposed ea=
rlier in this list, so that:</li><ol><li>Subject Principals and SPAGs are d=
efined in the Subject Identifiers spec</li><li>An additional attribute name=
d &quot;spag_id&quot; is added as an optional attribute of any subject_type=
.</li><li>An additional subject_type &quot;spag&quot; is defined (this is u=
sed primarily for &quot;control plane&quot; events.)</li></ol><li><b>Do bot=
h 1. and 2</b>: With this, we will address the issue that higher-level spec=
s cannot insert additional attributes in predefined subject types, and defi=
ne SPAGs within the Subject Identifiers spec.</li></ol><div>Thanks,</div></=
div><div>Atul</div><div><br></div><div></div></div>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>
</blockquote></div>
<span>_______________________________________________</span><br><span>Id-ev=
ent mailing list</span><br><span><a href=3D"mailto:Id-event@ietf.org" targe=
t=3D"_blank">Id-event@ietf.org</a></span><br><span><a href=3D"https://www.i=
etf.org/mailman/listinfo/id-event" target=3D"_blank">https://www.ietf.org/m=
ailman/listinfo/id-event</a></span><br></div></blockquote></div></div>_____=
__________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>

--000000000000ce909505b5e66aa5--


From nobody Mon Dec  7 13:55:34 2020
Return-Path: <phil.hunt@independentid.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DFCE3A0B74 for <id-event@ietfa.amsl.com>; Mon,  7 Dec 2020 13:55:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=independentid-com.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 s2_bUvnDAIpR for <id-event@ietfa.amsl.com>; Mon,  7 Dec 2020 13:55:29 -0800 (PST)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 915523A0B50 for <Id-event@ietf.org>; Mon,  7 Dec 2020 13:55:29 -0800 (PST)
Received: by mail-pg1-x532.google.com with SMTP id t3so10170569pgi.11 for <Id-event@ietf.org>; Mon, 07 Dec 2020 13:55:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=independentid-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=sDVD5hsBEw86sfUu7DlHYLTZtd8GoiDSsfJraoFHiQ8=; b=SczOzmL6+dAEZlIdbX7ACdVz/0IV+Tg2d1uVGaI3cMzxRAJoF8TgWydPq3QvpvSlk1 j2NQHK+1JKA4kMRe+YaddGJW7o1SuDaFym+BVUFBlfgAqi5sjIMLvyXNMAHYZKOfFY9/ W0eGBjpfkDO0XAC8i7YdYwqSxb263Kamkl8UnZZKUW04xPSE+F00V37HZqRzsnA9+hOF rQayiuCIn+Us2Z5dtxXIRyLJ9tJoZADvYBPSli5HmOMiQrTeWxqCrPzoAgEdu9QOOucG Adc2MCelAMtA+2CSiDQcThYVg5BD8TmiNcIWonQxJekUTbhneSWJw6dRqeGhxySub3yB 2BbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=sDVD5hsBEw86sfUu7DlHYLTZtd8GoiDSsfJraoFHiQ8=; b=p7l3SErOK/upjyIQuiqDb4MPJoeyEfHwN19Tq1fPOUE/hjnsUov05Z9dkmTtwLxHvT NSGiDp3AaQSB1qoFUt6j/STJpnvubYVk+U0UWhyYnat7GSSPMLXY3k0dcRb4bomcP7xu uNbLTDtIzZ5egyc9IYsUqf58EUB/3WSoXQcMGgJ8doilXxNWnqF5KaIJORdN7kLQkFT1 whF18v8FhQufyMNcb8GEMYMdYSVRGhdfihbRS+7sG76lmBQUAwCvn/3QSQruDAVx1ep7 SXRu3FvGROCFq+h+qpO+j9GVryzf+EoyH//KgwmfIZPQOFcyQaYEBOhDnsCCpDvXKvL/ ncgQ==
X-Gm-Message-State: AOAM532BHcj1fGsJjxHbJp2/bhBNXXu5d25NoNnSUlzphlsvxIvTFePp y1xX17HyMGDHHuezp0IOyOJbpg==
X-Google-Smtp-Source: ABdhPJzaxqclwYRwf2jaseWUG1DbhdHtMIYRAsE0wooSpNGQiVCPqmyDORHACi5SuGzvE3lBDouuig==
X-Received: by 2002:a63:5322:: with SMTP id h34mr20500845pgb.95.1607378128846;  Mon, 07 Dec 2020 13:55:28 -0800 (PST)
Received: from node-1w7jr9qrfoxxatha74ocgn2yg.ipv6.telus.net (node-1w7jr9qrfoxxatha74ocgn2yg.ipv6.telus.net. [2001:569:7a71:1d00:d89f:2170:e5cb:aeb8]) by smtp.gmail.com with ESMTPSA id gp17sm326908pjb.0.2020.12.07.13.55.28 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Dec 2020 13:55:28 -0800 (PST)
From: Phil Hunt <phil.hunt@independentid.com>
Message-Id: <40F396C8-FEF6-4232-B638-BDA40DACC780@independentid.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BC3DA9E5-BBEE-403B-BAC6-CC227FC3FA75"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 7 Dec 2020 13:55:27 -0800
In-Reply-To: <CAMCkG5tObvekze6c_ie1iVo8CcAqAGx45MxjoLUvHF8og5cShg@mail.gmail.com>
Cc: Atul Tulshibagwale <atultulshi=40google.com@dmarc.ietf.org>, ID Events Mailing List <Id-event@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
To: Atul Tulshibagwale <atultulshi@google.com>
References: <CAMCkG5v3FTnNz878Fg85hV1vYpVo1QO=AF49yvDOacw9bLw-vQ@mail.gmail.com> <6C154303-F3D3-45A5-9701-25FDF319E92E@independentid.com> <CAMCkG5tObvekze6c_ie1iVo8CcAqAGx45MxjoLUvHF8og5cShg@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/1sHmICZ-dAh59yhvao4Iu7Dqki8>
Subject: Re: [Id-event] Options regarding SPAGs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2020 21:55:32 -0000

--Apple-Mail=_BC3DA9E5-BBEE-403B-BAC6-CC227FC3FA75
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Atul,

RFC8417 consistently uses the term =E2=80=9Ca subject=E2=80=9D meaning =
subjects are singular.=20

Opening up the possibility of multi-subject events is a major change in =
the intent of SET. For know, I am just not comfortable with the =
trade-off.

Given that a SET may contain mulitiple Event URIs, how does the multiple =
subject identifcation apply to each event payload?  Does this create a =
logic bomb trying to figure out the permutations and combinations of =
multipe-subjects vs multiple events?

The original subject identifier spec had a lot of discussion about =
allowing the use of multiple subject identifier types to deal with =
identifier mis-matches that may occur between event publishers and =
subscribers. Eg. as we have seen in OIDC, RP=E2=80=99s don=E2=80=99t =
always track users by the same identifier as the OP.
=E2=80=94> If you have multiple security subjects identified, does this =
not further confound the OIDC identifier use case?

Phil Hunt
@independentid
phil.hunt@independentid.com




> On Dec 7, 2020, at 1:21 PM, Atul Tulshibagwale <atultulshi@google.com> =
wrote:
>=20
> Hi Phillip,
> Your suggestion makes sense, but I believe this is not something we =
have considered in the SSE work. (Also, to be clear, the =
"device-transfer" is not an event being considered in the current draft =
of SSE Event Types spec either, but just something we have hypothesized =
about while considering whether SPAGs belong in the event or in the =
subject identifier.)
>=20
> So from a Subject Identifiers spec perspective, the alternative (i.e. =
#4 in Dick's email) to not include a SPAG identifier as a claim in the =
Subject Identifier is valid.
>=20
> However since I believe it is a property of the subject principal =
rather than of the event, I'd prefer it to be a claim in the Subject =
Identifier.
>=20
> Separately, I'd also like to understand the issue of complexity of =
SETs: The limitations placed by the spec; intended but not specified by =
the authors; and what issues could result from creating more complex =
SETs. Right now, one SSE event is designed to be a single SET. If we =
have to create multiple SETs for some events, it will be a bit of =
additional spec work (and possibly downstream implementation work).
>=20
> Thanks,
> Atul
>=20
> On Sat, Dec 5, 2020 at 9:04 AM Phillip Hunt =
<phil.hunt@independentid.com <mailto:phil.hunt@independentid.com>> =
wrote:
> When we first started discussions around SET, one goal was to keep =
events simple/atomic. If multiple subjects are effected by the same =
event, why not issue multiple events and a =E2=80=9Ctxn=E2=80=9D value =
to indicate each SET is part of the same parent event/transaction?
>=20
> Creating compound events to express full context creates a lot of =
contextual =E2=80=9Cbinding=E2=80=9D between sender and receiver.=20
>=20
> I am not saying multiple subjects is always wrong. But this begins to =
feel like a lot of parsing complexity (affecting event parsing speed) on =
every message rather than send a few more simple messages.  For example =
ksql can capture multiple events in a stream to learn that the same =
event for multiple subjects is related if that needs to be known.=20
>=20
> Phil
>=20
>> On Dec 4, 2020, at 4:41 PM, Atul Tulshibagwale =
<atultulshi=3D40google.com@dmarc.ietf.org =
<mailto:40google.com@dmarc.ietf.org>> wrote:
>>=20
>> =EF=BB=BF
>> Hi Dick,
>> #4 may not always be an option if the event has more than one subject =
claim (e.g. for an event like "device transfer").=20
>>=20
>> Regarding other additions:
>> Subject Categories:
>> Earlier, I had proposed that a subject identifier of any subject_type =
have an optional common claim named "subject_category", which could =
identify the type of subject principal the subject identifier refers to. =
However, since the future of this request in the Subject Identifiers =
spec wasn't clear, we decided to add a new "subject_type" in the SSE =
spec, called "user-device-session". The SSE spec draft defines the =
algorithm to figure out the category of the subject principal based on =
the content of this subject identifier.
>>=20
>> As a result of this new subject type definition in the SSE spec =
draft, "subject_category" is no longer a requirement for the SSE work. =
However, since the SSE spec is still being drafted, if the Subject =
Identifiers spec has the ability to add a subject category claim to any =
subject_type, then we can possibly change the SSE spec to make use of =
it.
>>=20
>> SAML Subject Type:
>> I had proposed that a SAML subject type be introduced in the Subject =
Identifiers. This will help us send and receive events relating to a =
specific SAML-based federated session. I thought this would be a common =
subject type of interest to the Subject Identifiers spec. However, we =
have now added it as a subject type in the SSE draft spec. If the =
Subject Identifiers draft were to include this, it would be very easy =
for us to remove this from the SSE draft spec.
>>=20
>> BTW a good way to look at all my proposed changes to the Subject =
Identifiers draft is by reviewing my pull request here: =
https://github.com/richanna/secevent/pull/1 =
<https://github.com/richanna/secevent/pull/1>
>>=20
>> Thanks,
>> Atul
>>=20
>>=20
>> On Thu, Dec 3, 2020 at 5:43 PM Dick Hardt <dick.hardt@gmail.com =
<mailto:dick.hardt@gmail.com>> wrote:
>> I think there is also a fourth option:
>>=20
>> 4. a SPAG identifier can be placed in a separate top level object or =
top level property
>>=20
>> Atul: in the other thread, you mentioned that there were other =
additions that the OpenID Shared Signals and Events WG is interested in. =
Would you enumerate them as well so that we can address all potential =
issues?
>>=20
>>=20
>> =E1=90=A7
>>=20
>> On Thu, Dec 3, 2020 at 3:04 PM Atul Tulshibagwale =
<atultulshi=3D40google.com@dmarc.ietf.org =
<mailto:40google.com@dmarc.ietf.org>> wrote:
>> Hi all,
>> Based on Dick's request, I'd like to summarize the situation with =
SPAGs here.
>>=20
>> Background:
>> The present Subject Identifiers draft =
<https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d895=
be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt> forbids a subject =
identifier of a specific subject_type from having any claims that are =
not described in the subject_type. This prevents higher-level specs from =
proposing any additional claims to be included in subject identifiers of =
subject types that are defined in the Subject Identifier spec.
>> =20
>> SPAGs:
>> Subject Principal Administrative Groupings or SPAGs are an addition =
to the OpenID "Shared Signals and Events Profile of SETs" =
<https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profile-2_=
0.txt>, which is a revision of the "RISC Profile of SETs =
<https://bitbucket.org/openid/risc/src/master/openid-risc-profile-1_0.txt>=
". The present draft of the SecEvents Subject Identifiers spec is =
derived from a section in this RISC Profile. The SSE Profile now refers =
to the SecEvents Subject Identifiers draft.
>>=20
>> SPAGs are required to address the following needs:
>> Disambiguate a subject identifier if it belongs to more than one =
sub-organizations. For example, if the subject claim in an event is of =
the subject type "email", then a SPAG may be used to specify the =
sub-organization the specified email should be scoped down to. A dynamic =
organization may have the same email in multiple sub-organizations, and =
the event may apply to only one such sub organization.
>> Provide a lighter weight mechanism to start and stop event streams =
for sub-organizations. These could be OUs or dynamic groups within an =
organization, or separate tenants in a multi-tenanted transmitter or =
receiver.
>> Requirements from Subject Identifiers:
>> A SPAG may be specified as an additional attribute of a subject =
identifier with any subject type, in order to disambiguate and scope the =
event with that subject identifier.
>> A SPAG may be a new subject type of its own when it is used in an =
event that specifies the starting or stopping of a stream.
>> Options:
>> The following options are possible to address this requirement.
>> Minimal Change to the present Subject Identifiers draft: Remove the =
words "or not described" on line 247 =
<https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d895=
be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt#L247>. This way a =
higher-level spec that needs to add additional attributes to all subject =
identifiers used in that spec can add them and specify the additional =
attributes' optional or required nature. In this option, SPAGs will be =
defined in the SSE profile spec.
>> Include SPAGs in the Subject Identifiers spec: Include language for =
SPAGs proposed earlier in this list, so that:
>> Subject Principals and SPAGs are defined in the Subject Identifiers =
spec
>> An additional attribute named "spag_id" is added as an optional =
attribute of any subject_type.
>> An additional subject_type "spag" is defined (this is used primarily =
for "control plane" events.)
>> Do both 1. and 2: With this, we will address the issue that =
higher-level specs cannot insert additional attributes in predefined =
subject types, and define SPAGs within the Subject Identifiers spec.
>> Thanks,
>> Atul
>>=20
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org <mailto:Id-event@ietf.org>
>> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
>> _______________________________________________
>> Id-event mailing list
>> Id-event@ietf.org <mailto:Id-event@ietf.org>
>> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org <mailto:Id-event@ietf.org>
> https://www.ietf.org/mailman/listinfo/id-event =
<https://www.ietf.org/mailman/listinfo/id-event>


--Apple-Mail=_BC3DA9E5-BBEE-403B-BAC6-CC227FC3FA75
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Atul,<div class=3D""><br class=3D""></div><div =
class=3D"">RFC8417 consistently uses the term =E2=80=9Ca subject=E2=80=9D =
meaning subjects are singular.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Opening up the possibility of =
multi-subject events is a major change in the intent of SET. For know, I =
am just not comfortable with the trade-off.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Given that a SET may contain mulitiple =
Event URIs, how does the multiple subject identifcation apply to each =
event payload? &nbsp;Does this create a logic bomb trying to figure out =
the permutations and combinations of multipe-subjects vs multiple =
events?</div><div class=3D""><br class=3D""></div><div class=3D"">The =
original subject identifier spec had a lot of discussion about allowing =
the use of multiple subject identifier types to deal with identifier =
mis-matches that may occur between event publishers and subscribers. Eg. =
as we have seen in OIDC, RP=E2=80=99s don=E2=80=99t always track users =
by the same identifier as the OP.</div><div class=3D"">=E2=80=94&gt; If =
you have multiple security subjects identified, does this not further =
confound the OIDC identifier use case?</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div>Phil Hunt</div><div>@independentid</div><div><a =
href=3D"mailto:phil.hunt@independentid.com" =
class=3D"">phil.hunt@independentid.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Dec 7, 2020, at 1:21 PM, Atul Tulshibagwale &lt;<a =
href=3D"mailto:atultulshi@google.com" =
class=3D"">atultulshi@google.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">Hi Phillip,<div class=3D"">Your suggestion makes sense, but I =
believe this is not something we have considered in the SSE work. (Also, =
to be clear, the "device-transfer" is not an event being considered in =
the current draft of SSE Event Types spec either, but just something we =
have hypothesized about while considering whether SPAGs belong in the =
event or in the subject identifier.)</div><div class=3D""><br =
class=3D""></div><div class=3D"">So from a Subject Identifiers spec =
perspective, the alternative (i.e. #4 in Dick's email) to not include a =
SPAG identifier as a claim in the Subject Identifier is valid.</div><div =
class=3D""><br class=3D""></div><div class=3D"">However since I believe =
it is a property of the subject principal rather than of the event, I'd =
prefer it to be a claim in the Subject Identifier.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Separately, I'd also =
like to understand the issue of complexity of SETs: The limitations =
placed by the spec; intended but not specified by the authors; and what =
issues could result from creating more complex SETs. Right now, one SSE =
event is designed to be a single SET. If we have to create multiple SETs =
for some events, it will be a bit of additional spec work (and possibly =
downstream implementation work).</div><div class=3D""><br =
class=3D""></div><div class=3D"">Thanks,</div><div =
class=3D"">Atul</div></div><br class=3D""><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Sat, Dec 5, 2020 at 9:04 AM Phillip =
Hunt &lt;<a href=3D"mailto:phil.hunt@independentid.com" =
class=3D"">phil.hunt@independentid.com</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div dir=3D"auto" class=3D"">When we =
first started discussions around SET, one goal was to keep events =
simple/atomic. If multiple subjects are effected by the same event, why =
not issue multiple events and a =E2=80=9Ctxn=E2=80=9D value to indicate =
each SET is part of the same parent event/transaction?<div class=3D""><br =
class=3D""></div><div class=3D"">Creating compound events to express =
full context creates a lot of contextual =E2=80=9Cbinding=E2=80=9D =
between sender and receiver.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">I am not saying multiple subjects is =
always wrong. But this begins to feel like a lot of parsing complexity =
(affecting event parsing speed) on every message rather than send a few =
more simple messages.&nbsp; For example ksql can capture multiple events =
in a stream to learn that the same event for multiple subjects is =
related if that needs to be known.&nbsp;</div><div class=3D""><br =
class=3D""><div dir=3D"ltr" class=3D"">Phil</div><div dir=3D"ltr" =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">On Dec 4, =
2020, at 4:41 PM, Atul Tulshibagwale &lt;atultulshi=3D<a =
href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank" =
class=3D"">40google.com@dmarc.ietf.org</a>&gt; wrote:<br class=3D""><br =
class=3D""></blockquote></div><blockquote type=3D"cite" class=3D""><div =
dir=3D"ltr" class=3D"">=EF=BB=BF<div dir=3D"ltr" class=3D"">Hi Dick,<div =
class=3D"">#4 may not always be an option if the event has more than one =
subject claim (e.g. for an event like "device =
transfer").&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">Regarding other additions:</div><div class=3D""><b =
class=3D"">Subject Categories</b>:</div><div class=3D"">Earlier, I had =
proposed that a subject identifier of any subject_type have an optional =
common claim named "subject_category", which could identify the type of =
subject principal the subject identifier refers to. However, since the =
future of this request in the Subject Identifiers spec wasn't clear, we =
decided to add a new "subject_type" in the SSE spec, called =
"user-device-session". The SSE spec draft defines the algorithm to =
figure out the category of the subject principal based on the content of =
this subject identifier.</div><div class=3D""><br class=3D""></div><div =
class=3D"">As a result of this new subject type definition in the SSE =
spec draft, "subject_category" is no longer a requirement for the SSE =
work. However, since the SSE spec is still being drafted, if the Subject =
Identifiers spec has the ability to add a subject category claim to any =
subject_type, then we can possibly change the SSE spec to make use of =
it.</div><div class=3D""><br class=3D""></div><div class=3D""><b =
class=3D"">SAML Subject Type</b>:</div><div class=3D"">I had proposed =
that a SAML subject type be introduced in the Subject Identifiers. This =
will help us send and receive events relating to a specific SAML-based =
federated session. I thought this would be a common subject type of =
interest to the Subject Identifiers spec. However, we have now added it =
as a subject type in the SSE draft spec. If the Subject Identifiers =
draft were to include this, it would be very easy for us to remove this =
from the SSE draft spec.</div><div class=3D""><br class=3D""></div><div =
class=3D"">BTW a good way to look at all my proposed&nbsp;changes to the =
Subject Identifiers draft is by reviewing my pull request here:&nbsp;<a =
href=3D"https://github.com/richanna/secevent/pull/1" target=3D"_blank" =
class=3D"">https://github.com/richanna/secevent/pull/1</a></div><div =
class=3D""><br class=3D""></div><div class=3D"">Thanks,</div><div =
class=3D"">Atul</div><div class=3D""><br class=3D""></div></div><br =
class=3D""><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Thu, Dec 3, 2020 at 5:43 PM Dick Hardt &lt;<a =
href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank" =
class=3D"">dick.hardt@gmail.com</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr" class=3D"">I think =
there is also a fourth option:<div class=3D""><br class=3D""></div><div =
class=3D"">4. a SPAG identifier can be placed in a separate top level =
object or top level property</div><div class=3D""><br =
class=3D""></div><div class=3D"">Atul: in the other thread, you =
mentioned that there were other additions that the OpenID Shared Signals =
and Events WG is interested in. Would you enumerate them as well so that =
we can address all potential issues?</div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div></div><div =
hspace=3D"streak-pt-mark" style=3D"max-height:1px" class=3D""><img =
alt=3D"" style=3D"width: 0px; max-height: 0px; overflow: hidden;" =
src=3D"https://mailfoogae.appspot.com/t?sender=3DaZGljay5oYXJkdEBnbWFpbC5j=
b20%3D&amp;type=3Dzerocontent&amp;guid=3D831b7283-e9f5-4dbd-a507-5c398074b=
254" class=3D""><font color=3D"#ffffff" size=3D"1" =
class=3D"">=E1=90=A7</font></div><br class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec =
3, 2020 at 3:04 PM Atul Tulshibagwale &lt;atultulshi=3D<a =
href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank" =
class=3D"">40google.com@dmarc.ietf.org</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr" class=3D"">Hi =
all,<div class=3D"">Based on Dick's request, I'd like to summarize the =
situation with SPAGs here.</div><div class=3D""><br class=3D""></div><div =
class=3D""><b class=3D"">Background</b>:</div><div class=3D"">The =
present <a =
href=3D"https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6=
a78d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt" =
target=3D"_blank" class=3D"">Subject Identifiers draft</a> forbids a =
subject identifier of a specific subject_type from having any claims =
that are not described in the subject_type. This prevents higher-level =
specs from proposing any additional claims to be included in subject =
identifiers of subject&nbsp;types that are defined in the Subject =
Identifier spec.</div><div class=3D"">&nbsp;</div><div class=3D""><b =
class=3D"">SPAGs</b>:</div><div class=3D"">Subject Principal =
Administrative Groupings or SPAGs are an addition to the OpenID "<a =
href=3D"https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-pro=
file-2_0.txt" target=3D"_blank" class=3D"">Shared Signals and Events =
Profile of SETs"</a>, which is a revision of the "<a =
href=3D"https://bitbucket.org/openid/risc/src/master/openid-risc-profile-1=
_0.txt" target=3D"_blank" class=3D"">RISC Profile of SETs</a>". The =
present draft of the SecEvents Subject Identifiers spec is derived from =
a section in this RISC Profile. The SSE Profile now refers to the =
SecEvents Subject Identifiers draft.</div><div class=3D""><br =
class=3D""></div><div class=3D""></div><div class=3D"">SPAGs are =
required to address the following needs:</div><div class=3D""><ol =
class=3D""><li class=3D"">Disambiguate a subject identifier if it =
belongs to more than one sub-organizations. For example, if the subject =
claim in an event is of the subject type "email", then a SPAG may be =
used to specify the sub-organization the specified email should be =
scoped down to. A dynamic organization may have the same email in =
multiple sub-organizations, and the event may apply to only one such sub =
organization.</li><li class=3D"">Provide a lighter weight mechanism to =
start and stop event streams for sub-organizations. These could be OUs =
or dynamic groups within an organization, or separate tenants in a =
multi-tenanted transmitter or receiver.</li></ol><div class=3D""><b =
class=3D"">Requirements from Subject Identifiers</b>:</div></div><div =
class=3D""><ol class=3D""><li class=3D"">A SPAG may be specified as an =
additional attribute of a subject identifier with any subject type, in =
order to disambiguate and scope the event with that subject =
identifier.</li><li class=3D"">A SPAG may be a new subject type of its =
own when it is used in an event that specifies the starting or stopping =
of a stream.</li></ol><div class=3D""><b =
class=3D"">Options</b>:</div></div><div class=3D"">The following options =
are possible to address this requirement.</div><div class=3D""><ol =
class=3D""><li class=3D""><b class=3D"">Minimal Change to the present =
Subject Identifiers draft</b>: Remove the words "or not described" on <a =
href=3D"https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6=
a78d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt#L247" =
target=3D"_blank" class=3D"">line 247</a>. This way a higher-level spec =
that needs to add additional attributes to all subject identifiers used =
in that spec can add them and specify the additional attributes' =
optional or required nature. In this option, SPAGs will be defined in =
the SSE profile spec.</li><li class=3D""><b class=3D"">Include SPAGs in =
the Subject Identifiers spec</b>: Include language for SPAGs proposed =
earlier in this list, so that:</li><ol class=3D""><li class=3D"">Subject =
Principals and SPAGs are defined in the Subject Identifiers spec</li><li =
class=3D"">An additional attribute named "spag_id" is added as an =
optional attribute of any subject_type.</li><li class=3D"">An additional =
subject_type "spag" is defined (this is used primarily for "control =
plane" events.)</li></ol><li class=3D""><b class=3D"">Do both 1. and =
2</b>: With this, we will address the issue that higher-level specs =
cannot insert additional attributes in predefined subject types, and =
define SPAGs within the Subject Identifiers spec.</li></ol><div =
class=3D"">Thanks,</div></div><div class=3D"">Atul</div><div =
class=3D""><br class=3D""></div><div class=3D""></div></div>
_______________________________________________<br class=3D"">
Id-event mailing list<br class=3D"">
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank" =
class=3D"">Id-event@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event</a><br =
class=3D"">
</blockquote></div>
</blockquote></div>
<span class=3D"">_______________________________________________</span><br=
 class=3D""><span class=3D"">Id-event mailing list</span><br =
class=3D""><span class=3D""><a href=3D"mailto:Id-event@ietf.org" =
target=3D"_blank" class=3D"">Id-event@ietf.org</a></span><br =
class=3D""><span class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/id-event" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event</a></span><br =
class=3D""></div></blockquote></div></div>________________________________=
_______________<br class=3D"">
Id-event mailing list<br class=3D"">
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank" =
class=3D"">Id-event@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/id-event</a><br =
class=3D"">
</blockquote></div>
</div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_BC3DA9E5-BBEE-403B-BAC6-CC227FC3FA75--


From nobody Tue Dec  8 01:07:19 2020
Return-Path: <session-request@ietf.org>
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 9409F3A00E0; Tue,  8 Dec 2020 01:07:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: secevent-chairs@ietf.org, id-event@ietf.org, yaronf.ietf@gmail.com, kaduk@mit.edu
X-Test-IDTracker: no
X-IETF-IDTracker: 7.23.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160741843752.15162.3395638786009452165@ietfa.amsl.com>
Date: Tue, 08 Dec 2020 01:07:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/vrbmrws4Rmpy1CafJF5RGBPkxU0>
Subject: [Id-event] secevent - Not having a session at IETF 110
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Dec 2020 09:07:18 -0000

Yaron Sheffer, a chair of the secevent working group, indicated that the secevent working group does not plan to hold a session at IETF 110.

This message was generated and sent by the IETF Meeting Session Request Tool.




From nobody Thu Dec 10 15:48:01 2020
Return-Path: <dick.hardt@gmail.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9E943A1354 for <id-event@ietfa.amsl.com>; Thu, 10 Dec 2020 15:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 t_t1cx8qmEy4 for <id-event@ietfa.amsl.com>; Thu, 10 Dec 2020 15:47:50 -0800 (PST)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 36B173A138F for <id-event@ietf.org>; Thu, 10 Dec 2020 15:47:49 -0800 (PST)
Received: by mail-lf1-x12a.google.com with SMTP id h19so10770017lfc.12 for <id-event@ietf.org>; Thu, 10 Dec 2020 15:47:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=25In8jNQwkQ9PLbk/em+9pYF7+X5XHEqVvt2BIl0btk=; b=X+G7hNqu3tcPX9v9niVcAlPR6wZt4p2BLWeoPXcvTX1aH4xbNzX1FGnTxWtXJ53Xjq oklEKtthQ0zbL4BTisIAdkeufhgL8VAK3BSXB/0ejmrVapoTNzzddoT4IZ1PWybUXvNk 1iYlc3GjS9DKdinMUbObWtiA7jtBxdGI09M8zg4SkexzjKM0pkT9vYukZXggknrPD4gk TMO/+Rw1fCf+xjriTH6Oy37p9JYNnFD8GSep2IcvAYkvmhBNZCAf4VglS14Nn9OGYzou BGYHm+9OHlRfLkjQLzvdGrMFaOPlHRPvZxRmITBT39k1cJ6O5Mnec0mIWLhlvJYQHYAh Tlww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=25In8jNQwkQ9PLbk/em+9pYF7+X5XHEqVvt2BIl0btk=; b=exV1nVYvYiEb8h4+SBOWg7ZsRyRp/vs11tEiQCHDHcNFKo6gNIYtgU5jv3b93ThA+O H52DW4CtRnQsjd7z0C7+Tadv5GMnCnYNietlUizyIPG06pQAC5n/Rk86rlL7Cw72eodq RuLBKFtDLcKqgqXdqi4+9CFbMRrmGDeGiMt9tmk0sx4PQ7CE832zz5ZG39fWKtglufXm MTZifQFjX5nZX5SFik72P4lMKvlmIYpPLOpGiztED96GfJoJzkIJxxI1mjaFhFVGaW3w h77zlhubcqEyWubAe1t/SuKNJmHlnT4+ALiSsf5lvidOyXS4ywf8v5GH+HEyKLjkzOHv RkuA==
X-Gm-Message-State: AOAM533X4Ra/+vT4VMBJirK1NbnxqwKYrG3WWpKBFDEW+aV6DnEYRCfd pUfz+xWnF5Cx/WBQ3fEBezXI5TAzBPvrZw2sfKM=
X-Google-Smtp-Source: ABdhPJx92ZF7QRC/xEuOphHsY79Z4uCVqVCUgcOYKFZaANt2xmqFgdINY7N3JoUIBnWqowO9Xckjbeyscdm4iNImKlw=
X-Received: by 2002:a19:3818:: with SMTP id f24mr1466915lfa.89.1607644066968;  Thu, 10 Dec 2020 15:47:46 -0800 (PST)
MIME-Version: 1.0
References: <CAMCkG5vAnEyUeRjjRuyuk_mRQEXX2ZdZffGamzGg2+AzjMp9kQ@mail.gmail.com> <CAD9ie-tk53ztCTA8U2bNmaB9dd9x0bK6JNyN=kOU+=RJ8zEUCw@mail.gmail.com> <CAMCkG5v3FTnNz878Fg85hV1vYpVo1QO=AF49yvDOacw9bLw-vQ@mail.gmail.com>
In-Reply-To: <CAMCkG5v3FTnNz878Fg85hV1vYpVo1QO=AF49yvDOacw9bLw-vQ@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Thu, 10 Dec 2020 15:47:10 -0800
Message-ID: <CAD9ie-uzYxw=+5jzPAWL7L4iOBqVmZ2O5v8qhJQkFbHA-S9UFg@mail.gmail.com>
To: Atul Tulshibagwale <atultulshi@google.com>
Cc: SecEvent <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000897bc905b624cde8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/Hix1v3fgJi3jR4KC1e0yHCAaWIY>
Subject: Re: [Id-event] Options regarding SPAGs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Dec 2020 23:48:00 -0000

--000000000000897bc905b624cde8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Atul

I echo Phil's concerns wrt. multi subject SecEvents.

FYI: I am more interested in understanding the use cases so that we can
explore the various solutions than review your proposed changes. A SAML
subject type makes sense to me as it is another subject identifier that is
commonly used.

wrt. SPAG -- another option would be to wrap the secevent object in a SPAG
object -- this would also enable binding multiple secevents together.

Given what I understand of the use case, where one channel is being used to
exchange SecEvents that belong to different transmitters and senders,
wrapping the SecEvent preserves the semantics of a SecEvent, and the SPAG
wrapper identifiers the SPAG on the channel. Would that not work?

/Dick
=E1=90=A7

On Fri, Dec 4, 2020 at 4:41 PM Atul Tulshibagwale <atultulshi@google.com>
wrote:

> Hi Dick,
> #4 may not always be an option if the event has more than one subject
> claim (e.g. for an event like "device transfer").
>
> Regarding other additions:
> *Subject Categories*:
> Earlier, I had proposed that a subject identifier of any subject_type hav=
e
> an optional common claim named "subject_category", which could identify t=
he
> type of subject principal the subject identifier refers to. However, sinc=
e
> the future of this request in the Subject Identifiers spec wasn't clear, =
we
> decided to add a new "subject_type" in the SSE spec, called
> "user-device-session". The SSE spec draft defines the algorithm to figure
> out the category of the subject principal based on the content of this
> subject identifier.
>
> As a result of this new subject type definition in the SSE spec draft,
> "subject_category" is no longer a requirement for the SSE work. However,
> since the SSE spec is still being drafted, if the Subject Identifiers spe=
c
> has the ability to add a subject category claim to any subject_type, then
> we can possibly change the SSE spec to make use of it.
>
> *SAML Subject Type*:
> I had proposed that a SAML subject type be introduced in the Subject
> Identifiers. This will help us send and receive events relating to a
> specific SAML-based federated session. I thought this would be a common
> subject type of interest to the Subject Identifiers spec. However, we hav=
e
> now added it as a subject type in the SSE draft spec. If the Subject
> Identifiers draft were to include this, it would be very easy for us to
> remove this from the SSE draft spec.
>
> BTW a good way to look at all my proposed changes to the Subject
> Identifiers draft is by reviewing my pull request here:
> https://github.com/richanna/secevent/pull/1
>
> Thanks,
> Atul
>
>
> On Thu, Dec 3, 2020 at 5:43 PM Dick Hardt <dick.hardt@gmail.com> wrote:
>
>> I think there is also a fourth option:
>>
>> 4. a SPAG identifier can be placed in a separate top level object or top
>> level property
>>
>> Atul: in the other thread, you mentioned that there were other additions
>> that the OpenID Shared Signals and Events WG is interested in. Would you
>> enumerate them as well so that we can address all potential issues?
>>
>>
>> =E1=90=A7
>>
>> On Thu, Dec 3, 2020 at 3:04 PM Atul Tulshibagwale <atultulshi=3D
>> 40google.com@dmarc.ietf.org> wrote:
>>
>>> Hi all,
>>> Based on Dick's request, I'd like to summarize the situation with SPAGs
>>> here.
>>>
>>> *Background*:
>>> The present Subject Identifiers draft
>>> <https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d=
895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt>
>>> forbids a subject identifier of a specific subject_type from having any
>>> claims that are not described in the subject_type. This prevents
>>> higher-level specs from proposing any additional claims to be included =
in
>>> subject identifiers of subject types that are defined in the Subject
>>> Identifier spec.
>>>
>>> *SPAGs*:
>>> Subject Principal Administrative Groupings or SPAGs are an addition to
>>> the OpenID "Shared Signals and Events Profile of SETs"
>>> <https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profile=
-2_0.txt>,
>>> which is a revision of the "RISC Profile of SETs
>>> <https://bitbucket.org/openid/risc/src/master/openid-risc-profile-1_0.t=
xt>".
>>> The present draft of the SecEvents Subject Identifiers spec is derived =
from
>>> a section in this RISC Profile. The SSE Profile now refers to the SecEv=
ents
>>> Subject Identifiers draft.
>>>
>>> SPAGs are required to address the following needs:
>>>
>>>    1. Disambiguate a subject identifier if it belongs to more than one
>>>    sub-organizations. For example, if the subject claim in an event is =
of the
>>>    subject type "email", then a SPAG may be used to specify the
>>>    sub-organization the specified email should be scoped down to. A dyn=
amic
>>>    organization may have the same email in multiple sub-organizations, =
and the
>>>    event may apply to only one such sub organization.
>>>    2. Provide a lighter weight mechanism to start and stop event
>>>    streams for sub-organizations. These could be OUs or dynamic groups =
within
>>>    an organization, or separate tenants in a multi-tenanted transmitter=
 or
>>>    receiver.
>>>
>>> *Requirements from Subject Identifiers*:
>>>
>>>    1. A SPAG may be specified as an additional attribute of a subject
>>>    identifier with any subject type, in order to disambiguate and scope=
 the
>>>    event with that subject identifier.
>>>    2. A SPAG may be a new subject type of its own when it is used in an
>>>    event that specifies the starting or stopping of a stream.
>>>
>>> *Options*:
>>> The following options are possible to address this requirement.
>>>
>>>    1. *Minimal Change to the present Subject Identifiers draft*: Remove
>>>    the words "or not described" on line 247
>>>    <https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a=
78d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt#L247>.
>>>    This way a higher-level spec that needs to add additional attributes=
 to all
>>>    subject identifiers used in that spec can add them and specify the
>>>    additional attributes' optional or required nature. In this option, =
SPAGs
>>>    will be defined in the SSE profile spec.
>>>    2. *Include SPAGs in the Subject Identifiers spec*: Include language
>>>    for SPAGs proposed earlier in this list, so that:
>>>       1. Subject Principals and SPAGs are defined in the Subject
>>>       Identifiers spec
>>>       2. An additional attribute named "spag_id" is added as an
>>>       optional attribute of any subject_type.
>>>       3. An additional subject_type "spag" is defined (this is used
>>>       primarily for "control plane" events.)
>>>    3. *Do both 1. and 2*: With this, we will address the issue that
>>>    higher-level specs cannot insert additional attributes in predefined
>>>    subject types, and define SPAGs within the Subject Identifiers spec.
>>>
>>> Thanks,
>>> Atul
>>>
>>> _______________________________________________
>>> Id-event mailing list
>>> Id-event@ietf.org
>>> https://www.ietf.org/mailman/listinfo/id-event
>>>
>>

--000000000000897bc905b624cde8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Atul<div><br></div><div>I echo Phil&#39;s concerns wrt.=
 multi subject SecEvents.</div><div><br></div><div>FYI: I am more intereste=
d in understanding the use cases so that we can explore the various solutio=
ns than review your proposed changes. A SAML subject type makes sense to me=
 as it is another subject identifier that is commonly used.</div><div><br><=
/div><div>wrt. SPAG -- another option would be to wrap the secevent object =
in a SPAG object -- this would also enable binding multiple secevents toget=
her.</div><div><br></div><div>Given what I understand of the use case, wher=
e one channel is being used to exchange SecEvents that belong to different =
transmitters and senders, wrapping the SecEvent preserves the semantics of =
a SecEvent, and the SPAG wrapper identifiers the SPAG on the channel. Would=
 that not work?</div><div><br></div><div>/Dick</div></div><div hspace=3D"st=
reak-pt-mark" style=3D"max-height:1px"><img alt=3D"" style=3D"width:0px;max=
-height:0px;overflow:hidden" src=3D"https://mailfoogae.appspot.com/t?sender=
=3DaZGljay5oYXJkdEBnbWFpbC5jb20%3D&amp;type=3Dzerocontent&amp;guid=3Dba8899=
5e-95b8-4caf-b232-5090ed7ae93b"><font color=3D"#ffffff" size=3D"1">=E1=90=
=A7</font></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm=
ail_attr">On Fri, Dec 4, 2020 at 4:41 PM Atul Tulshibagwale &lt;<a href=3D"=
mailto:atultulshi@google.com">atultulshi@google.com</a>&gt; wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi Dick=
,<div>#4 may not always be an option if the event has more than one subject=
 claim (e.g. for an event like &quot;device transfer&quot;).=C2=A0</div><di=
v><br></div><div>Regarding other additions:</div><div><b>Subject Categories=
</b>:</div><div>Earlier, I had proposed that a subject identifier of any su=
bject_type have an optional common claim named &quot;subject_category&quot;=
, which could identify the type of subject principal the subject identifier=
 refers to. However, since the future of this request in the Subject Identi=
fiers spec wasn&#39;t clear, we decided to add a new &quot;subject_type&quo=
t; in the SSE spec, called &quot;user-device-session&quot;. The SSE spec dr=
aft defines the algorithm to figure out the category of the subject princip=
al based on the content of this subject identifier.</div><div><br></div><di=
v>As a result of this new subject type definition in the SSE spec draft, &q=
uot;subject_category&quot; is no longer a requirement for the SSE work. How=
ever, since the SSE spec is still being drafted, if the Subject Identifiers=
 spec has the ability to add a subject category claim to any subject_type, =
then we can possibly change the SSE spec to make use of it.</div><div><br><=
/div><div><b>SAML Subject Type</b>:</div><div>I had proposed that a SAML su=
bject type be introduced in the Subject Identifiers. This will help us send=
 and receive events relating to a specific SAML-based federated session. I =
thought this would be a common subject type of interest to the Subject Iden=
tifiers spec. However, we have now added it as a subject type in the SSE dr=
aft spec. If the Subject Identifiers draft were to include this, it would b=
e very easy for us to remove this from the SSE draft spec.</div><div><br></=
div><div>BTW a good way to look at all my proposed=C2=A0changes to the Subj=
ect Identifiers draft is by reviewing my pull request here:=C2=A0<a href=3D=
"https://github.com/richanna/secevent/pull/1" target=3D"_blank">https://git=
hub.com/richanna/secevent/pull/1</a></div><div><br></div><div>Thanks,</div>=
<div>Atul</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Thu, Dec 3, 2020 at 5:43 PM Dick Hardt &lt=
;<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.hardt@gmail=
.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div dir=3D"ltr">I think there is also a fourth option:<div><br></div><=
div>4. a SPAG identifier can be placed in a separate top level object or to=
p level property</div><div><br></div><div>Atul: in the other thread, you me=
ntioned that there were other additions that the OpenID Shared Signals and =
Events WG is interested in. Would you enumerate them as well so that we can=
 address all potential issues?</div><div><br></div><div><br></div></div><di=
v hspace=3D"streak-pt-mark" style=3D"max-height:1px"><img alt=3D"" style=3D=
"width: 0px; max-height: 0px; overflow: hidden;" src=3D"https://mailfoogae.=
appspot.com/t?sender=3DaZGljay5oYXJkdEBnbWFpbC5jb20%3D&amp;type=3Dzeroconte=
nt&amp;guid=3D831b7283-e9f5-4dbd-a507-5c398074b254"><font color=3D"#ffffff"=
 size=3D"1">=E1=90=A7</font></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Thu, Dec 3, 2020 at 3:04 PM Atul Tulshibag=
wale &lt;atultulshi=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=
=3D"_blank">40google.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi all,<div>Based o=
n Dick&#39;s request, I&#39;d like to summarize the situation with SPAGs he=
re.</div><div><br></div><div><b>Background</b>:</div><div>The present <a hr=
ef=3D"https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78=
d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt" target=3D"_blank=
">Subject Identifiers draft</a> forbids a subject identifier of a specific =
subject_type from having any claims that are not described in the subject_t=
ype. This prevents higher-level specs from proposing any additional claims =
to be included in subject identifiers of subject=C2=A0types that are define=
d in the Subject Identifier spec.</div><div>=C2=A0</div><div><b>SPAGs</b>:<=
/div><div>Subject Principal Administrative Groupings or SPAGs are an additi=
on to the OpenID &quot;<a href=3D"https://bitbucket.org/openid/risc/src/cae=
p-draft-01/openid-sse-profile-2_0.txt" target=3D"_blank">Shared Signals and=
 Events Profile of SETs&quot;</a>, which is a revision of the &quot;<a href=
=3D"https://bitbucket.org/openid/risc/src/master/openid-risc-profile-1_0.tx=
t" target=3D"_blank">RISC Profile of SETs</a>&quot;. The present draft of t=
he SecEvents Subject Identifiers spec is derived from a section in this RIS=
C Profile. The SSE Profile now refers to the SecEvents Subject Identifiers =
draft.</div><div><br></div><div></div><div>SPAGs are required to address th=
e following needs:</div><div><ol><li>Disambiguate a subject identifier if i=
t belongs to more than one sub-organizations. For example, if the subject c=
laim in an event is of the subject type &quot;email&quot;, then a SPAG may =
be used to specify the sub-organization the specified email should be scope=
d down to. A dynamic organization may have the same email in multiple sub-o=
rganizations, and the event may apply to only one such sub organization.</l=
i><li>Provide a lighter weight mechanism to start and stop event streams fo=
r sub-organizations. These could be OUs or dynamic groups within an organiz=
ation, or separate tenants in a multi-tenanted transmitter or receiver.</li=
></ol><div><b>Requirements from Subject Identifiers</b>:</div></div><div><o=
l><li>A SPAG may be specified as an additional attribute of a subject ident=
ifier with any subject type, in order to disambiguate and scope the event w=
ith that subject identifier.</li><li>A SPAG may be a new subject type of it=
s own when it is used in an event that specifies the starting or stopping o=
f a stream.</li></ol><div><b>Options</b>:</div></div><div>The following opt=
ions are possible to address this requirement.</div><div><ol><li><b>Minimal=
 Change to the present Subject Identifiers draft</b>: Remove the words &quo=
t;or not described&quot; on <a href=3D"https://github.com/richanna/secevent=
/blob/1fd045d251ff3c6be9a500c6a78d895be3c6b2bf/draft-ietf-secevent-subject-=
identifiers.txt#L247" target=3D"_blank">line 247</a>. This way a higher-lev=
el spec that needs to add additional attributes to all subject identifiers =
used in that spec can add them and specify the additional attributes&#39; o=
ptional or required nature. In this option, SPAGs will be defined in the SS=
E profile spec.</li><li><b>Include SPAGs in the Subject Identifiers spec</b=
>: Include language for SPAGs proposed earlier in this list, so that:</li><=
ol><li>Subject Principals and SPAGs are defined in the Subject Identifiers =
spec</li><li>An additional attribute named &quot;spag_id&quot; is added as =
an optional attribute of any subject_type.</li><li>An additional subject_ty=
pe &quot;spag&quot; is defined (this is used primarily for &quot;control pl=
ane&quot; events.)</li></ol><li><b>Do both 1. and 2</b>: With this, we will=
 address the issue that higher-level specs cannot insert additional attribu=
tes in predefined subject types, and define SPAGs within the Subject Identi=
fiers spec.</li></ol><div>Thanks,</div></div><div>Atul</div><div><br></div>=
<div></div></div>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>

--000000000000897bc905b624cde8--


From nobody Tue Dec 15 15:42:10 2020
Return-Path: <atultulshi@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05EFE3A08D9 for <id-event@ietfa.amsl.com>; Tue, 15 Dec 2020 15:42:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.598
X-Spam-Level: 
X-Spam-Status: No, score=-17.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t42tl76NpEeS for <id-event@ietfa.amsl.com>; Tue, 15 Dec 2020 15:42:06 -0800 (PST)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 518E53A08D5 for <id-event@ietf.org>; Tue, 15 Dec 2020 15:42:06 -0800 (PST)
Received: by mail-yb1-xb31.google.com with SMTP id y128so956841ybf.10 for <id-event@ietf.org>; Tue, 15 Dec 2020 15:42:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jEbQYyP6BgAuw8xGnRZCM6/4vllOz1pKvCPi8P60JEk=; b=hplxGo0cPdE+Q3uoMzaUG3Te6T+Dh/0NwOG+PHltHPQPEy6Cbn0fFWqcIswtOOfOvY H8P6pSJs05n6UvNLJhcL2lcnsVe6peHhLsqM+WI9PP4xRZLa6wJ8vTaANOQxelhlQu6W cIHVT2ps1CStyfWEpgEBgO0mF8uTB6DgZ9a0eVxeGbMGd5tZUakNp2RlidDM4whWUv0M 0O7rLVZcZHWu/fWjEJEjJMzoBToDMXpISiLGDNrOMTeNNgGgkk++BVEs+KzHueeeIRUN /svS2VJKphxz7kBu7UJZZM6VSLaTOvswD6Uv+nlKNUAmYUXWcPTq3xOiSWiXCp2DX6ow SsEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jEbQYyP6BgAuw8xGnRZCM6/4vllOz1pKvCPi8P60JEk=; b=Y04EFaE5ZUavZLewYkSN3LU7eMeM/hsmW9kMupOa5ilGQZ7nCgCKQ8twwxysPV/Mv0 PicMZvBzzqbQCJ5GhelSvHLnutL2xDxFO9ObV/6exn5tNmvCUrW8x/3+eaqH0mIIf67J NLoRqKyA62hC5L4Dz4dVBvNFyg4Z2mQrXAwBKOHPuLh0JZFo/OAZaijld/UPcYZ2NAKV 0+Lm+mmahYE62FaH5jbgY5YH/NeRIr4zGBeHn3N0DhKIRA0pu9K7iPXgqFRZfGG+i8fe zQOVAYSYCmTv6THrPoIROoVN77iEb/fzKE4uBXJtxmti4j1EDMT31kN3wXTAXuH9hPw2 0S3w==
X-Gm-Message-State: AOAM53201QAThbzw4vq/E3eX7YZsCn286Vv+6IZ4T5VFWLhKlipHGDAp wIL4v3N6AOWQy/r3vAg8Q3D/bS+xFK3w6PPl+UeGcA==
X-Google-Smtp-Source: ABdhPJzuEq4ymGYjBsRwFPv+ZbdTQozx2MeL1s3c8MC07yY3q4Wt3vQU5dFCg+B261bH4p4vbB3+NKw4E8mFyFu3iHs=
X-Received: by 2002:a25:ed7:: with SMTP id 206mr43745381ybo.136.1608075725196;  Tue, 15 Dec 2020 15:42:05 -0800 (PST)
MIME-Version: 1.0
References: <CAMCkG5vAnEyUeRjjRuyuk_mRQEXX2ZdZffGamzGg2+AzjMp9kQ@mail.gmail.com> <CAD9ie-tk53ztCTA8U2bNmaB9dd9x0bK6JNyN=kOU+=RJ8zEUCw@mail.gmail.com> <CAMCkG5v3FTnNz878Fg85hV1vYpVo1QO=AF49yvDOacw9bLw-vQ@mail.gmail.com> <CAD9ie-uzYxw=+5jzPAWL7L4iOBqVmZ2O5v8qhJQkFbHA-S9UFg@mail.gmail.com>
In-Reply-To: <CAD9ie-uzYxw=+5jzPAWL7L4iOBqVmZ2O5v8qhJQkFbHA-S9UFg@mail.gmail.com>
From: Atul Tulshibagwale <atultulshi@google.com>
Date: Tue, 15 Dec 2020 15:41:53 -0800
Message-ID: <CAMCkG5uaVQu6nYtXqYTDv_ZTPxhR7ghu1NfPq7dZJD8y+i9v=Q@mail.gmail.com>
To: Dick Hardt <dick.hardt@gmail.com>
Cc: SecEvent <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005fc12605b6894e14"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/AYD5V-PoFdfK-a0t423yGsUFSYc>
Subject: Re: [Id-event] Options regarding SPAGs
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2020 23:42:09 -0000

--0000000000005fc12605b6894e14
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Dick,
Ideally, we would be able to discuss the complexity of SecEvent tokens and
whether SPAG belongs in a subject-identifier separately. However in this
case they seem somewhat intertwined. Nevertheless, I'm limiting my response
with the assumption that there is only one subject claim in a SecEvent.

Right now, restricting a SecEvent to be about one SPAG can work for the
events we have real use-cases for in SSE. We will still need SPAG as a
subject type of its own for control plane SecEvents, but we can define that
in the SSE spec if it is too specialized of a use case for the general
SecEvents Subject Identifiers spec.

That said, I'd like us to focus on what it means to have a "spag_id" claim
within a subject identifier. The way I see it, SPAGs basically capture the
namespace separation for referring to subjects that may otherwise be
ambiguous.

If we do not allow for adding SPAGs to the spec, we are basically saying to
multi-tenanted hosts that need such separation to always use the "iss-sub"
subject_type and form their own pseudo-standard of how to differentiate
between subject principals that belong to different SPAGs. I can think of
transmitters defining a URL pattern for the "iss" claim that can be parsed
to figure out the sub-organization that the "sub" is about. It'll work, but
the opportunity to standardize something that many transmitters and
receivers need is lost.

So, even if we do not think we should add SPAGs to the spec right now, I
feel we should not preclude higher-level specs from adding such common
claims as SPAGs (i.e. the option #2 in my first email).

Thanks,
Atul

On Thu, Dec 10, 2020 at 3:47 PM Dick Hardt <dick.hardt@gmail.com> wrote:

> Hi Atul
>
> I echo Phil's concerns wrt. multi subject SecEvents.
>
> FYI: I am more interested in understanding the use cases so that we can
> explore the various solutions than review your proposed changes. A SAML
> subject type makes sense to me as it is another subject identifier that i=
s
> commonly used.
>
> wrt. SPAG -- another option would be to wrap the secevent object in a SPA=
G
> object -- this would also enable binding multiple secevents together.
>
> Given what I understand of the use case, where one channel is being used
> to exchange SecEvents that belong to different transmitters and senders,
> wrapping the SecEvent preserves the semantics of a SecEvent, and the SPAG
> wrapper identifiers the SPAG on the channel. Would that not work?
>
> /Dick
> =E1=90=A7
>
> On Fri, Dec 4, 2020 at 4:41 PM Atul Tulshibagwale <atultulshi@google.com>
> wrote:
>
>> Hi Dick,
>> #4 may not always be an option if the event has more than one subject
>> claim (e.g. for an event like "device transfer").
>>
>> Regarding other additions:
>> *Subject Categories*:
>> Earlier, I had proposed that a subject identifier of any subject_type
>> have an optional common claim named "subject_category", which could
>> identify the type of subject principal the subject identifier refers to.
>> However, since the future of this request in the Subject Identifiers spe=
c
>> wasn't clear, we decided to add a new "subject_type" in the SSE spec,
>> called "user-device-session". The SSE spec draft defines the algorithm t=
o
>> figure out the category of the subject principal based on the content of
>> this subject identifier.
>>
>> As a result of this new subject type definition in the SSE spec draft,
>> "subject_category" is no longer a requirement for the SSE work. However,
>> since the SSE spec is still being drafted, if the Subject Identifiers sp=
ec
>> has the ability to add a subject category claim to any subject_type, the=
n
>> we can possibly change the SSE spec to make use of it.
>>
>> *SAML Subject Type*:
>> I had proposed that a SAML subject type be introduced in the Subject
>> Identifiers. This will help us send and receive events relating to a
>> specific SAML-based federated session. I thought this would be a common
>> subject type of interest to the Subject Identifiers spec. However, we ha=
ve
>> now added it as a subject type in the SSE draft spec. If the Subject
>> Identifiers draft were to include this, it would be very easy for us to
>> remove this from the SSE draft spec.
>>
>> BTW a good way to look at all my proposed changes to the Subject
>> Identifiers draft is by reviewing my pull request here:
>> https://github.com/richanna/secevent/pull/1
>>
>> Thanks,
>> Atul
>>
>>
>> On Thu, Dec 3, 2020 at 5:43 PM Dick Hardt <dick.hardt@gmail.com> wrote:
>>
>>> I think there is also a fourth option:
>>>
>>> 4. a SPAG identifier can be placed in a separate top level object or to=
p
>>> level property
>>>
>>> Atul: in the other thread, you mentioned that there were other addition=
s
>>> that the OpenID Shared Signals and Events WG is interested in. Would yo=
u
>>> enumerate them as well so that we can address all potential issues?
>>>
>>>
>>> =E1=90=A7
>>>
>>> On Thu, Dec 3, 2020 at 3:04 PM Atul Tulshibagwale <atultulshi=3D
>>> 40google.com@dmarc.ietf.org> wrote:
>>>
>>>> Hi all,
>>>> Based on Dick's request, I'd like to summarize the situation with SPAG=
s
>>>> here.
>>>>
>>>> *Background*:
>>>> The present Subject Identifiers draft
>>>> <https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78=
d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt>
>>>> forbids a subject identifier of a specific subject_type from having an=
y
>>>> claims that are not described in the subject_type. This prevents
>>>> higher-level specs from proposing any additional claims to be included=
 in
>>>> subject identifiers of subject types that are defined in the Subject
>>>> Identifier spec.
>>>>
>>>> *SPAGs*:
>>>> Subject Principal Administrative Groupings or SPAGs are an addition to
>>>> the OpenID "Shared Signals and Events Profile of SETs"
>>>> <https://bitbucket.org/openid/risc/src/caep-draft-01/openid-sse-profil=
e-2_0.txt>,
>>>> which is a revision of the "RISC Profile of SETs
>>>> <https://bitbucket.org/openid/risc/src/master/openid-risc-profile-1_0.=
txt>".
>>>> The present draft of the SecEvents Subject Identifiers spec is derived=
 from
>>>> a section in this RISC Profile. The SSE Profile now refers to the SecE=
vents
>>>> Subject Identifiers draft.
>>>>
>>>> SPAGs are required to address the following needs:
>>>>
>>>>    1. Disambiguate a subject identifier if it belongs to more than one
>>>>    sub-organizations. For example, if the subject claim in an event is=
 of the
>>>>    subject type "email", then a SPAG may be used to specify the
>>>>    sub-organization the specified email should be scoped down to. A dy=
namic
>>>>    organization may have the same email in multiple sub-organizations,=
 and the
>>>>    event may apply to only one such sub organization.
>>>>    2. Provide a lighter weight mechanism to start and stop event
>>>>    streams for sub-organizations. These could be OUs or dynamic groups=
 within
>>>>    an organization, or separate tenants in a multi-tenanted transmitte=
r or
>>>>    receiver.
>>>>
>>>> *Requirements from Subject Identifiers*:
>>>>
>>>>    1. A SPAG may be specified as an additional attribute of a subject
>>>>    identifier with any subject type, in order to disambiguate and scop=
e the
>>>>    event with that subject identifier.
>>>>    2. A SPAG may be a new subject type of its own when it is used in
>>>>    an event that specifies the starting or stopping of a stream.
>>>>
>>>> *Options*:
>>>> The following options are possible to address this requirement.
>>>>
>>>>    1. *Minimal Change to the present Subject Identifiers draft*:
>>>>    Remove the words "or not described" on line 247
>>>>    <https://github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6=
a78d895be3c6b2bf/draft-ietf-secevent-subject-identifiers.txt#L247>.
>>>>    This way a higher-level spec that needs to add additional attribute=
s to all
>>>>    subject identifiers used in that spec can add them and specify the
>>>>    additional attributes' optional or required nature. In this option,=
 SPAGs
>>>>    will be defined in the SSE profile spec.
>>>>    2. *Include SPAGs in the Subject Identifiers spec*: Include
>>>>    language for SPAGs proposed earlier in this list, so that:
>>>>       1. Subject Principals and SPAGs are defined in the Subject
>>>>       Identifiers spec
>>>>       2. An additional attribute named "spag_id" is added as an
>>>>       optional attribute of any subject_type.
>>>>       3. An additional subject_type "spag" is defined (this is used
>>>>       primarily for "control plane" events.)
>>>>    3. *Do both 1. and 2*: With this, we will address the issue that
>>>>    higher-level specs cannot insert additional attributes in predefine=
d
>>>>    subject types, and define SPAGs within the Subject Identifiers spec=
.
>>>>
>>>> Thanks,
>>>> Atul
>>>>
>>>> _______________________________________________
>>>> Id-event mailing list
>>>> Id-event@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/id-event
>>>>
>>>

--0000000000005fc12605b6894e14
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Dick,<div>Ideally, we would be able to discuss the comp=
lexity of SecEvent tokens and whether SPAG belongs in a subject-identifier =
separately. However in this case they seem somewhat intertwined. Neverthele=
ss, I&#39;m limiting my response with the assumption that there is only one=
 subject claim in a SecEvent.</div><div><br><div>Right now, restricting a S=
ecEvent to be about one SPAG can work for the events we have real use-cases=
 for in SSE. We will still need SPAG as a subject type of its own for contr=
ol plane SecEvents, but we can define that in the SSE spec if it is too spe=
cialized of a use case for the general SecEvents Subject Identifiers spec.<=
/div></div><div><br></div><div>That said, I&#39;d like us to focus on what =
it means to have a &quot;spag_id&quot; claim within a subject identifier. T=
he way I see it, SPAGs basically capture the namespace separation for refer=
ring to subjects that may otherwise be ambiguous.</div><div><br></div><div>=
If we do not allow for adding SPAGs to the spec, we are basically saying to=
 multi-tenanted hosts that need such separation to always use the &quot;iss=
-sub&quot; subject_type and form their own pseudo-standard of how to differ=
entiate between subject principals that belong to different SPAGs. I can th=
ink of transmitters defining a URL pattern for the &quot;iss&quot; claim th=
at can be parsed to figure out the sub-organization that the &quot;sub&quot=
; is about. It&#39;ll work, but the opportunity to standardize something th=
at many transmitters and receivers need is lost.</div><div><br></div><div>S=
o, even if we do not think we should add SPAGs to the spec right now, I fee=
l we should not preclude higher-level specs from adding such common claims =
as SPAGs (i.e. the option #2 in my first email).</div><div><br></div><div>T=
hanks,</div><div>Atul</div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Thu, Dec 10, 2020 at 3:47 PM Dick Hardt &lt;<=
a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.hardt@gmail.c=
om</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><div dir=3D"ltr">Hi Atul<div><br></div><div>I echo Phil&#39;s concerns wr=
t. multi subject SecEvents.</div><div><br></div><div>FYI: I am more interes=
ted in understanding the use cases so that we can explore the various solut=
ions than review your proposed changes. A SAML subject type makes sense to =
me as it is another subject identifier that is commonly used.</div><div><br=
></div><div>wrt. SPAG -- another option would be to wrap the secevent objec=
t in a SPAG object -- this would also enable binding multiple secevents tog=
ether.</div><div><br></div><div>Given what I understand of the use case, wh=
ere one channel is being used to exchange SecEvents that belong to differen=
t transmitters and senders, wrapping the SecEvent preserves the semantics o=
f a SecEvent, and the SPAG wrapper identifiers the SPAG on the channel. Wou=
ld that not work?</div><div><br></div><div>/Dick</div></div><div hspace=3D"=
streak-pt-mark" style=3D"max-height:1px"><img alt=3D"" style=3D"width: 0px;=
 max-height: 0px; overflow: hidden;" src=3D"https://mailfoogae.appspot.com/=
t?sender=3DaZGljay5oYXJkdEBnbWFpbC5jb20%3D&amp;type=3Dzerocontent&amp;guid=
=3Dba88995e-95b8-4caf-b232-5090ed7ae93b"><font color=3D"#ffffff" size=3D"1"=
>=E1=90=A7</font></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">On Fri, Dec 4, 2020 at 4:41 PM Atul Tulshibagwale &lt;<a h=
ref=3D"mailto:atultulshi@google.com" target=3D"_blank">atultulshi@google.co=
m</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
><div dir=3D"ltr">Hi Dick,<div>#4 may not always be an option if the event =
has more than one subject claim (e.g. for an event like &quot;device transf=
er&quot;).=C2=A0</div><div><br></div><div>Regarding other additions:</div><=
div><b>Subject Categories</b>:</div><div>Earlier, I had proposed that a sub=
ject identifier of any subject_type have an optional common claim named &qu=
ot;subject_category&quot;, which could identify the type of subject princip=
al the subject identifier refers to. However, since the future of this requ=
est in the Subject Identifiers spec wasn&#39;t clear, we decided to add a n=
ew &quot;subject_type&quot; in the SSE spec, called &quot;user-device-sessi=
on&quot;. The SSE spec draft defines the algorithm to figure out the catego=
ry of the subject principal based on the content of this subject identifier=
.</div><div><br></div><div>As a result of this new subject type definition =
in the SSE spec draft, &quot;subject_category&quot; is no longer a requirem=
ent for the SSE work. However, since the SSE spec is still being drafted, i=
f the Subject Identifiers spec has the ability to add a subject category cl=
aim to any subject_type, then we can possibly change the SSE spec to make u=
se of it.</div><div><br></div><div><b>SAML Subject Type</b>:</div><div>I ha=
d proposed that a SAML subject type be introduced in the Subject Identifier=
s. This will help us send and receive events relating to a specific SAML-ba=
sed federated session. I thought this would be a common subject type of int=
erest to the Subject Identifiers spec. However, we have now added it as a s=
ubject type in the SSE draft spec. If the Subject Identifiers draft were to=
 include this, it would be very easy for us to remove this from the SSE dra=
ft spec.</div><div><br></div><div>BTW a good way to look at all my proposed=
=C2=A0changes to the Subject Identifiers draft is by reviewing my pull requ=
est here:=C2=A0<a href=3D"https://github.com/richanna/secevent/pull/1" targ=
et=3D"_blank">https://github.com/richanna/secevent/pull/1</a></div><div><br=
></div><div>Thanks,</div><div>Atul</div><div><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 3, 2020 =
at 5:43 PM Dick Hardt &lt;<a href=3D"mailto:dick.hardt@gmail.com" target=3D=
"_blank">dick.hardt@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr">I think there is also a fourt=
h option:<div><br></div><div>4. a SPAG identifier can be placed in a separa=
te top level object or top level property</div><div><br></div><div>Atul: in=
 the other thread, you mentioned that there were other additions that the O=
penID Shared Signals and Events WG is interested in. Would you enumerate th=
em as well so that we can address all potential issues?</div><div><br></div=
><div><br></div></div><div hspace=3D"streak-pt-mark" style=3D"max-height:1p=
x"><img alt=3D"" style=3D"width: 0px; max-height: 0px; overflow: hidden;" s=
rc=3D"https://mailfoogae.appspot.com/t?sender=3DaZGljay5oYXJkdEBnbWFpbC5jb2=
0%3D&amp;type=3Dzerocontent&amp;guid=3D831b7283-e9f5-4dbd-a507-5c398074b254=
"><font color=3D"#ffffff" size=3D"1">=E1=90=A7</font></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 3, 2020 =
at 3:04 PM Atul Tulshibagwale &lt;atultulshi=3D<a href=3D"mailto:40google.c=
om@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt; wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D=
"ltr">Hi all,<div>Based on Dick&#39;s request, I&#39;d like to summarize th=
e situation with SPAGs here.</div><div><br></div><div><b>Background</b>:</d=
iv><div>The present <a href=3D"https://github.com/richanna/secevent/blob/1f=
d045d251ff3c6be9a500c6a78d895be3c6b2bf/draft-ietf-secevent-subject-identifi=
ers.txt" target=3D"_blank">Subject Identifiers draft</a> forbids a subject =
identifier of a specific subject_type from having any claims that are not d=
escribed in the subject_type. This prevents higher-level specs from proposi=
ng any additional claims to be included in subject identifiers of subject=
=C2=A0types that are defined in the Subject Identifier spec.</div><div>=C2=
=A0</div><div><b>SPAGs</b>:</div><div>Subject Principal Administrative Grou=
pings or SPAGs are an addition to the OpenID &quot;<a href=3D"https://bitbu=
cket.org/openid/risc/src/caep-draft-01/openid-sse-profile-2_0.txt" target=
=3D"_blank">Shared Signals and Events Profile of SETs&quot;</a>, which is a=
 revision of the &quot;<a href=3D"https://bitbucket.org/openid/risc/src/mas=
ter/openid-risc-profile-1_0.txt" target=3D"_blank">RISC Profile of SETs</a>=
&quot;. The present draft of the SecEvents Subject Identifiers spec is deri=
ved from a section in this RISC Profile. The SSE Profile now refers to the =
SecEvents Subject Identifiers draft.</div><div><br></div><div></div><div>SP=
AGs are required to address the following needs:</div><div><ol><li>Disambig=
uate a subject identifier if it belongs to more than one sub-organizations.=
 For example, if the subject claim in an event is of the subject type &quot=
;email&quot;, then a SPAG may be used to specify the sub-organization the s=
pecified email should be scoped down to. A dynamic organization may have th=
e same email in multiple sub-organizations, and the event may apply to only=
 one such sub organization.</li><li>Provide a lighter weight mechanism to s=
tart and stop event streams for sub-organizations. These could be OUs or dy=
namic groups within an organization, or separate tenants in a multi-tenante=
d transmitter or receiver.</li></ol><div><b>Requirements from Subject Ident=
ifiers</b>:</div></div><div><ol><li>A SPAG may be specified as an additiona=
l attribute of a subject identifier with any subject type, in order to disa=
mbiguate and scope the event with that subject identifier.</li><li>A SPAG m=
ay be a new subject type of its own when it is used in an event that specif=
ies the starting or stopping of a stream.</li></ol><div><b>Options</b>:</di=
v></div><div>The following options are possible to address this requirement=
.</div><div><ol><li><b>Minimal Change to the present Subject Identifiers dr=
aft</b>: Remove the words &quot;or not described&quot; on <a href=3D"https:=
//github.com/richanna/secevent/blob/1fd045d251ff3c6be9a500c6a78d895be3c6b2b=
f/draft-ietf-secevent-subject-identifiers.txt#L247" target=3D"_blank">line =
247</a>. This way a higher-level spec that needs to add additional attribut=
es to all subject identifiers used in that spec can add them and specify th=
e additional attributes&#39; optional or required nature. In this option, S=
PAGs will be defined in the SSE profile spec.</li><li><b>Include SPAGs in t=
he Subject Identifiers spec</b>: Include language for SPAGs proposed earlie=
r in this list, so that:</li><ol><li>Subject Principals and SPAGs are defin=
ed in the Subject Identifiers spec</li><li>An additional attribute named &q=
uot;spag_id&quot; is added as an optional attribute of any subject_type.</l=
i><li>An additional subject_type &quot;spag&quot; is defined (this is used =
primarily for &quot;control plane&quot; events.)</li></ol><li><b>Do both 1.=
 and 2</b>: With this, we will address the issue that higher-level specs ca=
nnot insert additional attributes in predefined subject types, and define S=
PAGs within the Subject Identifiers spec.</li></ol><div>Thanks,</div></div>=
<div>Atul</div><div><br></div><div></div></div>
_______________________________________________<br>
Id-event mailing list<br>
<a href=3D"mailto:Id-event@ietf.org" target=3D"_blank">Id-event@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/id-event" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/id-event</a><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>

--0000000000005fc12605b6894e14--

