Re: [webauthn] [L3 CR] Transition Request Draft (#2355)

Above the draft for the transition request. 

There are a few aspects to discuss, possibly during today's call, net of privacy issues w/o answers by privacy (thanks @timcappalli).

If reviews give the key to entering CR, the key to exiting CR is in implementations.

- How do we want to demonstrate that implementations (e.g., Web Test) of the various features are present? 
- Which features should be considered necessary for exiting, and which ones could be lost?
   - If the latter, they should be marked as “at risk” and can be removed.
    - If, on the other hand, there is a feature that is not “at risk” but lacks an implementation, the CR transition request must be redone.
 - Set a date by which to exit CR (which is essentially the time for implementations)


To give some examples from the past.

**[CR L2](https://www.w3.org/TR/2020/CR-webauthn-2-20201222/)**
> For the Web Authentication specification to move to Proposed Recommendation we must show two browser implementations supporting the new features and extensions. The spec will be run through the Level 2 test harness.

**[CR L1](https://www.w3.org/TR/2018/CR-webauthn-20180320/)**: 
> For the Web Authentication specification to move to Proposed Recommendation we must show two independent, interoperable implementations of the Web Authentication API in browsers. We will also have multiple interoperable implementations of the AppID extension, validating the extensions framework. All other extensions are "at risk". If there are not multiple interoperable implementations, each may independently be removed or made informative at Proposed Recommendation.

[cc'ing @timcappalli, @emlun, @MasterKale, @nadalin]

-- 
GitHub Notification of comment by simoneonofri
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2355#issuecomment-3461381260 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 29 October 2025 12:55:33 UTC