RE: 01/10/2024 W3C Web Authentication Meeting

https://www.w3.org/groups/wg/webauthn/calendar/ says that our call today is at noon Pacific time.  Which is correct?

                                                                -- Mike

From: nadalin@prodigy.net <nadalin@prodigy.net>
Sent: Tuesday, January 9, 2024 3:09 PM
To: 'W3C Web Authn WG' <public-webauthn@w3.org>; 'John Fontana' <jfontana@yubico.com>; 'Phillips, Addison' <addison@lab126.com>; 'Christiaan Brand' <cbrand@google.com>; 'Ian Jacobs' <ij@w3.org>
Subject: 01/10/2024 W3C Web Authentication Meeting


Here is the agenda for the 01/10/2024 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-webauthn-2-20210408/
  2.  WD01 has now been published, https://www.w3.org/TR/webauthn-3/
  3.  No meeting 01/17/2024 -  CANCELLED

  1.  PWG Update (John B.)
  2.  We have 49 open issues, 25 of them have been tagged with the @RISK label, please review with the link below, if you don't agree we will discuss as the first item on the agenda

     *   Issues * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues?q=is%3Aopen+is%3Aissue+label%3A%40Risk>

  1.  W3c WebID proposal for authentication see WebID - W3C Wiki<https://www.w3.org/wiki/WebID>
  2.  L3 WD01 open pull requests and open issues




Pull requests * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pulls?q=is%3Aopen+is%3Apr+milestone%3AL3-WD-02>

        *   Mark SPK's `signatures` output as required. by agl * Pull Request #2011 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pull/2011>
        *   Enterprise packed attestation guidance by dwaite * Pull Request #1954 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pull/1954>
        *   Add packed attestation optional firmware version attribute by dwaite * Pull Request #1953 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pull/1953>
        *   Initial text for conditional create by pascoej * Pull Request #1951 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pull/1951>
        *   Add new getClientCapabilities method by timcappalli * Pull Request #1923 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pull/1923>



Pull requests * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pulls?q=is%3Aopen+is%3Apr+no%3Amilestone>

  1.  Correct capitalization on "Github" by MasterKale * Pull Request #2009 * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/pull/2009>
  2.  Drop assertion-time attestation. by agl * Pull Request #1997 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pull/1997>
  3.  Make the default value for the attestation member in assertion options be null by Kieun * Pull Request #1972 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pull/1972>
  4.  Clarify TPM attestation verification instructions by sbweeden * Pull Request #1926 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/pull/1926>



Issues * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues?q=is%3Aopen+is%3Aissue+milestone%3AL3-WD-02+>

        *   Conditional UI support by WebAuthn WebDriver Extension * Issue #2010 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/2010>
        *   Consider replacing "Github" with "GitHub" * Issue #2007 * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/issues/2007>
        *   rp.name, user.name and user.displayName length limit does not state binary encoding * Issue #1994 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1994>
        *   create() and get() return an algorithm, not a credential * Issue #1984 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1984>
        *   Ambiguous instructions in the Android Key Attestation Statement Format verification procedure * Issue #1980 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1980>
        *   Are notes in webauthn normative or informative? * Issue #1979 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1979>
        *   Extensions should specify partial dictionaries that modify AuthenticationExtensionsClient{Inputs, Outputs}JSON * Issue #1968 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1968>
        *   [Superset] Updating credential metadata and requesting deletion of stale credentials * Issue #1967 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1967>
        *   Further clarification of Unsigned Extension Outputs * Issue #1964 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1964>
        *   Should credentials requested with attestation=none include an AAGUID? * Issue #1962 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1962>
        *   Describe firmware OID usage in packed attestation * Issue #1952 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1952>
        *   Non-modal registration during conditional assertion * Issue #1929 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1929>
        *   Allow desired attestation format to be an ordered list * Issue #1917 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1917>
        *   Describe packed enterprise attestation * Issue #1916 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1916>
        *   Update Authenticator Taxonomy examples section * Issue #1912 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1912>
        *   Prescriptive behaviours for Autofill UI * Issue #1800 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1800>
        *   Should enterprise attestation support be flagged explicitly? * Issue #1742 * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/issues/1742>
        *   Discussing mechanisms for enterprise RP's to enforce bound properties of credentials * Issue #1739 * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/issues/1739>
        *   Provide passwordless example, or update 1.3.2. to be a passwordless example * Issue #1735 * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/issues/1735>
        *   Update top level use cases to account for multi-device credentials * Issue #1720 * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/issues/1720>
        *   Public Key Credential Source and Extensions * Issue #1719 * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/issues/1719>
        *   RP operations: some extension processing may assume that the encompassing signature is valid * Issue #1711 * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/issues/1711>
        *   Split RP ops "Registering a new credential" into one with and one without attestation * Issue #1710 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1710>
        *   Switch to permissive copyright license? * Issue #1705 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1705>
        *   Platform Errors for attestations. * Issue #1697 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1697>
        *   Should an RP be able to provide finer grained authenticator filtering in attestation options? * Issue #1688 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1688>
        *   Lookup Credential Source by Credential ID Algorithm returns sensitive data such as the credential private key * Issue #1678 * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/issues/1678>
        *   Synced Credentials * Issue #1665 * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/issues/1665>
        *   Cross-origin credential creation in iframes * Issue #1656 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1656>
        *   Trailing position of metadata * Issue #1646 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1646>
        *   [Editorial] Truncation description inaccurate * Issue #1645 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1645>
        *   Mechanism for encoding *direction* metadata may need more work * Issue #1644 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1644>
        *   Use of in-field metadata not preferred * Issue #1643 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1643>
        *   Unicode "tag" characters are deprecated for language tagging * Issue #1642 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1642>
        *   U+ notation incorrect * Issue #1641 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1641>
        *   Syncing Platform Keys, Recoverability and Security levels * Issue #1640 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1640>
        *   Possible experiences in a future WebAuthn * Issue #1637 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1637>
        *   reference CTAP2.1 PS spec and fix broken link * Issue #1635 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1635>
        *   Missing Test Vectors * Issue #1633 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1633>
        *   CollectedClientData.crossOrigin default value and whether it is required * Issue #1631 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1631>
        *   Support for remote desktops * Issue #1577 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1577>
        *   Prevent browsers from deleting credentials that the RP wanted to be server-side * Issue #1569 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1569>
        *   Support a "create or get [or replace]" credential re-association operation * Issue #1568 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1568>
        *   Adding info about HSTS for the RPID to client Data. * Issue #1554 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1554>
        *   Making PublicKeyCredentialDescriptor.transports mandatory * Issue #1522 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1522>
        *   cleanup <pre class=anchors> and use <pre class="link-defaults"> as appropriate * Issue #1489 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1489>
        *   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)<https://github.com/w3c/webauthn/issues/1484>
        *   Requesting properties of created credentials. * Issue #1449 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1449>
        *   PublicKeyCredentialParameters can't select curve (E.g. ed448) * Issue #1446 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1446>
        *   Minor cleanups from PR 1270 review * Issue #1291 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1291>
        *   Clearly define the way how RP handles the extensions * Issue #1258 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1258>
        *   export definitions? * Issue #1049 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1049>
        *   undefined terms and terms we really ought to define * Issue #462 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/462>

Issues * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/issues?q=is%3Aopen+is%3Aissue+-label%3Astat%3AOnGoing+-label%3Astat%3Apr-open+no%3Amilestone>

  1.  Misaligned steps in Section 7.2 * Issue #1913 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1913>
  2.  Clarify browser behavior when an authenticators return equivalent of "InvalidStateError" * Issue #1888 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1888>
  3.  Clarify how to differentiate between exceptions * Issue #1859 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1859>
  4.  Clarify the need for truly randomly generated challenges (aka challenge callback issue) * Issue #1856 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1856>
  5.  Dependencies section is out of date and duplicates terms index * Issue #1797 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1797>
  6.  Enterprise attestaion is a bool in WebAuthn and an Int in CTAP2.1 * Issue #1795 * w3c/webauthn (github.com)<https://github.com/w3c/webauthn/issues/1795>
  7.  Cross origin authentication without iframes (accommodating SPC in WebAuthn) * Issue #1667 * w3c/webauthn * GitHub<https://github.com/w3c/webauthn/issues/1667>



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<https://aka.ms/ghei36>

Received on Wednesday, 10 January 2024 19:01:29 UTC