Wiki
Clone wikifapi / FAPI_Meeting_Notes_2024-06-27_Pacific
FAPI WG Agenda & Meeting Notes (2024-06-27)
Date & Time: 2024-06-27 00:00 UTC Location: https://zoom.us/j/97456084642?pwd=bTRFVzk4ZmlRK1M3bEprRlN5c3JFZz09
Agenda
The meeting was called to order at 00:00 UTC.
1. Roll Call (Anoop)
- Attendees: Mark, Nat, Dima, Ed, Victor and Anoop
- Regrets:
2. Events Update
2.1. OIDF Workshop Fall
- OIDF workshop in the Mountain View area on Monday, October 28th prior to IIW. Location yet to be determined.
3. Liaison/Ext Org
3.1. US
- Gail met with CFPB and CFPB is welcoming pre-filing meetings with a potential standard setting organization.
Gail is working to setup meeting and coordinating follow-up with Linda Jeng
3.2. Canada
Joseph, Gail, and Mike has call with Open Banking Canada team ad director of financial services innovation team.
They have read OIDF’s CFPB letter and have requested a similar letter providing guidance, which OIDF has agreed to draft along with recommendations, rationale, and risks.
Will review draft in 2 weeks and publish publicly after edits.
3.3. Chile
Team addressed open question from CMF and CMF has inquired about FAPI2 timeline
4. FAPI 2.0 Timeline Discussion
Working group last call has started
Some issues, mainly editorial and clarifications have been found
We are still hopeful that we can close all the issues and move on during the summer (northern hemisphere).
2-6 weeks ETA fo finish open FAPI 2 issues before review and voting
5. Issues & PRs
5.2. Issue # 700
https://bitbucket.org/openid/fapi/issues/700/remove-the-list-of-four-ciphers-for-tls-12 * Ed will update as Errata and will send PR for review. * Errata timeline is 45 days
5.3. Issue 689
https://bitbucket.org/openid/fapi/issues/689/fapi-fedcm * Dima is working on this and will get insight. * This will be addressed at a later stage after FAPI2 release.
5.4. Issue # 694 / PR# 505
https://bitbucket.org/openid/fapi/branch/issue-694
RT rotation alternative wording (https://bitbucket.org/openid/fapi/pull-requests/505)
Possible votes:
Shall support refresh token rotation Should support refresh token rotation Shall WG describe how refresh token rotation works Shall implementation specify how rotation works Should not support refresh token rotation for reasons including interoperability, but if supported, it is up to the ecosystems/implementations to specify how
Add options to the issue for further discussion
- Mark will add comments to issue 694.
7. Next Call
Next call will be an Pacific Call. Next Pacific call will be in two weeks (07-11-2024 @ 5pm PST) UTC - 07-12-2024 1:00 AM.
Updated