- From: Lee Tien <tien@eff.org>
- Date: Tue, 25 Jun 2013 18:50:46 -0700
- To: "public-tracking@w3.org public-tracking@w3.org" <public-tracking@w3.org>
I am not sure the June Draft addresses these, but this is what I propose--not sure where they go. 132 An intermediary or hosting provider MUST NOT modify a DNT signal. 151 A user agent MAY implement the exception API. 153 Software that modifies, but does not initiate, a network interaction MUST adhere to the same standards as software that initiates a network interaction. (This is scoped as follows according to the issue tracker: “Cases out of scope of this issue: - Browser plugins are not considered since they are part of the UA - SW that modifies the browser behavior (e.g., via registry changes) is technically also part of the UA (should the UA protect itself?) Use cases considered were: - A proxy DNT handler for non-DNT browsers - An enterprise proxy that implements a corporate policy - A home router that handles DNT for a family - A internet provider intermediary (configurable by subscribers) that implements DNT within the network”) -- Lee Tien Senior Staff Attorney Electronic Frontier Foundation 815 Eddy Street San Francisco, CA 94109 (415) 436-9333 x 102 (tel) (415) 436-9993 (fax) tien@eff.org
Received on Wednesday, 26 June 2013 01:51:15 UTC