ACTION-56: Propose text on enabling auditing compliance
Propose text on enabling auditing compliance
- State:
- closed
- Person:
- Kevin Trilli
- Due on:
- February 1, 2012
- Created on:
- January 25, 2012
- Associated Issue:
- ISSUE-21
- Related emails:
- post-call housekeeping & upcoming discussions (from aleecia@aleecia.com on 2012-04-18)
- agenda: 18 April 2012 call (from aleecia@aleecia.com on 2012-04-18)
- Agenda for 2012-Mar-21 call (from aleecia@aleecia.com on 2012-03-21)
- RE: DNT Compliance and Audit Services (ACTION-56, ISSUE-21) (from jccannon@microsoft.com on 2012-02-06)
- Re: DNT Compliance and Audit Services (ACTION-56, ISSUE-21) (from tom@mozilla.com on 2012-02-03)
- RE: DNT Compliance and Audit Services (ACTION-56, ISSUE-21) (from wileys@yahoo-inc.com on 2012-01-31)
- DNT Compliance and Audit Services (ACTION-56, ISSUE-21) (from ktrilli@truste.com on 2012-01-31)
Related notes:
From 18 April call: Kevin can live with an optional array of URLs for the company or companies that performed auditing. Tom can live with adding that one optional field to the current work on response header/well-know URI.
[We all agreed that the TSL language was an unfortunate merge of words, and actually was not meant to reference TSLs as we think of them, was just to be a list. But that's all moot now anyway.]
This is now covered by action-185, and is now a TPE issue, no longer compliance.
Display change log.