3.1.   FS-ISAC (Anoop)

• They are aligned. We should see a new version of their document at the end of this month.

3.2.   OFX (Anoop)

• No particular security profile there. They consume any token.
• Not much take up.

3.3.   TC68 (Nat)

• There is a call tonight Japan time (tomorrow in UK and US).

4.1.   Streamlining the OBUK Implementer's Draft (Pam)

A new repository https://bitbucket.org/openid/obuk/ was set up. This repository is to work on the Open Banking profile of FAPI (and Modrna, etc.). The current repository that Open Banking is using has no issue tracked + version controlled repository, which is making it difficult to track the changes as well as find out the diffs.

The strategy here is to convert their current spec (called Implementer's Draft) in the markdown format without introducing any changes and commit it to the new repo, then start working on it.

Pam has already converted their Dynamic client registration into Markdown and will commit it to the repo.

We expect a lot of activities over the course of the week.

4.2.   Issues

• #102 -- Nat shared the current idea around keeping x-fapi- in the header. Sascha commented that since the implementations are new, we may as well change it now. Pam took an action item to check back with OpenBanking people.

6.1.   Testing

The new team (fintech labs) is still evaluating the feasibility.

6.2.   Next Call (Atlantic)

• The meeting was adjourned at 23:35 UTC.