
From nobody Wed Nov 25 09:04:59 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 9E1033A1ABB for <id-event@ietfa.amsl.com>; Wed, 25 Nov 2020 09:04:57 -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 9SWSF9Q9_tNM for <id-event@ietfa.amsl.com>; Wed, 25 Nov 2020 09:04:53 -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 821F83A1ABD for <id-event@ietf.org>; Wed, 25 Nov 2020 09:04:53 -0800 (PST)
Received: by mail-yb1-xb2e.google.com with SMTP id w5so373991ybj.11 for <id-event@ietf.org>; Wed, 25 Nov 2020 09:04:53 -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=wPhUuvvVyr8kwRQWu4l+qPWBnoG5EPfpnY1r6Go04CQ=; b=oHlxfOF0rUYjp7XKue6hyMYkbn2gYqk0XK8GDZ2fR9PbpwyxTQeNA77/SLhKxiJG9m y4nU2Uyvn44UNGMZe1/iCGzexu1/7y9azHdpjsywvKY/Kjh41oaNHbCQ+9AeTm3pQy9X PWejtngrx+in2kKquLFlhD7Kp3JtgIKWfhngATYTK+Fa/HLAjzOBMLvKJegG/mkpruXf 5ZEvSE2J3e0SFH5vMqz1A2KpePy45Lvx3pM4P/YDVBbWtSHO6bH55jGNIc3a6lWol9NB Jkh4CT89ehG9Zgpr7wLqwBGcxnTn5c/IXshuTmSCO9XHplzahx61SPY06QC0QeyNqa4N Wl3A==
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=wPhUuvvVyr8kwRQWu4l+qPWBnoG5EPfpnY1r6Go04CQ=; b=HhDZHYoct5hh5v7+N0rV0A8cnHZNjRUamoNnSJg3+VaXi8dQKxarAHmc19LTi7u2IM OuvY9icqhdRcmZBeOsknMGqc4C0I+oINCfoIdrtxUBWMDtJoom+LBP+nyt2hDY7Ulmw6 8tvnmD9CVI8QSlqlGwoqWf7MLFOp51CWKoieR/XaIPxtSuyHlSkkC+hDAGyY3H/1mIzb VJXpUrlAHzkJG1uFUp2zcmpCBoCvVbAPV2GHgF/tCWTifhPvhEo+lUWUQE1W2KBC5MRl Z2XVwsHz/IWFQ4B+pIlSfhzOEi2hLxEq6gfCITHrlyFY9uTy7xxJa4AJkK56IncQPtDp L+hA==
X-Gm-Message-State: AOAM530fP86bblGs9q3FFFw+V27CdMSeOecWL0N37iwwH+Z7Ja2/ysg7 OFiAg+uMPPoF/i9vWLIvq0fPxYlPcpsXoTBaWCgbJQ==
X-Google-Smtp-Source: ABdhPJzo+RcteDSdYfE6jGyJxLaMjIa8MR6UTttue64PJW+Z5WXltQW9cIweIzFD6BW8i++X2ztRy31y3udPg5wW0VQ=
X-Received: by 2002:a25:cd48:: with SMTP id d69mr5441886ybf.465.1606323892264;  Wed, 25 Nov 2020 09:04:52 -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>
In-Reply-To: <CAMCkG5u2sVALP38cAhDnvfXsORSxPe-LeZ0ignsUQBzwgr1U-Q@mail.gmail.com>
From: Atul Tulshibagwale <atultulshi@google.com>
Date: Wed, 25 Nov 2020 09:04:40 -0800
Message-ID: <CAMCkG5v251jTkQqpXUzRsq68ZQZ3YzUo1zwYUeDbn0hTypqLOA@mail.gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Cc: Justin Richer <jricher@mit.edu>, SecEvent <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fe93bb05b4f16c6c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/pL1pLtSGq7_Y2V8RsFvT1v-5X5c>
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, 25 Nov 2020 17:04:58 -0000

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

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 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 ever=
y
>> subject identifier, since it may not apply in many cases. Ignoring a SPA=
G
>> value may still be OK if, say, the receiver is a single tenanted receive=
r
>> and the SPAG in the subject identifier is a tenant identifier. Also, not=
e
>> 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 specificatio=
n
>> could add claims that may have additional semantics relating to the
>> interpretation of those claims. The Subject Identifiers specification co=
uld
>> 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 wi=
th
>> defining the SPAG claim in the SSE specification, if we have a way for t=
he
>> 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 groupings
>> 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 attrib=
ute that
>>> he=E2=80=99s proposing defines a scope (a.k.a. namespace) for the subje=
ct 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 that can b=
e
>>> 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 separat=
e 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 enab=
les
>>> supporting multiple issuers per host. This is required in some multi-te=
nant
>>> 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 t=
o
>>> 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 Identifie=
rs
>>> 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 restriction
>>> was to make the subject identifier objects compact and easily processed
>>> without getting a bunch of arbitrary stuff strung onto them, but I thin=
k
>>> the MUST NOT might go too far toward that.
>>>
>>>
>>> I would like to see the requirement relaxed but also have guidance as t=
o
>>> 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 t=
hey
>>> 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-su=
bject-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 def=
ine
>>> 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 identifie=
r.
>>> 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 th=
is
>>> 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 look=
s
>>> 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
>>>
>>>
>>>

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

<div dir=3D"ltr">Pinging this topic as discussed 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 Tulshibagwale &lt;<a href=3D"mailto:=
atultulshi@google.com">atultulshi@google.com</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Annabelle,<div=
><br><div>Could you please provide an update on whether this change (any of=
 the two proposed options) is possible in this Subject Identifiers specific=
ation? The work in the OpenID SSE WG cannot proceed without this clarificat=
ion.</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@goo=
gle.com" target=3D"_blank">atultulshi@google.com</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi=C2=A0Ya=
ron,<div><br></div><div>I agree that SPAGs would typically need to be under=
stood by the transmitter and receiver. However this claim need not be prese=
nt in every subject identifier, since it may not apply in many=C2=A0cases. =
Ignoring a SPAG value may still be OK if, say, the receiver is a single ten=
anted receiver and the SPAG in the subject identifier is a tenant identifie=
r. Also,=C2=A0note that SPAGs do not necessarily only identify tenants; the=
y may identify other subject principal groupings such as OUs, groups, etc.<=
/div><div><br></div><div>In general, specifications that use the Subject Id=
entifiers specification could add claims that may have additional semantics=
 relating to the interpretation of those claims. The Subject Identifiers sp=
ecification 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 Subject Identifiers specification as =
such. But I&#39;m OK with defining the SPAG claim in the SSE specification,=
 if we have a way for the Subject Identifiers specification to allow the ad=
dition of such a claim to any subject identifier.</div><div><br></div><div>=
Thanks,</div><div>Atul</div><div><br></div><div>PS: There has been some dis=
cussion in the OpenID SSE WG about multiple event streams versus using SPAG=
s to identify different subject groupings within the same stream. A good ve=
nue to discuss this is the <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 this 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 S=
SE profile spec when it&#39;s ready). </div><div><br></div></div><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 2, 2=
020 at 8:26 AM Yaron Sheffer &lt;<a href=3D"mailto:yaronf.ietf@gmail.com" t=
arget=3D"_blank">yaronf.ietf@gmail.com</a>&gt; wrote:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-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>

--000000000000fe93bb05b4f16c6c--


From nobody Mon Nov 30 16:45:03 2020
Return-Path: <wwwrun@rfc-editor.org>
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 EC3A63A138D; Mon, 30 Nov 2020 16:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8we1PnY_7s9; Mon, 30 Nov 2020 16:44:48 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A94E3A1429; Mon, 30 Nov 2020 16:44:10 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 07408F4076F; Mon, 30 Nov 2020 16:44:09 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, id-event@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20201201004409.07408F4076F@rfc-editor.org>
Date: Mon, 30 Nov 2020 16:44:09 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/LfaeitZYzPxFeSNj_mpr5iNhe9o>
Subject: [Id-event] =?utf-8?q?RFC_8935_on_Push-Based_Security_Event_Token?= =?utf-8?q?_=28SET=29_Delivery_Using_HTTP?=
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 00:44:56 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8935

        Title:      Push-Based Security Event Token (SET) 
                    Delivery Using HTTP 
        Author:     A. Backman, Ed.,
                    M. Jones, Ed.,
                    M. Scurtescu,
                    M. Ansari,
                    A. Nadalin
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2020
        Mailbox:    richanna@amazon.com, 
                    mbj@microsoft.com, 
                    marius.scurtescu@coinbase.com,
                    morteza@sharppics.com, 
                    nadalin@prodigy.net
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-secevent-http-push-14.txt

        URL:        https://www.rfc-editor.org/info/rfc8935

        DOI:        10.17487/RFC8935

This specification defines how a Security Event Token (SET) can be
delivered to an intended recipient using HTTP POST over TLS.  The SET
is transmitted in the body of an HTTP POST request to an endpoint
operated by the recipient, and the recipient indicates successful or
failed transmission via the HTTP response.

This document is a product of the Security Events Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon Nov 30 16:45:18 2020
Return-Path: <wwwrun@rfc-editor.org>
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 48E1B3A15A6; Mon, 30 Nov 2020 16:45:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hstzEFf1TYvp; Mon, 30 Nov 2020 16:45:10 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FF913A156C; Mon, 30 Nov 2020 16:44:34 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DA304F40779; Mon, 30 Nov 2020 16:44:32 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, id-event@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20201201004432.DA304F40779@rfc-editor.org>
Date: Mon, 30 Nov 2020 16:44:32 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/9JuMCVwnJdYXZYTXwgDkMBK0ZkI>
Subject: [Id-event] =?utf-8?q?RFC_8936_on_Poll-Based_Security_Event_Token?= =?utf-8?q?_=28SET=29_Delivery_Using_HTTP?=
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 00:45:17 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8936

        Title:      Poll-Based Security Event Token (SET) 
                    Delivery Using HTTP 
        Author:     A. Backman, Ed.,
                    M. Jones, Ed.,
                    M. Scurtescu, 
                    M. Ansari,
                    A. Nadalin
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2020
        Mailbox:    richanna@amazon.com, 
                    mbj@microsoft.com, 
                    marius.scurtescu@coinbase.com,
                    morteza@sharppics.com, 
                    nadalin@prodigy.net
        Pages:      16
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-secevent-http-poll-12.txt

        URL:        https://www.rfc-editor.org/info/rfc8936

        DOI:        10.17487/RFC8936

This specification defines how a series of Security Event Tokens
(SETs) can be delivered to an intended recipient using HTTP POST over
TLS initiated as a poll by the recipient. The specification also
defines how delivery can be assured, subject to the SET Recipient's
need for assurance.

This document is a product of the Security Events Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


