Ian G wrote re CPSs not available in English:
Which leads to the first easy fix: insist that all non-english CAs
translate all their docs. Then I can read the CPS! I personally am
unsatisfied at that, I see flaws.
1. Frank has made the case for regional and local CAs. The web is
wide, and CPSs are very long documents. So I think translating *all*
important documents to english is not only impractical but also
discriminatory, as non-english cultures (most of them) will then face a
barrier that the english do not do not.
I'll differ from you somewhat here. As a practical matter browser
vendors are a major audience for a CA's CPS, along with the CA's
auditor, possibly government agencies concerned with the CA's
operations, and whoever else might care to read it. I can understand a
CA issuing its CPS in the native language of the country in which it
operates; that's probably the best strategy to make sure the document is
properly understood by relevant government agencies and by its auditors
(if they're local).
However if a CA doesn't offer an English translation of its CPS and
other relevant documents then it disadvantages browser vendors and other
application software vendors who might be interested in supporting use
of the CA's certificates. I don't support making it mandatory that CAs
provide an English version of the CPS, but I have no problem with
telling CAs that not having an English version will likely cause delays
with their application.
Frank
--
Frank Hecker
hec...@mozillafoundation.org
_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
