-
Notifications
You must be signed in to change notification settings - Fork 25
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
Update protocol to generically allow >1 helper #117
Comments
This seems to be a dupe fo #68 -- can we close? |
Per discussion in the call today, I think this issue is about updating the various PDU definitions to allow for multiple helpers. For instance, |
Modify `struct Param`, `struct Report` and `struct CollectResp` to accommodate more than one helper. Note that the PPM protocol doesn't actually support multiple helpers to enhance privacy (#68) but we nonetheless want to define the PDUs so it is possible to introduce that feature in the future. We do this by introducing an `AggregatorId` type into various struct definitions, allowing participants to tell which aggregator an input share or output share corresponds to. We also introduce a special, reserved value of `AggregatorId` that allows clients to tell which aggregator is the leader to which reports should be uploaded. Finally, we use the aggregator ID in HPKE context construction instead of the existing constants 0x00 and 0x01 for leader and helper, respectively. Along the way, we introduce the `HpkeConfigId` type alias used in few different places. Resolves #117, #133
Modify `struct Param`, `struct Report` and `struct CollectResp` to accommodate more than one helper. Note that the PPM protocol doesn't actually support multiple helpers to enhance privacy (#68) but we nonetheless want to define the PDUs so it is possible to introduce that feature in the future. We do this by introducing an `AggregatorId` type into various struct definitions, allowing participants to tell which aggregator an input share or output share corresponds to. We also introduce a special, reserved value of `AggregatorId` that allows clients to tell which aggregator is the leader to which reports should be uploaded. Finally, we use the aggregator ID in HPKE context construction instead of the existing constants 0x00 and 0x01 for leader and helper, respectively. Along the way, we introduce the `HpkeConfigId` type alias used in few different places. Resolves #117, #133
Modify `struct Param`, `struct Report` and `struct CollectResp` to accommodate more than one helper. Note that the PPM protocol doesn't actually support multiple helpers to enhance privacy (#68) but we nonetheless want to define the PDUs so it is possible to introduce that feature in the future. We also move `task_id` from the HPKE AAD to the context's application info, and introduce the `HpkeConfigId` type alias in a few different places. Resolves #117, #133
No description provided.
The text was updated successfully, but these errors were encountered: