[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: OCSP-X vs SCVP
Michael Zolotarev wrote:
>
> > But that ain't how the world works, and
> > that ain't how
> > people want it to work.
>
> Proof, please. I want the proof.
>
The fact that people seem to care about this is proof enough for me...
> As one of the vendors, I dare to claim that it absolutely does not matter
> for *a vendor* whether to deal with ASN1 or XML. There are other problems to
> tackle, much more serious, than specifics of the encoding. And every vendor
> has tools to handle encoding. There are tools for XML, and tools ASN. You
> want one - ask me. Nobody starts from scratch.
It seems to me that many *non-vendors* might want to implement the protocol.
But I see your point. You weren't talking about an OCSP API, but instead an
ASN.1 (as opposed to XML) API. At that level, I agree: people can pick up
toolkits to work with either.
Many, though, seem to be reluctant to have to work with both. I suppose
there this is where the crux of the issue lies. Most PKI folk work in ASN.1,
while many non-PKI folk use XML. The non-PKI folk want their XML apps to use
PKI (as do the PKI folks, I might add), but they don't want to bloat their
apps with an ASN.1 toolkit. Similarly, the PKI folk don't want to bloat
their apps with an XML toolkit.
Either some non-PKI folk have to want PKI badly enough to accept the bloat,
or the PKI folk have to want to spread PKI badly enough to adopt XML. Either
way, someone has to give.
Marc
+------------------------------------------------------------------------+
Marc Branchaud \/
Chief PKI Architect /\CERT INTERNATIONAL INC.
marcnarc@xcert.com PKI References page: www.xcert.com
604-640-6227 www.xcert.com/~marcnarc/PKI/
+------------------------------------------------------------------------+