Test

903

https://github.com/w3c/webauthn/pull/903

jcj_moz

scribe: I have no lissues with iit.

https://github.com/w3c/webauthn/pull/906

agl: stems from discsuon christian wants to have a the F2F meeting
... I will address this after F2F and we get a decision

tony: sounds goodl

https://github.com/w3c/webauthn/pull/909

tony: do we have representation

Arnar:

tony: we will leave this is triage

https://github.com/w3c/webauthn/pull/910

kpaulH: I realized we don't need strsp for this is only for registration that implies type of client

tony: tying ot 909

kpaulH: kind of. yes.
... this is web authn extension.

tony: self issue is a reviewer

agl: is this standalone

kpaulh: standalone

toney: we should reference from 910 to 909. 909 can be standalone

910 is about registration extension

tony: taht takes us through the un-triaged PRs
... untriaged issues.

tony https://github.com/w3c/webauthn/issues/905

tony: leaving 905 un-triaged

discuss 906 at the meeting

https://github.com/w3c/webauthn/issues/907

tony: Kim you are saying what chrome does today

kpaulH: yes.
... not convinced it needs to be in the spec.

agl: changing Chrome here is fine idf we intended to go this way

jcj_moz: FFox leaves it blank. I think that makes sense.

elundberg: so how many values.

agl: four states.
... but 4 things. ...
... want to get to 3 and 3

elundberg: we lose the numeratino thing

agl: yes
... I can do a PR for this and we could always throw it out.

tony: adding jc and akshay

https://github.com/w3c/webauthn/issues/912

tony: not sure this has been looked at
... seems to have a big impact though
... this is big change.

elundberg: I think for specific extension, adsking for not just geo-location. I think it is beyond the scope
... ther are other apis that do the same thing
... implementing at the client, i don't know

tony: I see go location as the example. he was asking for ageneric change here

arnar: this processes on the client..

elundberg: I agree.

selfissue: I put in comment makes no sense to have client implement authenticator extension.
... close this until we get more explanation on the use case

arnar: one resolution here is to calll out a specific spec.....

jeffH: I agree

comment being added to issue

tony: that takes us through un-triage issue for PR

PR-Proposed Recommendation

selfissue: qusiton on 913
... am I right it does not update the CTAP reference.

elungberg: that is my oversight.
... I will update.

ony: anymore issues to talk about.

tony

jeffH: ... real quick on issue 911. I stuck a proposed milestone on it, but don't need to do it now. not clear it will be in our spec

tony: I put it on so we can talk about it next week.
... so some pull requests that are ready to go.
... no W3C meeting next week. we resume after the FIDO meeting

<jcj_moz> scribenick: jfontana

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
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: jcj_moz elundberg dmitriz selfissued apowers jeffh
Found ScribeNick: jfontana
WARNING: No scribe lines found matching ScribeNick pattern: <jfontana> ...
Inferring Scribes: jfontana

WARNING: No "Topic:" lines found.

Agenda: https://lists.w3.org/Archives/Public/public-webauthn/2018May/0322.html
Found Date: 16 May 2018
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.)