Mike, The latest draft is in deed 6 months old. What's left is a resolution on recommended proxy certificate logic. To avoid any confusion, let's continue any work with the OCSP requirements draft found at http://forge.ggf.org/projects/caops-wg/ : - Click on "Document Manager" (left menubar, need to login in order to see it) - Click on "Working Drafts" (center frame) I suggest that a teleconf is organized in order to sort out what was said at GGF15. How about Monday at 18:00 UTC? (7pm central Europe, 9am US pacific) /Olle On Jan 18, 2006, at 20:00, Mike Helm wrote:
This is a set of pointers to where/when OCSP discussion has taken place on the CAOPS mailing list. I think that this list is public, and easily accessible, so I will not repost it.
I think the most interesting material is in the May-June block, and Jesus Luna's most recent comments at the end of Oct. More on this later.
Apr 2005 http://www-unix.gridforum.org/mail_archive/caops-wg/2005/04/ msg00001.html [MS's version of document pre GGF-14]
May-June 2005 http://www-unix.gridforum.org/mail_archive/caops-wg/2005/05/ maillist.html http://www-unix.gridforum.org/mail_archive/caops-wg/2005/06/ maillist.html [All the content of the mailing list in May, and most in June, was OCSP]
Sep-Oct 2005 http://www-unix.gridforum.org/mail_archive/caops-wg/2005/09/ msg00000.html http://www-unix.gridforum.org/mail_archive/caops-wg/2005/10/ msg00001.html [launch of certiver-related open OCSP Java client API and OCSP service; see note below]
Oct 2005 http://www-unix.gridforum.org/mail_archive/caops-wg/2005/10/ msg00097.html http://www-unix.gridforum.org/mail_archive/caops-wg/2005/10/ msg00098.html http://www-unix.gridforum.org/mail_archive/caops-wg/2005/10/ msg00099.html http://www-unix.gridforum.org/mail_archive/caops-wg/2005/10/ msg00100.html [Set of comments from JL about OCSP proxy cert issues, responding to issues raised in earlier discussion & at GGF]
Frank Siebenlist discussed the client API licensing with CertiVeR, and as I understand it they have agreed to change the licensing to an Apache-like license; this would allow "vendors" like Globus and perhaps other middleware packagers to incorporate and use the source code. [Or so I understand it.]
There are probably some other sideways discussions that didn't take place completely or at all on the CAOPS list which could be useful. I don't think I will look any deeper but if any issue has been missed please bring it up.
Thanks, ==mwh Michael Helm ESnet/LBL