[Openid-specs-risc] Notes from the call on 2/2/2021

[Atul Tulshibagwale]

Hi all,
Here are the notes
<https://docs.google.com/document/d/1ZFwJJDwwSBNKX35VObClC1ctMbMMuHJtr5qY-7xsLW8/edit?usp=sharing>
from today's call:
Call on 2/2/2021

Attendees:

   -

   Atul Tulshibagwale (Google)
   -

   Asad Ali (Thales)
   -

   Peter Bjork (VMware)
   -

   Annabelle Backman (AWS)
   -

   Hazel (UK Foreign Office)
   -

   Matt Domsch (Sailpoint)

Agenda

   1.

   Increase participation (Hazel)
   2.

   Merge status (Atul)
   3.

   Subject categories (Atul)

Notes:

   -

   UK Foreign Office interested in white papers or guidance on how to
   implement and which building blocks to use, e.g. communicating group
   membership changes
   -

   Tim should communicate with Annabelle on any issues with the comments
   re: Kramdown and build script.
   -

   Subject types are identifier types and not subject types. If a subject
   is identified by email, then it could refer to the person, the mailbox or
   something else. Subject type is not opinionated on that. Similarly iss-sub
   is just a tuple of scope and identifier. There’s nothing that suggests that
   it needs to identify a human end-user. So to solve the problem of
   identifying applications, then iss-sub would be a valid way to do that.
   -

   Since use-cases for disambiguation between app and user (which is not
   apparent in iss-sub)
   -

   Conclusion in previous discussions in the WG has been that the
   subject-identifier should be able to disambiguate in most use-cases, so
   subject category or other disambiguation is not needed.
   -

   On the call we could not make a case for adding subject categories
   because we should attempt to disambiguate the subject principal from the
   claims in the events or based on different event types.





Atul Tulshibagwale

Software Engineer,

Google Workspace

atultulshi at google.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20210202/80c32252/attachment-0001.html>