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

Started glossary #74

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

degregat
Copy link
Contributor

No description provided.

@hdevalence
Copy link
Collaborator

The table format is great but I worry about introducing an extra set of terms for the common functionality. Since the keys aren't actually used in precisely the same way in each scheme, I think that there's not a precise definition of what each of the new terms are, which makes me worried about introducing them. But the functionality is clearly analogous, so maybe just not including the first column of the table would highlight the similarity without having to define new terms?

@degregat
Copy link
Contributor Author

I'm fine with that. I think it would help to be able to refer to it from the high level blocks, so just a numbering for that column?

@Vanuan
Copy link

Vanuan commented Apr 22, 2020

Some additional terms

A/G DP-3T PACT (MIT) PACT (UW) TCN Description
Broadcasting rotation interval, based on Bluetooth MAC address change interval Epoch length, variable Same as Interval Secret rotation Pseudorandom Identifier Rotation Interval
Diagnosis key Exposed key, known case key Report Key(s) shared publicly and synced locally
Contact Matching contact, known case key Doesn't specify matches Local match of a key shared publicly to a set of encountered pseudorandom identifiers

@Vanuan
Copy link

Vanuan commented Apr 22, 2020

I worry about introducing an extra set of terms for the common functionality

Maybe this column should be renamed to "description/definition" and moved to the right side?

@degregat
Copy link
Contributor Author

degregat commented Apr 22, 2020

Should we say Token, or Pseudorandom Identifier in the building blocks, to be sufficiently general?

@Vanuan
Copy link

Vanuan commented Apr 22, 2020

Maybe "rolling beacon key" is sufficiently non-ambiguous?

Why not just use the TCN term, temporary contact number?

What's the essence of this term?

  • it has a short lifetime (temporary, rolling)
  • it's broadcast to nearby devices (proximity, beacon, device)
  • it may serve as an identifier of an event, time duration, device (device id, encounter/contact id, handshake key)
  • it may be calculated from the underlying identifier
  • it is globally unique per infectious period

Some other ideas:

  • rolling device id
  • proximity id
  • contact event key

@Vanuan
Copy link

Vanuan commented Apr 26, 2020

Google has renamed to DailyTracingKey to TemporaryExposureKey

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

Successfully merging this pull request may close these issues.

3 participants