Hi Manuel,
I know this is old, but it still comes up as one top results on some searches about PKI, so I just wanted to leave a short answer.
Best practice is http and not https. When checking documentation like the one Fan Fan linked above, you will also always find only http in the CDP links.
I don't have a source in writing for as to why this is, but it's kind of a logical issue about how CRLs work. (and the same why OCSP also only uses http and the special OCSP signing certs have an extension that says "do not check revocation for this cert)
A client wants to access a webserver that uses one of your CAs' certs for https. It then has to check the revocation. For that, it accesses the CRL - also a WebServer. Now, if it would use https for the CRL, it would get shown a TLS cert from the WebServer that hosts the CDP. Then, it would need to check the revocation of THIS cert. For that, it looks into the cert, gets the CDP URL, connects to check the CRL - and is again on https, sees a Webserver cert, has to check its CRL, and so on and so on ... So, unless you use a cert from a different CA (with a differen CDP) or a public cert for your CRP, you potentiall shoot your clients into a vicious circle of revocation checkings they can't escape from ...