<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div><div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">Dear WG members,</div><div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);"><br></div><div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">Please find below a brief report from the co-conveners of Sub Team 4 (since we did not get to that agenda item today) as well as a list of notes, action items and specific discussion points that were either made on the WG call earlier today or that we did not manage to get to. It will be greatly appreciated if you can send your thoughts and comments on any of the points below to this mailing list as soon as you can. Staff will endeavor to update and circulate a new version of Annex E by the end of this week. Thank you!</div><div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);"><br></div><div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);"><b>(A) Report from Sub Team 4:</b></div><div><p class="MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; text-indent: -0.25in;"><br></p><p class="MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; text-indent: -0.25in;">The Subteam met on Friday as planned and discussed next steps.<o:p></o:p></p><p class="MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; text-indent: -0.25in;">2. We received the last of the reviewed comment summaries yesterday and are incorporating them into the list. We will recirculate the updated template list shortly.<o:p></o:p></p><p class="MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; text-indent: -0.25in;">3. Once the final list is circulated, there will be a final chance for the WG to indicate that particular comments have already been addressed by other Subteams.<o:p></o:p></p><p class="MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; text-indent: -0.25in;">4. We have a good second draft of our summary complete and we continue our work on refining it. We expect to have our summary for the WG meeting next Tuesday.<o:p></o:p></p><p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"> </p></div><div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);"><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><b>(B) Notes, Action Items and Additional Discussion Points on Annex E:</b></div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><br></div><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;"><u>Proposed Text Changes</u>:</div><ul><li>Section I.B(iii) - On the question of whether providers can charge a nominal cost-recovery fee: the word “standardized” will be deleted.</li><li><font face="Calibri,sans-serif">Section II.A(6)(b)(ii): On the reasons for requesters to use and retain information: either rephrase (i) and (ii) to be less “legalistic” and self-referencing (to clarify what the objectives are), or delete (ii) entirely</font></li><li><font face="Calibri,sans-serif">Section III.B – On the topic of “secure communication channels”: concern about too-narrow a definition of “secure”, so either a workable definition is developed (James Gannon to provide a first draft) or (preferably in the view of some WG members) this be rephrased as a best practice</font></li></ul><div><font face="Calibri,sans-serif"><u>Additional Discussion Items</u>:</font></div><ul><li><font face="Calibri,sans-serif">Section III.C(v) and (vi) - Any overlap that would merit merging, or keep “as is”?</font></li><li><font face="Calibri,sans-serif">Annex 1 – Both options have been retained; are there further comments/suggestions regarding this?</font></li><li><font face="Calibri,sans-serif">GENERALLY – Do the Annex E framework requirements demonstrate “verifiable evidence” that can justify disclosure?</font></li><li><font face="Calibri,sans-serif">Section I.D and GENERALLY – Do the Respect our Privacy and Save Domain Privacy comments require re-examining a provider’s flexibility to publish details or terminate for breach of terms of service? (Staff Note: this seems currently consistent with the WG’s approach on other Preliminary Recommendations about what a provider must include in its terms of service, and what it must publish about those terms – e.g. Preliminary Recommendations #6, #7, #8, #9)</font></li><li><font face="Calibri,sans-serif">Section III.D and GENERALLY – Does the overall discussion about many commenters’ belief that a court order should be obtained require the WG to re-examine its recommendation that “disclosure cannot be refused solely for lack of …. A court order”?</font></li></ul><div><font face="Calibri,sans-serif"><u>Further Staff Note</u>: </font></div><ul><li><font face="Calibri,sans-serif">Section III.C(iv) - On whether it should be optional or mandatory for providers to offer the ability for a customer to give up its domain name registration in lieu of disclosure, please note that in another Preliminary Recommendation (#8) the WG does not recommend this as a mandatory requirement; the wording of Preliminary Recommendation #8 contemplates that some providers will while others will not offer this option.</font></li></ul><div><font face="Calibri,sans-serif"><br></font></div><div><font face="Calibri,sans-serif">Cheers</font></div><div><font face="Calibri,sans-serif">Mary</font></div><div><font face="Calibri,sans-serif"><br></font></div><div><div><div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Mary Wong</font></font></div><div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Senior Policy Director</font></font></div><div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Internet Corporation for Assigned Names & Numbers (ICANN)</font></font></div><div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Telephone: +1 603 574 4889</font></font></div><div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Email: mary.wong@icann.org</font></font></div><div><br></div></div></div><br></div></div></div></body></html>