W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > October to December 1999

RE: xmldsig questions

From: Phillip M Hallam-Baker <pbaker@verisign.com>
Date: Tue, 21 Dec 1999 10:24:28 -0500
To: "Barb Fox (Exchange)" <bfox@Exchange.Microsoft.com>, "'Joseph M. Reagle Jr.'" <reagle@w3.org>, "Frederick Hirsch" <hirschf@CertCo.com>
Cc: <w3c-ietf-xmldsig@w3.org>, "John Boyer" <jboyer@uwi.com>, "David Solo" <david.solo@citicorp.com>
Message-ID: <004e01bf4bc7$78d40840$6e07a8c0@pbaker-pc.verisign.com>
> >4. In section 3.4, KeyInfo, I note that the spec allows including a
> >CRL, with element X509CRL. Can we also define including signed OCSP
> >responses, with an X509OCSP element? This would allow transmitted the
> >status of the certs with a transaction in an interoperable manner.

>David, Barbara, others?
>(Barb) X509OCSP: This isn't a big deal to add, but it has the potential to
open a
>can of snakes that we've carefully tried to avoid, "freshness of
certificates." We
>don't require certificates in XML signatures. They're just one form of
>that MAY be provided by a signer to a verifier. Attaching an OCSP response
>be considered additional evidence. What we want to avoid tho is our making
>implied recommendations about signers having to get and attach OCSP
responses (or
>certs, for that matter) to their signed documents. An OCSP response in
>seems pretty silly since if a verifier wants freshness information about a
>certificate, he can get his own OCSP response.

Actually I would avoid the construct for a quite different reason. OCSP
responses are mainly constructed on an ad-hoc basis in response to an
actual request. I don't see particular value in embedding ASN.1 structures
of that type in XML documents. The OCSP server should have the manners
to deliver the data in XML syntax.

So while I think there is a value in incorporating an OCSP token in a sig
package I don't think we want to assume that it will be PKIX OCSPv1 in
ASN1 format. In fact one of the original reasons for supporting a variant
response syntax in OCSP was to allow an XML reply.

In fact I have recently been rewritting OCSP-X to exclude the
Authorization functionality and rolled that into an XML based OCSP draft
for experimental track just so it does not get patented by some louse.
[Don't expect the drafts till I have spare time to finish 'em though]

Received on Tuesday, 21 December 1999 10:23:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:21:32 UTC