Re: 06/01/2022 W3C Web Authentication Meeting

Hi Tony,

I feel that we can drop the “WPWG continuation meeting” for now. We will want to have more discussion but I think we need to allow some time to pass and proposals to be drawn up. 
For record-keeping purposes, here’s the deck we used to structure that conversation:
 http://www.w3.org/2022/Talks/wpwg-authn-202205/wpwga-202205.pptx

If you would like me to attend for any other part of the discussion, let me know.

Ian

> On May 31, 2022, at 11:21 AM, <nadalin@prodigy.net> <nadalin@prodigy.net> wrote:
> 
>  
> Here is the agenda for the 06/01/2022 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
>  
>  • Here is the link to the Level 2 Webauthn Recommendation  https://www.w3.org/TR/2021/REC-webauthn-2-20210408/
>  • First Public Working Draft of Level 3 has now been published, https://www.w3.org/TR/webauthn-3/
>  • Face-to-Face June 9th in San Francisco (Tim C.)
>   • https://teams.microsoft.com/l/meetup-join/19%3ameeting_NmEzOTA2MzktNjc5Yi00ODVmLTg3NzEtZWEzNDEzYTZjYjk5%40thread.v2/0?context=%7b%22Tid%22%3a%2272f988bf-86f1-41af-91ab-2d7cd011db47%22%2c%22Oid%22%3a%2285b915b1-0e04-41d5-8232-ea70f71aed88%22%7d
>  • Face-to-face Agenda (John F.)
>  • Web Payments WG continuation meeting 
>  • SPWG Update (John B.)
>  • Copyright Licensing update/discussion (Wendy)
>  • I18N Issues 
>  • L3 WD01 open pull requests and open issues
>  
> Pull requests · w3c/webauthn (github.com)
>    • New PublicKeyCredential methods for JSON (de)serialization by MasterKale · Pull Request #1703 · w3c/webauthn · GitHub
>    • backup states in authenticator data by timcappalli · Pull Request #1695 · w3c/webauthn (github.com)device public key extension by equalsJeffH · Pull Request #1663 · w3c/webauthn · GitHub
>    • conditional UI via mediation by equalsJeffH · Pull Request #1576 · w3c/webauthn (github.com)
>    • Add recovery extension by emlun · Pull Request #1425 · w3c/webauthn (github.com)
>    • Ask for tests for normative changes in CONTRIBUTING.md by foolip · Pull Request #653 · w3c/webauthn (github.com)
>  
> 
> Pull requests · w3c/webauthn · GitHub
> 
>  • Mention constant-zero case in §6.1.1 Signature Counter Considerations by emlun · Pull Request #1736 · w3c/webauthn (github.com)
>  • Add "Code injection attacks" security consideration by emlun · Pull Request #1733 · w3c/webauthn (github.com)
>  • Readd the PRF extension. by agl · Pull Request #1732 · w3c/webauthn (github.com)
>  • Refer to options for the user verification check by infinisil · Pull Request #1718 · w3c/webauthn (github.com)
>  
> 
> Issues · w3c/webauthn (github.com)
> 
>    • Update top level use cases to account for multi-device credentials · Issue #1720 · w3c/webauthn · GitHub
>    • use "public key credential source" consistently · Issue #1707 · w3c/webauthn · GitHub
>    • DPK attestation may create possible side channel attack on the batch key. · Issue #1701 · w3c/webauthn (github.com)
>    • Platform Errors for attestations. · Issue #1697 · w3c/webauthn (github.com)
>    • Updating IANA WebAuthn Registries for Level 2 · Issue #1694 · w3c/webauthn (github.com)
>    • Backup state of credentials · Issue #1692 · w3c/webauthn (github.com)
>    • should reference "attestation statement format" registry instead of "extensions" registry · Issue #1689 · w3c/webauthn · GitHub
>    • Should an RP be able to provide finer grained authenticator filtering in attestation options? · Issue #1688 · w3c/webauthn (github.com)
>    • Provide request deserialization, response serialization · Issue #1683 · w3c/webauthn (github.com)
>    • Fix the "aborted flag" reference · Issue #1682 · w3c/webauthn · GitHub
>    • Lookup Credential Source by Credential ID Algorithm returns sensitive data such as the credential private key · Issue #1678 · w3c/webauthn · GitHub
>    • Synced Credentials · Issue #1665 · w3c/webauthn · GitHub
>    • Device-bound key extension · Issue #1658 · w3c/webauthn (github.com)
>    • Cross-origin credential creation in iframes · Issue #1656 · w3c/webauthn (github.com)
>    • Trailing position of metadata · Issue #1646 · w3c/webauthn (github.com)
>    • [Editorial] Truncation description inaccurate · Issue #1645 · w3c/webauthn (github.com)
>    • Mechanism for encoding *direction* metadata may need more work · Issue #1644 · w3c/webauthn (github.com)
>    • Use of in-field metadata not preferred · Issue #1643 · w3c/webauthn (github.com)
>    • Unicode "tag" characters are deprecated for language tagging · Issue #1642 · w3c/webauthn (github.com)
>    • U+ notation incorrect · Issue #1641 · w3c/webauthn (github.com)
>    • Syncing Platform Keys, Recoverability and Security levels · Issue #1640 · w3c/webauthn (github.com)
>    • Possible experiences in a future WebAuthn · Issue #1637 · w3c/webauthn (github.com)
>    • reference CTAP2.1 PS spec and fix broken link · Issue #1635 · w3c/webauthn (github.com)
>    • Missing Test Vectors · Issue #1633 · w3c/webauthn (github.com)
>    • CollectedClientData.crossOrigin default value and whether it is required · Issue #1631 · w3c/webauthn (github.com)
>    • Support for remote desktops · Issue #1577 · w3c/webauthn (github.com)
>    • Prevent browsers from deleting credentials that the RP wanted to be server-side · Issue #1569 · w3c/webauthn (github.com)
>    • Support a "create or get [or replace]" credential re-association operation · Issue #1568 · w3c/webauthn (github.com)
>    • Questions about user handle when supporting usernameless · Issue #1559 · w3c/webauthn (github.com)
>    • Move step 16 of Registration to between 21 and 22 · Issue #1555 · w3c/webauthn (github.com)
>    • Adding info about HSTS for the RPID to client Data. · Issue #1554 · w3c/webauthn (github.com)
>    • Add support for non-modal UI · Issue #1545 · w3c/webauthn (github.com)
>    • Making PublicKeyCredentialDescriptor.transports mandatory · Issue #1522 · w3c/webauthn (github.com)
>    • double check whether the Secure Payment Confirmation effort has implications on the WebAuthn spec · Issue #1492 · w3c/webauthn (github.com)
>    • cleanup <pre class=anchors> and use <pre class="link-defaults"> as appropriate · Issue #1489 · w3c/webauthn (github.com)
>    • Regarding the issue of Credential ID exposure(13.5.6), from what perspective should RP compare RK and NRK and which should be adopted? · Issue #1484 · w3c/webauthn (github.com)
>    • Move PRF Extension into its own specification · Issue #1462 · w3c/webauthn (github.com)
>    • Personal information updates & webauthn · Issue #1456 · w3c/webauthn (github.com)
>    • Requesting properties of created credentials. · Issue #1449 · w3c/webauthn (github.com)
>    • PublicKeyCredentialParameters can't select curve (E.g. ed448) · Issue #1446 · w3c/webauthn (github.com)
>    • "privacy ca" term in images/fido-attestation-structures.svg · Issue #1421 · w3c/webauthn (github.com)
>    • More explicitly document use cases · Issue #1389 · w3c/webauthn (github.com)
>    • Addition of a network transport · Issue #1381 · w3c/webauthn (github.com)
>    • Minor cleanups from PR 1270 review · Issue #1291 · w3c/webauthn (github.com)
>    • Specify authenticator attachment for authentication operation · Issue #1267 · w3c/webauthn (github.com)
>    • Clearly define the way how RP handles the extensions · Issue #1258 · w3c/webauthn (github.com)
>    • add feature detection blurb... · Issue #1208 · w3c/webauthn (github.com)
>    • think about adding note wrt how client platform might obtain authenticator capabilities · Issue #1207 · w3c/webauthn (github.com)
>    • Update name, displayname and icon for RP and user · Issue #1200 · w3c/webauthn (github.com)
>    • export definitions? · Issue #1049 · w3c/webauthn (github.com)
>    • ReIssues · w3c/webauthn (github.com)covering from Device Loss · Issue #931 · w3c/webauthn (github.com)
>    • undefined terms and terms we really ought to define · Issue #462 · w3c/webauthn (github.com)
>  
> Issues · w3c/webauthn · GitHub
>  • Provide passwordless example, or update 1.3.2. to be a passwordless example · Issue #1735 · w3c/webauthn (github.com)
>  • Drop generic client extension processing? · Issue #1730 · w3c/webauthn · GitHub
>  • Credential Creation Options are inconsistent to Request · Issue #1716 · w3c/webauthn · GitHub
>  • Process to report non-compliant credentials · Issue #1713 · w3c/webauthn · GitHub
>  • RP operations: some extension processing may assume that the encompassing signature is valid · Issue #1711 · w3c/webauthn · GitHub
>  • Split RP ops "Registering a new credential" into one with and one without attestation · Issue #1710 · w3c/webauthn · GitHub
>  • Why not make things simple? · Issue #1709 · w3c/webauthn · GitHub
>  • Advice on language to use? · Issue #1708 · w3c/webauthn · GitHub
>  • Switch to permissive copyright license? · Issue #1705 · w3c/webauthn · GitHub
>  • caBLE for Payments · Issue #1681 · w3c/webauthn (github.com)
>  • Cross origin authentication without iframes · Issue #1667 · w3c/webauthn (github.com)
>   
> 4.   Other open issues
> 5.   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 
>  
>  
>  
>  
> Get Outlook for Android

--
Ian Jacobs <ij@w3.org>
https://www.w3.org/People/Jacobs/
Tel: +1 917 450 8783

Received on Tuesday, 31 May 2022 21:05:06 UTC