Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Which version of ENF is Radar using? #47

Closed
fsbaraglia opened this issue Jan 6, 2021 · 4 comments
Closed

Which version of ENF is Radar using? #47

fsbaraglia opened this issue Jan 6, 2021 · 4 comments

Comments

@fsbaraglia
Copy link

Hola,

I have this statement inside my iPhone :
image

I see as well this in the exposure.json:

{
      "Timestamp" : "2021-01-06 00:29:09 +0100",
      "Files" : [
        {
          "Hash" : "-----xxxxxFBB43",
          "KeyCount" : 355502,
          "AppBundleIdentifier" : "es.gob.radarcovid",
          "Timestamp" : "2021-01-06 00:29:12 +0100"
        }
      ],
      "AppBundleIdentifier" : "es.gob.radarcovid"
    }

but I don't see any risk of exposure in the Radar App.
I am curious to know which version of the Exposure Notification Framework / the Exposure Notification System RADAR is using?

Version 1 or 2?

@pantic79
Copy link
Contributor

pantic79 commented Jan 9, 2021

Hello @fsbaraglia,

currently we are using version 2. Please, consider that a key match could imply a risky situation or not based on the attenuation and exposition duration.

Thanks.

@fsbaraglia
Copy link
Author

fsbaraglia commented Jan 9, 2021

Hi @pantic79 ,

nice, thank you very much for the info.
Interesting. in practice, the attenuation and exposition duration has not qualified the Match, right?
Do you have some official Apple documentation about this?

Thanks

@pantic79
Copy link
Contributor

pantic79 commented Jan 9, 2021

Hi @fsbaraglia,

that's right!.

As far as we are using the DP3T SDK I could refer to this document. It's not recently updated but you could get some useful ideas from it.

Thanks.

@fsbaraglia
Copy link
Author

nothing new, we can close the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants