- From: Harry Halpin <hhalpin@w3.org>
- Date: Fri, 15 Mar 2013 16:10:02 +0100
- To: Ryan Sleevi <sleevi@google.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
If so, it may be useful to discuss with them their feedback (via Zooko)
to the API.
I have thought, and this came up in an OECD discussion with the IETF
chair, that per-algorithm security considerations *in a separate RFC*
might be a good idea. Note this is a separate conversation than the
registry, but would address their comments by putting the ball back in
their court, so to speak.
Then our API can point to their RFC, which they can then keep updated as
long as the CFRG runs. Did the CFRG discuss this, or the API, at all?
cheers,
harry
Received on Friday, 15 March 2013 15:10:14 UTC