Hi Here are some minor changes you may want to consider making in the document. All the best Matt Abstract ...or otherwise invalid certificates from *being used*. ...OCSP services must be discoverable, fault tolerant and *have* low latency. 2. Introduction ...for relying parties to perform revocation *checks on* certificates... 3. Practical Considerations and Expectations ...presents a *scalability* problem... 3.1 Certificate Revocation Lists ...somewhat like *a trusted* responder)... 7.1.2 OCSP Clearing house In order for such a service to be *trustworthy*... 9 Other Considerations (I feel the first sentence is rather clunky - perhaps something like the following is better) While OCSP as a technology has been around for several years, *it has yet to make a significant impact to the Grid community.* On Wed, 2006-03-22 at 18:11 +0100, Oscar Manso wrote:
Dear all, We attach the last review of the document in the usual formats. .doc with track changes and .pdf with all the changes being accepted. A summary of introduced changes can be found at the end of the document. We would like to remind Milan to introduce his contact data.
Oscar and Jesus
-- Matthew Viljoen CCLRC e-Science Centre Rutherford Appleton Laboratory Tel: +44 (0) 1235 778144 E-mail: m.j.viljoen@rl.ac.uk Web: http://www.e-science.clrc.ac.uk/web/staff/matthew_viljoen