- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The paper proposes a federated learning framework for clients with heterogeneous differential-privacy budgets and operational policy constraints. Its main idea is to compute a policy-residual score for each locally trained model and use this residual, rather than data volume alone, to determine aggregation weights, while retaining client-specific record-level DP guarantees.
Critical strengths
- The paper identifies an interesting distinction between numerical DP budgets and satisfaction of broader operational privacy policies, and the policy-residual aggregation mechanism is conceptually clear.
- The theoretical treatment covers residual ordering and DP guarantees for both disjoint and overlapping client data, while experiments compare against several recent private-FL baselines on two datasets.
Critical weaknesses
-
The practical motivation for heterogeneous privacy requirements needs to be considerably strengthened. The framework assumes that collaborating clients can operate with materially different privacy budgets and policy targets. While technically possible, such unequal privacy protection may be difficult to justify in a real multi-organisation collaboration, particularly where participants jointly contribute to the same global model. The paper motivates this through “GDPR-, PIPL-, and HIPAA-inspired” profiles, but also acknowledges that the numerical targets are not prescribed by these regulations and would need to be configured by individual organisations. This leaves an important practical question: under what realistic governance scenario would collaborating organisations accept substantially different protection levels rather than adopting a mutually agreed minimum protection level?
-
All major experiments use only three clients with one fixed privacy-budget configuration, (1,2,3). This same configuration is used across the principal baseline comparisons, and even the detailed privacy-accounting appendix only verifies realised privacy losses for these three values. The paper therefore does not show how FedPRA behaves as either the absolute privacy levels or the degree of heterogeneity changes. A more convincing evaluation should vary the privacy-budget configurations, e.g., homogeneous versus mildly and strongly heterogeneous settings, and report the resulting global-model utility, worst-client utility, residuals and privacy guarantees.
Questions for authors
-
What realistic cross-organisation deployment scenario motivates allowing participants to adopt substantially different DP budgets and operational privacy targets? How would fairness and governance concerns arising from unequal privacy protection be resolved?
-
How sensitive is FedPRA to the magnitude and heterogeneity of the privacy budgets? Could the authors evaluate several configurations and show how global utility, worst-client performance, policy residuals and the overall DP guarantee vary?
-
Since the current results combine heterogeneous DP budgets, policy-aware local training, class reweighting/resampling and residual-based aggregation, can the authors more clearly isolate the privacy–utility trade-off attributable specifically to heterogeneous privacy protection?
Paper Summary
This paper identifies a potential mismatch between privacy-budget ordering and policy-satisfaction ordering in federated learning. To address this issue, the authors propose FedPRA, a framework that combines a differentiable policy engine with policy-residual aggregation.
Strengths
Weaknesses
Review Summary
FedPRA identifies a potentially meaningful problem and proposes a corresponding solution. Overall, this is a relatively solid manuscript with a clear framework and encouraging experimental results. However, I have broad familiarity with this field but little direct research experience on this specific topic. After reading the other reviewers' comments, I found that they raised several similar and more insightful concerns. Taking these considerations into account, I would personally lean toward a weak rejection.