Randomize ESR "status" frequency and request size
this issue is related to https://github.com/ROBERT-proximity-tracing/documents/issues/20
"status" is done at fix 1 day frequency :
This may allow to track when the user is doing a "report" as this message would likely be an out of 1 day sync request "erase" , "unregister" or "deleteExposureHistory"
Request frequency should be randomized as well as request volume by adding padding data as (as far as i know) TLS is not hiding stream volume.
Other protocols such as DP-3T address this request size analysis issue (https://github.com/DP-3T/documents/blob/master/DP3T%20-%20Data%20Protection%20and%20Security.pdf p9)
or address it as a valid threat :