In the space domain, satellite ground systems have used a combination of guards, one way transmission, and others, although I am in favor of system-specific certificate whitelisting via running OCSP with local VAs, backed up by smart clients, with CRLs on the filesystem and in network shares.
CRL processing can cause timeouts, which is why it is always less preferred than the much more lightweight OCSP by comparison.
Furthermore, CRLs are blacklists, and newer OCSP is not exclusively, and, OCSP permits more flexibility with the various trust models that exist for it.
CRLs and OCSP are about individual certificates.
The beauty of Merkle Hash Trees for validation is it permits Statements e.g.
CAx = CA2 and 156 ≤ X < 343 (5)
The statement cj indicates that the certificate with serial number X = 156 issued by CA2 has been revoked, while the certificates with serial numbers from X = 157 to X = 343 (both included) issued by CA2 have not been revoked.
From https://www.researchgate.net/publication/220066804_Certifica...
A CRL is not equivalent to modern OCSP, because modern OCSP can operate as a whitelist or a blacklist. However, CRLs are generally more secure than some of the OCSP variants because strong OCSP is used less (Nonced+authenticated/registered), and CRLs are not subject to replay attack like vanilla OCSP can be.