- From: ANTHONY NADALIN <nadalin@prodigy.net>
- Date: Tue, 14 Jan 2025 23:10:11 +0000
- To: 'Michael Jones' <michael_b_jones@hotmail.com>, 'W3C Web Authn WG' <public-webauthn@w3.org>, "'Phillips, Addison'" <addison@lab126.com>, 'Christiaan Brand' <cbrand@google.com>, 'Ian Jacobs' <ij@w3.org>
- Message-ID: <SA1P223MB0970E34B192B8A0F6BA5F66EAA182@SA1P223MB0970.NAMP223.PROD.OUTLOOK.COM>
Here is the agenda for the01/15/2025 W3C Web Authentication WG Meeting, that will take place as a 60 minute teleconference. Remember call is at 11AM Pacific Time. Reminder that we will be using ZOOM from now on, please make sure you go to Web Authentication bi-weekly (w3.org)<https://www.w3.org/events/meetings/4bab6a90-bdb5-400f-ab87-64a7a852d86a/20230517T150000> Select scribe please someone be willing to scribe so we can get down to the issues 1. Here is the link to the Level 2 Webauthn Recommendation https://www.w3.org/TR/2021/REC-webaut<https://www.w3.org/TR/2021/REC-webauthn-2-20210408/> 2. L3 Target Publication Schedule discussion (SIMONE) * Before publishing WD: we are missing a section for outlining the changes from L2, as requested by the process and having an example of the one from VS JSONSchema [1] * Before publishing CR and after publishing the WD * Asks for horizontal review (after the WD), giving them a minimum of 28 days - Demonstrate implementation, so we need to check if tests are available and, in this case, the situation is already in a good state [2] [1] https://www.w3.org/TR/2023/WD-vc-json-schema-20231115/#revision-history [2] https://wpt.fyi/results/webauthn?label=master&label=experimental&aligned * 1. https://arstechnica.com/security/2024/12/passkey-technology-is-elegant-but-its-most-definitely-not-usable-security/ discussions 2. 02/05/2025 WebAuthn Meeting CANCELLED 3. 03/05/2025 WebAuthn Meeting CANCELLED 4. 03/19/2025 WebAuthn Meeting CANCELLED 5. Canidate Recommendation open pull requests and open issues Pull requests · w3c/webauthn<https://github.com/w3c/webauthn/pulls?q=is%3Aopen+is%3Apr+milestone%3A%22L3+Candidate+Recommendation+%22> 1. Address cross-origin create() in §5.10 by emlun · Pull Request #2231 · w3c/webauthn<https://github.com/w3c/webauthn/pull/2231> 2. Adding Revision history section by simoneonofri · Pull Request #2224 · w3c/webauthn<https://github.com/w3c/webauthn/pull/2224> 3. Update Use Cases for L3 by timcappalli · Pull Request #2139 · w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pull/2139> 4. Cleanup: Manual References by timcappalli · Pull Request #2111 · w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pull/2111> Pull requests · w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pulls?q=is%3Aopen+is%3Apr+no%3Amilestone> 1. Fix bikeshed warnings by timcappalli · Pull Request #2227 · w3c/webauthn<https://github.com/w3c/webauthn/pull/2227> Issues · w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues?q=is%3Aopen+is%3Aissue+milestone%3AL3-WD-02+> 1. Issues · w3c/webauthn · GitHub<https://github.com/w3c/webauthn/issues?q=is%3Aopen+is%3Aissue+-label%3Astat%3AOnGoing+-label%3Astat%3Apr-open+no%3Amilestone> * Clean up bikeshed issues before L3 publish · Issue #2226 · w3c/webauthn<https://github.com/w3c/webauthn/issues/2226> * Prepare for CR · Issue #2225 · w3c/webauthn<https://github.com/w3c/webauthn/issues/2225> 1. L4 Pull requests * Pull requests · w3c/webauthn<https://github.com/w3c/webauthn/pulls?q=is%3Aopen+is%3Apr+milestone%3A%22L4%28First+Published+Working+Draft%29%22> 1. L4 Technical issues * Issues · w3c/webauthn<https://github.com/w3c/webauthn/labels/type%3Atechnical> 1. L4 Editorial issues * Issues · w3c/webauthn<https://github.com/w3c/webauthn/labels/type%3Aeditorial> 4. Other open issues or discussions 5. Adjourn
Received on Tuesday, 14 January 2025 23:10:23 UTC