Svoboda | Graniru | BBC Russia | Golosameriki | Facebook

ISSUE-137: Does hybrid tracking status need to distinguish between first party (1) and outsourcing service provider acting as a first party (s)

Does hybrid tracking status need to distinguish between first party (1) and outsourcing service provider acting as a first party (s)

State:
CLOSED
Product:
Tracking Preference Expression (DNT)
Raised by:
Roy Fielding
Opened on:
2012-04-12
Description:
Tom's proposal has a status response reason for "s", meaning third-party service provider acting as a first party, which is distinct from "1", meaning first-party. That conflicts with some service provision contacts that forbid disclosure, and doesn't take into account the fact that some first-party sites consist of many different service providers at different layers of implementation, nor should we care given that the first-party is responsible for selecting its own service providers.
Related Actions Items:
Related emails:
  1. Re: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-12-17)
  2. RE: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-12-05)
  3. RE: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-12-05)
  4. RE: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-12-04)
  5. RE: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-12-04)
  6. Re: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-12-04)
  7. Re: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-12-03)
  8. Re: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-12-03)
  9. Re: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-12-03)
  10. Re: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-11-21)
  11. Re: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-11-15)
  12. Re: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-11-14)
  13. Re: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-11-14)
  14. Re: Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-11-14)
  15. Batch closing of TPE issues (Deadline: December 03) (from [email protected] on 2013-11-14)
  16. Re: Agenda for June 05 call on TPE (from [email protected] on 2013-06-05)
  17. Agenda for June 05 call on TPE (from [email protected] on 2013-06-04)
  18. Agenda for May 22 call (from [email protected] on 2013-05-21)
  19. F2F: Open Issues for the TPE Discussion on Tuesday (from [email protected] on 2013-05-05)
  20. Re: DNT: Agenda for March 20 call (revised) (from [email protected] on 2013-03-19)
  21. Re: DNT: Agenda for March 20 call (from [email protected] on 2013-03-19)
  22. DNT: Agenda for March 20 call (from [email protected] on 2013-03-19)
  23. Revision on agenda -- deID decisions now on Tuesday (from [email protected] on 2013-02-04)
  24. Agenda update for Monday and Tuesday in Cambridge (compliance spec) (from [email protected] on 2013-02-04)
  25. Re: action-317, discussion of the service-provider flag and the same-party resource (from [email protected] on 2013-01-24)
  26. Re: action-317, discussion of the service-provider flag and the same-party resource (from [email protected] on 2013-01-23)
  27. Re: Agenda for 21 January 2012 TPE call - V03 (regrets) (from [email protected] on 2013-01-23)
  28. Re: Agenda for 21 January 2012 TPE call - V03 (from [email protected] on 2013-01-23)
  29. Agenda for 21 January 2012 TPE call - V03 (from [email protected] on 2013-01-22)
  30. Re: action-317, discussion of the service-provider flag and the same-party resource (from [email protected] on 2013-01-22)
  31. Re: action-317, discussion of the service-provider flag and the same-party resource (from [email protected] on 2013-01-22)
  32. Agenda for 21 December 2012 TPE call - V02 (from [email protected] on 2013-01-21)
  33. Agenda for 21 December 2012 TPE call - V01 (from [email protected] on 2013-01-21)
  34. Re: Agenda for 28 November 2012 call - V02 (from [email protected] on 2012-11-27)
  35. Agenda for 28 November 2012 call - V02 (from [email protected] on 2012-11-27)
  36. Re: Agenda for 28 November 2012 call - V01 (from [email protected] on 2012-11-25)
  37. Agenda for 28 November 2012 call - V01 (from [email protected] on 2012-11-25)
  38. Agenda for 07 November 2012 call - V01 (from [email protected] on 2012-11-05)
  39. Re: Towards closing the remaining issues in the TPE specification (from [email protected] on 2012-10-03)
  40. Re: Towards closing the remaining issues in the TPE specification (from [email protected] on 2012-10-02)
  41. Towards closing the remaining issues in the TPE specification (from [email protected] on 2012-10-01)
  42. ISSUE-49 and ISSUE-137 are related (from [email protected] on 2012-09-19)
  43. Re: Agenda for September 19, 2012 call (from [email protected] on 2012-09-19)
  44. Re: Agenda for September 19, 2012 call (from [email protected] on 2012-09-18)
  45. Agenda for September 19, 2012 call (from [email protected] on 2012-09-18)
  46. Agenda for August 30, 2012 call (from [email protected] on 2012-09-18)
  47. Re: ISSUE-137 Service provider flag (from [email protected] on 2012-09-10)
  48. ISSUE-137 Service provider flag (from [email protected] on 2012-09-10)
  49. Re: Agenda for 5 September 2012 call (from [email protected] on 2012-09-04)
  50. Re: Agenda for 5 September 2012 call (from [email protected] on 2012-09-04)
  51. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-30)
  52. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-30)
  53. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-30)
  54. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-30)
  55. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-30)
  56. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-30)
  57. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-30)
  58. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-30)
  59. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-29)
  60. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-29)
  61. RE: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-29)
  62. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-29)
  63. RE: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-29)
  64. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-29)
  65. RE: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-29)
  66. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-29)
  67. RE: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-29)
  68. Re: Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-29)
  69. Service Provider Status (ISSUE-137) (from [email protected] on 2012-08-29)
  70. Re: Input to ISSUE-137 (service provider flag) (from [email protected] on 2012-08-27)
  71. Re: Input to ISSUE-137 (service provider flag) (from [email protected] on 2012-08-27)
  72. Input to ISSUE-137 (service provider flag) (from [email protected] on 2012-08-27)
  73. Agenda for August 30, 2012 call (from [email protected] on 2012-08-27)
  74. Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from [email protected] on 2012-08-18)
  75. Agenda for August 15, 2012 call (from [email protected] on 2012-08-13)
  76. Re: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from [email protected] on 2012-08-08)
  77. Re: agenda for August 08, 2012 call (from [email protected] on 2012-08-07)
  78. agenda for August 08, 2012 call (from [email protected] on 2012-08-07)
  79. agenda for August 08, 2012 call (from [email protected] on 2012-08-07)
  80. Re: Agenda for July 18, 2012 DNT WG Call on TPE (from [email protected] on 2012-07-18)
  81. ISSUE-137: Does hybrid tracking status need to distinguish between first party (1) and outsourcing service provider acting as a first party (s) (from [email protected] on 2012-04-12)

Related notes:

Rigo: I would say no, because the data processor / service provider is under the liability and responsibility of the first party

Rigo Wenning, 12 Apr 2012, 15:49:06

Current protocol description as of r1.112 treats a service provider that meets the constraints on third-party acting as a first-party as being the same as a first-party, as is consistent with typical service provider contracts.

Roy Fielding, 29 Apr 2012, 11:14:12

The current proposal subsumes data processors under the 1st party.

Matthias Schunter, 21 Jun 2012, 23:16:50

ISSUE-156 is depending on this issue and has been postponed until this issue has been resolved.

Matthias Schunter, 18 Jul 2012, 16:56:20

Resolved in rev 1.145 by removing the S tracking status value and replacing
it with a requirement that a service provider acting as a first party identify
the responsible first party via the policy link, if provided, or the owner of
the origin server domain. That solves the use case that Ed Felton raised regarding distinguishing between a service provider acting on behalf of some other first party and the same provider acting on its own sites.

Roy Fielding, 8 Aug 2012, 08:08:05

2013-01-23: Likely to lead to a call for objections + chairs decision. Question is "MUST service providers on a site (following the sites policies and silo-ing the data) still declare their presence using the "s" flag".

Matthias Schunter, 28 Jan 2013, 13:57:45

There is nonetheless continuing debate as to whether it should be *possible* for a service provider that is an HTTP end-point to indicate that they are a service provider, and who they are providing service to.

David Singer, 12 Feb 2013, 14:55:32

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <[email protected]>.
$Id: 137.html,v 1.1 2019/02/01 09:32:29 vivien Exp $