In the discussion of a cookie based consent mechanism, it does not address the impact that blocking third party cookies can have in such systems.
To address this, I propose changing "Even if this can be done in a scalable way, for example by editing the target URL with a mutually agreed encoding, the third-party could not persist it in one of its own cookies, because even if cookies were not blocked the tracking data would then be available web-wide, i.e on any site which embedded the same third-party.” to “While consent for a third-party could be stored by editing the target URL with a mutually agreed encoding, storing it in a cookie would make it available web-wide, i.e. on any site which embedded the same third-party. In addition, a cookie based solution does not address users that configure their user agents to reject all third party cookies or browsers that block third party cookies by default.”
In the discussion of a cookie based consent mechanism, it does not address the impact that blocking third party cookies can have in such systems.
To address this, I propose changing "Even if this can be done in a scalable way, for example by editing the target URL with a mutually agreed encoding, the third-party could not persist it in one of its own cookies, because even if cookies were not blocked the tracking data would then be available web-wide, i.e on any site which embedded the same third-party.” to “While consent for a third-party could be stored by editing the target URL with a mutually agreed encoding, storing it in a cookie would make it available web-wide, i.e. on any site which embedded the same third-party. In addition, a cookie based solution does not address users that configure their user agents to reject all third party cookies or browsers that block third party cookies by default.”