Re: TPWG Agenda for the October 09 call (V04)

Hi Jack,


thanks for asking.

Our main goal of phase M1+M2 is to foster consensus and convergence. The 
idea was that at M1, all change proposals are on the table. Between M1 
until M2, people discuss, merge, fine tune, ... to converge.

At M2, all change proposals are finalized and the group can discuss 
whether there are change proposals that the group can live with. 
(ideally, at M3, the group will say "we can live with change proposal X 
or Y").

Personally, I expected that converging onto one change proposal should 
not take longer than 1 week. However, at this point, I am not sure 
whether this will be the same for all issues. After all, we aim at 
convergence and - if I am certain that an additional week may help -- I 
would be tempted to add another week on a case-by-case basis.


Regards,
matthias




Our original
On 08/10/2013 19:15, Jack L. Hobaugh Jr wrote:
> Hi Matthias,
>
> Thank you for the clarification on the M2 Phase duration for Issue-5.
>
> For planning purposes, I have two follow-up questions:
>
> 1) Can you clarify whether the duration for Phase M2 will remain at 1 
> week for all issues or will the duration for Phase M2 be adjusted on 
> an issue-by-issue basis?
>
> 2) And somewhat related to my first question, will the Phase M2 
> duration be the same for Issue-10 as for Issue-5?
>
> Best regards,
>
> Jack
>
> *Jack L. Hobaugh Jr
> *Network Advertising Initiative| Counsel & Senior Director of Technology
> 1634 Eye St. NW, Suite 750 Washington, DC 20006
> P: 202-347-5341| jack@networkadvertising.org 
> <mailto:jack@networkadvertising.org>
>
>
>
>
>
> On Oct 8, 2013, at 5:00 AM, "Matthias Schunter (Intel Corporation)" 
> <mts-std@schunter.org <mailto:mts-std@schunter.org>> wrote:
>
>> Hi David,
>>
>>
>> thanks for asking.
>>
>> Now that the change proposals for ISSUE-5 have been frozen (or will 
>> be frozen by EoB today), our current plan is to allow for 1 week to 
>> see whether a consensus emerges.
>> If no consensus has emerged, we currently plan to issue a call for 
>> objections 1 week later (with a closing date of October 23 as 
>> indicated in the plan).
>>
>> Feedback/comments are welcome...
>>
>>
>> Regards,
>> matthias
>>
>>
>>
>>
>>
>> On 07/10/2013 20:16, David Singer wrote:
>>> at least on the definition of tracking, I think it's possible a 
>>> consensus could emerge, so I would also like clarity on how we 
>>> handle this phase (and for how long).
>>>
>>> On Oct 7, 2013, at 8:25 , Jack L. Hobaugh Jr 
>>> <jack@networkadvertising.org <mailto:jack@networkadvertising.org>> 
>>> wrote:
>>>
>>>> Hi Matthias,
>>>>
>>>> Thank you for providing the "V04" clarifications.
>>>>
>>>> For Issue-5 and Issue-10, it is understood that TPWG will begin 
>>>> phase M2 on October 8.
>>>>
>>>> It is also understood that M2 starts a duration for a "[d]iscussion 
>>>> whether clear consensus emerges for one change proposal" and that 
>>>> Phase M3 would include an announcement for "Call for objections to 
>>>> validate / determine consensus" that would start a 14-day window 
>>>> for submitting objections.
>>>>
>>>> I believe there remains some confusion within the TPWG regarding 
>>>> the duration of Phase M2.
>>>>
>>>> Would you please provide the planned duration of Phase M2 or the 
>>>> planned date for the beginning of Phase M3 (in the event consensus 
>>>> is not reached) for Issue-5 and Issue-10?
>>>>
>>>> Best regards,
>>>>
>>>> Jack
>>>>
>>>> Jack L. Hobaugh Jr
>>>> Network Advertising Initiative | Counsel & Senior Director of 
>>>> Technology
>>>> 1634 Eye St. NW, Suite 750 Washington, DC 20006
>>>> P: 202-347-5341 | jack@networkadvertising.org 
>>>> <mailto:jack@networkadvertising.org>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Oct 7, 2013, at 5:33 AM, Matthias Schunter (Intel Corporation) 
>>>> <mts-std@schunter.org <mailto:mts-std@schunter.org>> wrote:
>>>>
>>>>> Hi Team,
>>>>>
>>>>>
>>>>> thanks a lot for submitting your issues on time. The list of 
>>>>> ISSUEs now ends with ISSUE-237 and we have 45 active issues to pursue.
>>>>>
>>>>> Enclosed is another draft of an agenda for next Wednesday based on 
>>>>> feedback I received.
>>>>> Feedback/comments are welcome.
>>>>>
>>>>> V04:
>>>>> - I added a discussion on how to perform changes to the working drafts
>>>>> - I moved the survey of new issues to the end to ensure sufficient 
>>>>> time for processing the active issues
>>>>>
>>>>>
>>>>> Regards,
>>>>> matthias
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> 1. Confirmation of scribe.  Volunteers welcome
>>>>>
>>>>> 2. Offline-caller-identification (see end for instructions)
>>>>>
>>>>> 3. Introducing changes to the editors drafts (Matthias)
>>>>>
>>>>> 4. Discussion on testing of specifications (Carl)
>>>>>
>>>>> ----------------------------------
>>>>> ---- issues for this Call ---
>>>>>
>>>>> Note: See more info at the end for details.
>>>>>
>>>>> 5.  ISSUE-10 [Justin]
>>>>> http://www.w3.org/2011/tracking-protection/track/issues/10
>>>>> http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Party_Definitions
>>>>>     DEADLINES for ISSUE-10:
>>>>>     October 02: M1 Call for final list of change proposals
>>>>>     October 08: M2 List of change proposals is frozen + Discussion 
>>>>> whether clear consensus emerges for one change proposal
>>>>>   6. ISSUE-5  [Matthias]
>>>>> http://www.w3.org/2011/tracking-protection/track/issues/5
>>>>> http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Tracking_Definition
>>>>>     DEADLINES for ISSUE-5:
>>>>>     October 02: M1 Call for final list of change proposals
>>>>>     October 08: M2 List of change proposals is frozen + Discussion 
>>>>> whether clear consensus emerges for one change proposal
>>>>>   7. ISSUE-24 [Carl]
>>>>> http://www.w3.org/2011/tracking-protection/track/issues/24
>>>>> http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Security
>>>>>
>>>>>     DEADLINES for ISSUE-24:
>>>>>     Oct 02: M0: Initial call for change proposals; Submit all 
>>>>> change proposals
>>>>>     Oct 08: M1 Call for final list of change proposals
>>>>>
>>>>> 08. ISSUE-25 [Justin]
>>>>> http://www.w3.org/2011/tracking-protection/track/issues/25
>>>>> http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Audience_Measurement
>>>>>
>>>>>     DEADLINES for ISSUE-25:
>>>>>     Oct 02: M0: Initial call for change proposals; Submit all 
>>>>> change proposals
>>>>>     Oct 08: M1 Discuss change proposals + Call for final list of 
>>>>> change proposals
>>>>>
>>>>> 09. ISSUE-170 [Matthias] Definition of and what/whether 
>>>>> limitations around data append and first parties
>>>>> http://www.w3.org/2011/tracking-protection/track/issues/170
>>>>> http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_First_Party_Compliance
>>>>>
>>>>>     DEADLINES for ISSUE-170:
>>>>>     Oct 09: M0: Initial call for change proposals; Submit all 
>>>>> change proposals
>>>>>     Oct 15: M1 Discuss change proposals + Call for final list of 
>>>>> change proposals
>>>>>
>>>>> 09. ISSUE-16 [Carl] Definition of and what/whether limitations 
>>>>> around data append and first parties
>>>>> http://www.w3.org/2011/tracking-protection/track/issues/16
>>>>> http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Transience_Collection
>>>>>
>>>>>     DEADLINES for ISSUE-170: What does it mean to collect, retain, 
>>>>> use and share data?
>>>>>     Oct 09: M0: Initial call for change proposals; Submit all 
>>>>> change proposals
>>>>>     Oct 15: M1 Discuss change proposals + Call for final list of 
>>>>> change proposals
>>>>>
>>>>> 10. (if time permits): Introduction/explanation of new issues 
>>>>> (Matthias)
>>>>>     fyi:  The new issues that we have not discussed are ISSUE-224 
>>>>> through ISSUE-237.
>>>>>
>>>>> ================ Summary Documentation on Resolving ISSUES 
>>>>> =================
>>>>> Complete list of issues against the compliance-current spec:
>>>>> http://www.w3.org/2011/tracking-protection/track/products/5
>>>>>
>>>>> PHASES to resolve issues:
>>>>> M0 (announcement): Initial call for change proposals; All change 
>>>>> proposals should be drafted
>>>>> M1 (discussion): Initial change proposals have been submitted; 
>>>>> Discussion on change proposals; Call for final list of change 
>>>>> proposals
>>>>> M2 (discussion): List of change proposals is frozen; Discussion 
>>>>> whether clear consensus emerges for one change proposal
>>>>> M3 (announcement): Call for objections to validate / determine 
>>>>> consensus
>>>>> M5 (deadline): Deadline for inputs to call for objections (2 weeks 
>>>>> after M3); Analysis starts
>>>>> M7 (announcement): Results are announced
>>>>>
>>>>> STATUS of the ISSUES:
>>>>> - OPEN During phases M0, M1, M2
>>>>> - PENDING REVIEW: During phases M3, M5
>>>>> - CLOSED after M7
>>>>> All other issues are RAISED.
>>>>> -----
>>>>> This URL
>>>>> As indicated in our plan, the following issues are currently OPEN 
>>>>> for discussion in our calls.
>>>>> ================ Infrastructure =================
>>>>>
>>>>> Zakim teleconference bridge:
>>>>> VoIP: sip:zakim@voip.w3.org
>>>>> Phone +1.617.761.6200 passcode TRACK (87225)
>>>>> IRC Chat: irc.w3.org <http://irc.w3.org><http://irc.w3.org/>, port 
>>>>> 6665, #dnt
>>>>>
>>>>> OFFLINE caller identification:
>>>>> If you intend to join the phone call, you must either associate your
>>>>> phone number with your IRC username once you've joined the call
>>>>> (command: "Zakim, [ID] is [name]" e.g., "Zakim, ??P19 is schunter" 
>>>>> in my
>>>>> case), or let Nick know your phone number ahead of time. If you 
>>>>> are not
>>>>> comfortable with the Zakim IRC syntax for associating your phone 
>>>>> number,
>>>>> please email your name and phone number to
>>>>> npdoty@w3.org <mailto:npdoty@w3.org><mailto:npdoty@w3.org>. We 
>>>>> want to reduce (in fact,
>>>>> eliminate) the time spent on the call identifying phone numbers. Note
>>>>> that if your number is not identified and you do not respond to
>>>>> off-the-phone reminders via IRC, you will be dropped from the call.
>>>>>
>>> David Singer
>>> Multimedia and Software Standards, Apple Inc.
>>>
>>
>