3.1.   FDX Event

4.1.   Berlin Group (Francis Pouatcha)

Embedded approach.

Chris is sceptical on BG adopting FAPI. However, he believes that it can be shown that the BG model can be implemented with FAPI.

4.2.   UK (Chris)

1. CMA9 on track for certification 1. eIDAS

5.1.   PR 183 Mark pushed request object spec as deprecated

• https://bitbucket.org/openid/fapi/pull-requests/183

Callers agreed on the approach.

5.2.   PR 175 Add security consideration around sharing keys

• https://bitbucket.org/openid/fapi/pull-requests/175

Approved.

5.3.   PR 182 Add non-normative examples of various objects

• https://bitbucket.org/openid/fapi/pull-requests/182

5.4.   PR 186 Add clauses requiring AS to be sure of/show client identity

• https://bitbucket.org/openid/fapi/pull-requests/186

Add it to privacy considerations. Close this PR after verified the privacy consideration text.

5.5.   PR 187 Created a sensible privacy considerations clause for dealing with issue #90

• https://bitbucket.org/openid/fapi/pull-requests/187

Nat proposed multi-steps approach:

1. to examine the structure and discuss on issue #90;
2. if it looks good, then accept the PR;
3. start creating issues to deal with text within each sub-clauses;
4. discuss the text on the issues;
5. create PRs for those issues;