- From: Ken Ebert <ken@sovrin.org>
- Date: Mon, 3 Dec 2018 09:24:33 -0700
- To: tonynad@microsoft.com
- Cc: public-webauthn@w3.org
- Message-ID: <CA+TjgodJszfpuywqqqieX1ROFyJ57zVdYW1MK4mSAxFmKKbhrQ@mail.gmail.com>
As a newcomer to the WG, I am not clear regarding potential negative consequences of the 2-3 weeks to resolve concerns with the W3C to make the extensions optional and normative. This is likely to be obvious to everyone else, but I could benefit from some enlightenment. Thanks, Ken Ebert On Mon, Dec 3, 2018 at 12:06 AM Anthony Nadalin <tonynad@microsoft.com> wrote: > The current consensus position within the working group was to continue to > push to keep the “extensions” as optional and normative, due to delays on > meeting the ongoing requirements of the W3C for extensions an option was > proposed at the last WG call to mark the extensions as optional and > non-normative, but still publish the extensions as part of the > specification. I would estimate that we would be 2-3 weeks more of > discussions with the W3C staff to complete the answers they are looking for > if we wanted to continue to make the extensions as optional and normative. > > > > If WG member would like to change the current position from as optional > and normative to optional and non-normative please respond to this message, > or if you have other suggestions please also respond. >
Received on Monday, 3 December 2018 16:25:06 UTC