16:56:18 RRSAgent has joined #webauthn 16:56:18 logging to http://www.w3.org/2017/06/21-webauthn-irc 16:56:20 RRSAgent, make logs public 16:56:20 Zakim has joined #webauthn 16:56:22 Zakim, this will be 16:56:22 I don't understand 'this will be', trackbot 16:56:23 Meeting: Web Authentication Working Group Teleconference 16:56:23 Date: 21 June 2017 16:56:30 agenda: https://lists.w3.org/Archives/Public/public-webauthn/2017Jun/0201.html 16:56:58 weiler has joined #webauthn 16:59:31 regrets+ wseltzer 16:59:37 present+ weiler 17:00:18 selfissued has joined #webauthn 17:02:06 jeffh has joined #webauthn 17:02:12 gmandyam has joined #webauthn 17:02:20 present+ gmandyam 17:02:36 apowers has joined #webauthn 17:03:12 present+ selfissued, nadalin, JFontana, apowers 17:03:39 present+ Angelo 17:04:20 present+ ChristiaanBrand 17:06:32 present+ JeffH 17:06:42 scribe: gmandyam 17:06:57 present+ AkshayKumar 17:07:43 Tony - examine open PR's for WD-06 17:08:40 First up - PR 379: https://github.com/w3c/webauthn/pull/379 17:09:30 AngeloKai: Need to merge in master. There are some privacy concerns. Would like to get input from other browser vendors - particularly Moz (JC Jones). 17:09:47 Nadalin - does Google have a similar use case to PR 379 17:10:22 AngeloKai - there is a general problem on how to find authenticators that will work with the user. (in response to Google request for explanation) 17:11:13 denis has joined #webauthn 17:11:30 much of the discussion is in this issue: https://github.com/w3c/webauthn/issues/345 17:11:37 AngeloKai - using this feature (isAuthReady), the RP can decide what user experience they need to provide to the user to direct them to attach authenticators if necessary 17:11:41 weiler has changed the topic to: agenda: https://lists.w3.org/Archives/Public/public-webauthn/2017Jun/0201.html 17:11:48 denis has left #webauthn 17:12:02 ChristaanBrand - understood. No objection at this time. 17:12:27 jeffh - PR is still not ready to merge 17:12:56 ChristiaanBrand - it is a nice-to-have feature, but we won't prioritize implementation 17:15:06 ChristiaanBrand - to clarify - we may not implement feature as RP, but will implement in browser if it becomes part of the standard 17:16:06 AngeloKai - there are precedents in the web platform, e.g. Permissions API 17:16:14 jeffH - why not use Permissions API? 17:17:18 AngeloKai - because Permissions API asks the user for permission to use an API. In this case, you are asking the user to create a credential. 17:20:01 gmandyam: why is not the perms api relevant to platform authenticators (authnrs) ? 17:21:50 christiaan: two things here: (a) whether the user wants to reg with RP (?), and (b) whether user gives RP perms to interact with authnr [not sure i got this correctly..] 17:22:06 ChristaanBrand - the issues of authenticator availability and granting permissions to the API are orthogonal. I don't know if we want a flow where we need an additional permission grant from the user when the user interaction is required for the credential already. 17:22:14 ... do we need two perms models here for these two aspects ? 17:23:50 AngeloKai - a permissions API for e.g. geolocation will allow application access to GPS. The resulting action (return of location) data due to grant of permission is well understood. 17:24:24 AngeloKai - with webauthn, there is more than just grant of the API permission. There is a user gesture required. 17:25:59 s/employes/employed/ 17:26:41 s/(return of location) data/(return of location data) 17:27:17 AngeloKai - will augment intro section to better describe UI flow in PR 17:27:30 AngeloKai - this will also address outstanding TAG issue 17:27:57 jeffh - the rationale of why this is only for platform authenticators needs to be in the spc 17:28:06 s/spc/spec 17:28:56 AngeloKai - Still need a solution for detecting whether device is paired with authenticator 17:29:28 ChristiaanBrand - not sure this applies to cross-platform authenticators. 17:30:19 nadalin - will keep as WD-06 pending Moz input 17:30:42 If still open by WD-06 publish date, can move to CR milestone 17:31:45 nadalin - next PR https://github.com/w3c/webauthn/pull/460. Still needs work. 17:33:44 gmandyam - will close out https://github.com/w3c/webauthn/pull/484 and replace with new PR refining terminology section. 17:34:29 https://github.com/w3c/webauthn/pull/495 and https://github.com/w3c/webauthn/pull/498 need to be reviewed 17:35:54 jeffh - https://github.com/w3c/webauthn/pull/498 is meant to address some algorithm breakage to to 384 merge. (see https://github.com/w3c/webauthn/issues/472#issuecomment-309871552) 17:36:18 jeffh - there look to be broader issues with webauthn algorithms violating the web model 17:36:54 jeffh - reopened Zbarsky's issue that was fixed with PR 371 due to PR 384 breakage 17:37:11 nadalin - is this WD-06 issue? 17:37:20 jeffh - we can delay to CR 17:37:44 selfissued - we should touch base with mwest re: credential spec 17:38:06 nadalin - goal is to make WD-06 as close to CR as possible 17:38:25 jeffh - 60-70 issues are tagged CR 17:40:49 AngeloKai - algorithm fix up would be good. It might be good to reclassify several CR-tagged issues. 17:42:27 nadalin - not detecting major changes in WD-06 versus WD-05 17:42:44 jeffh - a diff between current state and last WD would show significant changes 17:44:17 AngeloKai - TLS-related items should be addressed as well] 17:44:28 s/]/ 17:45:17 jeffH - such issues should not necessarily be addressed in WD-06. Expect more WD's between -06 and CR. And CR does not mean we are done. 17:45:37 AngeloKai - and we have other spec reviews that will come up 17:46:35 jeffH - think there will be a WD-07. 495 and 498 don't necessarily need to be in WD-06 17:46:42 nadalin - will leave at WD-06 for now 17:47:10 Review of issues impacting -06 ... 17:47:44 See https://github.com/w3c/webauthn/milestone/10 17:49:41 jeffH - maybe we don't need to get hung up on milestones.Just rely on ED. 17:49:51 nadalin - nominate AngeloKai as backup editor. 17:50:32 jeffH - update mastheads to designate former editors. 17:54:36 jeffH - request someone to address issues 283 and 292 17:55:05 AngeloKai - will take on assignment 17:55:51 jeffH - intending to propose PR for issue 278 17:57:01 jeffH - need volunteers for unassigned issues 17:58:10 selfissued - will take on issue 488 17:59:44 345 assigned to AngeloKai 18:01:16 nadalin - will have meeting on July 5 18:01:21 Meeting adjourned 18:01:24 rrsagent, draft minutes 18:01:24 I have made the request to generate http://www.w3.org/2017/06/21-webauthn-minutes.html weiler 18:01:35 rrsagent, make log public 18:01:37 rrsagent, draft minutes 18:01:37 I have made the request to generate http://www.w3.org/2017/06/21-webauthn-minutes.html weiler 18:11:48 jfontana has joined #webauthn 18:13:07 chair: nadalin, jfontana 18:13:09 rrsagent, draft minutes 18:13:09 I have made the request to generate http://www.w3.org/2017/06/21-webauthn-minutes.html weiler 19:13:24 Zakim has left #webauthn 19:23:45 weiler has joined #webauthn 19:24:21 weiler_ has joined #webauthn 20:27:36 weiler_ has joined #webauthn 20:28:47 weiler__ has joined #webauthn