-
Notifications
You must be signed in to change notification settings - Fork 0
FAPI_Meeting_Notes_2024 10 02_Atlantic
Nat Sakimura edited this page Jul 10, 2026
·
1 revision
- Date&Time: 2024-10-02 14:00 UTC
- Location: Zoom
- Roll Call
- Adoption of Agenda
- Events & External Orgs Updates
- PRs
- Issues
- FAPI2 Spec Updates
- AOB
Attendees:
- Dave Tonge (Chair)
- Elizabeth Garber (OIDF)
- Filip Skokan
- Brian Campbell
- Peter Wallach (Mastercard)
- Bjorn Hjelm
- Robert Gallagher (Mastercard)
- Hideki Ikeda
Apologies: Nat, Mike, Les, Joseph
- Mike, Les, and Joseph are currently meeting with the Chilean team for an outreach workshop on open finance.
- Ongoing conversations with FDX and CFPB in the US.
- OIDF published an open letter in May calling on CFPB to include high security and communications protocol in their upcoming rulemaking.
- Positive conversations with CFPB about the potential role of OIDF and FAPI in a US open banking ecosystem.
- FDX has applied to CFPB to be a standard-setting body for data formats.
- OIDF is exploring partnership with FDX and potentially making a direct application to CFPB.
- A subgroup of the OIDF board is looking at different ways to progress this.
- One outstanding PR for separating the HTTP signing part from the message signing spec. Email sent to the mailing list for feedback.
- FAPI 1 errata announcement sent to the mailing list. Review requested (Issue #700).
- FAPI 2 final spec is nearly complete, with final editorial bits being addressed.
Issue #707: Error Codes for HTTP Message Signatures
- New issue raised by Tack suggesting dedicated error codes for HTTP message signatures.
- Discussion concluded that adding OAuth error codes for HTTP message signing is not appropriate, especially within FAPI.
- Brian and Filip pointed out that the layering is incorrect, and such error codes don't belong in FAPI.
- Agreed that guidance on HTTP status codes might be worth discussing, but not as OAuth error codes.
- Dave will capture the discussion in the issue but leave it open for further consideration.
Issue #425: FAPI 2.0 Purpose and FAPI WG Scope
- Nat posted confirmation of previous discussion.
- Agreed to wait for the adoption of new OpenID processes (expected this month) which will clarify the rechartering process.
Dave Tonge provided an update on the progress of the FAPI 2 final specification:
- The specification is nearing completion, with only a few final editorial updates remaining.
- Dave mentioned having a discussion with Mark earlier that day regarding these final editorial changes.
- While specific details of the editorial updates were not provided in the meeting, they are likely focused on ensuring consistency, clarity, and accuracy throughout the document.
- The delay in finalizing the specification was acknowledged, with Dave apologizing for the extended timeline.
- Despite the delay, the update suggests that the publication of the FAPI 2 final specification is imminent.
- Dave and Mark to complete the final editorial revisions.
- Once editorial changes are implemented, the specification will likely go through a final review process.
- After the review, assuming no major issues are found, the FAPI 2 final specification should be ready for publication.
The working group members were not asked for any specific actions related to the FAPI 2 specification at this time, but they should anticipate its release in the near future and be prepared for any potential implementation considerations that may arise from the final version.
- Review FAPI 1 errata (Issue #700) - All members
- Complete final editorial updates for FAPI 2 spec - Dave and Mark
- Address remaining HTTP signature and CIBA issues - Dave (or volunteers)
- No additional items discussed.
The meeting concluded earlier than scheduled due to fewer items to discuss.
Next meeting: TBA