<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Happy to help on 1.3.2 initially, also would like to be on 1.3.3<div class=""><br class=""></div><div class="">David</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 15 Jul 2015, at 6:50 am, Mary Wong <<a href="mailto:mary.wong@icann.org" class="">mary.wong@icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class=""><div class="">Dear WG members,</div><div class=""><br class=""></div><div class="">Following from the WG call earlier today, the co-chairs and staff after some consultation would like to propose the following approach for your consideration:</div><div class=""><br class=""></div><div class=""><u class="">1. Use of Sub Teams for Specific Topics</u>:</div><ul class=""><li class="">Sub-teams comprising a few WG volunteers each can be formed to do the initial review of public comments received on the three topics suggested by Steve on the call, i.e. (1) Section 1.3.2 of the Initial Report (on escalation of relay requests and the handling of disclosure/publication requests from third parties other than IP rights holders); (2) Section 1.3.3 (on the open question regarding online financial transactions); and (3) Annex E (the Illustrative Disclosure Framework).</li><li class="">To assist the WG evaluate the usefulness of sub teams, a sub team for Section 1.3.2 can be formed first and serve as a “test case” for the exercise.</li><li class="">As outlined on the call, a sub team will do a “first pass” through a template, based on the Public Comment Review Tool, that staff will populate with all the input received on that particular issue. The sub team will report back to the full WG in a timely fashion, including suggesting a WG response and/or proposed action in relation to the comments received.</li><li class="">Sub teams may elect to do their work via email and online tools (e.g. Google Docs or a wiki page), with or without supplemental conference calls. Any calls will be recorded and transcribed for transparency purposes, and drafts and other documents prepared using online tools will also be made available to the full WG. (Do note, however, that depending on call scheduling and timing, staff support may not be available for all requested calls if several sub teams are used concurrently.)</li></ul><div class=""><b class="">PLEASE VOLUNTEER FOR SUB TEAM 1.3.2 IF YOU ARE INTERESTED IN ASSISTING WITH THIS INITIAL REVIEW. </b>Staff will endeavor to provide the template tool for 1.3.2 to the sub team as soon as possible, hopefully by Monday.</div><div class=""><br class=""></div><div class=""><u class="">2. Full WG Review of Other Comments to Continue in Parallel</u>:</div><ul class=""><li class="">Staff will “collapse” (per James’ suggestion on the call) all those template responses received that were simply a Yes or No answer to a question, without any further comment added – these will be reflected in the Public Comment Review Tool accordingly, as a single collective entry. The current Tool (covering Preliminary Recommendations 1 through 9) will be updated in time for the WG to begin this review on the next call.</li></ul><div class=""><br class=""></div><div class=""><u class="">3. Collated Information</u>:</div><ul class=""><li class="">In addition to the updated spreadsheet just circulated by Graeme, we can also send you archived mail files of the contributions received to the public comment forum, should you or your group wish to conduct searches through each comment yourselves.</li></ul><div class=""><br class=""></div><div class="">We hope the above will be helpful in facilitating good progress on the work to be done in preparation for the Final Report.</div><div class=""><br class=""></div><div class="">Thanks and cheers</div><div class="">Mary</div><div class=""><br class=""></div><div class=""><div class=""><div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri">Mary Wong</font></font></div><div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri">Senior Policy Director</font></font></div><div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri">Internet Corporation for Assigned Names & Numbers (ICANN)</font></font></div><div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri">Telephone: +1 603 574 4889</font></font></div><div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri">Email: <a href="mailto:mary.wong@icann.org" class="">mary.wong@icann.org</a></font></font></div><div class=""><br class=""></div></div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""> </div><div class=""><div class=""><br class=""></div><br class=""></div></div>
_______________________________________________<br class="">Gnso-ppsai-pdp-wg mailing list<br class=""><a href="mailto:Gnso-ppsai-pdp-wg@icann.org" class="">Gnso-ppsai-pdp-wg@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</div></blockquote></div><br class=""></div></body></html>