Re: 04/17/2019 W3C Web Authentication WG Meeting Agenda

I went thru the PRs, results noted below.  flagged issues in the list
below that already have PRs open. HTH, =JeffH

On Tue, Apr 16, 2019 at 3:41 PM Anthony Nadalin <tonynad@microsoft.com>
wrote:

> Here is the agenda for the 04/17/2019 W3C Web Authentication WG Meeting,
> that will take place as a 60 minute teleconference. Remember call is at
> NOON PDT
>
>  Select scribe please someone be willing to scribe so we can get down to
> the issues
>
>    1. Open Level 2 Draft #1 (L2-WD-01) Pull Requests and Issues
>
> link to list below PRs:
https://github.com/w3c/webauthn/pulls?q=is%3Aopen+is%3Apr+milestone%3AL2-WD-01



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

recommend close no further action
<https://github.com/w3c/webauthn/pull/500#pullrequestreview-227871232>


>    -  https://github.com/w3c/webauthn/pull/653
>
> recommend: keep open, mark priority Low


>    - https://github.com/w3c/webauthn/pull/909
>
> Waiting for publication of new CTAP draft


>    - https://github.com/w3c/webauthn/pull/1095
>
> waiting on equalsJeffH to contribute, fixes issue #1088


>    - https://github.com/w3c/webauthn/pull/1184
>
>  fixes issue #1178

dismissed my prior in-error review, LGTM modulo minor comment.


>    - https://github.com/w3c/webauthn/pull/1191  - fixes #991
>
> needs further review / revision

equalsJeffH to review


>    - https://github.com/w3c/webauthn/pull/1192
>
>  fixes issue #1179

pls merge this :)


>    - https://github.com/w3c/webauthn/pull/1193  - fixes #1180
>
>  pls merge this :)


>    - https://github.com/w3c/webauthn/pull/1195
>
> reviewed, minor comment



link to list below issues:
https://github.com/w3c/webauthn/issues?q=is%3Aopen+is%3Aissue+milestone%3AL2-WD-01

>
>    - https://github.com/w3c/webauthn/issues/863
>    - https://github.com/w3c/webauthn/issues/872
>    - https://github.com/w3c/webauthn/issues/911
>    - https://github.com/w3c/webauthn/issues/973
>    - https://github.com/w3c/webauthn/issues/978
>    - https://github.com/w3c/webauthn/issues/991 - PR #1191
>    - https://github.com/w3c/webauthn/issues/996
>    - https://github.com/w3c/webauthn/issues/1004
>    - https://github.com/w3c/webauthn/issues/1060
>    - https://github.com/w3c/webauthn/issues/1088 - PR #1095
>    - https://github.com/w3c/webauthn/issues/1099
>    - https://github.com/w3c/webauthn/issues/1122
>    - https://github.com/w3c/webauthn/issues/1147
>    - https://github.com/w3c/webauthn/issues/1149
>    - https://github.com/w3c/webauthn/issues/1166
>    - https://github.com/w3c/webauthn/issues/1174
>    - https://github.com/w3c/webauthn/issues/1178 - PR #1184
>    - https://github.com/w3c/webauthn/issues/1179 - PR #1192
>    - https://github.com/w3c/webauthn/issues/1180 - PR #1193
>    - https://github.com/w3c/webauthn/issues/1194
>    - https://github.com/w3c/webauthn/issues/1190
>    -
>    - https://github.com/w3c/webauthn/issues/1199
>    - https://github.com/w3c/webauthn/issues/1198
>
>
>    1. Other open issues
>    2. Adjourn
>
> Because of toll fraud issues MIT has been experiencing, I've been asked to
> change our call coordinates and password and, as an ongoing thing, not
> distribute the call coordinates publicly.  That means not including the
> WebEx call number or URL in our agendas or minutes.
>
>
>
> You can find the new call coordinates at this link, accessible with your
> W3C member login credentials.
>
> https://www.w3.org/2016/01/webauth-password.html
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2016%2F01%2Fwebauth-password.html&data=04%7C01%7Ctonynad%40microsoft.com%7Cbd2ce0eea33c4f834f1a08d69ccd2069%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636868802206920167%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=yyQE%2F%2BDafpleWGk032WuLtn4lfFN5%2Bhf4u6t60zaEZ0%3D&reserved=0>
>