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

Proposal: Privacy Preserving Metrics #504

Open
marten-seemann opened this issue Jan 12, 2023 · 0 comments
Open

Proposal: Privacy Preserving Metrics #504

marten-seemann opened this issue Jan 12, 2023 · 0 comments

Comments

@marten-seemann
Copy link
Contributor

I’ve discussed this with various people over the last year or so, but we never wrote up a tracking issue. It’s already part of our roadmap: https://github.com/libp2p/specs/blob/master/ROADMAP.md#%EF%B8%8F-telemetry-protocol.

The proposal is to provide a generalized way to collect metrics that can be used by libp2p services (e.g. hole punching, swarm dialers, etc.) as well as libp2p users. Metrics collection should happen in a privacy preserving way, enabling us to turn on metrics by default without users having to give up their privacy, as would be the case in a more traditional metrics collection system.

There’s interesting work going on in the IETF PPM working group at the moment: They’re working on a protocol where a node reports a measurement value to two separate aggregator nodes (which are assumed to not collaborate). Through some fancy cryptography, the aggregators 1. run some sanity checks on the value (e.g. make sure that it’s within a certain value range) and 2. compute an aggregated value, which, when combined with the value derived by the other aggregator, yields the desired result (e.g. the average value over all measurements).

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

No branches or pull requests

1 participant