4.1.   API Days (Nat)

• http://www.apidays.io/

• There are two tracks that are of interest to us.

  • The STATE OF API SECURITY : OAUTH, JSON WEB TOKENS, OPEN ID Connect, UMA;
  • BANKING APIS and PSD2 (Payment Service Delivery)

• Sascha is trying to get in touch with the CA guy.
• Dave has introduced Don to one of the organizer. Don said he may be available for the meeting.
• We should submit the proposal through their web site.

Action:

* Nat to draft the proposals.
* Copy Don on them.

4.2.   UK Implementation Entity (Dave)

• Dave has joined the Data work stream. Their scope is very wide. They are currently a closed group but Dave will give the FAPI WG information as soon as it becomes available.
• Dave also is requesting to join the security WG. He expects to join them either directly through their invitation or through FDATA. It would be really good if we can coordinate our draft with them.

4.3.   Figo (Anton)

• Anton contacted them by email and presented WG. They are interested in our work to see how we can align.
• Anton has provided answers to their question and waiting for the feedback.

4.4.   Apigee (Nat)

• Dave made an introduction to Nat over email and they have contacted us back.
• They are willing to work with us. The contact person, Saravanakumar Rajagopal, will introduce their chief architect, Greg Brail, to us shortly.

4.5.   EBA (Dave)

• EBA comments were published at: https://www.eba.europa.eu/regulation-and-policy/payment-services-and-electronic-money/regulatory-technical-standards-on-strong-customer-authentication-and-secure-communication-under-psd2
• Dave got a comment on it that s/he was pleased see our comment.

5.1.   Restructuring (Nat)

• Restructured document is available at: the repo as

  • Financial_API_WD_001.md Financial API - Part 1: Read Only API Security Profile
  • Financial_API_WD_002.md Financial API - Part 2: Read and Write API Security Profile
  • Financial_API_WD_003.md Financial API - Part 3: Open Data API
  • Financial_API_WD_004.md Financial API - Part 4: Protected Data API and Schema - Read only
  • Financial_API_WD_005.md Financial API - Part 5: Protected Data API and Schema - Read and Write

• Part 1 is the most complete one and we need the close review by the WG.
• Once that is ready, then we can move the Part 1 towards the Implementors draft vote.
• For implementor's vote, we need to have 45 days review period, which can be concurrent with the announcement of the vote.
• NOTE: For the final vote, we need two or more interoperable implementations to support the spec.

Dave asked about the appearance of "DDA" as it may be confusing. Since Anoop agreed to remove those references, we are going to remove it per #34.

7.1.   Pre-IETF (Nat/John)

• Karen will give us answer on the room allocation today but it is probably too late for organizing a workshop.
• We could still have a meeting there though.

8.1.   Change of Atlantic Call timing

• The WG decided to move the call time one hour later (from UTC perspective) to match the end of the end of the daylight saving time in Europe and the US.

  • Next Atlantic call will be 2016-11-23 15:00 UTC.

8.2.   Next Call (Pacific)

• 2016-11-16 23:00 UTC

  (15:00 PDT, 23:00 UK, 00:00+1 Denmark, 08:00+1 JST)