August 2018 - Gnso-epdp-team

Organization and Discussion of Survey Results
by Kurt Pritz Aug. 6, 2018

Aug. 6, 2018

Hi Everyone: Thank you for your thoughtful and timely responses to the survey. The ICANN support team and I have read every one in order to gauge the landscape and present a coherent path forward. Attached are the summary spreadsheet of your survey results and a slide deck for our upcoming meeting. You will see in the slides and in the spreadsheet, we have presented sort of an issue summarization. As part of the triage report, this is intended to indicate why there is lack of consensus on certain sections of the Temporary Specification. In certain cases they indicate a path forward, e.g., prioritizing certain sections. Certainly, the summarization is only meant to indicate where and why a conflict of opinion exists and not create prejudice in any way. (You will also see that we have summarized the issues associated in Sections 1-4 of the Temporary Specification only and not the first Appendix. We will complete the task after our meeting.) As you might guess, I am keen on getting through the Triage as quickly as possible. At this stage, the Triage document is envisaged to include: A summary of responses indicating the position of each group on each section Each of the comments delivered in a matrix (spreadsheet) An issue summarization, distilling the issues raised in each section of the Temporary Specification. I think we owe the GNSO Council some type of summary such as this During the meeting, we will review and ask you to comment on the issue summaries during our meeting. (Please look at them with the mind that, so long as they don’t prejudice the ensuing discussion, we can include them in the triage.) For the meeting tomorrow, you might find it helpful to have a printed version of the Temporary Specification and have access to the attached spreadsheet as we go through the slides. Thank you again for your work on this. Best regards, Kurt

1 0

Re: [Gnso-epdp-team] RySG - alternate introductions
by Andrea Glandon Aug. 6, 2018

Aug. 6, 2018

Dear Marc, Thank you for these introductions. They have been posted on the wiki as well. https://community.icann.org/x/4IpHBQ Kind Regards, Andrea Glandon From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of "Anderson, Marc via Gnso-epdp-team" <gnso-epdp-team(a)icann.org> Reply-To: "Anderson, Marc" <mcanderson(a)verisign.com> Date: Monday, August 6, 2018 at 10:21 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] RySG - alternate introductions All, As was pointed out by Alan Greenberg, alternates can’t post to this list but may need to fill in for or even replace members at some point. As such the RySG would like to provide introductions from their alternates. Thank you, Marc -=-=-=-=-=-=-=-=-=- Arnaud Wittersheim Hello everyone, My name is Arnaud Wittersheim, one of the alternate representing the RySG in the ePDP process. I work at Nameshield, a european company specializing in intangible asset protection, as new gtlds project manager and compliance manager on topics such as GDPR. I have over fifteen years of experience in the domain name industry on registry and registrar topics and thus a rather good view of policies and contracts such as the RAA and RA. I have attended several ICANN summits as an observer, including those in Vancouver and Panama this year. This is my first participation in a consensus policy development process. I hope that my skills can be useful for the ePDP whose success I wish. Looking forward to working with you all Thank you Arnaud Wittersheim -=-=-=-=-=-=-=-=-=- Beth Bacon I have over 12 years of experience with ICANN policy and over 8 years of active participation in ICANN SO/ACs, previously in the GAC and currently with the Registries Stakeholder Group. I have been working on privacy issues for the past 5 years, first in the Department of Commerce and now at PIR as Director of Policy and Privacy. Additionally, I have several years of practical experience operationalizing privacy (especially GDPR) requirements into new and existing agreements, policies, and procedures to serve the unique business needs of Registries. Beth Bacon, Director of Policy and Privacy Public Interest Registry -=-=-=-=-=-=-=-=-=- Sebastien Ducos Hello Everyone, I am Sebastien Ducos, one of the RySG Alternates. I have a long background in Internet technologies tracing back 20+ years and in domain names specifically for the last 10. My first ICANN was in Toronto, 6 years ago. I am part of the Client Engagement team at Neustar working with generic, brand, geo and and country code TLD clients. I am also chair of the geoTLD.group which has been working on GDPR for the last 2.5 years when our members .frl and .amsterdam first came to us with the issue. Looking forward to working with all of you, albeit quietly as an Alternate. Sebastien Ducos -=-=-=-=-=-=-=-=-=-=- Marc Anderson mcanderson(a)verisign.com<mailto:mcanderson@verisign.com> Cell: 571.521.9943 Office: 703.948.3404 12061 Bluemont Way, Reston, VA 20190 Verisign.com<http://www.verisign.com/> [Description: Description: Description: Verisign™]

3 2

RySG - alternate introductions
by Anderson, Marc Aug. 6, 2018

Aug. 6, 2018

All, As was pointed out by Alan Greenberg, alternates can't post to this list but may need to fill in for or even replace members at some point. As such the RySG would like to provide introductions from their alternates. Thank you, Marc -=-=-=-=-=-=-=-=-=- Arnaud Wittersheim Hello everyone, My name is Arnaud Wittersheim, one of the alternate representing the RySG in the ePDP process. I work at Nameshield, a european company specializing in intangible asset protection, as new gtlds project manager and compliance manager on topics such as GDPR. I have over fifteen years of experience in the domain name industry on registry and registrar topics and thus a rather good view of policies and contracts such as the RAA and RA. I have attended several ICANN summits as an observer, including those in Vancouver and Panama this year. This is my first participation in a consensus policy development process. I hope that my skills can be useful for the ePDP whose success I wish. Looking forward to working with you all Thank you Arnaud Wittersheim -=-=-=-=-=-=-=-=-=- Beth Bacon I have over 12 years of experience with ICANN policy and over 8 years of active participation in ICANN SO/ACs, previously in the GAC and currently with the Registries Stakeholder Group. I have been working on privacy issues for the past 5 years, first in the Department of Commerce and now at PIR as Director of Policy and Privacy. Additionally, I have several years of practical experience operationalizing privacy (especially GDPR) requirements into new and existing agreements, policies, and procedures to serve the unique business needs of Registries. Beth Bacon, Director of Policy and Privacy Public Interest Registry -=-=-=-=-=-=-=-=-=- Sebastien Ducos Hello Everyone, I am Sebastien Ducos, one of the RySG Alternates. I have a long background in Internet technologies tracing back 20+ years and in domain names specifically for the last 10. My first ICANN was in Toronto, 6 years ago. I am part of the Client Engagement team at Neustar working with generic, brand, geo and and country code TLD clients. I am also chair of the geoTLD.group which has been working on GDPR for the last 2.5 years when our members .frl and .amsterdam first came to us with the issue. Looking forward to working with all of you, albeit quietly as an Alternate. Sebastien Ducos -=-=-=-=-=-=-=-=-=-=- Marc Anderson mcanderson(a)verisign.com<mailto:mcanderson@verisign.com> Cell: 571.521.9943 Office: 703.948.3404 12061 Bluemont Way, Reston, VA 20190 Verisign.com<http://www.verisign.com/>

2 1

Reminder - survey part 1 due Monday 6 August by 19.00 UTC
by Marika Konings Aug. 5, 2018

Aug. 5, 2018

Reminder – Part 1 of the survey is due Monday 6 August 2018 by 19.00 UTC: https://www.surveymonkey.com/r/CC6F9F8. Also, please remember that the survey is ONLY for EPDP Team members who are expected to fill out the survey on behalf of their appointing organizations. If you are not sure about your status, please check: https://community.icann.org/x/4IpHBQ. Best regards, Marika, Berry, and Caitlin

1 0

Rafik as Vice-Chair
by Alan Greenberg Aug. 4, 2018

Aug. 4, 2018

I asked for time to consult with my colleagues and have done so. We have no problem with Rafik being named Vice-Chair of the EPDP based on the following presumptions/conditions: 1. There is a direct conflict with Rafik acting as the first level handling of a complaint about a leadership decision (a Liaison responsibility) and serving in that leadership. If the GNSO Chair chooses to act in his place in that role (any complaint that stands would go to the Chair next in any case), or to appoint someone else who is will be closely following the proceedings (and agrees not to launch a compliant!), the conflict goes away. 2. Our assumption is that the role of Vice-Chair will be purely to on occasion act as the Chair of a meeting when Kurt is not available, or to handle other administrative tasks. In this case, we see no conflict. If, on the other hand, he and Kurt would take on the role that other Chairs/Co-Chairs/Vice-Chairs teams have and strategize on to how to overcome conflicts or impasses within the work team, then there is a direct conflict as it puts one of the EPDP constituent groups in a privileged position. Although Rafik is not one of the formal members of the NCSG contingent on the EPDP, as a possible incoming NCSG Chair and a key member of the NCSG Policy Committee, he cannot disassociate himself completely from being involved. Alan

4 5

IPC's Introduction Statement
by Alex Deacon Aug. 3, 2018

Aug. 3, 2018

Hi All, As requested here is the (or something close to the) intro statement of the IPC I made on our first call. My name is Alex Deacon. Both myself and Diane will be representing the IPC in this EPDP. Diane is an experienced IP lawyer and expert in matters relating to privacy including the GDPR. As for myself my experience is in internet technology policy and Infrastructure including DNS, authentication authorization identity and encryption. Diane and I bring set of skills that is not only wide and deep but also relevant to the task at hand. Our goals here are simple. It is to participate actively, constructively and respectfully toward the definition of an consensus policy for a global RDS system that meets the needs of the IP community in a GDPR compliant way. Lastly, and to repeat something Diane eloquently said in her intro to the list yesterday, we both look forward to listening, learning, contributing and working collaboratively with the team to find solutions that achieve the important mission of this group. Thanks! Alex -- ___________ *Alex Deacon* Cole Valley Consulting alex(a)colevalleyconsulting.com +1.415.488.6009

1 0

Triage Survey - Part 1
by Anderson, Marc Aug. 3, 2018

Aug. 3, 2018

Kurt and all, I'm in the process of working through all the sections that make up part 1 of the triage survey. In order to make sure I properly understand the deliverable I went back to charter and re-read the section on the first deliverable (triage document). For ease of reference here is the section: The first deliverable of the EPDP Team shall be a triage document of the Temporary Specification, which includes items that have the Full Consensus support of the EPDP Team that these should be adopted as is (with no further discussion or modifications needed). These items need to be: ********* In the body of the Temporary Specification (not in the Annex) ********* Within the "picket fence" (per limitations on Consensus Policy as set out in the Contracts) ********* Not obviously in violation of the GDPR / Assumed to be compliant with GDPR [Presumed to be legal according to the members' best knowledge of GDPR] ********* Consistent with ICANN's Bylaws Deliberations of this first deliverable should include at least one round of elimination of clauses, if appropriate, and a second round of Full Consensus approval of a whole set of clauses. In short for the first deliverable we ae tasked to identify what sections of the Temporary Specification should be included, as is, in the final consensus policy recommendations of this working group. Looking at part 1 of the triage survey, the questions include a box to fill out for sections the constituency does NOT support as is. This to me implies that the purpose of this triage survey is not just to inform discussions on the first triage report deliverable, but also the second "Initial Report" deliverable. To make sure everyone is on the same page could you clarify the purpose of this triage survey and how it will be used. Thank you, Marc Marc Anderson mcanderson(a)verisign.com<mailto:mcanderson@verisign.com> Cell: 571.521.9943 Office: 703.948.3404 12061 Bluemont Way, Reston, VA 20190 Verisign.com<http://www.verisign.com/>

2 2

High-level meeting summary and action items from EPDP Team meeting - 1 August 2018
by Caitlin Tubergen Aug. 3, 2018

Aug. 3, 2018

Dear All, Below, please find a high-level summary from today’s EPDP Team Meeting. For more detailed notes, please refer to the wiki page: https://go.icann.org/2n9gcBf [go.icann.org] As a reminder, our next meeting will be Tuesday, 7 August, 13:00UTC. Best regards, Marika, Berry, and Caitlin EPDP Team Meeting #1 – 1 August 2018 Meeting Summary In this summary: “Team Members” and the “Team” are the meeting participants representing ICANN’s stakeholder groups, constituencies and advisory committees. The “Support Team” is the ICANN staff members supporting this group. The “Chair” is the Chair or Vice Chair acting as Chair. Most important actions from today’s meeting: For contribution to the “triage” document, Team Members will complete Part 1 of the (now distributed) survey - one survey response per group. Due date: 19:00UTC, August 6. The Team Members prepared statements to introduce their respective groups. To preserve that thought product, each team member who prepared a written statement will mail it to gnso-secs(a)icann.org. Each team member that made an oral statement can send a written version to the same address. In the latter case, please use the transcript as the starting point as there should be little or no edits or embellishments to the original statement. Due: 8 August. The Chair will advise the GNSO Council leadership that, pending the receipt of one comment from the Team, Rafik Dammak was confirmed as Vice Chair and that, a replacement for his role in reporting complaints about the team leadership to the Council should be replaced. Due date: August 3 All EPDP Team members and alternates to review the statement of participation and reflect on these items. Due date: August 3. Major discussion points in addition to the action items: An “early Input” request has been mailed to Supporting Organization and Advisory Committee leaders. Replies are due in 21 days. The Early Input request is a PDP requirement but is, in this case, largely redundant with the Survey that has been distributed to the Team, where the Team and the Early Input distribution has essentially the same breadth of distribution. The Charter deliverables are, in order (see, https://community.icann.org/x/0opHBQ [community.icann.org] We plan to deliver the first two prior to the Barcelona meeting but have identified possible schedule slack time so that, if an extension is needed, we might be able to extend the delivery. Triage Initial Report: Temporary Specification Initial Report: Access The Chair reviewed a speaking-order methodology for issue discussion at meetings. There was general support although it was recognized that the process of consensus-building remains complex and must be respected. The Chair reviewed plans to possibly engage with mediation expertise. There was not time for discussion on the matter and more information would be provided for discussion before decisions were made in that regard. Meetings will occur on Tuesday and Thursday at 13:00UTC. The next meeting is 7 August, 13:00UTC. We are planning a face-to-face meeting in mid to late September, potentially in Los Angeles to simplify logistics but ability of the Team to travel there will be weighed. A schedule for the ICANN Barcelona meeting was reviewed. The plan for developing the Triage report was reviewed (and is now launched).

3 2

Re: [Gnso-epdp-team] Draft Agenda - 7 August 2018 EPDP Team Meeting
by Caitlin Tubergen Aug. 2, 2018

Aug. 2, 2018

Dear EPDP Team Members, Apologies for the additional email, but please note that the reference in the previous email to Annex A should read Appendix A. This has been corrected below. Best regards, Caitlin From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Thursday, August 2, 2018 at 5:11 PM To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] Draft Agenda - 7 August 2018 EPDP Team Meeting Dear EPDP Team Members, Please find a draft agenda for our next meeting on Tuesday, 7 August at 13:00UTC below. Best regards, Marika, Berry, and Caitlin AGENDA: EPDP on Registration Data Temporary Specification, 7 August, 13:00 UTC The meeting scheduled for 7 Aug, 13:00UTC will center on the results of the first survey section found at https://www.surveymonkey.com/r/CC6F9F8 Before reviewing the agenda please note that: Obviously, there is not time to complete this agenda in this one meeting. We will break at a suitable point. In creating this agenda, we did not see the purpose in trying to pre-determine when that might be Depending on survey results, discussions on some sections might be allotted more or less time Roll Call & SOI Updates (5 min) Overview of EPDP Input Survey Part 1 Results (5 minutes) Substantive discussion of Temporary Specification The format for each of these discussions will be to divide the survey in half and discuss each in turn. Therefore, the discussion of the survey results is divided into two parts: Sections in the main body of the Specification (Sections 1-4) The Appendix A: Registration Data Directory Services Each group should target five minutes to discuss reasons for approval or edits with any of the sections of the Temporary Specification. If there are differences that appear immediately resolvable, we will take the time for a brief discussion toward that end. Each group will be called in random order (GNSO constituencies and stakeholder groups first). If you have a reason for speaking first (or some other place in the order), please inform the Chair or Support Team with the reason why so that might be accommodated. For example, when we discuss Transfers, we might allow the registrars to speak first as they best understand the mechanics of that process. Sections 1 – 4 (55 minutes) 1 Scope 2 Definitions and Interpretations 3 Policy Effective Date 4 Lawfulness and Purposes of Processing gTLD Registration Data Appendix A (55 minutes) Registration Data Directory Services In each case for A & B, we will summarize the Temporary Specification provisions of potential agreement and discuss a plan to address provisions that diverge. Wrap and confirm next meeting to be scheduled for Thursday 8 August at 13.00 UTC

1 0

Draft Agenda - 7 August 2018 EPDP Team Meeting
by Caitlin Tubergen Aug. 2, 2018

Aug. 2, 2018

Dear EPDP Team Members, Please find a draft agenda for our next meeting on Tuesday, 7 August at 13:00UTC below. Best regards, Marika, Berry, and Caitlin AGENDA: EPDP on Registration Data Temporary Specification, 7 August, 13:00 UTC The meeting scheduled for 7 Aug, 13:00UTC will center on the results of the first survey section found at https://www.surveymonkey.com/r/CC6F9F8 Before reviewing the agenda please note that: Obviously, there is not time to complete this agenda in this one meeting. We will break at a suitable point. In creating this agenda, we did not see the purpose in trying to pre-determine when that might be Depending on survey results, discussions on some sections might be allotted more or less time Roll Call & SOI Updates (5 min) Overview of EPDP Input Survey Part 1 Results (5 minutes) Substantive discussion of Temporary Specification The format for each of these discussions will be to divide the survey in half and discuss each in turn. Therefore, the discussion of the survey results is divided into two parts: Sections in the main body of the Specification (Sections 1-4) The Appendix A: Registration Data Directory Services Each group should target five minutes to discuss reasons for approval or edits with any of the sections of the Temporary Specification. If there are differences that appear immediately resolvable, we will take the time for a brief discussion toward that end. Each group will be called in random order (GNSO constituencies and stakeholder groups first). If you have a reason for speaking first (or some other place in the order), please inform the Chair or Support Team with the reason why so that might be accommodated. For example, when we discuss Transfers, we might allow the registrars to speak first as they best understand the mechanics of that process. Sections 1 – 4 (55 minutes) 1 Scope 2 Definitions and Interpretations 3 Policy Effective Date 4 Lawfulness and Purposes of Processing gTLD Registration Data Annex A (55 minutes) Registration Data Directory Services In each case for A & B, we will summarize the Temporary Specification provisions of potential agreement and discuss a plan to address provisions that diverge. Wrap and confirm next meeting to be scheduled for Thursday 8 August at 13.00 UTC

1 0