<jeffh> there is already a PR, yes? --> https://github.com/w3c/webauthn/pull/882

<jeffh> my mic is not working....

<jeffh> hello?

<jcj_moz> yeah, not hearing you jeffh

<jeffh> mention pr above?

<jeffh> thx JC

I can scribe

<jeffh> so this new one would supersede the old one

tony: open PRs

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

tony: need review, mike and Sam

<jcj_moz> https://github.com/w3c/webauthn/pull/1041/files

tony: merge, yes .
... just waiting for reviews on #1036

<jeffh> pls review https://github.com/w3c/webauthn/pull/375!!!

tony: issues.
... a few here.

<jeffh> pls relay

tony: we are getting down to the deadlines for when we need to determine what's in/out for PR
... today #106, ongoing, not concerned with
... #294, we can deal with the implementations; akshay need to define how edge works
... akshay can you update #294 for the record
... #334

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

tony: think it will be covered.
... duplicate terminology #58

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

tony: we are ok here

#403 https://github.com/w3c/webauthn/issues/403\

<jcj_moz> ...forbidden

tony: goes back to #1020

<jeffh> note "onGoing" label

rolf: I read Chrome is looking to withdraw Token Binding.

tony: does that include Token Binding for webauthN

agl: yes

rolf: this is challenging for us.

tony: but others will implement

<jeffh> what is link for dial-in directions?

<jeffh> thx weiler

tony: #462 this is ongoing. https://github.com/w3c/webauthn/issues/462

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

jc_jones: seeing if we can go with my postive review and drop Mikes bad review

I believe so.

I stand corrected.

#375

apowers: click on links and read deeper.

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

tony: trying to close down by next week for PR
... what are chances her

jeffH: not the end of world if it does not happen. we can punt

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

tony: did we get anything back from accessibility group

weiler: yes.
... I will get that back by next week.
... let me go back. first and third bullets look actionable. I asked for more help.

@weiler: hopefully they will give us more.

scribe: I did not see enough there that was actionable.

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

jeffH: that is spec hygiene. check we should make before making another publication re:PR
... when we publish to TR name space, we should verify if the spec is ready to publicsh.

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

tony: not taking action

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

tony: kinda punt to cred man

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

tony: been through this one lately, akshay

jeffH: please review the PR.

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

tony: i believe this one gets close.
... or someone write something and do something different. maybe just add a sentence. Emil proposed something
... I will contact him. maybe open a quick PR

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

tony: jeffH you looked at this one.

jeffH: i was tempted to close it. I think more appropriate for platform folks to OK and close
... it would be good for windows. what is win equivalent functionality on this. would be good to have a link

akshay 1045? yes.

jeffK: would also be good to have link to android .

tony: can christiaan or agl verify

agl: not sure I understand the question. they want alternative namespace?

jeffH: not really. think he wants equivalent of appID and facet

christiaan: i'm sure, it is vague, you can claim a URL or origin...this would be bound to a record...this is likely implementation specifc on each platform.
... this is how we are handling this in android.

jeffH: would be good to have links to the directions or whatever

christiaan: I will try to find that and I can add that.

akshay: lets put this in the comments.

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

tony: close this one. i am in favor of that.

agl: agreed

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

jeffH: this is more spec hygiene

tony: that takes us through the un-triaged issues.
... we still have one Mike J is looking at. which is #1043

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

tony: i don't think we wanted to tackle at this point in time.

jc-Jones: my suggestion is that we will live with it.
... yes.

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

tony: shane is still looking for a pointer
... assign this to Anar, let him do the PR
... this takes us through PR, issues and un-triaged issues.
... want to close this down by next meeting. So we can pull this through to Proposed Rec.
... any major concerns on this approach
... lets try to close it down next week and get a PR produced.
... OK, any other business.

jeffH: one quick item. the token binding request for the fetch spec has not been assigned. If there are browsers are not participating can they speak up, if they want to see this land

<jeffh> this needs implementer support expressed: https://github.com/whatwg/fetch/pull/715

tony: akshay can you find you guys in that group WHATWG

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)

Succeeded: s/??/Sam/
Present: weiler apowers akshay jcj_moz jfontana nadalin john_bradley Rolf christiaan agl jeffh
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: 29 Aug 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.)