Dear all, This is a followup on the actions we agreed upon during the November interim meeting in November (notes in https://datatracker.ietf.org/meeting/interim-2020-oauth-12/materials/minutes-interim-2020-oauth-12-202011021200-00). Apologies for the delay. The TL;DR is that we decided it might be useful to put together a document that describes the identity scenarios relying on current browser features and that we’d like to preserve. Such document should help grounding discussions with browser vendors by making it easy to pinpoint how specific changes might impair functionality in important scenarios, and what functionality we are trying to preserve (in case the new browser feature can offer alternate path to the same outcomes).
Tackling on all the possible scenarios is too big a task for George and myself alone, hence we devised a proposed mechanism to generate and maintain that list collaboratively. You can find a framing proposal in https://datatracker.ietf.org/doc/html/draft-bertocci-identity-in-browser-00, and the github repo workspace https://github.com/IDBrowserUseCases/docs. Thanks to Daniel and Torsten for their help on figuring out how to use mmark to write internet drafts. We do have a list of candidate scenarios, but before going too deep in it we wanted to give the group the chance to take a look at the model and get your feedback before we charge down that path. This is a pretty unusual collaboration model and getting it to work might be tricky. Please let us know what you think! Cheers G&V
_______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
