<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;">I have largely stayed out of this - most of what I would have said has been said.<div><br></div><div>That said, I do support Chuck’s approach. And yes, the EWG did a lot of basic work on what information is gather, how, for whom and the myriad of uses. While Kathy and Stephanie are right - there was no final report, there was a lot of work up front, which is a very useful place to start.</div><div><br></div><div>As to areas of competence, I think we have already covered what we need - for Phase One. Remember, our task is - in this first phase - about policy, not what will come afterwards. So yes, we do need people with the expertise of a Stephanie on data protection law (I’ll put my hand up as well - I was one of the founding members of the Australian Privacy Foundation and am still on its telecommunications policy committee). We also need people like Andrew, with his technical grasp of what is or is not possible. And clearly, we need the Registry/registrar expertise on what the RAA requires in the way of information and how it is used, plus the IP and law enforcement people - on uses. But before we get too far into the weeds, please, can we start with some reasonably high level discussions on some basic principles, and yes, using a lot of preliminary work the EWG did, plus other stuff on Whois going back to the Final Report at least, and the studies done since then. </div><div><br></div><div>That will keep us all busy enough for some time to come.</div><div><br></div><div>Holly</div><div> </div><div><div><div>On 26 Feb 2016, at 9:10 pm, Gomes, Chuck <<a href="mailto:cgomes@verisign.com">cgomes@verisign.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" style="font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">My intent all along has been to a de novo approach. We have to do that when we do policy development. That said, I do not think that that means we ignore work that has already been done. In my opinion, the EWG did an impressive amount of work on this and I think we should take advantage of that just like we should take advantage of other work that has been done over the years. But that doesn’t mean that we accept the conclusions of the EWG unchallenged; we are simply starting with the EWG Final Report for two reasons: 1) it provides a lot of<span class="Apple-converted-space"> </span><b>possible</b><span class="Apple-converted-space"> </span>requirements for an RDS and therefore helps us get a huge start on creating a list of<b><span class="Apple-converted-space"> </span>possible</b><span class="Apple-converted-space"> </span>requirements, hopefully saving us some time; 2) the Issues Report that tasks the WG says that we should start there.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Chuck<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div><div style="border-style: solid none none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: 3pt 0in 0in;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: windowtext;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: windowtext;"><span class="Apple-converted-space"> </span><a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" style="color: purple; text-decoration: underline;">gnso-rds-pdp-wg-bounces@icann.org</a><span class="Apple-converted-space"> </span>[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" style="color: purple; text-decoration: underline;">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]<span class="Apple-converted-space"> </span><b>On Behalf Of<span class="Apple-converted-space"> </span></b>Stephanie Perrin<br><b>Sent:</b><span class="Apple-converted-space"> </span>Friday, February 26, 2016 12:55 AM<br><b>To:</b><span class="Apple-converted-space"> </span><a href="mailto:gnso-rds-pdp-wg@icann.org" style="color: purple; text-decoration: underline;">gnso-rds-pdp-wg@icann.org</a><br><b>Subject:</b><span class="Apple-converted-space"> </span>Re: [gnso-rds-pdp-wg] Notes and action items from Next-Generation RDS PDP WG Meeting - deep concerns<o:p></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 12pt; font-family: 'Times New Roman', serif;">As I said somewhat facetiously during the chat, you should have seen the dissents I refrained from emitting....the EWG did not start from a de novo position. Given the repeated failure to even define the purpose of WHOIS (see the SAC Blind men and the elephant report) we do need to take a de novo approach. The EWG report provided good analysis on some issues, and some new approaches. It certainly did not solve all the problems or deal with all the issues. Brace yourself for me repeatedly pointing these lacunae out, as I know a lot more about all the issues than I did when I started with the EWG....<br>Stephanie Perrin<o:p></o:p></p><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">On 2016-02-25 20:27, Gomes, Chuck wrote:<o:p></o:p></div></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Please see my responses below Kathy.</span><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Chuck</span><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><o:p></o:p></div><div><div style="border-style: solid none none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: 3pt 0in 0in;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: windowtext;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: windowtext;"><span class="Apple-converted-space"> </span>Kathy Kleiman [<a href="mailto:kathy@kathykleiman.com" style="color: purple; text-decoration: underline;">mailto:kathy@kathykleiman.com</a>]<span class="Apple-converted-space"> </span><br><b>Sent:</b><span class="Apple-converted-space"> </span>Thursday, February 25, 2016 5:18 PM<br><b>To:</b><span class="Apple-converted-space"> </span>Gomes, Chuck;<span class="Apple-converted-space"> </span><a href="mailto:gnso-rds-pdp-wg@icann.org" style="color: purple; text-decoration: underline;">gnso-rds-pdp-wg@icann.org</a><br><b>Subject:</b><span class="Apple-converted-space"> </span>Re: [gnso-rds-pdp-wg] Notes and action items from Next-Generation RDS PDP WG Meeting - deep concerns</span><o:p></o:p></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Hi Chuck,<span class="Apple-converted-space"> </span><br>I'm sorry, but I don't understand the starting point of the draft work plan. It says that the "Bulk of Work in phase 1 relates to recommending requirements for Registration Directory Services." After review of the EWG, it states that we will "Develop a comprehensive list of possible requirement [sic] (without a debate) as a first step."<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">[Chuck Gomes] That statement is an assumption based on the WG charter. Do you not think that the WG’s main task, which will consume most of our time, will involve most of our time? If not, please show me what I am missing in the charter.</span></i></b><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br><br>It seems to me that the first step should be evaluating the data collected by the registrars for registration purposes. The next step should be evaluating the purposes for which that data is collected. The third step should be seeking out additionally purposes for which folks not registrars would like to use the data. The fourth step should be to determine whether the information could legally be made available for those additional purposes, and whether those additional purposes are even desirable or useful (or are there dangers and concerns?)<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">[Chuck Gomes] The EWG already spent countless hours evaluating the data collected and had multiple opportunities for public comment on their work. Are you suggesting that we should repeat that work? The first of the eleven questions deals with users and purposes so your suggested first two steps seem to be covered by the WG deliberations on the first charter question. In other words, it seems to me that the proposed approach covers your first two steps at the beginning like you are suggesting. The only difference is that the approach suggests identifying possible requirements first.</span></i></b><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br><br>Jumping straight into "Develop a comprehensive list of possible requirements (without debate)" skips the whole analysis (above) that I understand is necessary under EU nations' laws (and the many other countries with data protection laws) and jumps straight into -- "who wants this data?! Get your data here!"<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">[Chuck Gomes] The analysis will not be skipped. It will happen when we do our deliberation.</span></i></b><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br><br>For the draft work plan, section 3 below ("Review and discuss draft work plan"), I would start with these opening bullet points:<br>- what domain name registration data is collected and for what purpose?<span class="Apple-converted-space"> </span><b><i><span style="color: rgb(31, 73, 125);">[Chuck Gomes]<span class="Apple-converted-space"> </span></span></i></b><span style="color: rgb(31, 73, 125);"> First area of deliberation.</span><br>- what specific laws and restrictions limit the re-use or secondary use of this domain name registration data? (data gathering, legal analysis section)<b><i><span style="color: rgb(31, 73, 125);">[Chuck Gomes]<span class="Apple-converted-space"> </span></span></i></b><span style="color: rgb(31, 73, 125);"> This will happen in our deliberation on each possible requirement.</span><br>- what additional uses would people like to use the domain name registration data and why?<b><i><span style="color: rgb(31, 73, 125);">[Chuck Gomes]<span class="Apple-converted-space"> </span></span></i></b><span style="color: rgb(31, 73, 125);"> First area of deliberation.</span><br>- Outreach to the Supporting Organizations, Advisory Committees and outreach to the greater Internet Community<b><i><span style="color: rgb(31, 73, 125);">[Chuck Gomes]<span class="Apple-converted-space"> </span></span></i></b><span style="color: rgb(31, 73, 125);"> We will do this multiple times during our work.</span><br>- Deliberations as to whether these additional uses are legal, possible, optional -- and what the costs and benefits are of providing this data for the secondary purposes that people are seeking it.<span class="Apple-converted-space"> </span><br><br>On a related note, I used to program large-scale databases on Wall Street and respectfully submit that the term "requirements" in the first 3 bullet points of section 3 is being used incorrectly (or confusingly) as a technical matter. Until we do the detailed analysis of the key issues of what data collected, its primary purpose, sought secondary use, proportionality, etc, we can't possibly know or lay out the "requirements" we are seeking for the new Registration Directory Services. "Requirements" is best used as the term for the features we intend to build into our new RDS system. We are nowhere near the "requirements" stage yet -- we are at the preliminary data gathering, use and user analysis, legal review, and other preliminaries. Shaping, scoping, defining and describing the "requirements" of the new system will come later. What other term can we use?<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">[Chuck Gomes] We are using the term from the charter. I agree that it may fit better in some cases than others but I suggest we don’t get too hung up on terminology. If we can improve it, fine, but let’s not spend too much time debating terminology until it becomes critical, i.e., when we actually get into our deliberation.</span></i></b><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br><br><i>To the other question of the WG, what "rough categories of expertise" are needed:<br></i>I would add groups that specialize in free speech, freedom of expression, human rights, domestic violence, international journalist organizations, and groups that specialize in political oppression. It is these groups that know intimately who is being harassed, stalked and even killed based on Whois data -- and many of them participated in the last public comment held by the Proxy/Privacy Accreditation Working Group. They are definitely reachable and in tune with our issues.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">[Chuck Gomes] We are way past the 24-hour deadline on this. If the membership review team has not finalized the categories yet, they of course can take your input into consideration but it is possible they have already completed the list. </span></i></b><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br><br>I deeply apologize for missing the meeting this week. We had a death of a family friend and given daytime commitments, I could not participate in the late-night call.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">[Chuck Gomes] Please accept my condolences.</span></i></b><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br><br>Tx for your review.<span class="Apple-converted-space"> </span><br>Best,<br>Kathy (Kleiman)<br><br><br>On 2/25/2016 9:57 AM, Gomes, Chuck wrote:<br><br><br><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Thanks for the feedback Kathy. I will let those who were on the EWG respond to what happened after London but I did insert some personal responses below.</span><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Chuck</span><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><o:p></o:p></div><div><div style="border-style: solid none none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: 3pt 0in 0in;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: windowtext;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; color: windowtext;"><span class="Apple-converted-space"> </span><a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" style="color: purple; text-decoration: underline;">gnso-rds-pdp-wg-bounces@icann.org</a><span class="Apple-converted-space"> </span>[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" style="color: purple; text-decoration: underline;">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]<span class="Apple-converted-space"> </span><b>On Behalf Of<span class="Apple-converted-space"> </span></b>Kathy Kleiman<br><b>Sent:</b><span class="Apple-converted-space"> </span>Thursday, February 25, 2016 9:04 AM<br><b>To:</b><span class="Apple-converted-space"> </span><a href="mailto:gnso-rds-pdp-wg@icann.org" style="color: purple; text-decoration: underline;">gnso-rds-pdp-wg@icann.org</a><br><b>Subject:</b><span class="Apple-converted-space"> </span>Re: [gnso-rds-pdp-wg] Notes and action items from Next-Generation RDS PDP WG Meeting - deep concerns</span><o:p></o:p></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Hi Chuck,<br>Tx you for the reminder for the last call of comments. I would like to raise concerns about some of the items in the work plan. My objections have to do with the focus of the<i> </i>"Outline of Approach for Phase 1" extensively on input from the EWG Final Report. The work plan, as circulated (particularly under its "Assumptions") implies an understanding and acceptance of the EWG Final Report that never existed. Let me explain<b> </b>(and invite my EWG friends and all present at that time) to supplement this record:<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">[Chuck Gomes] Please tell me why you think there is an acceptance of the EWG Final Report? No such assumption was made by the Leadership Team. As you share below, the intent is for it to be a starting point.</span></i></b><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><br><br>Background: <span class="Apple-converted-space"> </span></b>the EWG Final Report was greatly changed from the interim to the final draft. Not a little bit, but significantly, substantively, clearly changed. Dozens of new pages were added; entirely new analysis and recommendations. The final Report was difficult, even impossible, to understand. Long public sessions were held at the ICANN meeting in London where speaker after speaker raised issues, concerns and questions, questions, questions. There were so much ambiguity in the text, so many sections that were unclear, so many cross-references that were not complete that even those of us who have been in this field for many years found it impossible to understand specifically what was being recommended and why. Further, there were major questions raised about the large amount of data being collected and retained, indications of nearly unlimited access for certain types of users, and many more concerns. <span class="Apple-converted-space"> </span><i>There were so many questions that commenters at the microphone agreed we/they could not even start a full and substantive critique of the Final Report because it is unclear even what was being recommended on certain key and substantive points. The essence of drafting rules and technical policy is, of course, clarity and we agreed in these public session in London that it was lacking in this Final Report.** Answers were promised; answers never came. The EWG Final Report remains an ambiguous, unclear document.<span class="Apple-converted-space"> </span><br><br></i><b>No Final Public Comment:<span class="Apple-converted-space"> </span></b>Unfortunately, despite major and extensive changes between the interim and final drafts, and ICANN precedent itself, the EWG Final Report never went to public written comment. (In all my time in ICANN, which is a lot, I have never seen a final report which did not go to public comment - particularly a final report as complex, difficult, convoluted and significantly-changed as this one.) There was no final comment period for this report -- just a promise that no group would ever accept the Final Report as an absolute starting point; and that all future groups working with the EWG Final Report would know that it never received a final review, never received consensus, and was never even understood by those critiquing it in the public sessions.<b><span class="Apple-converted-space"> </span><br><br>Dissent:<span class="Apple-converted-space"> </span></b>Further, the EWG Final Report received a strong dissent from the only member of the EWG with a data protection background - the person who was a key drafter of the Canadian Data Protection Report. Her<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">issues and concerns have, of course, never been addressed because the EWG Final Report never went out for that final round of public comment and final round of revisions.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">[Chuck Gomes] I fully expect and encourage the dissenter (Stephanie) to add possible requirements that address her concerns.</span></i></b><br><b><br>Accordingly:<span class="Apple-converted-space"> </span></b>calls for acceptance and reliance on the EWG Final Report should be much more carefully worded and limited in the Work Plan than they are now. I know the Board wants us to refer it as a reference point and touch point, but not the only or exclusive starting point<b>. <span class="Apple-converted-space"> </span></b>The work plan has references to other sources other than the EWG Final Report, but what are they, where are they and who will find and summarize them? Given the speed we want to work, it is incumbent on the WG, at this early point in development, in this Work Plan, to determine what these other sources might be and how we can access them quickly, efficiently and effectively. I would like to request that the Work Plan include provisions for subteams to form and Staff to help find, use and summarize these other sources so that they will be available as quickly as the EWG Report (and noting that it may be difficult for members of the community to drop other work and write short White Papers.) But it is clear that we need to fairly and fully pull in the widest range of information and input at this critical point of Phase 1 -- the RDS Working Group richly deserves it!<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">[Chuck Gomes] If you think the wording asks for acceptance and reliance on the EWG Final Report, please suggest alternative wording. Regarding other sources, many of them are identified in the EWG Report, in the Issues Report and I encourage WG members to identify other sources. Stephanie’s minority statement is one source already mentioned, although I consider it part of the EWG Report.</span></i></b><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></i></b><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">In my view, I see no need for writing white papers. What we will need though in the early parts of our work is for everyone to identify possible requirements so that we create as comprehensive a list as possible. That list will then be deliberated on by the WG to determine which ones we agree should be recommended.</span></i></b><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br><br>Best,<span class="Apple-converted-space"> </span><br>Kathy (Kleiman)<br>p.s. In summary, I would like to ask Assumptions be modified to reflect the huge questions and concerns raised about the EWG Final Report in London, and the complete lack of any final comment period on a hugely and substantively-changed final report. I would also like to request that Outline of Approach to Phase 1 be modified to reflect a concerted effort of the WG, Leadership Team subteam(s) and Staff to identify, define and summarize the "sources other than the EWG Final Report" that will be used and what resources will be devoted by Staff to collecting and summarizing them for ease of use by the WG.<span class="Apple-converted-space"> </span><br><br>Best regards,<br>Kathy<br><br>On 2/24/2016 1:34 AM, Marika Konings wrote:<span class="Apple-converted-space"> </span><br><br><br><br><o:p></o:p></div><div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Dear All,<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Please find below the notes and action items of today’s meeting. I would like to draw special attention to the following action items and deadlines associated with these:<o:p></o:p></div></div><ul type="disc" style="margin-bottom: 0in;"><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b>Action item #1</b>: All to review categories identified by small team and provide feedback within 24 hours (see attached)<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b>Action item #4</b>: All to review work plan approach as has been circulated with the agenda and provide any comments / questions on the mailing list within 48 hours. (see attached)<o:p></o:p></li></ul><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Please share any input or questions you may have with the mailing list.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Best regards,<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Marika<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b>Notes/Action items 24 February 2016 - Next–Generation RDS PDP WG Meeting</b><o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><i>1. Roll call/ SOI</i><o:p></o:p></div></div><ul type="disc" style="margin-bottom: 0in;"><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Note, observers have read-only access to the mailing list and do not receive the call details. If you want to change your status, you can inform the GNSO Secretariat accordingly.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Members are required to provide a Statement of Interest in order to participate in the Working Group.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Updates to SOIs are requested at the start of every meeting.<o:p></o:p></li></ul><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">A<b>ction item #1</b>: Please complete / update your Statement of Interest if you have not done so yet. <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><i>2. Review of WG membership & expertise update</i><o:p></o:p></div></div><ul type="disc" style="margin-bottom: 0in;"><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Small team has been discussing how to identify current level of expertise<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Identified a number of rough categories of expertise that is expected to be needed for this effort: Legal (IP, criminal, civil), Technical (Protocol development, Security, Audit), Data Protection, Operational (Registrar, Registries), Commercial/e-business, Non commercial/not for profit, government advisory, law enforcement (police, investigators, courts), individual internet user.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Proposal to put these categories into a zoomerang poll to allow for WG members to self-identify their expertise<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Small team would like to receive input on the categories identified and possible sub-categories<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Consider removing investigators as it can be considered part of 'police'. There are also other agencies that are involved in investigations, maybe that is why it has been identified as a separate category. Should investigators (non-government) be a separate category? This would include organisations like consumer organisations.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Security may not only be technical expertise, there may also be non-technical aspects to it. Consider having a security category that is not under the technical heading.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">DNS technical specialists should also be considered as a category<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Categories are intended to get a general sense of expertise available<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Consider updating law enforcement to public safety to capture a broader category of investigators?<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Should public defenders be added to the legal category? Might already be covered by legal/criminal?<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Consider a category for cybersecurity. <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Experts can be invited to just join when a particular topic is discussed - not only looking at filling gaps in membership, but also identify specific support that may be needed in an expert capacity. <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Consider adding a category for WHOIS software / service developer<o:p></o:p></li></ul><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b>Action item #1</b>: All to review categories identified and provide feedback within 24 hours<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b>Action item #2</b>: staff to develop survey on the basis of the categories identified and request WG members to participate<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b>Action item #3</b>: small team to review feedback received to the survey and identify whether additional outreach is needed based on the survey results. <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><i>3. Review and discuss draft work plan approach</i><o:p></o:p></div></div><ul type="disc" style="margin-bottom: 0in;"><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Bulk of work in phase 1 relates to recommending requirements for Registration Directory Services<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Use EWG Final Report as starting point, as instructed by the ICANN Board. Substantial public input was provided and incorporated by this effort. Not restricted to the EWG Final Report, but an important starting point. <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Develop a comprehensive list of possible requirement (without a debate) as a first step. Deliberations on each possible requirement will be the next step after developing this comprehensive list, including reaching consensus on whether requirements should be included or not.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Outreach to SO/ACs is expected during various stages of the PDP, periodically as needed. This outreach may take various forms, formal, informal. There is a requirement for formal input at the early phase of the process. <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Interdependency of all eleven questions in the charter will main that the WG may need to go back and forth between questions. <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">First five questions are critical as they are essential to responding to the foundational question of whether a new RDS is needed. <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">No comment period held on the Final EWG Report. EWG Report expected to be starting point - not stopping there, just a first list of possible requirements that the WG is expected to add to.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Should purpose be defined before discussion uses? Purposes and uses are part of the charter which are expected to result in possible requirements (see question 1).<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Leadership team has started developing a first list of possible requirements - draft as a starting point for the full WG to review and add to. SO/AC/SG/Cs can also be asked to add to the list of possible requirements. Objective to have comprehensive list of requirements. <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Once this comprehensive list is 'complete' (WG is of the view that all possible requirements have been added), systematic review of the requirements by the WG. <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Deliberation of some requirements could be deferred to later phases, if deemed appropriate. <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Following this work, the WG is expected to deliberate on foundational question: is a new RDS needed or can the existing WHOIS system be modified to satisfy the recommended requirements for questions 1-5. Answer to this question will determine subsequent steps. <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Who will come up with costing based on the requirements identified? Is it possible to estimate costs until you get to phase 2 and 3? Might be possible to get a high level idea in phase 1, but you cannot do it thorougly until you get to phase 2 when the policies are identified. Phase 1 could identify what costs need to be measured while phase 2 may ballpark those. Cost impact expected across the whole eco-system. Impact assessment will be important question.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Outreach to SO/ACs may involve those groups to consult with their respective constituencies that may take more than 35 days. Smaller requests more frequently may facilitate feedback. All should be communicating regularly with their respective groups - bring feedback to the WG on an ongoing basis. If any request for input would be associated with a minimum 35 day timeline it would have a significant impact on the overall timeline.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Leadership team will work on the detail of the work plan based on the approach outlined and comments received.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Those on the call were supportive of the approach outlined. Provide opportunity for those not on the call to provide feedback on the approach. <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Leadership team would like to be able to send out a first cut of a work plan by the end of this week so it can be further discussed and reviewed during next week's meeting.<o:p></o:p></li></ul><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b>Action item #4</b>: All to review work plan approach as has been circulated with the agenda and provide any comments / questions on the mailing list within 48 hours. <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b>Action item #5</b>: Leadership team to send out first draft of work plan by the end of this week.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><i>4. Discuss proposed outreach to SO/AC/SG/Cs to solicit early input</i><o:p></o:p></div></div><ul type="disc" style="margin-bottom: 0in;"><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Required to formally request input at early stage, minimum of 35 days response time. Considering asking for general input.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Request formal input shortly after ICANN meeting in Marrakech. <o:p></o:p></li></ul><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b>Action item #6:</b><span class="Apple-converted-space"> </span>Leadership team to develop draft outreach message for WG review.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><i>5. ICANN meeting in Marrakech F2F meeting</i><o:p></o:p></div></div><ul type="disc" style="margin-bottom: 0in;"><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">See<span class="Apple-converted-space"> </span><a href="http://doodle.com/poll/7f9h9spwwmys26c5" style="color: purple; text-decoration: underline;">http://doodle.com/poll/7f9h9spwwmys26c5</a>. To date 46 expected to participate in person, 20 are planning to participate remotely and 5 are not able to attend.<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">See<span class="Apple-converted-space"> </span><a href="https://meetings.icann.org/en/marrakech55/schedule/wed-rds" style="color: purple; text-decoration: underline;">https://meetings.icann.org/en/marrakech55/schedule/wed-rds</a><span class="Apple-converted-space"> </span>for further details.<o:p></o:p></li></ul><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><i>6. Confirm next steps and next meeting</i><o:p></o:p></div></div><ul type="disc" style="margin-bottom: 0in;"><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Next meeting will be scheduled for Tuesday 1 March at 16.00 UTC <o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Chuck will not be available for the next meeting - Susan Kawaguchi has volunteered to chair the meeting on 1 March.<o:p></o:p></li></ul></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br><br><br><br><br><o:p></o:p></div><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';">_______________________________________________<o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';">gnso-rds-pdp-wg mailing list<o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><a href="mailto:gnso-rds-pdp-wg@icann.org" style="color: purple; text-decoration: underline;">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"> <o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br><br><br><o:p></o:p></div><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';">_______________________________________________<o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';">gnso-rds-pdp-wg mailing list<o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><a href="mailto:gnso-rds-pdp-wg@icann.org" style="color: purple; text-decoration: underline;">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre><pre style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre></blockquote><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div>_______________________________________________<br>gnso-rds-pdp-wg mailing list<br><a href="mailto:gnso-rds-pdp-wg@icann.org" style="color: purple; text-decoration: underline;">gnso-rds-pdp-wg@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></div></blockquote></div><br></div></body></html>