On 02/13/2009 05:56 PM, Ian G:
But it isn't me that sets the criteria, it is in this case ETSI, and the *policy* clearly says that ETSI is acceptable, and apparently ETSI say non-publication is ok. So you either have to take it up with ETSI (good luck) or you have to add a new policy or practices point which says that regardless of ETSI, the CPS must be published.
I suggest Frank reconsiders this as well. I'm in favor to requiring publishing the CPS regardless of what ETSI has to say. It would make everything a lot easier on Mozilla's part and it's accepted practice really.
On the other hand we can live with alternative and confirmed information too, I'm not sure if it's worth the effort though.
-- Regards Signer: Eddy Nigg, StartCom Ltd. Jabber: start...@startcom.org Blog: https://blog.startcom.org -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
