[gnso-rds-pdp-wg] Notes and Actions from 12 April WG call

Tue Apr 12 19:34:41 UTC 2016

Apologies for my absence. My alarm wasn't set up properly. Nathalie Coupet  

    On Tuesday, April 12, 2016 3:20 PM, Lisa Phifer via gnso-rds-pdp-wg <gnso-rds-pdp-wg at icann.org> wrote:

 Dear all,

Below please find notes and action items from today's WG call.

Best regards,
Lisa

Notes and Actions from RDS PDP WG meeting on Tuesday, 12 April 16:00UTC

1. Roll call / SOIs

·        Members are required toprovide a Statement of Interest in order to participate in the WG. 
·        Updates to SOIs are requestedat the start of every meeting. No SOI updates were noted.

2. Read-out from each small team leader on progress to date

·        Privacy team update -proceeding but still work left to go, still need to assign a fewdocuments and still identifying a few additions. Have found that althoughsome docs are reviewed by other teams, they still need to be reviewed bythe privacy team from a privacy and data protection perspective. Volunteers not yet involved are still welcome to volunteer for additionalassignments.

Action: Vicky Sheckler to be added to privacy team; volunteer toreview docs by emailing privacy list.

Action: Team leaders to reach out to volunteers if more help isstill needed by end of week. Members on the call volunteering to helpafter this week or after existing assignments are finished include AndrewSullivan, Farell Folly, and Ayden Ferdeline.

·        Purpose team update - allidentified docs have been assigned, about 80% of docs have beensummarized, the remainder of volunteers have committed to completingtheir reviews shortly. Noted that team commentary/insights may be usefulto include in team's output. See agenda item 3 for discussion of plan toconsolidate summaries (which are of varying levels) into teamoutput.

·        Data team update - all docswere assigned just after last week's call, about 75-80% of summaries havebeen submitted, still missing a few, the rest should arrive shortly.There has also been some discussion on-list about which inputs are mosthelpful from a data elements perspective - that will be included inteam's output.

3. Proposed plan to consolidate summaries and complete & present teamoutputs to full WG

·        Refer to proposed plan(attached and posted on wiki athttps://community.icann.org/x/iTeAAw)
·        Many summaries have beensubmitted already and we’re making good progress, but we do still needvolunteers to complete the rest of the summaries, preferably thisweek.
·        Want to consolidate summariesin as concise a way as possible to serve as a guide as the full WG movesforward. We do need to finish the work plan before deliberations. Nextsteps include…
·        Staff is updating checklistswith summaries and will gather into consolidated PDF
·        Teams are asked to considerinputs docs and summaries to address several questions, including 
         (i) did the inputproduce any insights to inform the WG's work plan, 
         (ii) which inputs arelikely to be most critical during WG deliberations – note that WG willnot be limited by this insight, but it may be helpful when the time comesfor deliberation
         (iii) which inputs ifany generated the most discussion within the teams – note that it is fineand even expected that teams will not fully agree on answers toquestions; those differing views will be discussed within the fullWG
         (iv) which inputs areobsolete or superceded, 
         (v) what input gaps ifany may need to be addressed later
         (vi) other key takeawaysthe team wishes to share with the full WG
·        Each team to discussquestions and use input lists, summaries, and answers to questions tocomplete their team's output 
·        Even if comments discussed onthe email list do not end up in the team’s concise summary, they willstill be available in the team’s email archive and helpful insights foruse as the WG moves ahead
·        Summaries will help us findand use inputs more quickly but that will not replace going back to inputdocs at the right time during the WG's detailed deliberations
·        Summaries themselves may bevoluminous and take some time to complete. The teams will need time todiscuss summaries in order to answer the questions posed in the plan.Need to be realistic about timeframes.
·        Teams are asked to indicatewhere there are disagreements but are not to begin deliberations(attempting to resolve differences) until we return to the full WG mode.Discussion will follow finalization of work plan and initiation of earlyoutreach to SO/ACs and SG/Cs
·        Teams can decide whatmethod(s) this wish to use to answer questions.
·        For example, teams may wishto ask members to define or rank importance/relevance level for all orsome docs, to help avoid lengthy discussion – but method(s) are up toeach team.
·        Is it realistic to try towrap up this initial input gathering/summarizing by the end of April?Teams need more time to complete this phase; this will be assessed basedon progress by next WG call.
·        For next WG call, teams areasked to report back progress and status. 

Action: Staff to updated proposed plan to include reference tohandling of points of disagreement in the team's output (see question iiiabove) and then distribute plan to full WG via email.

Action: All teams to complete summaries and move into addressingquestions enumerated in this plan, using whatever method they may choose,reporting progress and preliminary thoughts on at least some of thequestions during next WG call.

4. Confirm next meeting date (Wednesday, 20 April at 05:00 UTC)

Meeting materials:https://community.icann.org/x/iTeAAw
RDS PDP WG Wiki:https://community.icann.org/x/rjJ-Ag
Phase 1 Documents:https://community.icann.org/x/p4xlAw (including each small team'slatest checklist)
Small Team Members and Mailing List Archives:https://community.icann.org/x/DDCAAw 

_______________________________________________
gnso-rds-pdp-wg mailing list
gnso-rds-pdp-wg at icann.org
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20160412/c3c40ef0/attachment.html>