June 2018 - council - lists.icann.org

FAQ published on implementing the Temporary Specification
by Mary Wong 22 Jun '18

22 Jun '18

Dear Councilors, You may be interested to know that ICANN Org has just published the following FAQ on implementing the Temp Spec: https://www.icann.org/resources/pages/gtld-registration-data-specs-faqs-201… Best regards, Mary Sent from a mobile phone, apologies for errors and brevity

1 0

GNSO Council related meetings ICANN62
by Nathalie Peregrine 22 Jun '18

22 Jun '18

Dear councilors, Please find attached the ics calendar invitations for the following meetings: Monday 25 June 2018 08:00 – 08:30: GNSO Policy Briefing 12:15 – 15:00: GNSO Working session 17:00 – 18:30: High Interest Session: Community Input to GNSO Expedited PDP Charter Development Tuesday 26 June 2018 08:30 – 09:00: GNSO Policy Briefing 09:00 – 15:00 GNSO EPDP on Temporary Specification for gTLD Registration Data - Initiation Request and Charter DT meeting 11:30 – 12:30: GNSO & GAC meeting 16:30 – 16:45: Last 15 mins of Cross-Community Session: WHOIS/RDS Policy: Post-GDPR Development and Next Steps for EPDP update 17:00 – 18:30: Cross-Community Session: Accreditation and Access to Non-Public WHOIS Data Post-GDPR 18:30 – 19:30: closed Informal Council meeting Wednesday 27 June 2018 08:00 – 09:00: joint ccNSO – GNSO Council session 08:30 – 09:00: GNSO Policy Briefing 09:00 – 10:15: Placeholder for PDP discussion 13:00 – 15:00: GNSO Council meeting 18:30 – 19:30: GNSO Strategic Outlook session (closed) Thursday 28 June 2018 08:30 – 09:00: GNSO Policy Briefing 12:15 – 13:15: GNSO Wrap-Up session Alternatively, please go to the ICANN62 website schedule,<https://62.schedule.icann.org/meetings> login, and on the bottom right hand side of each meeting frame, choose ADD. This will add the meetings you select to your schedule. Once you have finished doing this go to EXPORT/ DOWNLOAD MY SCHEDULE, this will automatically add the events to your default calendar. Thank you! Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Public comment opens: Initial Report on the Protections for Certain Red Cross Names in all gTLDs – Policy Amendment Process
by Berry Cobb 22 Jun '18

22 Jun '18

Dear GNSO Council. FYI. The Reconvened PDP WG on the Red Cross names published their initial report for public comment yesterday for 40 days. After the comment period closes, the WG will review all comments and prepare its Final Report for GNSO Council consideration. The WG is targeting the August meeting. Additionally, Thomas Rickert (WG Chair) will provide a brief update to the Council at its ICANN 62 meeting next Wednesday. Thank you. B Announcement below: _____ <https://urldefense.proofpoint.com/v2/url?u=http-3A__icann.org_news_announce…> Initial Report on the Protections for Certain Red Cross Names in all gTLDs – Policy Amendment Process [icann.org] Open Date: 21 June 2018 Close Date: 31 July 2018 Originating Organization: GNSO Categories/Tags: Policy Development Brief Overview: Obtain community input on proposed recommendations for amending prior consensus recommendations with respect to the reservation protection of ICRC, IFRC, and National Societies, as instructed by the GNSO Council. This is the IGO-INGO Working Group's Initial Report. Link: <https://www.icann.org/public-comments/red-cross-protection-initial-2018-06-…> https://www.icann.org/public-comments/red-cross-protection-initial-2018-06-… <https://urldefense.proofpoint.com/v2/url?u=http-3A__icann.org_news_announce…> Read more [icann.org] Berry Cobb GNSO Policy Consultant @berrycobb

1 0

Final Proposed Agenda GNSO Council Meeting - 27 June 2018 at 18:00 UTC (13:00 - 15:00 local time)
by Nathalie Peregrine 22 Jun '18

22 Jun '18

Dear all, Please below find the updated final proposed agenda for the GNSO Council Meeting on 27 June 2018 at 18:00 UTC (13:00 – 15:00 local time). Final proposed agenda 27 June 2018 – GNSO Council Meeting ICANN62, Panama Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/xBUFBQ [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> v3.3, updated on 30 January 2018 For convenience: · An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. · An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 18:00 UTC: https://tinyurl.com/ybuhhqmo [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_ybuhhqmo&d…> Local time in Panama: 13:00 11:00 Los Angeles; 14:00 Washington; 19:00 London; 23:00 Islamabad; (Thursday 28 June) 03:00 Tokyo; 04:00 Hobart GNSO Council Meeting Remote Participation: https://62.schedule.icann.org/meetings/699481 [62.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__62.schedule.icann.org_…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> of the GNSO Council meeting on the 24 May 2018 were posted on 14 June 2018 Minutes of the GNSO Council meeting on the 12 June 2018 will be posted on 28 June 2018 Item 2. Opening Remarks / Review of Projects & Action List (10 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…>and Action Item List [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Item 3. Consent Agenda (0 minutes) Item 4: COUNCIL UPDATE – SSAC to Brief the GNSO on Use of Emoji in Domain Names (15 minutes) On 2 November 2017, the ICANN Board, in considering SAC095 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>, adopted [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> the following: · Resolved (2017.11.02.09), the Board hereby directs that conformance to IDNA2008 and its successor will continue to be a necessary condition to determine valid IDN TLD labels. · Resolved (2017.11.02.10), the Board requests that the Country Code Names Supporting Organization (ccNSO) and the Generic Names Supporting Organization (GNSO) engage with the SSAC to more fully understand the risks and consequences of using a domain name that includes emoji in any of its labels, and inform their respective communities about these risks. · Resolved (2017.11.02.11), the Board requests that the ccNSO and GNSO integrate conformance with IDNA2008 and its successor into their relevant policies so as to safeguard security, stability, resiliency and interoperability of domain names. · Resolved (2017.11.02.12), the Board directs the ICANN CEO, or his designee(s), to engage with gTLD and ccTLD communities on the findings and recommendations in SAC095 Accordingly, the GNSO Council has invited the Security and Stability Advisory Committee (SSAC) to brief the GNSO Council on the risks of emoji as domain names in any of its labels and to help inform what specific steps the GNSO may need to take to properly account for those risks. Here, the Council will receive a briefing from Patrik Fältström, to help the Council determine what next steps may be necessary. 4.1 – Update (Patrik Fältström - SSAC) 4.2 – Council discussion 4.3 – Next Steps Item 5: COUNCIL VOTE – IGO-INGO Access to Curative Rights Protection Mechanisms (15 minutes) The IGO-INGO Access to Curative Rights Protection Mechanisms PDP WG had been working to resolve a final recommendation relating to IGO jurisdictional immunity and registrants’ rights to file court proceedings. During the course of trying to determine consensus on a set of options for this final recommendation, several WG members challenged the proposed method for determining initial consensus and appealed via section 3.7 of the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…>. Following discussions with the members utilizing the appeal process and the GNSO chair and the Council liaison to the WG, the Council liaison to the WG solicited input from the WG members on the set of options under consideration. The WG has since held several meetings to try and reach final consensus for its Final Report, including opening up the formal consensus call on 10 May 2018. The WG Chair has designated his assessment of consensus levels for recommendations 1-4, as well as for the 6 options under consideration for recommendation 5. A second section 3.7 appeal was filed in June 2018, to assert that the Chair, Council liaison, and policy staff are not performing their role, that short deadlines are being imposed, and that proper procedure is not being followed for the consensus call. With the connection to a previous PDP on IGO protections, where work continues to reconcile inconsistencies with GAC Advice, and the GNSO Council’s emphasis on improving the timely resolution of PDPs, the Council requests that the Final Report be delivered in time for consideration for the July 2018 GNSO Council meeting. Here, the Council will vote on whether or not to request delivery of the Final Report by the Council’s July meeting. 5.1 – Presentation of motion (Heather Forrest) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL VOTE – Approval of Changes Made to the Customer Standing Committee (CSC) Charter (15 minutes) The ccNSO and RySG appointed members to form the Charter Review Team from their respective SO and SG to conduct a review of the Customer Standing Committee (CSC) Charter in accordance with the Terms of Reference. The CSC Charter review team (RT) sought comment and input on its findings and proposed amendments to the CSC Charter, as included in the RT's Initial Report. On 11 May 2018, Council member volunteers were sought to develop a draft comment for Council consideration for public comment [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> on the Initial Report on Review of the CSC Charter. The Council discussed the Initial Report during their meeting on 24 May 2018 and submit their comments during the public comment process. Taking into account comments received, the Review Team prepared a Final Report and Amended Charter for consideration and adoption by the ccNSO and GNSO Councils. Here, the Council will vote to approve the changes made to the CSC Charter as a result of the Charter Review Process. 6.1 – Presentation of motion (Donna Austin) 6.2 – Council discussion 6.3 – Council vote (voting threshold: simple majority) Item 7: COUNCIL UPDATE – Protections for Certain Red Cross Names in All gTLDs Policy Amendment Process (10 minutes) Following discussions around possible ways of reconciling inconsistent GAC advice and GNSO policy recommendations relating to National Society names of the Red Cross Movement and the two names of the international components of the Movement (http://sched.co/9xr2 [sched.co]<https://urldefense.proofpoint.com/v2/url?u=http-3A__sched.co_9xr2-29&d=DwMG…>), the ICANN Board passed a resolution requesting that the GNSO Council initiate the process outlined in Section 16 of the GNSO’s Policy Development Process (PDP) Manual, which sets forth the requisite steps for amending policy recommendations that have been approved by the GNSO Council but not yet approved by the ICANN Board (https://www.icann.org/resources/board-material/prelim-report-2017-03-16-en#… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>). The Board’s request related to the 190 Red Cross National Society names and the two international movement names and a limited defined set of their variants. On 03 May 2017, the Council resolved [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> to initiate the Section 16 process as requested by the Board, which resulted in the limited reconvening of the original PDP on Protection of IGO and INGO Identifiers in All gTLDs. The Reconvened WG began its deliberations on 14 June 2017 and is nearing completion of its preliminary work, expecting to publish its Initial Report in the near future. Here, the Council will receive an update on the status of the Reconvened WG. 7.1 – Update (Thomas Rickert - WG Chair) 7.2 – Council discussion 7.3 – Next Steps Item 8: COUNCIL VOTE – Initiation of Expedited Policy Development Process on the ICANN Board Temporary Specification (30 minutes) On 11 May 2018, ICANN released the Temporary Specification [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> on gTLD Registration Data, which served as the main agenda topic for the subsequent Board Workshop in Vancouver. This proposed Temporary Specification provides an interim solution until the community completes a policy development process on the temporary specification which is expected to complete within a one year period. On 14 May 2018, ICANN released a revised Temporary Specification [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> and scheduled a webinar on 15 May 2018 to discuss the topic. The Board passed a resolution [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, noting their intent to adopt the Temporary Specification on or around 17 May 2018. On 17 May 2017, the ICANN Board approved [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> the proposed Temporary Specification for gTLD Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, which establishes temporary requirements for how ICANN and its Contracted Parties will comply with both ICANN contractual requirements and the European Union’s General Data Protection Regulation (GDPR). On 21 May 2018, the Council and SG/C chairs met to discuss possible next steps for the ICANN Board adoption of the Temporary Specification. On its 24 May 2018 meeting, the Council discussed possible next steps following ICANN Board adoption of the Temporary Specification. On 5 June 2018, the Council met with the ICANN Board to discuss a set of questions [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…>the Council and ICANN Board developed, as well as overall next steps. Subsequently, Council leadership and staff developed a Mindmap [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> to help understand the elements around a potential Expedited Policy Development Process (EPDP), such as timing, team composition, and planning for ICANN62. On 12 June 2018, the Council held an Extraordinary Council Meeting to discuss next steps on addressing the Temporary Specification. There, the Council agreed in principle that an EPDP was the right way to address the issue and that next steps should be taken, specifically drafting of the charter and initiation. In the period leading up to and at ICANN62, the Council has worked together to draft the charter for the EPDP. Here, the Council will vote to initiate an EPDP on the Temporary Specification, as well as to adopt the EPDP’s charter. 8.1 – Presentation of motion (Council Leadership) 8.2 – Council discussion 8.3 – Council vote (voting threshold: Supermajority) Item 9: ANY OTHER BUSINESS (15 minutes) 9.1 – GNSO Chair election timeline 9.2 – Call for Volunteers - Revised ICANN Procedure Handling WHOIS Conflicts with Privacy Law 9.3 – Open Microphone ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> References for Coordinated Universal Time of 18:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 (-1 day) 11:00 San José, Costa Rica (CST) UTC-6 (-1 day) 12:00 New York/Washington DC, USA (EDT) UTC-4 14:00 Buenos Aires, Argentina (ART) UTC-3 15:00 Rio de Janeiro, Brazil (BRST) UTC-3 15:00 London, United Kingdom (GMT) UTC+1 19:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 19:00 Paris, France (CEST) UTC+2 20:00 Islamabad, Pakistan (PKT) UTC+5 23:00 Singapore (SGT) UTC+8 (+1 day) 02:00 Tokyo, Japan (JST) UTC+9 (+1 day) 03:00 Sydney/Hobart, Australia (AEDT) UTC+10 (+1 day) 04:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 28 of October 2018, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 4 of November 2018 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_&d=…> and https://tinyurl.com/ybuhhqmo [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_ybuhhqmo&d…>

1 0

Public comment forum now open for the Initial Report from the Reconvened PDP Working Group on Red Cross Names
by Mary Wong 21 Jun '18

21 Jun '18

Dear Councilors, Please see below for a link to the public comment forum that was just opened on the Initial Report from the reconvened PDP Working Group on the names of the Red Cross National Societies, the International Committee of the Red Cross and the International Federation of Red Cross and Red Crescent Societies. The comment period will remain open for 40 days, closing on 31 July 2018. Staff understands that Thomas Rickert, the Working Group chair, will be providing the Council with a brief status update during your public meeting at ICANN62 next week. Thanks and cheers Mary & Berry From: Mary Wong <mary.wong(a)icann.org> Date: Thursday, June 21, 2018 at 16:58 To: "gnso-igo-ingo(a)icann.org" <gnso-igo-ingo(a)icann.org> Subject: Public comment forum now open for our Initial Report Dear all, As Berry is traveling, I am pleased to send this notification on behalf of him and the staff supporting this effort. The Initial Report has now been published for public comment, with a duration of 40 days such that the comment period will close on 31 July 2018: https://www.icann.org/public-comments/red-cross-protection-initial-2018-06-…. As noted previously by Berry, in addition to the Initial Report itself (https://gnso.icann.org/en/issues/igo-ingo/red-cross-protection-policy-amend…), we have also posted the proposed list of finite and specific Red Cross names so that the community can see and comment on it as well: https://gnso.icann.org/en/issues/igo-ingo/red-cross-identifiers-proposed-re…. Thanks and cheers Mary & Berry From: Gnso-igo-ingo <gnso-igo-ingo-bounces(a)icann.org> on behalf of "mail(a)berrycobb.com" <mail(a)berrycobb.com> Date: Wednesday, June 20, 2018 at 16:07 To: "gnso-igo-ingo(a)icann.org" <gnso-igo-ingo(a)icann.org> Subject: [Gnso-igo-ingo] Initial Report for Public Comment Hi All, Please find attached a redline and clean version of the WG’s Initial Report to be published for public comment starting tomorrow for 40 days. For those that submitted proposed changes, thank you. There were no objections to the consensus levels assigned to the proposed recommendations nor were there objections to the list of identifiers listed as an outstanding issue. Thus, those identifiers are included in the list of names to be protected. Once the PCF is posted on icann.org, I will send a link to the list. Note: as you will see in the redline, there are still a few outstanding items for the WG to consider when it reconvenes to consider the comments submitted and readies the report for submission to the GNSO Council. I left them intact as markers for when the time comes. Thank you all. B Berry A. Cobb 720.839.5735 mail(a)berrycobb.com<mailto:mail@berrycobb.com> @berrycobb

1 0

Fwd: IPC Outreach Reception - ICANN 62
by Heather Forrest 20 Jun '18

20 Jun '18

Dear Council colleagues, On behalf of Brian Winterfeldt, President of the IPC, I'm pleased to convey the invitation below. Best wishes, safe travels, see you in Panama, Heather

1 0

For your review: GNSO June 2018 Project List
by Terri Agnew 20 Jun '18

20 Jun '18

Dear Councilors, Attached please find the updated Project List in both red-line and clean version for your review before the Council meeting. If there are no comments, the list will be posted on the website on page: <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc il_project&d=DgMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f 4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=bcZnPuqiDY4_TMPBs 3UPEUuqx-bS0HF55Trpa8n_FnY&s=YH_cwffIV-OMrgs6pTu37csGmNJ3QHxniBkjyRh9J2s&e=> http://gnso.icann.org/en/council/project and be directly viewed at : <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_meetings _projects-2Dlist.pdf&d=DgMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM& r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=bcZnPuq iDY4_TMPBs3UPEUuqx-bS0HF55Trpa8n_FnY&s=Md4eGTKVkiG-gC-Gmw4artPvS0zM3M5oceJO4 BALy7g&e=> http://gnso.icann.org/meetings/projects-list.pdf Thanks so much, Kind regards, Terri

1 0

Fwd: Fine Report CSC Charter Review Team
by Heather Forrest 20 Jun '18

20 Jun '18

Dear Council colleagues, Please find below an email from Bart Boswinkel communicating the Final Report of the Customer Standing Committee (CSC) Charter Review and calling on the Council to consider in particular a recommendation for further analysis by the GNSO and ccNSO Councils. We have an opportunity to discuss CSC-related matters with the ccNSO Council when we meet with them on Wednesday at 0800. Best wishes, Heather ---------- Forwarded message ---------- From: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Tue, Jun 19, 2018 at 8:04 PM Subject: Fine Report CSC Charter Review Team To: "Heather Forrest (Heather.Forrest(a)acu.edu.au)" < Heather.Forrest(a)acu.edu.au> Cc: "CSC-review(a)icann.org" <CSC-review(a)icann.org>, Marika Konings < marika.konings(a)icann.org> Dear Heather Please find attached a copy of the Final Report of the Customer Standing Committee (CSC) Charter Review prepared by the CSC Charter Review Team, along with a standalone version of the Proposed Amended CSC Charter. In accordance with the CSC Charter and the ICANN bylaws, any recommended changes to the CSC Charter as a result of the CSC Charter review are to be ratified by both the GNSO and ccNSO Councils. Therefore the CSC Review Team seeks consideration of the Proposed Amended Charter by the GNSO Council with a view to having the recommended changes ratified. We also call your attention to a recommendation in the Final Report requesting that the ccNSO and GNSO Councils conduct an analysis of the requirements of the IANA Naming Function Review and the CSC Effectiveness Review with a view to creating synergies and avoiding overlap. We understand that some progress has been made in this regard and we thank the Council for their prompt attention to this matter. Regards On behalf of the CSC Charter Review Team Bart Boswinkel

1 0

ePDP DT / Leadership Issues
by McGrady, Paul D. 19 Jun '18

19 Jun '18

I think we have at least two questions to address: 1. What is the ideal configuration of the leadership team for an EPDP? * 1 chair * 2 or more co-chairs * 1 chair and 1 or more vice-chairs * Some other model 2. Depending on the answer to the above, who should be nominated for leadership and what is that process? Historically, WG's select their own leadership and that is ratified by the Council. Is that the same plan for the ePDP? Let's discuss. PS: From the chat on today's call I saw (and want to capture for your discussion): Ayden Ferdeline: Chair - Thomas Rickert Best, Paul ________________________________ The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations.

1 0

ICANN Org Proposed Unified Access Model
by Ayden Férdeline 19 Jun '18

19 Jun '18

Could this, in any way, have implications for the EPDP? https://www.icann.org/news/blog/data-protection-privacy-update-seeking-comm… There is no deadline for the submission of feedback, and it does not appear on the public comment page, so I presume it is an informal request for community input. Best wishes, Ayden

3 2