Re: Why is the crlNumber an OCTET STRING?

Russ Housley <[email protected]> writes:

>The CRL number is helpful in any situation where the CRL issuer produces CRLs
>with different scopes.

How would the crlNumber help there?  And in particular, since thisUpdate is a
monotonically increasing sequence number, why is there a need for a second
parallel monotonically increasing sequence number?  It looks like an easy way
to implement crlNumber is:

  crlNumber := thisUpdate;

Which, in effect, is what the 8601-based implementation that's causing the
problem is doing, it's literally just copying the value of thisUpdate into
crlNumber.

Peter.