[Openid-specs-risc] Subject identifiers / categories call

[Tim Cappalli]

This is a great summary Atul.

I have an action item to discuss multiple subjects vs single subject with multiple claims with Mike and report back on Tuesday.

tim


 Tim Cappalli | @timcappalli<https://www.twitter.com/timcappalli>
[Microsoft logo]

From: Atul Tulshibagwale via Openid-specs-risc<mailto:openid-specs-risc at lists.openid.net>
Sent: Tuesday, August 25, 2020 21:09
To: Openid-specs-risc<mailto:openid-specs-risc at lists.openid.net>
Subject: [Openid-specs-risc] Subject identifiers / categories call

Hi all,
We had the call earlier today to discuss multiple subject identifiers and subject categories in subject identifiers. Annabelle wasn't able to attend. The following is a (incomplete) summary of the discussion:

  1.  We agreed that the subject processing can be greatly simplified if when we specify multiple subjects in a single event, we always interpret that to mean that the intended subject of the event is an "AND" of all subject identifiers.
  2.  An interesting proposal from Praveen (Microsoft) was that we could have a different subject-type that had fields like "user" and "device". Upon discussion we figured out each one of these fields would require the same subject-identifier structure, so it won't be any different from the multiple subject-identifiers proposal being considered right now. It'll be great if Praveen can share his example to this list anyway, for further discussion.
  3.  We agreed that defining event-specific subject identifier combinations would not be good for implementers.
  4.  subject-categories are required to disambiguate use-cases where a subject identified by a subject-type of say, phone-number or iss-sub need to be classified as either a device or a user.
I've added the notes to the weekly sync doc<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1ZFwJJDwwSBNKX35VObClC1ctMbMMuHJtr5qY-7xsLW8%2Fedit%3Fusp%3Dsharing&data=02%7C01%7Ctim.cappalli%40microsoft.com%7Cfff1926f9af140313f3408d8495cbd41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637340009966110532&sdata=KnVprkVVP5XbBUfD4HSa1%2FcsnCRn1Z27UBU51y5kERg%3D&reserved=0>, but since I was actively participating in the discussion, the notes are (very) incomplete.

Atul

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20200826/3e395a5d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: EA3D9D0B1CF64289A146B639C4E9ED58[7529884].gif
Type: image/gif
Size: 44334 bytes
Desc: EA3D9D0B1CF64289A146B639C4E9ED58[7529884].gif
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20200826/3e395a5d/attachment-0001.gif>