standardization
play

Standardization: W3C & IETF Alex Fowler, Global Privacy & - PowerPoint PPT Presentation

Standardization: W3C & IETF Alex Fowler, Global Privacy & Public Policy Leader, Mozilla W3C Web & User Privacy Tracking Workshop April 29, 2011 Why standardize? What should get standardized? Should standards groups define policy?


  1. Standardization: W3C & IETF Alex Fowler, Global Privacy & Public Policy Leader, Mozilla W3C Web & User Privacy Tracking Workshop April 29, 2011

  2. Why standardize? What should get standardized? Should standards groups define policy? 04/2011 | Page 2

  3. Why standardize? Find consensus among stakeholders in open/public forum Define outcomes and understand tradeoffs Reduce complexity (consumer values, business practices, technology) Leverage past experiences and lessons learned Foster interoperability and consistent user experience Simplify implementation for developers and IT groups Define compliance and enforcement 04/2011 | Page 3

  4. What should get standardized? Tracking White Response Protection Listing Header Capability Lists DNT Compliance/ DOM Header Audit 04/2011 | Page 4

  5. Should standards groups define policy? We do have the expertise We don’t have full range of stakeholders 04/2011 | Page 5

  6. IETF submission on DNT IETF Draft Proposal, “Do Not Track: A Universal Third-Party Web Tracking Opt Out,” March 7, 2011, jointly submitted with Jonathan Mayer and Arvind Narayanan of Stanford’s Center for Internet and Society • defines the syntax and semantics of HTTP header-based mechanism for DNT, and • specifies how web services should respond to such a mechanism All dimensions are up for discussion and we welcome suggested improvements! 04/2011 | Page 6

  7. TPLs & DNT header TPLs are independent from the DNT header and DOM element: • Goals and effects of the technologies seem to be quite different • TPLs affect how clients interpret and access content, while DNT header and the DOM element ultimately affect what servers do to preserve privacy • Standardization needs are very different (e.g., TPLs are about list syntax, DNT is about protocol design) 04/2011 | Page 7

  8. DNT across two standards groups IETF W3C • Standards-track • TPL working specification of group, with DOM DNT HTTP subcommittee at header W3C • IETF generally • considerable maintains change experience control over HTTP working on protocol privacy-related standards • Public forum 04/2011 | Page 8

  9. Possible division of work Tracking White Response Protection Listing Header Capability Lists DNT Compliance/ DOM Header Audit 04/2011 | Page 9

  10. Thank You. Alex Fowler 415 309 3712 afowler@mozilla.com 04/2011 | Page 10

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend