Re: [webauthn] Update COSEAlgorithmIdentifier uses and examples to prefer fully-specified alg IDs (#2276)

> Update non-normative examples, and update recommendations for RP to prefer the new values. These are not yet implemented by clients and authenticators, but will gracefully fall back to the legacy values until implemented.

If these identifiers are not implemented by clients and authenticators, then how can you be sure they will "gracefully fall back to the legacy values"? As a Level 3 RP, should I use _both_ IDs "just in case". For example,

```javascript
[
  {
    type: public-key,
    alg:-50
  },
  {
    type: public-key,
    alg:-8,
  },
  {
    type: public-key,
    alg:-9,
  },
  {
    type: public-key,
    alg:-7,
  },
  {
    type: public-key,
    alg:-48,
  },
  {
    type: public-key,
    alg:-35,
  },
  {
    type: public-key,
    alg:-257,
  },
]
```

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


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

Received on Wednesday, 2 April 2025 15:28:44 UTC