Positive signal from invalid traffic detection providers, though open questions remain about the impact on fraud detection with initial parameter settings. As IP Protection launches, we’ll continue to solicit feedback.
Major unresolved issues with or opposition to this design: None
You should also know that...
This has already come across the desk of the TAG as part of the IP Protection review request (noting some PRT questions asked + answered as part of that).
We're back to give the TAG the opportunity to consider this work separately from the broader IP work (as encouraged by some conversation on the associated blink-dev thread).
The most "separated" view of this work is as an approach to enabling random sampling over an otherwise protected signal. In that vein, we're looking at continuing conversations in an IETF forum based on the IETF draft.
<!-- Content below this is maintained by @w3c-tag-bot -->
OpenedJul 30, 2025
Explainer
https://github.com/GoogleChrome/ip-protection/blob/main/prt_explainer.md
Where and by whom is the work is being done?
Feedback so far
Multi-stakeholder feedback:
Major unresolved issues with or opposition to this design: None
You should also know that...
This has already come across the desk of the TAG as part of the IP Protection review request (noting some PRT questions asked + answered as part of that).
We're back to give the TAG the opportunity to consider this work separately from the broader IP work (as encouraged by some conversation on the associated blink-dev thread).
The most "separated" view of this work is as an approach to enabling random sampling over an otherwise protected signal. In that vein, we're looking at continuing conversations in an IETF forum based on the IETF draft.
<!-- Content below this is maintained by @w3c-tag-bot -->Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1125