<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Yes, it should be Baseline.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">-Daniel<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Am 20.02.20 um 14:19 schrieb
n-sakimura:<br>
</div>
<blockquote type="cite"
cite="mid:AD1E7003-B824-47F5-9883-814A7B405C6C@cu.nri.co.jp">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Thanks. That sounds good, though the name that was talked about in
the room in the F2F London was “Baseline” instead of “Basic”.
<div><br>
</div>
<div>Best, </div>
<div><br>
</div>
<div>Nat<br>
<br>
<div dir="ltr">
<div><span style="background-color: rgba(255, 255, 255, 0);">PLEASE
READ:This e-mail is confidential and intended for</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">the
named recipient only. If you are not an intended
recipient,<br>
please notify the sender and delete this e-mail.</span></div>
</div>
<div dir="ltr"><br>
<blockquote type="cite">2020/02/19 15:59、Daniel Fett via
Openid-specs-fapi
<a class="moz-txt-link-rfc2396E" href="mailto:openid-specs-fapi@lists.openid.net"><openid-specs-fapi@lists.openid.net></a>のメール:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="moz-cite-prefix">+1</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">FWIW, I'm currently preparing a
first draft for 2.0. I currently expect 2.0 to consist of
separate documents for the attacker model, the two
profiles, grant management and potentially CIBA.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">-Daniel<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Am 19.02.20 um 16:34 schrieb
Dave Tonge via Openid-specs-fapi:<br>
</div>
<blockquote type="cite"
cite="mid:CAP-T6TQQZ3_jyEKSL6Mpt-6rwO4UF_nuQ0i2+qAg2a2_gAwZyg@mail.gmail.com">
<div dir="ltr">
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">
Dear WG<br clear="all">
</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 had a good discussion on the call today around the
next steps for FAPI and came to the
following conclusion:</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">
1. We should use versioning to indicate that the FAPI
evolution is a new major version</div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">
2. We need to keep support for the current FAPI-R and
FAPI-RW for some time as they have been implemented by
many people and have a good suite of conformance
tests.</div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">
3. There were no objections to the names of "Basic"
and "Advanced"</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">
With this in mind we propose:</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">
1. The current "Financial-grade API - Part 1:
Read-Only API Security Profile" (FAPI Read) spec
should be changed to "<span
style="font-family:Arial,Helvetica,sans-serif">Financial-grade
API 1.0 - Part 1: Read-Only API Security Profile
(FAPI 1.0 Read)</span></div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">
2. The current "Financial-grade API - Part 2: Read and
Write API Security Profile" (FAPI Read/Write) spec
should be changed to "<span
style="font-family:Arial,Helvetica,sans-serif">Financial-grade
API 1.0 - Part 2: Read and Write API Security
Profile (FAPI 1.0 Read/Write)</span><span
style="font-family:Arial,Helvetica,sans-serif"><br>
</span></div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">
<span style="font-family:Arial,Helvetica,sans-serif">3.
We introduce two new documents:</span></div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">
<span style="font-family:Arial,Helvetica,sans-serif"> - </span><span
style="font-family:Arial,Helvetica,sans-serif">Financial-grade
API 2.0 - Basic Security Profile" (FAPI 2.0 Basic)</span></div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">
<span style="font-family:Arial,Helvetica,sans-serif"> - </span><span
style="font-family:Arial,Helvetica,sans-serif">Financial-grade
API 2.0 - Advanced Security Profile" (FAPI 2.0
Advanced)</span><span
style="font-family:Arial,Helvetica,sans-serif"><br>
</span></div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">
<span style="font-family:Arial,Helvetica,sans-serif"><br>
</span></div>
<div class="gmail_default" style="">This will allow us
to maintain the existing specs (and their associated
conformance suites). It will also allow the evolution
of FAPI that we've been discussing to move ahead -
including with new names to signal use-cases beyond
financial read and financial read/write. The new
documents (2.0 Basic and 2.0 Advanced) can be
re-ordered and won't need to maintain backwards
compatibility to the numbering of sections and list
items.</div>
<div class="gmail_default" style=""><br>
</div>
<div class="gmail_default" style="">It would be good to
get feedback from the WG about this proposal as we are
keen to move forward.</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=""><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div
style="font-size:1em;font-weight:bold;line-height:1.4">
<div
style="color:rgb(97,97,97);font-family:"Open
Sans";font-size:14px;font-weight:normal;line-height:21px">
<div
style="font-family:Arial,Helvetica,sans-serif;font-size:0.925em;line-height:1.4;color:rgb(220,41,30);font-weight:bold">
<div
style="font-size:14px;font-weight:normal;color:rgb(51,51,51);font-family:lato,"opensans",arial,sans-serif;line-height:normal">
<div
style="color:rgb(0,164,183);font-weight:bold;font-size:1em;line-height:1.4">
<div
style="font-weight:400;color:rgb(51,51,51);line-height:normal">
<div
style="color:rgb(0,164,183);font-weight:bold;font-size:1em;line-height:1.4">Dave
Tonge</div>
<div
style="font-size:0.8125em;line-height:1.4">
<div class="gmail_default"
style="font-family:"trebuchet
ms",sans-serif">
FAPI Co-Chair</div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Openid-specs-fapi mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-fapi@lists.openid.net" moz-do-not-send="true">Openid-specs-fapi@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-fapi" moz-do-not-send="true">http://lists.openid.net/mailman/listinfo/openid-specs-fapi</a>
</pre>
</blockquote>
<p><br>
</p>
<span>_______________________________________________</span><br>
<span>Openid-specs-fapi mailing list</span><br>
<span><a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-fapi@lists.openid.net">Openid-specs-fapi@lists.openid.net</a></span><br>
<span><a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-fapi">http://lists.openid.net/mailman/listinfo/openid-specs-fapi</a></span><br>
</div>
</blockquote>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>