[privacy-request] Issue: Incremental Font Transfer 2024-07-09 (#140) marked as REVIEW REQUESTED

svgeesus has just labeled an issue for https://github.com/w3cping/privacy-request as "REVIEW REQUESTED":

== Incremental Font Transfer 2024-07-09 ==
The Privacy IG prefers groups to complete a self-review around the time of FPWD. See https://w3ctag.github.io/security-questionnaire/.

- name of spec to be reviewed: Incremental Font Transfer
- URL of spec: https://www.w3.org/TR/2024/WD-IFT-20240709/
- Does your document have an in-line Privacy Considerations section, ideally one separate from Security Considerations?  If not, correct that before proceeding further.
  - Yes
- Do you need a reply by a particular date?
  - No
- Please point to the results of your own self-review (see https://w3ctag.github.io/security-questionnaire/ , https://w3c.github.io/fingerprinting-guidance/, https://tools.ietf.org/html/rfc6973)
  - https://github.com/w3c/IFT/issues/194
- Where and how to file issues arising?
  - As individual issues on [our GitHub](https://github.com/w3c/IFT), please
- Pointer to any explainer for the spec? https://github.com/w3c/IFT/blob/main/IFT-Explainer.md

Other comments:

This new draft addresses review feedback from the earlier proposals. There is no longer a Range Request vs Patch Subset choice, and there is no longer any special protocol required. The client no longer sends individual, possibly trackable requests to the server for a patch specific to the current user. Instead, it selects from pre-generated patches, which are the same for all users. Compared to the earlier proposals, the risks of fingerprinting have thus been reduced and there should also no longer be an impact on CDN caching.


See https://github.com/w3cping/privacy-request/issues/140


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 24 July 2024 12:56:20 UTC