<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div dir="ltr"></div>
<div dir="ltr">Hi all!</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">I see that two of the last three issues were resolved during FAPI call today! Great!</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Now only this one has not been merged. Sorry I missed the call, but is this one able to be closed via the list this week? Or do we need to wait for further discussion next week? It looks like we are very close to last WG call!</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Gail </div>
<div dir="ltr"><br>
</div>
<div dir="ltr">
<div class="gmail_default" style="-webkit-text-size-adjust: auto; font-family: "trebuchet ms", sans-serif;">
<b>Normative:</b></div>
<div class="gmail_default" style="-webkit-text-size-adjust: auto; font-family: "trebuchet ms", sans-serif;">
1. grant type restrictions, <a href="https://bitbucket.org/openid/fapi/issues/577/fapi2sp-appears-to-permit-response_types">issue</a> and <a href="https://bitbucket.org/openid/fapi/pull-requests/442">PR</a></div>
</div>
<div dir="ltr"><br>
<blockquote type="cite">On Dec 13, 2023, at 2:28 AM, Dave Tonge <dave.tonge@momentumft.co.uk> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif">Dear FAPI WG</div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif">We are keen to move the FAPI 2.0 Security Profile and Attacker model to final. There are a few remaining issues that it would be good to resolve before we move to working group last call:</div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><b>Normative:</b></div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif">1. grant type restrictions,
<a href="https://bitbucket.org/openid/fapi/issues/577/fapi2sp-appears-to-permit-response_types">
issue</a> and <a href="https://bitbucket.org/openid/fapi/pull-requests/442">PR</a></div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif">2. clock skew,
<a href="https://bitbucket.org/openid/fapi/issues/603/require-servers-to-allow-for-clock-skew">
issue</a> and <a href="https://bitbucket.org/openid/fapi/pull-requests/440">PR</a></div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><b>Editorial:</b></div>
<div class="gmail_default" style=""><font face="trebuchet ms, sans-serif" style="">1.
</font>consistency of "shall only", <a href="https://bitbucket.org/openid/fapi/issues/631/shall-vs-shall-only">
issue</a> and <a href="https://bitbucket.org/openid/fapi/pull-requests/453">PR</a></div>
<div class="gmail_default" style=""><br>
</div>
<div class="gmail_default" style="">Unfortunately I can't make the call today, but hopefully the above issues can be resolved and merged in order for us to move forward with the next stage.</div>
<div class="gmail_default" style=""><br>
</div>
<div class="gmail_default" style="">In addition, for FAPI 2.0 Message Signing we are keen to gather any information about implementations, especially for HTTP Message Signing: <a href="https://bitbucket.org/openid/fapi/issues/633/implementations-of-fapi2-message-signing">https://bitbucket.org/openid/fapi/issues/633/implementations-of-fapi2-message-signing</a></div>
<div class="gmail_default" style=""><br>
</div>
<div class="gmail_default" style=""><br>
</div>
<div class="gmail_default" style="">Thanks</div>
<div class="gmail_default" style=""><br>
</div>
<div class="gmail_default" style="">Dave</div>
<div class="gmail_default" style="">FAPI WG Co-Chair</div>
<div class="gmail_default" style=""><br>
</div>
</div>
<br>
<p dir="ltr"><font size="1">Moneyhub Enterprise is a trading style of Moneyhub Financial Technology Limited which is authorised and regulated by the Financial Conduct Authority ("FCA"). Moneyhub Financial Technology is entered on the Financial Services Register
(FRN 809360) at <a href="https://register.fca.org.uk/" target="_blank">https://register.fca.org.uk/</a>. Moneyhub Financial Technology is registered in England & Wales, company registration number 06909772. Registered address: C/O Roxburgh Milkins Limited
Merchants House North, Wapping Road, Bristol, United Kingdom, BS1 4RW, United Kingdom. Moneyhub Financial Technology Limited 2022 © Moneyhub Enterprise.</font><br>
</p>
<p dir="ltr" style="font-weight:bold"><span style="color:rgb(128,128,128);font-family:Arial;font-weight:400"><font size="1">DISCLAIMER: This email (including any attachments) is subject to copyright, and the information in it is confidential. Use of this email
or of any information in it other than by the addressee is unauthorised and unlawful. Whilst reasonable efforts are made to ensure that any attachments are virus-free, it is the recipient's sole responsibility to scan all attachments for viruses. All calls
and emails to and from this company may be monitored and recorded for legitimate purposes relating to this company's business. Any opinions expressed in this email (or in any attachments) are those of the author and do not necessarily represent the opinions
of Moneyhub Financial Technology Limited or of any other group company.</font></span></p>
<br>
</div>
</blockquote>
</body>
</html>