<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Spec Call Notes 15-Aug-19<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Torsten Lodderstedt<o:p></o:p></p>
<p class="MsoNormal">Nat Sakimura<o:p></o:p></p>
<p class="MsoNormal">Mike Jones<o:p></o:p></p>
<p class="MsoNormal">Brian Campbell<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">OpenID Connect for Identity Proofing<o:p></o:p></p>
<p class="MsoNormal"> Feedback on Identity Proofing draft from OIDF Japan<o:p></o:p></p>
<p class="MsoNormal"> Sent by Naohiro Fujie<o:p></o:p></p>
<p class="MsoNormal"> There was substantial feedback on syntax and location of elements<o:p></o:p></p>
<p class="MsoNormal"> Torsten is filing issues based on the feedback<o:p></o:p></p>
<p class="MsoNormal"> Mike requested that the feedback be sent to the working group list<o:p></o:p></p>
<p class="MsoNormal"> Feedback from US mobile carriers<o:p></o:p></p>
<p class="MsoNormal"> Sent by Michael Engan<o:p></o:p></p>
<p class="MsoNormal"> On relationship between claims and evidence<o:p></o:p></p>
<p class="MsoNormal"> Mike requested that the feedback be sent to the working group list<o:p></o:p></p>
<p class="MsoNormal"> Tony Nadalin wrote that we should align with ISO 29003<o:p></o:p></p>
<p class="MsoNormal"> Issue #1100 - Analyse ISO 29003<o:p></o:p></p>
<p class="MsoNormal"> Torsten isn't sure what concrete actions should be taken<o:p></o:p></p>
<p class="MsoNormal"> We should have Tony make specific actionable suggestions<o:p></o:p></p>
<p class="MsoNormal"> EU minimal viable KYC document<o:p></o:p></p>
<p class="MsoNormal"> PRIORITY GROUP 2 PROPOSAL FOR AN ATTRIBUTE-BASED & LoA-RATED KYC FRAMEWORK FOR THE FINANCIAL SECTOR IN THE DIGITAL AGE<o:p></o:p></p>
<p class="MsoNormal"> Torsten started to read it<o:p></o:p></p>
<p class="MsoNormal"> Torsten plans to file some tickets<o:p></o:p></p>
<p class="MsoNormal"> Nat suggested a conference call with the contact people Stephane Mouy and Eric Wagner<o:p></o:p></p>
<p class="MsoNormal"> Torsten plans to publish another version today<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">OAuth JAR and IANA Registrations<o:p></o:p></p>
<p class="MsoNormal"> Ben Kaduk provided feedback on OAuth JAR on collisions between JWT claim names and OAuth request parameter names<o:p></o:p></p>
<p class="MsoNormal">" Brian suggested that rather than linking registries or creating complex rules for IANA to follow that the likely collisions be registered<o:p></o:p></p>
<p class="MsoNormal"> Mike agreed that the registries should not be linked, as there are many JWT claims that will never be OAuth request parameters<o:p></o:p></p>
<p class="MsoNormal"> We can prevent likely collisions by registering claims like "aud", "sub", "iss", "cnf", "jti", etc. as OAuth request parameters<o:p></o:p></p>
<p class="MsoNormal"> Also "exp", "iat", "nbf" - probably everything in RFC 7519 plus "cnf"<o:p></o:p></p>
<p class="MsoNormal"> We should not need to register OAuth request parameters as JWT claims<o:p></o:p></p>
<p class="MsoNormal"> The only time that conflicts matter is when a JWT claim is being used as an OAuth request parameter<o:p></o:p></p>
<p class="MsoNormal"> Nat stated that the context is clear when the JWT is used as an OAuth request<o:p></o:p></p>
<p class="MsoNormal"> Brian stated that OAuth JAR should register the values as OAuth request parameters and explain why they are registered<o:p></o:p></p>
<p class="MsoNormal"> Mike agrees<o:p></o:p></p>
<p class="MsoNormal"> JAR should reserve the names to prevent them being used as OAuth request parameters<o:p></o:p></p>
<p class="MsoNormal"> Nat will do this - Mike offered to review the result<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Login with Apple<o:p></o:p></p>
<p class="MsoNormal"> Apple appears to be fixing some things one-by-one<o:p></o:p></p>
<p class="MsoNormal"> For instance, they have added "nonce"<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Open Issues<o:p></o:p></p>
<p class="MsoNormal"> https://bitbucket.org/openid/connect/issues?status=new&status=open<o:p></o:p></p>
<p class="MsoNormal"> #1099 - Use ICAO codes for nationality and issuer country?<o:p></o:p></p>
<p class="MsoNormal"> These include codes for refugees and international organizations<o:p></o:p></p>
<p class="MsoNormal"> But they are three-letter codes<o:p></o:p></p>
<p class="MsoNormal"> Mike suggested allowing 3-letter ICAO codes when there is no corresponding ISO 2-letter code<o:p></o:p></p>
<p class="MsoNormal"> #973 - Core 2 / 3.1.3.7 - azp claim underspecified and overreaching<o:p></o:p></p>
<p class="MsoNormal"> See William Denniss' message "Resolving the `azp` inconsistency" on the next call<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Next Call<o:p></o:p></p>
<p class="MsoNormal"> The next call is Monday, August 19 at 4pm Pacific Time<o:p></o:p></p>
</div>
</body>
</html>