tony: PRs.
https://github.com/w3c/webauthn/pull/966
no update
https://github.com/w3c/webauthn/pull/1366
jc_moz: I am working on it.
https://github.com/w3c/webauthn/pull/1375
jc_moz: working on this one also
https://github.com/w3c/webauthn/pull/1392
jc_moz: work to do
https://github.com/w3c/webauthn/pull/1398
tony: waiting for john to review
https://github.com/w3c/webauthn/pull/1408
tony: jeffH and akshay
review
... this is IANA.
akshay: can you explain what appID extension
bradley: it has been here. It is
being added to the. registry
... it has been added to registry, we do not need to
re-register
tony: no untriaged PRs
... issues
https://github.com/w3c/webauthn/issues/1381
nickM: look at the PR. next goal is to share out with this group as we talk to Google.
https://github.com/w3c/webauthn/issues/1406
jeffH: need to update the
text.
... being done in some chrome extensions and openSSH - or they
want to.
https://github.com/w3c/webauthn/issues/1407
tony: any open issues to discuss
akshay: any update on transaction confirmation?
bradley: web payments seems keen to work with us and compromise on something both sides can live with
jeffH: adrian commented on this last week. take a look at that. web payments joint task force, he wrote a proposal. read and comment
akshay: payment request API has
many details.
... need to find out what we want.
jeffH: look at what gets displayed to user
akshay: there is a lot to expose
jeffh: would could comment on that write-up.
bradley: goal, stuff in payments
object is part of web payment API.
... combine web authn in web authn dialog, or into payments
dialog.
... want to avoid two different interactions.
Leddy: transaction confirmation does not have to be payments, could be other transactions.
akshay: discussion will hinge on how many schemes you need
leddy: come back with a number of
templates to look at what you see is what you sign
... paper had some use cases. I will get a more specific
suggestion.
tony: this is a little out of our scope here
jeffH: specifically web pay
tony: this is not our core thing here
bradley: depends how we. do it.
jeffH: could potentially happen under the hood of browsers. that is what Adrian is proposing
nickS: forming a community group
on web authn adoption.
... main focus resources for devs
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: jfontana wseltzer jcj_moz nmooney elundberg nadalin sbweeden akshay bill davidturner martin nina jeffh johnbradley selfissued jeff_hodges brettmcdowell_ No ScribeNick specified. Guessing ScribeNick: jfontana Inferring Scribes: jfontana WARNING: No "Topic:" lines found. WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]