Friday, 30 November 2012
- RE: Sitecom adds Do Not Track to its routers
- Re: Sitecom adds Do Not Track to its routers
- RE: Sitecom adds Do Not Track to its routers
- RE: action-334, issue-112, a summary on sub-domains for exceptions
- RE: action-334, issue-112, a summary on sub-domains for exceptions
- RE: action-334, issue-112, a summary on sub-domains for exceptions
- Re: action-334, issue-112, a summary on sub-domains for exceptions
- RE: action-334, issue-112, a summary on sub-domains for exceptions
- RE: action-334, issue-112, a summary on sub-domains for exceptions
- RE: action-334, issue-112, a summary on sub-domains for exceptions
- Re: action-334, issue-112, a summary on sub-domains for exceptions
Wednesday, 28 November 2012
Thursday, 29 November 2012
- Sitecom adds Do Not Track to its routers
- RE: action-317, discussion of the service-provider flag and the same-party resource & issue-112
- Re: Moving forward
- action-317, discussion of the service-provider flag and the same-party resource
Wednesday, 28 November 2012
- RE: action-334, issue-112, a summary on sub-domains for exceptions
- RE: action-334, issue-112, a summary on sub-domains for exceptions
- RE: action-334, issue-112, a summary on sub-domains for exceptions
- RE: action-334, issue-112, a summary on sub-domains for exceptions
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: action-334, issue-112, a summary on sub-domains for exceptions
- action-334, issue-112, a summary on sub-domains for exceptions
- Re: Moving forward
- Re: Moving forward
- RE: Moving forward
- Re: Moving forward
- Moving forward
Tuesday, 27 November 2012
- RE: ISSUE-112 - was Agenda
- Re: Agenda for 28 November 2012 call - V02
- ISSUE-112 - was Agenda
- Agenda for 28 November 2012 call - V02
Sunday, 25 November 2012
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: Agenda for 28 November 2012 call - V01
- Agenda for 28 November 2012 call - V01
Friday, 23 November 2012
Thursday, 22 November 2012
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- tracking-ISSUE-189 (EUConsent): Explicit informed consent mechanism needed [Global Considerations]
Wednesday, 21 November 2012
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- ISSUE-188 UK ICO published anonymization guide
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- DNT humor for the holidays
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: navigator.doNotTrack
Tuesday, 20 November 2012
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
Monday, 19 November 2012
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- No call this week, TPE next week
- RE: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- ISSUE-64 Re: Proposals for Compliance issue clean up
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
Sunday, 18 November 2012
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
Saturday, 17 November 2012
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
Friday, 16 November 2012
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: action-324, public compliance texts (issue-45)
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
Thursday, 15 November 2012
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: ACTION-286: Propose DAA text regarding de-identification (for unlinkability discussion)
- RE: ACTION-286: Propose DAA text regarding de-identification (for unlinkability discussion)
- Re: ACTION-286: Propose DAA text regarding de-identification (for unlinkability discussion)
- Re: ACTION-286: Propose DAA text regarding de-identification (for unlinkability discussion)
- Re: ACTION-286: Propose DAA text regarding de-identification (for unlinkability discussion)
- Re: ACTION-286: Propose DAA text regarding de-identification (for unlinkability discussion)
- Re: ACTION-286: Propose DAA text regarding de-identification (for unlinkability discussion)
- Re: ACTION-286: Propose DAA text regarding de-identification (for unlinkability discussion)
- Re: ACTION-286: Propose DAA text regarding de-identification (for unlinkability discussion)
- Re: ACTION-286: Propose DAA text regarding de-identification (for unlinkability discussion)
- ACTION-286: Propose DAA text regarding de-identification (for unlinkability discussion)
Wednesday, 14 November 2012
- proposal ISSUE-188 ("unlinkable"): 3.6.2 - "1024-unlinkable"
- proposal ISSUE-188 ("unlinkable"): 3.6.1 - "render unlinkable"
- tracking-ISSUE-188 (unlinkable): Definition of unlinkable data [Tracking Definitions and Compliance]
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: Next f2f and charter issues
- Re: Next f2f and charter issues
- Re: Next f2f and charter issues
- Next f2f and charter issues
- RE: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: Questionable Research
- Re: Questionable Research
- Re: Questionable Research
- Re: Agenda for 14 November 2012 call
- RE: Questionable Research
- Re: Questionable Research
- Re: Questionable Research
- Re: Questionable Research
- Re: Questionable Research
- Re: Questionable Research
- Re: Proposals for Compliance issue clean up
- Questionable Research
- Re: Proposals for Compliance issue clean up
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: Propose to close issue-32 (Re: [Action-106][Issue-32] Sharing of data between entities via cookie syncing / identity brokering)
- Re: ISSUE-187 - some thoughts on using javascript
- Re: Agenda for 14 November 2012 call
- Re: ISSUE-187 - some thoughts on using javascript
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- action-268, use of first and third party terms in the TPE
Tuesday, 13 November 2012
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- ACTION-287 - Define "User Expectation"
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- ACTION-326 and ACTION-327 BLOCKED on ISSUE-5
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: Proposals for Compliance issue clean up
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: Proposals for Compliance issue clean up
- ACTION-289: Define "unlinkable" related to section 3.6 on unlinkable data in compliance document
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: Proposals for Compliance issue clean up
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Agenda for 14 November 2012 call
- Propose to close issue-32 (Re: [Action-106][Issue-32] Sharing of data between entities via cookie syncing / identity brokering)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
Monday, 12 November 2012
- RE: Proposals for Compliance issue clean up
- RE: ACTION-302 - Background and Cleanup WRT "Intermediary"
- RE: Proposals for Compliance issue clean up
- Re: Proposals for Compliance issue clean up
- Re: Proposals for Compliance issue clean up
- Re: issue-60 (first and third party) -- Re: Proposals for Compliance issue clean up
- RE: issue-60 (first and third party) -- Re: Proposals for Compliance issue clean up
- Re: Proposals for Compliance issue clean up
- Re: Proposals for Compliance issue clean up
- issue-60 (first and third party) -- Re: Proposals for Compliance issue clean up
- Proposals for Compliance issue clean up
- Re: Proposals for Compliance issue clean up
- RE: Proposals for Compliance issue clean up
- Re: Proposals for Compliance issue clean up
Saturday, 10 November 2012
- ISSUE-152: Moving from compliance to TPE spec
- ISSUE-150: propose to close without text
- ISSUE-21: Moving from Compliance to TPE
- RE: Proposals for Compliance issue clean up
- RE: Proposals for Compliance issue clean up
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- RE: Proposals for Compliance issue clean up
- Re: Proposals for Compliance issue clean up
- Re: Proposed text on ACTION-196: Draft text on whether url shorteners are first or third parties?
Friday, 9 November 2012
- Re: ISSUE-187 - some thoughts on using javascript
- RE: Proposals for Compliance issue clean up
- Re: Proposals for Compliance issue clean up
- Re: Proposals for Compliance issue clean up
- RE: ISSUE-187 - some thoughts on using javascript
- Re: ISSUE-132: compliance or tpe?
- Re: ISSUE-187 - some thoughts on using javascript
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Proposals for Compliance issue clean up
- RE: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- RE: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- ISSUE-31: Framing and text structure
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Towards closing the remaining issues in the TPE specification
- ISSUE-132: compliance or tpe?
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: ISSUE-187 - some thoughts on using javascript
- Re: ISSUE-187 - some thoughts on using javascript
- Re: Please check: List of Participants - Global Considerations Task Force
- RE: ISSUE-187 - some thoughts on using javascript
- Re: ISSUE-187 - some thoughts on using javascript
- Re: ISSUE-187 - some thoughts on using javascript
- RE: ISSUE-187 - some thoughts on using javascript
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: tracking-ISSUE-187: What is the right approach to exception handling? [Tracking Preference Expression (DNT)]
- RE: ISSUE-187 - some thoughts on using javascript
Thursday, 8 November 2012
- Re: ISSUE-187 - some thoughts on using javascript
- Re: ISSUE-187 - some thoughts on using javascript
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: ISSUE-187 - some thoughts on using javascript
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: ISSUE-187 - some thoughts on using javascript
- Re: ISSUE-187 - some thoughts on using javascript
- Re: ISSUE-187 - some thoughts on using javascript
- Re: ISSUE-187 - some thoughts on using javascript
- Re: ISSUE-187 - some thoughts on using javascript
- RE: ISSUE-187 - some thoughts on using javascript
- Re: ISSUE-187 - some thoughts on using javascript
- professional work environment / disciplinary actions
- RE: Please check: List of Participants - Global Considerations Task Force
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Please check: List of Participants - Global Considerations Task Force
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- RE: Modifying a DNT Header (ISSUE-153, ACTION-285)
- RE: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- RE: ISSUE-187 - some thoughts on using javascript
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: action-307, issue-119, absolutely not tracking
- Re: action-307, issue-119, absolutely not tracking
- ISSUE-187 - some thoughts on using javascript
- Re: action-307, issue-119, absolutely not tracking
- Re: action-307, issue-119, absolutely not tracking
- Re: action-307, issue-119, absolutely not tracking
- Re: action-307, issue-119, absolutely not tracking
- RE: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: action-307, issue-119, absolutely not tracking
- Re: action-307, issue-119, absolutely not tracking
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: action-307, issue-119, absolutely not tracking
- Re: action-307, issue-119, absolutely not tracking
Wednesday, 7 November 2012
- RE: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- RE: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: action-307, issue-119, absolutely not tracking
- tracking-ISSUE-187: What is the right approach to exception handling? [Tracking Preference Expression (DNT)]
- Re: ACTION-267 - Propose first/third party definitions from existing DAA documents
- Re: action-307, issue-119, absolutely not tracking
- action-307, issue-119, absolutely not tracking
- Re: ACTION-273: Multiple First Parties
- ACTION-273: Multiple First Parties
- ACTION-302 - Background and Cleanup WRT "Intermediary"
- Re: ISSUE-138, ACTION-319, exceptions without javascript
- Re: Modifying a DNT Header (ISSUE-153, ACTION-285)
- Re: Multiple DNT Headers (ACTION-283, ISSUE-150)
- Re: Definition of "visit" (ACTION-303)
- Re: action-249, action-316, action-168, tracking status qualifiers
- Re: ISSUE-138, ACTION-319, exceptions without javascript
- Re: ACTION-254: Draft text on freq. capping that would avoid new definitions and/or remove redundant normative requirement
- action-325: Help re-factor into appendices
Tuesday, 6 November 2012
- Re: action-249, action-316, action-168, tracking status qualifiers
- action-249, action-316, action-168, tracking status qualifiers
- Re: tracking-ISSUE-186 (Chapell): Ensure that browsers communicate DNT functionality accurately [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-186 (Chapell): Ensure that browsers communicate DNT functionality accurately [Tracking Definitions and Compliance]
- Re: Agenda for 07 November 2012 call - V01
- RE: Agenda for 07 November 2012 call - V01
- Re: Agenda for 07 November 2012 call - V01
Monday, 5 November 2012
- RE: Agenda for 07 November 2012 call - V01
- RE: Agenda for 07 November 2012 call - V01
- RE: Agenda for 07 November 2012 call - V01
- RE: Agenda for 07 November 2012 call - V01
- Re: tracking-ISSUE-186 (Chapell): Ensure that browsers communicate DNT functionality accurately [Tracking Definitions and Compliance]
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ISSUE-45 ACTION-246 Clarified proposal on compliance statements
- RE: tracking-ISSUE-186 (Chapell): Ensure that browsers communicate DNT functionality accurately [Tracking Definitions and Compliance]
- RE: ACTION-314: Draft non-normative examples of how a multi-domain site technically can ask for exceptions
- tracking-ISSUE-186 (Chapell): Ensure that browsers communicae DNT functionality accurately [Tracking Definitions and Compliance]
- Re: Batch Closing of TPE-related ISSUEs: ISSUE-171, ISSUE-116, ISSUE-138, ISSUE-173, ISSUE-160
- ACTION-314: Draft non-normative examples of how a multi-domain site technically can ask for exceptions
- RE: ACTION-314: Draft non-normative examples of how a multi-domain site technically can ask for exceptions
- Re: ACTION-314: Draft non-normative examples of how a multi-domain site technically can ask for exceptions
- Re: Batch Closing of TPE-related ISSUEs: ISSUE-171, ISSUE-116, ISSUE-138, ISSUE-173, ISSUE-160
- Batch Closing of TPE-related ISSUEs: ISSUE-171, ISSUE-116, ISSUE-138, ISSUE-173, ISSUE-160
- Agenda for 07 November 2012 call - V01
- Re: ISSUE-28: MRC presentation
- RE: Proposed Text for Local Law and Public Purpose
- Re: ISSUE-28: MRC presentation
Friday, 2 November 2012
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- RE: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ISSUE-28: MRC presentation
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ISSUE-28: MRC presentation
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ISSUE-28: MRC presentation
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
Thursday, 1 November 2012
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- ACTION-328: Address how multiple first parties can be expressed in tracking status representation
- ISSUE-28: MRC presentation
- Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal
- RE: Graduated response (ACTION-279)
- Re: Graduated response (ACTION-279)