Re: 06/12/2019 W3C Web Authentication WG Meeting Agenda

Hi,  I've marked these L2-WD-02 issues that are assigned to me
(equalsJeffH) as "stat:OnGoing" and I am encouraging us to *skip them*
during the concall today (see below with updated copy of Tony's pr+issues
list with these 7 issues removed) :

> lsissues -M 17 -l stat:ongoing -a equalsjeffh

#1049 export definitions?
  https://github.com/w3c/webauthn/issues/1049

#1004 `publicKey` member name in `CredentialCreationRequestOptions` should
be `"public-key"`, or vice-versa?
  https://github.com/w3c/webauthn/issues/1004

#911 Integrate with Feature Policy and possibly Permissions and define
appropriate identifier value for WebAuthn
  https://github.com/w3c/webauthn/issues/911

#876 NULL or DOMException
  https://github.com/w3c/webauthn/issues/876

#462 undefined terms and terms we really ought to define
  https://github.com/w3c/webauthn/issues/462

#358 Eliminate duplicate terminology
  https://github.com/w3c/webauthn/issues/358

#80 adopt consistent terms for RP server-side and client-side components
  https://github.com/w3c/webauthn/issues/80

ALSO, I reassigned issue #199 to L3-WD-01 because we explicitly are not for
now addressing "silent authn", see:
https://github.com/w3c/webauthn/pull/1140#pullrequestreview-200662729

I've removed #199 below...


On Tue, Jun 11, 2019 at 3:22 PM Anthony Nadalin <tonynad@microsoft.com>
wrote:

> Here is the agenda for the 06/12/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. Level 2 Draft 1 has been published,
>    https://www.w3.org/TR/webauthn-2/
>    2. TPAC Registration is open https://www.w3.org/2019/09/TPAC/
>    3. Open Level 2 Draft #2 Pull Requests and Issues
>
>
>    - https://github.com/w3c/webauthn/pull/653
>    - https://github.com/w3c/webauthn/pull/909
>    - https://github.com/w3c/webauthn/pull/966
>    - https://github.com/w3c/webauthn/pull/1219
>    - https://github.com/w3c/webauthn/pull/1222
>    - https://github.com/w3c/webauthn/pull/1223
>    - https://github.com/w3c/webauthn/pull/1230
>    - https://github.com/w3c/webauthn/pull/1232
>
>
>
>    -
>    - https://github.com/w3c/webauthn/issues/334
>    -
>    - https://github.com/w3c/webauthn/issues/863
>    <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwebauthn%2Fissues%2F863&data=04%7C01%7Ctonynad%40microsoft.com%7Cb0daa78a704443f51bc008d6d3325665%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636928610488186377%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=GFSSpFgQUboS9j%2BLGNaqchhqYwa95T1Nwloy%2FhNqKBA%3D&reserved=0>
>    -
>    - https://github.com/w3c/webauthn/issues/465
>    - https://github.com/w3c/webauthn/issues/863
>    - https://github.com/w3c/webauthn/issues/872
>    -
>    -
>    - https://github.com/w3c/webauthn/issues/929
>    - https://github.com/w3c/webauthn/issues/996
>    -
>    - https://github.com/w3c/webauthn/issues/1039
>    - https://github.com/w3c/webauthn/issues/1044
>    -
>    - https://github.com/w3c/webauthn/issues/1061
>    - https://github.com/w3c/webauthn/issues/1099
>    - https://github.com/w3c/webauthn/issues/1100
>    - https://github.com/w3c/webauthn/issues/1101
>    - https://github.com/w3c/webauthn/issues/1105
>    - https://github.com/w3c/webauthn/issues/1133
>    - https://github.com/w3c/webauthn/issues/1147
>    - https://github.com/w3c/webauthn/issues/1149
>    - https://github.com/w3c/webauthn/issues/1162
>    - https://github.com/w3c/webauthn/issues/1174
>    - https://github.com/w3c/webauthn/issues/1188
>    - https://github.com/w3c/webauthn/issues/1196
>    - https://github.com/w3c/webauthn/issues/1197
>    - https://github.com/w3c/webauthn/issues/1199
>    - https://github.com/w3c/webauthn/issues/1200
>    - https://github.com/w3c/webauthn/issues/1201
>    - https://github.com/w3c/webauthn/issues/1202
>    - https://github.com/w3c/webauthn/issues/1204
>    - https://github.com/w3c/webauthn/issues/1206
>    - https://github.com/w3c/webauthn/issues/1207
>    - https://github.com/w3c/webauthn/issues/1208
>    - https://github.com/w3c/webauthn/issues/1215
>    - https://github.com/w3c/webauthn/issues/1229
>    - https://github.com/w3c/webauthn/issues/1233
>
>
>
>    - https://github.com/w3c/webauthn/issues/1211
>    - https://github.com/w3c/webauthn/issues/1218
>    - https://github.com/w3c/webauthn/issues/1220
>    - https://github.com/w3c/webauthn/issues/1221
>    - https://github.com/w3c/webauthn/issues/1231
>
>
>
>
>
>    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%7Cb0daa78a704443f51bc008d6d3325665%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636928610488226355%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=nexQIdr1Y4f3R%2BVR4yA8zPKSc95721wtg%2BtLbQFRUmk%3D&reserved=0>
>
>
>
>
>
>
>
>


-- 
Thanks, HTH,

=JeffH