<html><head></head><body><div class="ydp95126260yahoo-style-wrap" style="font-size: 13px;"><div id="ydp95126260yiv1443181295"><div><div class="ydp95126260yiv1443181295ydpf6244ee3yahoo-style-wrap" style="font-size: 13px;" dir="ltr"><div id="ydp95126260yiv1443181295ydpf6244ee3yiv3978159904"><div><div class="ydp95126260yiv1443181295ydpf6244ee3yiv3978159904ydpb5033976yahoo-style-wrap" style="font-size: 13px;"><div dir="ltr"><div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">OpenID AB/Connect Call Note (2019-07-18)<br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">Date: 2019-07-18 15:00 UTC<br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">Location: GoToMeeting <a href="https://www3.gotomeeting.com/join/695548174" style="color:rgb(25, 106, 212);text-decoration-line:underline;" rel="nofollow" target="_blank">https://www3.gotomeeting.com/join/695548174</a><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">[Agenda]<br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">1. Roll Call<br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">2. Adoption of the agenda<br></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">3. Issues<br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">4. AOB<br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">[ Roll Call ]<br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">Present: Nat, Daniel, George, Bjorn<br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">Regret:<br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">[Adoption of the agenda]<br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">Identity Assurance issues<br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">[Issues]<br></font></div><div><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">#1069 : <span>Identity Assurance Section 5.1 on reason for request, <br></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span>Due to lack of people, will require further discussion<br></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><br></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><br></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span>#1077 : <span>Identity Assurance - Need Input from other Jurisdictions</span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Have a lot of feedback from different groups</span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Still open because lacking input from one specific Japanese group, not sure which one<br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Left open as Reminder, OIDF-J should provide some comments <br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>1078: <span>Identity Assurance - Incorporate EU/EC KYC Token work</span><br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Nat introduced Torsten to chair of group<br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>1088 : <span>register new claims in OAuth Token Introspection Response Registry</span><br></span></span></font></div><div><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif">Add IANA registration section <br></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><span>Send the ratified spec to IANA for registration.</span><br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>1092 : <span>Support multiple nationalities?</span><br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Not sure if needed, identity documents usually don't have 2 nationalities but people get asked these questions at border crossings<br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>How to obtain proof? Recorded when documents are presented for verification. <br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Use array to support this?</span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Whats the purpose of the question? To establish there are multiple nationalities or yes/no question or do additional identity assurance based on response?<br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>The purpose is to be able to respond with multiple nationalities.<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>The spec's purpose is to perform identity assurance with nationality as an attribute, dual nationality is just another attribute. <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Is there proof associated. As for KYC, need to produce documents for verification and is recorded in claim.<br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Main question is do we want array to express multiple nationalities?<br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>If this is in response to a transaction where user could choose nationality for the transaction.</span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>If purpose is to produce identity information to an RP where RP needs to know user has proven via passport that they have dual citizen , then needs array. <br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>If goal is just to show identity proofed data that was chosen for a given transaction, then don't need array.<br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>If there's only one then could be claim, but could also be array to allow future proofing.<br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>1093 : <span>Extensibility: how do we support extensibility for trust frameworks, evidence types, verification methods and id documents?</span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>How do we setup IANA registry? <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Registry can only be created by RFCs, but values can be added to it.<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Do we want to create RFC for it? <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>What is the expectation on frameworks? Just going to be arbitratry? Just a string?<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>What level are we aiming for? <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>This essentially identifies frameworks and their descriptions.<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>If RP is participating and IDP's framework is proven, do we need this registry at all?<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>If IDP publishes metadata for trust frameworks as string and there is no binding to the framework does it matter to have a registry a string?<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Could have a simple doc if just trying to keep list of strings and descriptions.<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Need more description of issue. <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Depends on how we want to use it.</span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>1094 : <span>How to treat unknown identifiers in claims parameter</span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>If claim is essential and IDP does not understand, then should return error. <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>But description does not mention anything regarding essential claims.</span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Spec says no error is returned even if claim is essential. <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Does not explicitly mention IdP not recognizing claim. <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Up to RP to obtain claim if not returned<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Is must understand what we want in this context?<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Default today is to ignore, and RP is responsible for figuring out and dealing with response.</span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><span><span><span>Do we need a must understand flag to be added? </span></span></span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><span>Try to find Must Understand in JWx.</span></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><span><br></span></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><span>1097: <span>Include Legal Persons</span></span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Might want to liaise with UMA since they've done a lot of work around legal persons.<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>George/Bjorn should raise question to UMA</span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Legal person issue is important and has more cost impact for financial institutions but also very difficult, <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Not sure if we want to tackle this before implementer's draft<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Need to liaise with ISO TC68 also. <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Marked for post implementer's draft<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>1098: <span>Add verification_score</span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Need more explanation of verification score : what is attached and what does it mean?<br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>1099: <span>Use ICAO codes for nationality and issuer country?</span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Needs more expertise input <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>It's minor change so will accept if not objections, Daniel to create pull request<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>1100 ; <span>Analyse ISO 29003</span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Reminder to look into ISO doc <br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Next steps before implementer's draft:</span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>a) apply all agreed changes or decide to defer particular issues<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>b) after WG consensus, propose the foundation to start public review period<br></span></span></font></div><div><br></div><div><br></div><div dir="ltr" data-setdir="false"><font size="2"><font face="Helvetica Neue, Helvetica, Arial, sans-serif">[AOB]</font></font><br></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>George waiting for Mike to post native SSO spec<br></span></span></font></div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><div><div dir="ltr" data-setdir="false"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>Latest draft already merged in repository<br></span></span></font></div><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span></span></span></font></div></span></font><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span>George to create issue for it</span></span></font><br><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span><br></span></span></font></div><div dir="ltr"><font size="2" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span><span></span><br></span></font></div></div></div></div></div></div></div></div></div></body></html>