Re: [webauthn] Use fully-specified COSEAlgorithmIdentifiers in examples and recommendations (#2283)

Sorry, but I have objections to the PR itself for existing algorithms (-7, -35, -36, -8). 

It has cons and is a lot of make work for lot of companies without realistically RP/Platform/Authenticator ever being able to deprecate these existing COSE end points. 

From Windows perspective, we can't make changes to older platforms. And it is not planning to make changes for newer code points. We don't see any benefit. 
From security key perspective, they have unupgradable security keys with existing algorithm code points burned in. 
From our Entra/MSA as an RP perspective, we cannot remove/deprecate  exisiting

I am not commenting about whether these newer code points are beneficial for other specs outside of WebAuthn. But I don't see any benefit out of these new code points. 

I am fine adding new algorithm for Ed448 if you care because that doesn't exist today from WebAuthn perspective. 

-- 
GitHub Notification of comment by akshayku
Please view or discuss this issue at https://github.com/w3c/webauthn/pull/2283#issuecomment-2891407297 using your GitHub account


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

Received on Monday, 19 May 2025 15:15:39 UTC