Re: New Work Item Proposal: Revocation List 2020

> 
> Nikos, could you please raise an issue on the spec so we can track that
> we need to cite these class of papers in the spec?

Done. It is issue #3
> 
> It's worth mentioning that this mechanism dates back decades, so I'm
> wondering what the new finding the paper cited is presenting? Nikos, do
> you know?
> 

Each CA maintains a different revocation bitvector per date. Each certificate belongs to the bitvector that corresponds to the certificate's expiration date. So suppose that a CA has generated 1K certificates that expire the same date, a client that wishes to verify the status of one of them will download in the worst case 1K bits. 

Best,
Nikos