W3C home > Mailing lists > Public > public-webcrypto@w3.org > July 2014

[W3C Web Crypto WG] suggested resolution for bug 25985 on browser interoperability

From: GALINDO Virginie <Virginie.Galindo@gemalto.com>
Date: Fri, 25 Jul 2014 21:58:40 +0000
To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
CC: Harry Halpin <hhalpin@w3.org>, Wendy Seltzer <wseltzer@w3.org>
Message-ID: <540E99C53248CE468F6F7702588ABA2AC3669125@A1GTOEMBXV002.gto.a3c.atos.net>
Dear all,

Here is a proposed resolution for the bug 25985 on browser interoperability https://www.w3.org/Bugs/Public/show_bug.cgi?id=25985

Based on the exchanges related to this bug, one possible way to move forward is to define a browser profile after interoperability testing is conducted with
different implementations. This browser profile should be non-normative and should describe the exact behavior of the browser in case part of the algorithms are not available, or partially available, or disabled by the user. As such it is required to treat that bug once implementations have been demonstrated, which means after the call for implementation (see process http://www.w3.org/2005/10/Process-20051014/tr.html#cfi)

Suggested resolution :

The bug stays open, but its resolution is expected to happen after first implementation tests are conducted.

This resolution will be submitted to WG participants vote during our call next Monday as announced over the mailing list [1]



[1] http://lists.w3.org/Archives/Public/public-webcrypto/2014Jul/0016.html

(please ignore statement below)

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 Friday, 25 July 2014 22:00:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:23 UTC