Wiki

Clone wiki

fapi / FAPI_Meeting_Notes_2023-04-06_Pacific

FAPI WG Agenda & Meeting Notes (2023-04-06)

Date & Time: 2023-04-07 00:00 UTC Location: https://zoom.us/j/97456084642?pwd=bTRFVzk4ZmlRK1M3bEprRlN5c3JFZz09

The meeting was called to order at 00:00 UTC.

1.   Roll Call (Anoop)

  • Attendees: Nat, Dima and Anoop
  • Regrets:

Agenda

Link to the comment sheet that OIDF is compiling:
https://docs.google.com/spreadsheets/d/1JHDypzbKg8x2AMfC_z4pzDBk4waVJBp2/edit#gid=571622526

Currently, it includes:

  • Bahrain Open Banking Framework - Bahrain OBF
  • Bank Interfaces for Standardized Payments - BISTRA
  • Consumer Data Standards - CDR
  • Czech Standard for Open Banking - COBS
  • Financial Data Exchange API - FDX
  • Open API Framework for Hong Kong
  • India Stack
  • Japan Open Banking Framework
  • NextGenPSD2
  • Open Banking In Nigeria (draft)
  • API Centre standards
  • Open Banking Brasil
  • PolishAPI
  • STET PSD2 API
  • Singapore Financial Data Exchange - SGFinDex
  • Slovak Banking API Standard
  • SNAP
  • KSA Open Banking Standard
  • Open Banking Platform
  • Swiss NextGen API
  • UK Open Banking Standard

Also, we need to find out what is the best way of crediting individuals and the foundation of the work. Chris will ping Gail and Nat on this.

  • Draft Updates
    • Dave has sent the fixed Implementer's draft documents to Mike J [related to message signing]
    • Dave is creating a submission package now. [ Grants Management ]
  • PR Updates
    • Apart from one PR that we are parking until HTTP signature is settled, there is no standing PR.
    • Request/Response binding fix is waiting for IETF result next week.
  • Issue Updates
    • CIBA
      • Discussed the changes it needs for supporting FAPI2.
      • Whether signing is required or not should be based on whether the base profile requires signing (e.g., FAPI2 Message Signing + CIBA should require it, while FAPI2 Security Profile + CIBA should not.)
      • 5.2.2.6
      • Assigned to Filip.
    • Network Layer Protections restrict use of more recent TLS 1.2 ciphers
      • Moving to TLS 1.3 removes the restrictions on the ciphers.
      • However, the certification suite does not support TLS 1.3.
      • Nat to create an issue on the tracker regarding this.
  • GAIN POC2 is gaining traction
    • ID

2.   Next Call

Next call will be an Pacific Call. Next Pacific call will be in two weeks (04-20-2023 @ 5pm PST) UTC - 04-21-2023 1:00 AM.

Updated