[Openid-specs-authzen] Meeting Notes for Oct 24 2023

[Nat Sakimura]

Thanks.

Please make sure to set the repo up in such a way that issues are copied to
this email list. That's per OIDF policy.

Cheers,

Nat

On Wed, 25 Oct 2023 at 07:38, Allan Foster via Openid-specs-authzen <
openid-specs-authzen at lists.openid.net> wrote:

>
>
> Housekeeping
>
>
> Mike L will freeze the policy charter mail list later today.
>
> The AuthZEN mail list is live and operational
>
> Contribution agreements are being processed as they are received
>
>
> Co-chairs - Alan, Gerry, Andrew, David
>
> - There was some discussion on whether we need that many
>
> - By acclamation, we now have four co-chairs
>
>
> Review OIDF web site content
>
> - Mike asked that we review the web site for any updates or corrections
>
>
> GitHub repo -
>
> - Atul issued a PR to remove the license file. Anyone who submitted
> content up until now myst review and approve the PR. Approvals received
> from Omri,  Alex, and David. Atul will check with Pieter and then he can
> initiate the transfer with Mike.
>
>
> Slack -
>
> Can set up channel, but any IPR related conversation, etc. cannot occur
> here. Only keeps 90 days of content.
>
>
> Regular order:
>
> How to organize ourselves?
>
>
> Allan recounts the four topic areas discussed at IIW and notes are filled
> in for each (subsequently reduced to three):
>
>
> 1) Terminology: need to define the terms we will be using to avoid
> confusion
>
> 1A) Capture use cases: to help refine what is in and out of scope and to
> make sure we are addressing real world requirements.
>
> - Eve will bring a list of known docs to next meeting
>
> - Design patterns could also help drive prototyping and bring reality
>
> - Alex started a draft on deployment patterns, could be starting point for
> a document
>
>
> 2) PEP-PDP
>
> - Preliminary draft contributed by SGNL. Andrew suggests we discuss time
> frame to agree on this as a starting point, and continue the work from
> there.
>
> - Should we start separate calls to dig into details? Not yet
>
> - Voice calls only don’t help advance the work quickly enough. In other
> groups, General agreement that we will use GitHub repo for discussion via
> issues and pull requests.
>
>
> 3) Policy administration
>
> - There are a couple presentations from IIW, like ALFA press by David and
> Policy experiences by Phil/Gerry that can be added to repo
>
> - Need to scope this work clearly, could be future looking and not support
> current options
>
> - Still don’t intend  to create another runtime policy language
>
> - This thread should tie into work on use cases, so that we are clear on
> intentions
>
> - We will set up the workstream but it will likely follow on to the other
> streams
>
>
> Open discussion:
>
> Is there a way to advertise to other groups at OIDF?
>
> - co chairs can reach out to Mike L for introductions
>
> - You can join slack channels for the other WGs
>
> - You can join other groups and spread word directly
>
> - OIDF holds workshop every 6 months for all WGs
>
> - Next workshop is Jan 18 in Japan
>
> - One day session ahed of each IIW
>
> - One day workshop before EIC
>
> - Meeting room is available at Identiverse if this group wants to hold a
> working session
>
>
> Other events:
>
> - OIDF coordinated a session with CISA for next  Monday to share info on
> SSF and AuthZEN
>
> - David and Gerry submitted talk for RSA 2024
>
> - Allan will pursue panel sessions at EIC and Identiverse
>
> --
> Sent from Canary <https://canarymail.io>
>
> --
> Openid-specs-authzen mailing list
> Openid-specs-authzen at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-authzen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-authzen/attachments/20231025/e18b447c/attachment-0001.html>