Re: [IETF-PKIX] OCSP at IETF

[Michael Myers <mmyers@xxxxxxxxxxxx>]

I agree.  In fact, I had some archive language in an earlier draft.  So
shall it be written--as an optional extension.



> -----Original Message-----
> From: IETF X.509-based public key infrastructure mailing list
> [mailto:IETF-PKIX@LISTS.TANDEM.COM]On Behalf Of Jeff Weinstein
> Sent: Friday, April 17, 1998 1:58 AM
> To: IETF-PKIX@LISTS.TANDEM.COM
> Subject: Re: [IETF-PKIX] OCSP at IETF
>
>
> I strongly agree with Stephen on this.  One great value that OCSP
> services could add would be to provide historical as well as current
> revocation information.
>
>         --Jeff
>
> Stephen Farrell wrote:
> >
> > Hi Mike,
> >
> > Not sure if this needs a change, but...
> >
> > Part 1 now has a time input to the cert validation
> > algorithm (the time at which the cert should have been/be
> > valid).
> >
> > If OCSP is to fit seamlessly into this algorithm then you'll
> > need an extension to the request so that the response doesn't
> > refer to the current time, but to the time which was input
> > to the cert validation alg.
> >
> > Regards,
> > Stephen.
>