Re: 08/14/2024 W3C Web Authentication Meeting Agenda

Hi Michael,

I’m investigating the issue.

Thank you,

Simone

> On 16 Aug 2024, at 07:01, Michael Jones <michael_b_jones@hotmail.com> wrote:
> 
> I missed this because it wasn’t in the calendar.  What can we do to have future WebAuthn meetings make it into the W3C calendar and have e-mailed calendar invitations go out?
>                                                                  Thanks,
>                                                                 -- Mike
>  From: Simone Onofri <simone@w3.org>
> Sent: Wednesday, August 14, 2024 8:47 AM
> To: ANTHONY NADALIN <nadalin@prodigy.net>
> Cc: 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>
> Subject: Re: 08/14/2024 W3C Web Authentication Meeting Agenda
>  Hi all,
> 
> as the event is not in website calendar, I attached a replacement.
> 
> Probably I can stay only for the first 30 mins, if someone would like to scribe, feel free.
> 
> However, as in some groups people prefer to use Google Docs > Markdown > GitHub, we can do also in this way.
> 
> Thank you,
> 
> Simone
> 
> 
> > On 14 Aug 2024, at 04:21, ANTHONY NADALIN <nadalin@prodigy.net> wrote:
> > 
> >  Here is the agenda for the 08/14/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)
> >  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/
> >     • Charter Extension in progress (Web Authentication Working Group Charter (w3c.github.io))
> >     • 08/21/2024 CANCELLED
> >     • F2F TPAC 2024 (Sept 24-27, Anaheim CA)
> >         • Full day on the 24th 9-5  and the payments WG meeting will happen 16:30-18:00 as part of the 24th
> >         • Mask Policy at meeting room is left up to the individual while in the room
> >     • WD01 has now been published, https://www.w3.org/TR/webauthn-3/
> >     • PWG Update (John B., Adam L.)
> >     • L3 Publication Schedule
> >         • Deadline for wide review
> > Sunday, October 27 0024
> >         • Group Call for Consensus (CfC) to move to Candidate Recommendation, wide review is done
> > Monday, October 28 0024
> >         • Transition request to Candidate Recommendation
> > Thursday, November 7 0024
> >     • L3 WD02 open pull requests and open issues
> >   Pull requests · w3c/webauthn (github.com)
> >     • Add PR template by timcappalli · Pull Request #2108 · w3c/webauthn (github.com)
> >     • Add topOrigin to the limited verification algorithm. by zacknewman · Pull Request #2104 · w3c/webauthn · GitHub
> >     • Add Signal API by nsatragno · Pull Request #2093 · w3c/webauthn (github.com)
> >     • Enterprise packed attestation guidance by dwaite · Pull Request #1954 · w3c/webauthn (github.com)
> >     •  
> >  Pull requests · w3c/webauthn (github.com)
> >     • Change type of credProps.authenticatorDisplayName to DOMString by emlun · Pull Request #2115 · w3c/webauthn (github.com)
> >     • Move topOrigin definition after crossOrigin by emlun · Pull Request #2114 · w3c/webauthn (github.com)
> >     • Cleanup: Manual References by timcappalli · Pull Request #2111 · w3c/webauthn (github.com)
> >     • Add new error codes by MasterKale · Pull Request #2095 · w3c/webauthn (github.com)
> >     • Clarify TPM attestation verification instructions by sbweeden · Pull Request #1926 · w3c/webauthn (github.com)
> > 
> > Issues · w3c/webauthn (github.com)
> >     • [[Create]] should not access the global object directly · Issue #2092 · w3c/webauthn (github.com)
> >     • Align the order of fields in PublicKeyCredentialDescriptorJSON with PublicKeyCredentialDescriptor · Issue #2082 · w3c/webauthn (github.com)
> >     • CredentialCreationOptions/mediation not yet defined in CredMan · Issue #2079 · w3c/webauthn · GitHub
> >     • Make PublicKeyCredentialRequestOptions.rpId a DOMString · Issue #2066 · w3c/webauthn · GitHub
> >     • §6.1. Steps to generate authenticator data should include BE and BS flags · Issue #2064 · w3c/webauthn · GitHub
> >     • create() and get() return an algorithm, not a credential · Issue #1984 · w3c/webauthn (github.com)
> >     • Ambiguous instructions in the Android Key Attestation Statement Format verification procedure · Issue #1980 · w3c/webauthn (github.com)
> >     • Are notes in webauthn normative or informative? · Issue #1979 · w3c/webauthn (github.com)
> >     • Extensions should specify partial dictionaries that modify AuthenticationExtensionsClient{Inputs, Outputs}JSON · Issue #1968 · w3c/webauthn (github.com)
> >     • [Superset] Updating credential metadata and requesting deletion of stale credentials · Issue #1967 · w3c/webauthn (github.com)
> >     • Should credentials requested with attestation=none include an AAGUID? · Issue #1962 · w3c/webauthn (github.com)
> >     • Non-modal registration during conditional assertion · Issue #1929 · w3c/webauthn (github.com)
> >     • Adding some sentences to describe credential sharing between multiple users · Issue #1921 · w3c/webauthn (github.com)
> >     • Allow desired attestation format to be an ordered list · Issue #1917 · w3c/webauthn (github.com)
> >     • Describe packed enterprise attestation · Issue #1916 · w3c/webauthn (github.com)
> >     • Misaligned steps in Section 7.2 · Issue #1913 · w3c/webauthn (github.com)
> >     • Prescriptive behaviours for Autofill UI · Issue #1800 · w3c/webauthn (github.com)
> >     • Should enterprise attestation support be flagged explicitly? · Issue #1742 · w3c/webauthn · GitHub
> >     • Discussing mechanisms for enterprise RP's to enforce bound properties of credentials · Issue #1739 · w3c/webauthn · GitHub
> >     • Provide passwordless example, or update 1.3.2. to be a passwordless example · Issue #1735 · w3c/webauthn · GitHub
> >     • Update top level use cases to account for multi-device credentials · Issue #1720 · w3c/webauthn · GitHub
> >     • Public Key Credential Source and Extensions · Issue #1719 · 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.com)
> >     • Switch to permissive copyright license? · Issue #1705 · w3c/webauthn (github.com)
> >     • Should an RP be able to provide finer grained authenticator filtering in attestation options? · Issue #1688 · w3c/webauthn (github.com)
> >     • 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
> >     • 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)
> >     • 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)
> >     • Adding info about HSTS for the RPID to client Data. · Issue #1554 · w3c/webauthn (github.com)
> >     • Making PublicKeyCredentialDescriptor.transports mandatory · Issue #1522 · 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)
> >     • 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)
> >     • Minor cleanups from PR 1270 review · Issue #1291 · w3c/webauthn (github.com)
> >     • Clearly define the way how RP handles the extensions · Issue #1258 · w3c/webauthn (github.com)
> >     • export definitions? · Issue #1049 · w3c/webauthn (github.com)
> >     • undefined terms and terms we really ought to define · Issue #462 · w3c/webauthn (github.com)
> >  Issues · w3c/webauthn · GitHub
> >                 • Remove `RegistrationResponseJSON.id` and `AuthenticationResponseJSON.id` · Issue #2119 · w3c/webauthn (github.com)
> >                 • Cross-window `Virtual Authenticator Database` · Issue #2117 · w3c/webauthn (github.com)
> >                 • CollectedClientData.crossOrigin not referenced in RP ops · Issue #2113 · w3c/webauthn (github.com)
> >                 • Rename PublicKeyCredentialHints to PublicKeyCredentialHint? · Issue #2112 · w3c/webauthn (github.com)
> >                 • Make `AuthenticatorAttestationResponseJSON.publicKeyAlgorithm` optional · Issue #2106 · w3c/webauthn (github.com)
> >                 • Add `topOrigin` to the limited verification algorithm · Issue #2102 · w3c/webauthn (github.com)
> >                 • CollectedClientData fields are not ordered correctly and crossOrigin should be required · Issue #2101 · w3c/webauthn (github.com)
> >                 • UTF-8 decode should not be required for response.clientDataJSON and cData · Issue #2100 · w3c/webauthn (github.com)
> >                 • Does Related Origins introduce a need for "Related RP IDs" support in `.get()`? · Issue #2099 · w3c/webauthn (github.com)
> >                 • Define `TypeError` behavior during `.get()` · Issue #2094 · w3c/webauthn (github.com)
> >                 • Add examples for PRF extension · Issue #2088 · w3c/webauthn (github.com)
> >                 • Additional guidance/clarification on RP ID and origin validation · Issue #2059 · w3c/webauthn (github.com)
> >                 • excludeCredentials on Get · Issue #2057 · w3c/webauthn · GitHub
> >                 • CollectedClientData serialization is confusing WebIDL and/or Infra values for ECMAScript values · Issue #2056 · w3c/webauthn (github.com)
> >                 • Deprecate AuthenticatorAttachment in favor of PublicKeyCredentialHints. · Issue #2053 · w3c/webauthn (github.com)
> >                 • Editorial convention: Semantic line breaks · Issue #2045 · w3c/webauthn (github.com)
> >                 • How to guarantee created resident key is actually received by RP in adverse networking conditions? · Issue #2038 · w3c/webauthn (github.com)
> >                 • New Authenticator Extension: Time Since UV · Issue #2034 · w3c/webauthn (github.com)
> >                 • Defining new OIDs to facilitate WebAuthn interoperability with CMS · Issue #2026 · w3c/webauthn (github.com)
> >                 • Reflect caching of user gestures in WebAuthn assertion · Issue #2023 · w3c/webauthn (github.com)
> >                 • Revised txAuthSimple extension · Issue #2022 · w3c/webauthn (github.com)
> >                 • Clarify how to differentiate between exceptions · Issue #1859 · w3c/webauthn (github.com)
> >                 • Clarify the need for truly randomly generated challenges (aka challenge callback issue) · Issue #1856 · w3c/webauthn (github.com)
> >                 • Cross origin authentication without iframes (accommodating SPC in WebAuthn) · Issue #1667 · w3c/webauthn · GitHub
> >    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

Received on Monday, 19 August 2024 10:13:42 UTC