thanks JC?

<jcj_moz> this conference is WebAuthn call, 3 Oct 2019

<elundberg> present

<jcj_moz> trackbot, start meeting

tony: first thing on agenda is call yesterday on extensions
... sam, ralph, philippe, tony, johnF, giri
... issue want to make extentions optional but normative
... comes down to one thing, extensions, not all have shown interop. the framework has. AppID implemented , chrome , edge.
... we wound up. if we can show, since extensions are implemented on UAF, we are going to argue that since these are UAF implemented, that the framework does not matter and can be ported to FIDO2 extension framework without isseu
... AppID has proven that out
... seemed acceptable by Ralph and PHL

correction PLH

self-issue: plan seems fine, who will write it up

tony: need to verfiy one to one extension match
... anyone that doesn't match will have to be non-normative.
... between john and myself to write up
... any other questions on this approch.

none

tony: other issue was Mozilla issue submitted by Boris.

jcj/MOZ: that is #294

scribe: I think we hav eto fix this in credman

jeffH: i agree

jcj-Moz: there is nothing we can do in our document. the browsers go async.
... we have to fix, but hopefully we only have to have an editor's draft update in credman'

tony: PLH do you want to jump int

PLH: how critical is this, can WG say this not a critical issue.
... but if needs fix, we want to hear what is a proper fix.
... would be nice to have Mozilla on board for that resolution.

jeffH: jc and I were talking about this. JC has proposed text. we should forward that to list to put it on the record
... and see if Boris thinks this suggestion works

tony: PLH if Boris says this is OK.

PLH: if mozilla is willing to stand down that would be resolution

<plh> https://lists.w3.org/Archives/Public/public-webauthn/2018Sep/0439.html

PLH: you need to answer this on the list.
... this is about issue #750?

jeffH: isue #750 is different.
... it is #294

PLH: but we have to look at #750

jcj_moz: this is about null dictionary
... I need to do code for it.

jeffH: Boris is saying the web idl is resolved, so that gives us a way to resolve...

jcj_moz: argument is web idl. the way we are using dictionary to overide each other makes the key work ambiguous.
... argument is we shouldn't...since web idl did not update with normative language. think answer is we can't rely on web idl to mandate what is needed for web authn
... algorithm will needs bailouts.
... we need to do more than list just as not required.

jeffH: my comment in issue #750 on July 6

jcj_moz: bail out points instead of relying web idl. potentially creates an interop problem and that is Boris's concern
... we do have to determine invalid

PHL: will we have a test for this?

jcj_moz: yes.

PLH: is this a blocker

jcj_moz: i agree with Boris on this. I think we should make this change. It should not effect anyone's implementation. will look the same externally.

tony: that is main question.

PLH: can make argument, i am hearing you can change error. But it will still generate some type of error.

agl: I do not this break any implementations.

jcj_moz: I don't think it will break interop.

akshay: I think we should do this....

jcj_moz: this will impact credman not when web authn.
... like whatever happens here will need to happen for other credman implementations. it is not just web authn, it is overloading credman

agl: whatever chrome is doing we are okay with. I trust we can navigate this sensibly

jcj_moz: the way this works in Mozilla is a house of cards. we check required fields, but hard to follow why it works.

jeffH: so issues #750 is marked for L2 right now. should it be milestone in PR?

agl: yes, we say it is a blocker.

jeffH: i changed it back

tony: does that satisfy you pLH?

PLH: sounds like a good way to move forward, if it satisfies Mozilla it makes me happy.

tony: and we have to get you the UAF interop

jeffH: how does issue #294 figure in. it is credman issue.
... will credman hold up webauthn at this point.

tony: I don't think so.

elundberg: do we merge typos

PLH: merging typos is fine

tony: anything else today.

christiaan: this PR #1050 is it compelted

akshay: I can do it today or tomorrow

christiaan: big help if you give thumbs up.

tony: anything else?
... no call next week or the week after during TPAC

<wseltzer> https://www.w3.org/Security/strong-authentication-and-identity-workshop/

wseltzer: we shared an announcement at strong auth and ID workshop and thanks MSFT for hosting and share input.

jcj_moz: meeting on the 17th. TPAC starts 10/22

tony: will be on the 17th.
... will be meeting on the 17th.

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)

Succeeded: s/vvjvrfljtgirrjftkccutvdbhjvgdgtblbgijhibjcvd//
Present: jeffh plh wseltzer selfissued elundberg jcj_moz jfontana
No ScribeNick specified.  Guessing ScribeNick: jfontana
Inferring Scribes: jfontana

WARNING: No "Topic:" lines found.


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 03 Oct 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.)