- From: Harry Halpin <hhalpin@w3.org>
- Date: Sun, 01 Nov 2015 10:27:18 -0500
- To: Ryan Sleevi <sleevi@google.com>, GALINDO Virginie <Virginie.Galindo@gemalto.com>
- CC: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
- Message-ID: <56362F56.9010001@w3.org>
On 10/31/2015 04:15 PM, Ryan Sleevi wrote:
> I'm unclear of the value - to the WG or to the community at large - to
> be publishing algorithms removed from the spec due to lack of
> interest. Given that we regularly see feedback from the public related
> to confusion about the W3C process and workflow, my sense is that no
> matter how much we try to disclaim it as "For historic purposes only",
> people will see such Notes and expect them to be implemented / ask
> that they be implemented, when it's very clear they won't be.
There's two classes of algorithms:
1) Ones that *may* or even *likely* will have two interoperable
implementations in the future (RSA-PSS for example)
2) Others than may *never* be implemented.
If folks want to keep the the second out, just mention which ones you
think they are and we can keep them out the Proposed Note.
cheers,
harry
>
> On Sat, Oct 31, 2015 at 9:57 AM, GALINDO Virginie
> <Virginie.Galindo@gemalto.com <mailto:Virginie.Galindo@gemalto.com>>
> wrote:
>
> Dear all,
>
> This email is triggering a call for consensus, based on the recent
> discussions we had with working groups members. It addresses how
> the WG will handle the algorithms removed from the Web Crypto API,
> and the new algorithms foreseen to be integrated in the main Web
> Crypto API specification.
>
> One should note that using the method of a "Proposed Edited
> Recommendation", we can continue to edit the WebCrypto API to add
> new algorithms in after the Spec has reached Recommendation
> without going all the way back to a new Working Draft but simply
> returning to a new Proposed Recommendation [1].
>
> Your answer to the following proposal are expected by the 15th of
> novembre, 23:59 UTC.
> If no objection is received, the proposal will be endorsed.
>
> We are suggesting the Working Group take up a new
> *non-Recommendation* specification called "Proposed Algorithms for
> Web Cryptography API Note", which will be a container for the
> algorithms not integrated in the Web Crypto API.
>
> Like any other non-Rec Note, the document is to have this text
> attached:
> "Publication as a Working Group Note does not imply endorsement by
> the W3C Membership. This is a draft document and may be updated,
> replaced or obsoleted by other documents at any time. It is
> inappropriate to cite this document as other than work in progress."
>
> The Proposed Algorithm Note is to be composed of algorithms
> removed from the Web Crypto Candidate Recommendation and any
> additional specifications that the Working Group believes are
> well-defined but have not yet demonstrated two interoperable
> implementations. Once any algorithm in the Proposed Algorithm Note
> has two interoperable implementations *and* is judged to be
> sufficiently mature in terms of specification, the algorithm can
> be added to the Web Crypto API by the editors of the Web Crypto API.
>
> This will likely be the main activity of the Working Group after
> the Web Crypto API goes into Recommendation status and the Web
> Crypto Working Group is moved into 'maintenance mode.'
>
> Virginie & Harry
>
> ------------------------------------------------------------------------
> This message and any attachments are intended solely for the
> addressees and may contain confidential information. Any
> unauthorized use or disclosure, either whole or partial, is
> prohibited.
> E-mails are susceptible to alteration. Our company shall not be
> liable for the message if altered, changed or falsified. If you
> are not the intended recipient of this message, please delete it
> and notify the sender.
> Although all reasonable efforts have been made to keep this
> transmission free from viruses, the sender will not be liable for
> damages caused by a transmitted virus.
>
>
Received on Sunday, 1 November 2015 15:27:32 UTC