June 2018 - council - lists.icann.org

Proposed agenda GNSO Council Wrap Up Session
by Marika Konings 28 Jun '18

28 Jun '18

Dear All, Please find below the proposed agenda for the GNSO Council wrap up session. As a reminder, the wrap up takes place today from 12.15 – 13.15 in Salon 7. Best regards, Marika Proposed Agenda for GNSO Council Wrap Up Session 1. volunteers for the GNSO Review of the GAC Communique, 2. volunteers to work with Donna to develop input to the short term and long term improvements for reviews (deadline for comments: 31 July). 3. Council input on draft proposal of the new fellowship program approach (deadline for comments: 27 July) 4. EPDP DT a. Confirmation of next DT call b. Leadership EOI: i. Deadline for submissions ii. Confidentiality iii. Who reviews/decides? iv. Impact on timeline c. EPDP Team Composition i. Any concerns about latest draft? ii. GNSO Council liaison d. EPDP Charter i. Commitment to get comments / proposed edits in as soon as possible ii. Encourage list discussion to resolve differences Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Re: [council] [Epdp-dt] Unified Access Model
by Johan Helsingius 28 Jun '18

28 Jun '18

On 27-06-18 17:02, Johan Helsingius wrote: > Looking forward to the GAC/Board meeting. Will report back. Again apologies for the rather unpolished and unstructured notes, but wanted to get them to you promptly. >From the GAC / board discussion on GDPR: - Does the board plan adjustments to temp spec? Göran confirmed the discussion should happen in the GNSO EPGP. Chris Disspain stated that the board doesn't plan any changes, but doesn't rule it out. - Unfied Access Model Org will seek guidance from DPAs based on model proposed by icann.org. progress depends on if org gets advice from DPAs, and what the advice is - Coordination of the different threads and efforts Chris Disspain sees EPDP and access model as parallel efforts, but "there is a framework for coordination", the board will assess the situation each 90 days as it decides about renewing temporary specification, closely affiliating with GNSO and GAC. Org is eagerly waiting for budget input from GNSO On a question on GAC participation/liaison with the EPDP, Manal did mention the wish for 5 members, and mentioned desire for equal / balanced representation. There was concern expressed about scope (wanting access and accreditation included), but Chris Disspain stated that from the point of timing, it might be better to do access separately, perhaps as another temporary specification (that can then later be made the subject of a PDP / EPDP).

2 2

GAC on EPDP
by Johan Helsingius 28 Jun '18

28 Jun '18

Some quick heads-up notes from the GAC discussion on the EPDP. The GAC discussion presented issues to be discussed with the GNSO and the board: - Membership - GAC wants "parity with GNSO stakeholder groups" - They want to know the current thinking on scope, expected timeline in determining scope, and incorporating GAC input on scope - Respective roles of board and GNSO in defining scope - Who is in charge of overall process? Julf

5 6

Heqads up - GAC advice on GDPR
by Johan Helsingius 27 Jun '18

27 Jun '18

GAC is still busy drafting their Panama Communiqué, but it looks like it will contain advice to the board with regards to GDPR / Whois / Temporary Specification that will contain something like: 1. GAC advices the ICANN Board to take all steps necessary to ensure development and implementation of a access model that addresses accreditation, authentication, access and accountability, and applies to all contracted parties as quickly as possible 2. GAC asks the ICANN Board to publish status report four weeks prior to ICANN63 In the rationale, they state "In order to protect the public interest, as well as the secure, stable, and resilient operation of the DNS, the development and implementation of a unified access model is of utmost importance. The GAC considers that direct involvement and action is required by ICANN Org to facilitate and support this." They will also have advice on IGO identifiers, basically being unhappy that the board hasn't followed previous advice. Julf

1 0

Please review: GNSO Council motions 27 June 2018
by Nathalie Peregrine 27 Jun '18

27 Jun '18

Dear all, Please find below the resolutions voted during the GNSO Council meeting held today in Panama, on Wednesday 27 June 2018. These will be posted shortly on the Resolutions page<https://gnso.icann.org/en/council/resolutions> of the GNSO web site. Motion to approve the Customer Standing Committee Amended Charter Submitted by Donna Austin Seconded by Heather Forrest Whereas: 1. The Customer Standing Committee (CSC) was established as one of the post IANA Transition entities and conducted its first meeting on 6 October 2016. 2. The ICANN Bylaws, Section 17.3 (c) and the CSC Charter required the ccNSO and RySG to conduct a review of the CSC Charter one year after the first meeting of the CSC. 3. In May 2017, a drafting team appointed by the ccNSO and RySG developed a Terms of Reference for the Charter Review, which was subsequently adopted by the ccNSO and RySG in July 2017. 4. The ccNSO and RySG appointed members to form the Charter Review Team from their respective SO and SG to conduct a review of the CSC Charter in accordance with the Terms of Reference. 5. The Charter Review Team conducted a series of consultations with the CSC, the direct customers of the IANA naming function, the independent PTI Directors, and the community at large and published an Initial Report of their findings and an Amended CSC Charter for public comment on 11 April 2018 until 1 June 2018. 6. The GNSO Council discussed the Initial Report during their meeting of 24 May 2018, and submitted comments on the Initial Report as part of the public comment process. 7. The public comment period resulted in a number of comments that were considered and addressed by the Charter Review Team in their Final Report and Amended Charter. 8. The GNSO Council, along with the ccNSO Council, is required to ratify any recommended changes to the CSC Charter. 9. The ccNSO and GNSO Councils discussed the Charter Review process during their most recent face-to-face meeting in San Juan, on 12 March 2018, and are expected to discuss the Final Review<https://gnso.icann.org/sites/default/files/file/field-file-attach/csc-chart…> and Amended Charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/csc-revis…> at the forthcoming ICANN meeting in Panama, on 27 June 2018. Resolved: 1. The GNSO Council approves the changes made to the CSC Charter as a result of the Charter Review Process, and will inform the ccNSO Council accordingly. 2. The GNSO Council will work on a joint communication with the ccNSO Council to inform the CSC that the Amended Charter has been ratified and should now be put into place. 3. The GNSO Council also notes the recommendation in the Final Report 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 and has appointed two Councilors to conduct the recommended analysis in cooperation with two representatives from the ccNSO. 4. The GNSO Council thanks the CSC Review Team for their efforts in undertaking the Review. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…> Motion – Completion of the Final Report of the IGO/INGO Access to Curative Rights Protection Mechanisms PDP (Curative Rights PDP) Submitted by Heather Forrest Seconded by Michele Neylon Whereas, 1. The origin of the IGO/INGO Access to Curative Rights Protection Mechanisms Policy Development Process (Curative Rights PDP) traces back to a consensus recommendation from a previous PDP, the Protection of IGO and INGO Identifiers in All gTLDs PDP (IGO/INGO Protection PDP). The IGO/INGO Protection PDP considered whether and how the names and acronyms of international governmental organizations (IGOs) and international non-governmental organizations (INGOs) should be protected at the top and second levels of the domain name system (DNS). This earlier PDP resulted in a number of recommendations that were inconsistent with GAC advice on this topic. On 30 April 2014, the ICANN Board approved the PDP recommendations that were consistent with GAC advice, so that the GAC, GNSO and the affected community groups could continue to work on reconciling the remaining inconsistencies. 2. A faciliated dialogue between the GAC and GNSO took place at ICANN58 in March 2017. Based on these discussions, in May 2017, the GNSO Council agreed to initiate a new PDP to revisit the IGO/INGO Protection PDP’s recommendation concerning certain Red Cross names. 3. On 5 June 2014, the Council of the Generic Names Supporting Organization (GNSO) chartered the Curative Rights PDP. This new PDP was initiated to evaluate (i) whether the UDRP and/or URS should be amended to enable their access and use by IGOs and INGOs whose identifiers had been recommended for protection by the IGO-INGO Protection PDP and if so, in what way; or (ii) whether a separate narrowly-tailored procedure modeled on these curative rights protection measures to apply only to protected IGO and INGO identifiers should be developed. 4. The Curative Rights PDP Working Group commenced its work in August 2014 and issued its Initial Report for public comments in January 2017, with the public comment period closing on 30 March 2017. Following its analysis of the input received, the Curative Rights PDP Working Group came to agreement on modifying one of its initial recommendations by ICANN59 in June 2017. 5. Since June 2017, the Curative Rights PDP WG has been engaged in trying to reach consensus on one remaining issue concerning IGO jurisdictional immunity. In December 2017, a Working Group member filed an appeal pursuant to Section 3.7 of the GNSO Working Group Guidelines<https://gno.icann.org/sites/default/files/file/field-file-attach/annex-1-gn…> (the Guidelines) to challenge the mechanisms the Co-Chairs proposed be used to determine consensus in relation to this remaining issue. An attempt to resolve the member’s concerns with the PDP Co-Chairs took place in January 2018 in accordance with the Guidelines. Following unsuccessful resolution with the Co-Chairs, the matter was raised with the GNSO Council Chair as prescribed by Section 3.7. Discussions between the GNSO Council Chair, the GNSO Council liaison, the appellants and the PDP Co-Chairs culminated in a proposal for the GNSO Council Liaison to meet with and gather inputs from WG members at and after ICANN61 to assist in the consensus-building process by providing WG members with an opportunity to express their views on the WG’s draft recommendations. A summary report of those meetings was prepared and shared with the Working Group in April 2018 in resolution of the Section 3.7 appeal, and the GNSO Council liaison offered to continue to support the WG in developing its Final Report. As of 16 June 2018, the Working Group is continuing to work toward a Final Report. 6. In January 2018, the GNSO Council held a Strategic Planning Session at which the Council agreed that, to ensure effective allocation of resources and improve management of the community’s workload, a timely resolution of policy development processes should be a priority. 7. At its May 2018 meeting, the GNSO Council liaison informed the Council that the Curative Rights PDP would aim to wind up its work by June 2018. 8. As the scope of the Curative Rights PDP includes consideration of the applicability and usability of existing second level dispute resolution processes (i.e. curative mechanisms) in relation to IGO/INGO names and acronyms, its outcome is likely to affect the full scope of the final protections that are ultimately decided upon for IGO acronyms, and thus the differences that remain between GAC advice and conclusions of the earlier IGO/INGO Protection PDP. Given the length of time that has elapsed since the Board first placed IGO acronyms on a temporary reserved list and the possibility of additional conflict between GAC advice and GNSO policy on the topic of IGO protections, the GNSO Council believes it is imperative that the Curative Rights PDP is concluded in a timely and effective manner. 9. On 10 June 2018, a new Section 3.7 appeal was made under the GNSO Working Group Guidelines challenging the involvement of the PDP Chair (the other Co-Chair having resigned in May), the GNSO Council liaison and policy staff in developing the PDP’s Final Report. This new appeal is currently proceeding through the recommended steps in the GNSO Working Group Guidelines. The appellant has expressed willingness for the substantive work of the PDP to continue towards resolution of the Final Report while the appeal process progresses. 10. Following consultation with the Working Group Chair, GNSO Council Liaison, and GNSO Council leadership team, and notwithstanding the most recent appeal, the GNSO Chair proposed on 13 June 2018 that the target date for completing and submitting the Curative Rights PDP Final Report to the GNSO Council be revised to July 2018 to provide the Working Group with additional time necessary to complete its work and finalize the Final Report. Resolved, 1.The GNSO Council acknowledges the effort of the Curative Rights PDP Working Group since ICANN60 to reach consensus on its final recommendations, and requests that the Final Report be submitted in time to meet the July 2018 GNSO Council meeting document deadline. The GNSO Council directs ICANN staff to inform the Working Group that, in line with the Council’s priority to ensure responsible allocation of resources and timely management of the PDP, the GNSO Council expects to consider this matter at its July 2018 meeting. 2. The GNSO Council acknowledges and appreciates the effort of Susan Kawaguchi in the role of GNSO Council Liaison to assist in resolving the Section 3.7 appeals and to facilitate the group’s efforts to achieve the milestone of a Final Report in a timely manner. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…> Kind regards, 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

GNSO Chair election timeline and incoming councilors
by Nathalie Peregrine 27 Jun '18

27 Jun '18

Dear all, Please see attached the timeline for the GNSO Chair nomination open date and election. Please remember that new councilors are eligible for nomination as Council chair so the Stakeholder Groups and Constituencies’ elections should be over by the date of nominations. New councilors are to be announced on the 25th August 2018. Kind regards, 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

Re: [council] [Epdp-dt] EPDP Scope Matrix
by McGrady, Paul D. 27 Jun '18

27 Jun '18

Thanks Marika and Michele. All, while I appreciate Keith’s work, I actually find it unhelpful and a step backwards. It appears that much of the content of Section 4 of the Temp Spec has been pushed off to another ePDP rather than being dealt with in context and holistically as the Board in its motion, the SSAC in its advice and the European Commission in its public statement yesterday in our combined GAC/GNSO Session indicate are our next steps here. Let’s not revert back to trying to carve up the Temp Spec into pieces and push off the inconvenient bits. It is time for the community to solve this entire problem. For transparency, I am copying in the usual Council list. I understand that we set up a separate list for this work, but our work here in Panama has been in public and transparent. I think we should stick with that. Best, Paul From: Epdp-dt [mailto:epdp-dt-bounces@icann.org] On Behalf Of Michele Neylon - Blacknight Sent: Wednesday, June 27, 2018 7:15 AM To: Marika Konings <marika.konings(a)icann.org>; Epdp-dt(a)icann.org Subject: Re: [Epdp-dt] EPDP Scope Matrix Very helpful – thanks -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: Epdp-dt <epdp-dt-bounces(a)icann.org<mailto:epdp-dt-bounces@icann.org>> on behalf of Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> Date: Wednesday 27 June 2018 at 06:45 To: "Epdp-dt(a)icann.org<mailto:Epdp-dt@icann.org>" <Epdp-dt(a)icann.org<mailto:Epdp-dt@icann.org>> Subject: [Epdp-dt] EPDP Scope Matrix Dear All, On behalf of Keith, please find attached the scope matrix that was referenced during the discussions yesterday. Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>. ________________________________ 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

Motion to approve the Customer Standing Committee Amended Charter
by Austin, Donna 27 Jun '18

27 Jun '18

Hi All The documents Heather forwarded to the Council related to the Customer Standing Committee, particularly the Amended Charter of the Customer Standing Committee, are relevant to the Motion to approve the Customer Standing Committee Amended Charter that I forwarded to the Council list last Saturday. All documents are attached here for ease of reference. Thanks Donna From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Austin, Donna via council Sent: Saturday, June 16, 2018 6:38 PM To: council(a)gnso.icann.org Subject: [council] Motion to approve the Customer Standing Committee Amended Charter Dear Councilors Please find attached a motion for consideration by the Council on 27 June 2018, to approve the Customer Standing Committee Amended Charter. I expect that the Final Report of the Customer Standing Committee Charter Review, which includes the Amended Charter, will be provided to the Council on Monday or Tuesday of next week. Thanks Donna Donna Austin Neustar, Inc. / Senior Policy Manager, Registry Solutions Mobile: +1 310 890 9655 donna.austin(a)team.neustar<mailto:donna.austin@team.neustar> / Website: home.neustar<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.home.neustar_&d=DwM…> Follow Neustar: LinkedIn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_compan…> / Twitter<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_neustar…> Reduce your environmental footprint. Print only if necessary. ________________________________ The information contained in this email message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this email message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.

1 1

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

27 Jun '18

Dear all, Please below find the updated final proposed agenda for the ICANN62 GNSO Council Meeting on 27 June 2018 at 13:00 local time, 18:00 UTC. Final Proposed Agenda 27 June 2018 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 [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> (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 [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>. 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 [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>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 [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> (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 [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> (Council Leadership) 8.2 – Council discussion 8.3 – Council vote (voting threshold: Supermajority) Taking this action is within the GNSO’s remit as outlined in ICANN’s Bylaws as the GNSO ‘shall be responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the GNSO as set forth in these Bylaws’ (Art.11.1). Furthermore, this action complies with the requirements set out in Annex A-1 GNSO Expedited Policy Development Process of the ICANN Bylaws as well as the EPDP Manual. 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

Slide deck GNSO Council: Strategic Outlook Trends Identification Wednesday 27 June 2018 18h30 - 19h30
by Nathalie Peregrine 26 Jun '18

26 Jun '18

Dear all, On behalf of the Multistakeholder Strategy & Strategic Initiatives (MSSI) team, and in preparation for the closed GNSO Council session on Strategic Outlook Trends Identification on Wednesday 27 June 2018 from 18h30 – 19h30 in Salon 7, please find the slides attached to this email for your perusal prior to the session. Kind regards, 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