Re: [lamps] [EXTERNAL] Re: [CMP Updates] Requesting a current CRL

[Russ Housley <[e-mail]>]

This is an interesting observation, but it does not seem to cover a certificate with multiple CRL distribution points, indirect CRLs, and delta CRLs.  I'm not sure we want all of that complexity here.  That said, it does make sense to me to list a distribution point name and the thisUpdate for each one.

CRLStatusList ::= SEQUENCE OF CRLStatus

CRLStatus ::= SEQUENCE {
   crldpn    DistributionPointName,
   thisUpdate    Time }

CRLs ::= SEQUENCE OF CertificateList

   GenMsg:    {id-it TBD}, CRLStatusList
   GenRep:    {id-it TBD}, CRLs  |  < absent >

Russ


> On Oct 8, 2021, at 4:10 PM, Lijun Liao <[e-mail]> wrote:
> 
> Please also consider the following some complicated scenarios:
> 
> 1. The CA may have multiple CRLs with different scopes. In RFC 4210, id-it 6
> seems to work only for the CA with maximal one CRL scope.
> 
> 2. The CA may issue full CRL and delta CRLs. Between the period of two full
> CRLs, one or more delta CRLs will be issued.
> 
> Specifying only thisUpdate does not cover above scenarios, I will suggest to
> define a new GenMesage (following the direction of Option B) as follows:
> 
> New Section
> 5.3.19.x Extended CRL Retrieval
> 
> CRLGenMsg: {id-it TBD}, ExtendedCRLRetrieval
> 
> ExtendedCRLRetrieval ::= SEQUENCE {
>    lastCRL    LastCRL OPTIONAL, 
>               -- the meta data of last CRL known to the client 
>    crlNumber  INTEGER OPTIONAL
>               -- only CRL with this number will be returned
> }
> 
> LastCRL ::= SEQUENCE {
>    thisUpdate          TIME,
>    sha256DigestValue   OCTET STRING
>                        -- SHA256 Fingerprint of CRL
> }
> 
> GenRep: {id-it TBD}, SEQUENCE (0..MAX) OF CertificateList
>                      -- The CA may have multiple CRLs with different scopes 
> 
> At the first time, the client sends an ExtendedCRLRetrieval with an empty
> SEQUENCE, and the CA returns the current CRLs of all scopes.
> 
> For the case without delta CRL, the client sends the following request to
> get the current CRL only if it is generated after the lastCRL.
> 
> ExtendedCRLRetrieval
>    lastCRL
>        thisUpdate
>        sha256DigestValue
> 
> The field sha256DigestValue is needed to identify the scope of CRL.
> 
> If the current CRL is a delta CRL, the client has to get the full CRL on
> which this delta CRL bases on. It sends the following request:
> 
> ExtendedCRLRetrieval
>     lastCRL   -- required only if there is more than 1 scope, since
>               -- RFC 5280 allows two CRLs with different scopes to have
>               -- the same crlNumber
>     crlNumber 
> 
> 
> Since the response is a sequence of CertificateList, option 1A cannot be
> applied here.
> 
> Lijun
> 
> On Fri, Oct 8, 2021 at 6:41 PM Russ Housley <[e-mail] <mailto:[e-mail]>> wrote:
> 
> 
>> On Oct 8, 2021, at 12:36 PM, Brockhaus, Hendrik <[e-mail] <mailto:[e-mail]>> wrote:
>> 
>> My question is, is it OK to reuse id-it-currentCrl together with id-it-crlThisUpdate like this
>> 
>>    GenMsg:    {id-it 6}, < absent >
>>    GenRep:    {id-it 6}, CertificateList  |  < absent >
> 
> Yes, because <absent> is exactly the same response that would be given if {id-it 6} is unrecognized by the server.
> 
> Russ
> _______________________________________________
> Spasm mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/spasm <https://www.ietf.org/mailman/listinfo/spasm>
> 
> 
> -- 
> Lijun Liao