- From: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
- Date: Mon, 12 May 2014 10:58:47 +0200
- To: Ryan Sleevi <sleevi@google.com>
- CC: "public-webcrypto@w3.org" <public-webcrypto@w3.org>, Harry Halpin <hhalpin@w3.org>
- Message-ID: <239D7A53E5B17B4BB20795A7977613A4022CD7C0451B@CROEXCFWP04.gemalto.com>
Hello Ryan, Sure. Lets me clarify. I used the term ‘Blocking Bug’ in bracket to reflect the level of bug chosen by Rich when filling the bug in bugzilla. This does not give to this bug any super power to block the specification. Instead, I believe that from the process, each bug is blocking the spec to move to next phase of the spec, if it not solved with a resolution which is suitable to the person who raised the bug. Regards, Virginie From: Ryan Sleevi [mailto:sleevi@google.com] Sent: lundi 12 mai 2014 03:37 To: GALINDO Virginie Cc: public-webcrypto@w3.org; Harry Halpin Subject: Re: [W3C Web Crypto WG] Security considerations and recommended algorithms bug Virginie, Can you please comment on what you mean by "Blocking Bug"? That has a very specific connotation within the W3C process. On Fri, May 9, 2014 at 6:12 AM, GALINDO Virginie <Virginie.GALINDO@gemalto.com<mailto:Virginie.GALINDO@gemalto.com>> wrote: Hi all, This is just to bring your attention on the fact that we received a “blocking bug” from Rich Salz and Kenny Patterson about the need to improve our security considerations in Bug 25607 [1] Ryan is working on it, but views/support from all implementers would be helpful … Regards, Virginie [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25607 ________________________________ 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 ________________________________ 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 Monday, 12 May 2014 08:59:12 UTC