W

Wendy: TPAC. physical meeting is cancelled. Virtual meeting is in the works.
... looking for feedback in terms of scheduling meetings.

tony: keep the same content. waht we signed up for

wendy: that is an option. some groups working on other methods
... we are looking how we can help facilitate.
... we can keep the day we picked, or change if group wants.
... will have TPAC in Vancouver 2022

tony: we will decide on an elongated meeting or not.
... will also take comments on virtual
... SPWG meeting this morning

jeffH: not a whole lot to relate. language for draft ended up in privacy principles doc

<wseltzer> [TPAC week is 26-30 October, 2020]

jeffH: we should be able to to enterprise attestation things.

tony: also discussed other changes
... so just a short update
... move to open PRs.

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

Akshay: hopefully sort out next week

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

jeffH: it may well be FIDO publishes based on How to FIDO doc. then we can reference from Web Authn spec
... we should fill in the gaps
... and also say for futher details is this How to doc

tony: timing will be key

https://github.com/w3c/webauthn/pull/1330-

tony: still blocked.

elundberg: yes

elundburg: found some things on review. still working

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

tony: still needs some work.

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

agl: suspended this is april because of CTAP issues, those are being resolved.

tony: wd-03?

agl: yes. looking at L2

shane: what is motivating this. what is it for.

agl: google does lot with SSH certs. we are basically trying to build up tech we use internally

shane: makes a lot of sense.

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

agl: i also dislike ECDAA
... I could review

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

bradley: back to #1410, working on this

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

JeffH: I think the short answer is yes.

tony: what is the game plan

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

nickM: no additional updates today

tony: that takes us through open technical items.

NicS: still based on caBLE yes

tony: we are moving this out to caBLE timeframe

nickS: if cable doesn't land in 2.1, this would get moved.

tony: keep it for now

nickM: what are the consequences.

tony: just have to decide caBLE is not going to make it and move it out

nickM: have to look at it every week

nickS: will come with a plan next week.

tony: other issues to talk about .

agl; extension for password managers to get a asymetric key

tony: we have a couple of un-triaged issues

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

scribe: question for google on SafetyNet
... leave it un-triaged.

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

jeffh: that is a process thing.

wendy: I will ask Dom for suggestions

NickS: third communtiy group meeting coming up. trying to focus on two balls UX concerns, also talking about a site for wireframes.
... so people can get started easily
... try to align with How to FIDO... doc
... evnetually

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/jfontana_/jfontana/G
Present: nmooney jfontana selfissued wseltzer jeffh agl akshay davidt davidw elundberg eric jamesbarclay nadalin martin nsteele rae sbeweeden jbarclay
Regrets: jcj_moz
No ScribeNick specified.  Guessing ScribeNick: jfontana
Inferring Scribes: jfontana

WARNING: No "Topic:" lines found.

Agenda: https://lists.w3.org/Archives/Public/public-webauthn/2020May/0069.html

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.)