RE: WebAuthn Spec Status

I agree as well. Based on our conversations with web developers, the core functionality they need is there: registration and authentication of credentials. As we finish WD-07, we should consider the spec feature complete and treat the WD-08 milestone as a short interim status just before the CR milestone. As we clean up the spec, we should keep in mind that spec polishing can also occur at the PR<http://www.w3.org/2017/Process-20170301/#rec-pr> and W3C Rec<http://www.w3.org/2017/Process-20170301/#rec-publication> milestone period.

In terms of timeline, I believe TPAC in November would be the right time to advance the specs to CR status assuming the functionalities are complete. @Alexei Czeskis<mailto:aczeskis@google.com>, @J.C. Jones<mailto:jc@mozilla.com> what do you think?

From: J.C. Jones [mailto:jc@mozilla.com]
Sent: Monday, September 25, 2017 9:34 AM
To: Alexei Czeskis <aczeskis@google.com>
Cc: W3C Web Authn WG <public-webauthn@w3.org>
Subject: Re: WebAuthn Spec Status

I agree. The core functionality is close enough that we can get inter-operable implementations, and announcing a movement CR is important to get RPs to start their adoption.

To me, WD-08 appears to be a perfect goal to announce as a Candidate Recommendation.

Cheers,
J.C.

On Sun, Sep 24, 2017 at 10:43 PM, Alexei Czeskis <aczeskis@google.com<mailto:aczeskis@google.com>> wrote:
Hi all,

From my point of view, the spec is pretty much feature complete as we finish of WD-07.

I propose making WD-08 only about clean-up (no renaming APIs or variables -- just clarifying wording, etc).  Let's make WD-08 the final draft that we then propose to go to CR.

What do you all think?

Thanks!
-Alexei


________________

            . Alexei Czeskis .:. Securineer .