We followed the same spec on the Google side (obviously). Our implementation of the request encapsulation/decapsulation for OHTTP is open sourced in Google Quiche.…
That's the general idea. We're trying to limit the amount of abuse a single Google Account, device, or other first-party identity can cause. We have some more ideas and details we hope to share over time, but the goal…
Correct. You can see exactly how we're constructing the messages here: https://source.chromium.org/chromium/chromium/src/+/main:ser... Note that in addition to normal HPKE we're also adding a Date header to the…
You bring up an excellent point, and it’s something we really should discuss in our explainer: https://github.com/WICG/turtledove/blob/main/FLEDGE_k_anonym... We’ve been calling this problem key consistency, basically…
We followed the same spec on the Google side (obviously). Our implementation of the request encapsulation/decapsulation for OHTTP is open sourced in Google Quiche.…
That's the general idea. We're trying to limit the amount of abuse a single Google Account, device, or other first-party identity can cause. We have some more ideas and details we hope to share over time, but the goal…
Correct. You can see exactly how we're constructing the messages here: https://source.chromium.org/chromium/chromium/src/+/main:ser... Note that in addition to normal HPKE we're also adding a Date header to the…
You bring up an excellent point, and it’s something we really should discuss in our explainer: https://github.com/WICG/turtledove/blob/main/FLEDGE_k_anonym... We’ve been calling this problem key consistency, basically…