<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Arial">Attending<br>
<br>
Paul M, John B, Brian C, Darren P, Mike G., Thomas D, Mike V, Nat
S., Tony N., <br>
<br>
John B reported that the docs have been split, reflecting decision
into <br>
<br>
1) core spec<br>
2) native API bindings <br>
<br>
Two docs will evolve separately<br>
<br>
John reports that there is still some cleaning up to do after the
split<br>
<br>
John asks for feedback on naming of docs<br>
<br>
i) OIDC Native Applications Token Agent Core<br>
</font><font face="Arial"><font face="Arial">ii) OIDC Native
Applications </font>Token Agent Native API Bindings<br>
<br>
John asks for review of spec, Use issue tracker on BitBucket<br>
<br>
Tom D suggests that we should normalize 'trusted agent' &
'token agent' terminology.<br>
<br>
Tom D interested in contributing to bindings spec. <br>
<br>
John notes that bindings spec is thin. <br>
<br>
John will send invite to Tom to allow him to contribute to
bindings spec via BitBucket <br>
<br>
2) On issue of how TA obtains access tokens, John will send note
to list summarizing options with their pros/cons<br>
<br>
Mike V asks if anybody has been able to review A2P3 spec? Mike
points out similarities between NAPPS & A2P3, albeit latter
may have more privacy focus. Any chance on harmonization.<br>
<br>
Mike's thought is that in A2P3 there is a separation between
authentication & token issuance - with privacy advantages. <br>
<br>
John points out that there is nothing in current NAPPS that
stipulates that authentication need be performed by the AZ.<br>
<br>
Mike V will provide summary of A2P3, comparison to NAPPS, and
potential convergence path. <br>
<br>
Darren argues that this feels similar to relationship between SAML
& Shib. <br>
<br>
Tony points out we need be careful of IPR taint. <br>
<br>
Next call January 24 at 6pm EST<br>
<br>
Close<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</font>
</body>
</html>