[CFRG] Re: 回复: I-D Action: draft-irtf-cfrg-det-sigs-with-noise-03.txt

[Daniel Huigens <[e-mail]>]

Hi folks,

Speaking in the capacity of Web Cryptography API editor here.

WebKit has shipped an implementation of Ed25519 that on macOS produces
randomized signatures, presumably because its CryptoKit has implemented
this draft.

The current draft specifying Ed25519 in Web Crypto [1] only refers to
RFC 8032, but Apple has requested that we explicitly allow generating
randomized signatures as well, e.g. by referring to this draft.
Therefore I'd like to ask:

1. Is it expected that this draft will become an RFC, such that
   it's reasonable to refer to the draft already (at least from
   the Editor's draft of Web Crypto, for example)?

2. If the draft does become an RFC, is it necessary to refer to it
   explicitly at that point? Or, will all references to RFC 8032 also
   allow randomized signatures automatically, given that this draft
   updates that RFC? (I imagine this is also relevant for IETF specs
   like RFC 9580 (OpenPGP) which refers to RFC 8032 as well, though
   e.g. RFC 8446 (TLS 1.3) refers to "[RFC8032] or its successors".)

Best,
Daniel

[1]: https://wicg.github.io/webcrypto-secure-curves/


---

Daniel Huigens
Cryptography Team Lead
Proton AG