search

corona-warn-app / cwa-documentation

Project overview, general documentation, and white papers. The CWA development ends on May 31, 2023. You still can warn other users until April 30, 2023. More information:
https://coronawarn.app/en/faq/#ramp_down
Apache License 2.0
3.29k stars 345 forks source link

Is there a "quarantine" period for uploaded DKs? #937

Closed Ein-Tim closed 1 year ago

Ein-Tim commented 1 year ago

Your Question

The following table in the referenced document above includes a description of a profile demo:

Available Profiles

Profile Effect
demo Includes incomplete days and hours into the distribution run, thus creating aggregates for the current day and the current hour (and including both in the respective indices). When running multiple distributions in one hour with this profile, the date aggregate for today and the hours aggregate for the current hour will be updated and overwritten. This profile also turns off the expiry policy (Keys must be expired for at least 2 hours before distribution) and the shifting policy (there must be at least 140 keys in a distribution).

It says: "Keys must be expired for at least 2 hours before distribution". Taking this into account, I have two questions:

  1. Is this actually the live configuration of the server?
  2. How does this actually work? This is how I always thought it worked:

Device uploads DKs at 10:00 pm (all keys of the past 14 days are uploaded, the key from today will be uploaded as soon as the day is over) -> Server receives the keys -> Keys are put into "quarantine" for two hours before distribution (no download by client apps possible) -> 2 hours pass, the keys go out of "quarantine" and can be downloaded by client apps

But I think this is actually wrong and it should be like this: Device uploads DKs at 10:00 pm (all keys of the past 14 days are uploaded, the key from today will be uploaded as soon as the day is over) -> Server receives the keys -> All keys can instantly be downloaded by client apps, as no keys were uploaded that aren't older than 2 hours

Can you confirm or correct this statement? Thank you!

Ein-Tim commented 1 year ago

@thomasaugsten / @mlenkeit Could you share an answer, please? (-:

mlenkeit commented 1 year ago

@Ein-Tim as the profile name suggests, this is a demo profile with settings that are not meant for production.

The way it works is rather something like this: Device uploads DKs at 10:00 pm (all keys of the past 14 days are uploaded, the key from today will be uploaded as soon as the day is over including the key from today) -> Server receives the keys -> _the keys of the past 14 days are included in the next day/hour package -> 2 hours pass, the key from today is included in the next day/hour package.

I hope this helps to clarify the question!

Happy holidays, Max

Ein-Tim commented 1 year ago

@mlenkeit

That answers the question very well! Thank you, Max, and have relaxing & happy holidays!