- ispcp - lists.icann.org

FW: [council] Draft Motion on EPDP Phase 1 Recommendation 7 and Thick Whois Transition Policy
by philippe.fouquart＠orange.com Oct. 21, 2020

Oct. 21, 2020

Dear ISPCP colleagues, Please note the following, which is for discussion at council next week. The (“draft”) motion reviews the status of the implementation of EPDP phase 1 rec 7 and its impact on the Thick WHOIS Transition Policy. The IRT has reached an impasse as described in the letter I shared in May. As background, I’d encourage you to have a look at the attached summary from our council liaison to the IRT, it reviews the nature of the disagreement as to whether “an appropriate legal basis” exists with regards to the transfer of contact fields bw the registar and the registry. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Pam Little Sent: Friday, October 16, 2020 11:53 AM To: council(a)gnso.icann.org; council <council-bounces(a)gnso.icann.org> Cc: gnso-secs <gnso-secs(a)icann.org> Subject: [council] Draft Motion on EPDP Phase 1 Recommendation 7 and Thick Whois Transition Policy Dear Councilors, Further to Berry's email below, please find attached a draft motion for discussion at the upcoming Council meeting next week. The draft is the output of the Council small team convened after the September Council meeting consisting of Rafik, Marie, John, Philippe, Flip, Maxim and myself. I am grateful for their hard work and contributions during this busy time leading up to ICANN69. From a procedural perspective, I believe this matter is very important to the Council. I encourage you to review the draft before the meeting. Thank you for your attention. Kind regards, Pam ------------------------------------------------------------------ Sender:policy <policy(a)bacinblack.com<mailto:policy@bacinblack.com>> Sent At:2020 Oct. 12 (Mon.) 08:59 Recipient:council@gnso.icann.org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc:gnso-secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject:Re: [council] Final Proposed Agenda | GNSO Council Meetings part 1 and 2 | 21 October 2020 at 13:00 CET / 11:00 UTC Dear All, Please see below for a slight amendment to item #4 of the agenda that was sent a few hours ago. Item 4: COUNCIL DISCUSSION - Discuss Small Team Options Regarding EPDP Phase 1 Recommendation 7 (25 minutes) In adopting the Expedited Policy Development Process (EPDP) on the Temporary Specification Final Report and Recommendations, the Council requested that an informal Implementation Review Team (IRT) be established, which was done. After the recommendations were approved by the ICANN Board, the informal IRT transitioned to a formal IRT and has diligently been working to implement the policy recommendations. Within the IRT, there are diverging views amongst some IRT members on how to implement recommendation 7, especially in relation to the Thick WHOIS Transition Policy for .COM, .NET, and .JOBS The ICANN Board, taking note of the potential impasse, sent a letter<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> to the GNSO Council on 11 March 2020. The Council considered the letter and agreed that recommendation 7 did not explicitly overturn the Thick Whois Transition Policy; to do so will require the GNSO Council to initiate policy development. The Council sent a response<https://urldefense.com/v3/__https:/www.icann.org/en/system/files/correspond…> to the ICANN Board on 29 May 2020. The IRT has continued to try and implement recommendation 7 but has still been unable to reach agreement. As such and per the Council’s letter, the Council requested a briefing from, ”the GNSO Council liaison detailing the precise nature of the impasse so that the GNSO Council can make an informed determination on how to proceed.” During its September Council meeting, the Council received a briefing from the GNSO Council liaison to the IRT, Sebastien Ducos. The Council agreed to convene a small team of Councilors that was charged with establishing a path forward to try and resolve the impasse. That small team met to determine what the best practical path forward may be. Here, the Council will consider the options proposed by the small team, including a draft motion [to be sent under separate cover] that would do two things 1) Affirm the intent of EPDP Phase 1 Recommendation 7; and 2) initiate an EPDP on the Thick WHOIS Transition Policy. 4.1 - Introduction of topic (Council Vice-Chair, Pam Little) 4.2 – Council discussion 4.3 – Next steps Thank you. B Berry Cobb GNSO Policy Consultant Principal | BAC in Black Consulting<http://bacinblack.com/> Mob: +1 (720) 839-5735 [https://encrypted-tbn0.gstatic.com/images?q=tbn%3AANd9GcQLU_cPLRHNEaDTAD-_n…]<https://twitter.com/berrycobb> [https://www.pinclipart.com/picdir/middle/180-1804091_2019-supply-chain-solu…]<https://www.linkedin.com/in/berrycobb/> From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Nathalie Peregrine Sent: Sunday, October 11, 2020 16:15 To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [council] *with correct date in body of email* : Final Proposed Agenda | GNSO Council Meetings part 1 and 2 | 21 October 2020 at 13:00 CET / 11:00 UTC Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 21 October 2020 at 11:00 UTC. Draft GNSO Council Agenda 21 October 2020 - Part I 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/OAebC This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019 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. GNSO Council meeting held 13:00 CET (Hamburg time) Coordinated Universal Time: 11:00 UTC: https://tinyurl.com/y3nxs8rf 04:00 Los Angeles; 07:00 Washington; 12:00 London; 14:00 Moscow; 20:00 Tokyo; 22:00 Melbourne GNSO Council Meeting Remote Participation: Not available until 24 hours before. ___________________________________ Item 1: Administrative Matters (10 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 <https://gnso.icann.org/sites/default/files/policy/2020/minutes/minutes-gnso…> of the GNSO Council meeting on 20 August 2020 were posted on 04 Sep 2020. Minutes<https://gnso.icann.org/sites/default/files/policy/2020/minutes/minutes-gnso…> of the GNSO Council meeting on the 24 September 2020 were posted on 9 October 2020. 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 <https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (10 minutes) 3.1 - Action Decision Radar<https://community.icann.org/download/attachments/40175174/program_managemen…> - Next Steps for WHOIS Conflicts Procedure Implementation Advisory Group The GNSO Council has considered the proposed immediate actions and subsequent steps as outlined in the WHOIS Conflicts Procedure IAG (WHOIS IAG) Small Team’s proposal<http://mm.icann.org/pipermail/council/attachments/20201006/2a0c0c3e/Summary…>. The proposal outlines recommended next steps to consider with respect to modifying the implementation of the WHOIS Conflicts Procedure, in light of public comments received and changes to data protection law that may have affected the implementation of the Procedure. Specifically, the GNSO Council requests: 1. ICANN org, in consultation with contracted parties, to draft a proposal for a modification to the existing Procedure based on its past experience with both the WHOIS Conflicts Procedure and the registrar data retention waiver process. In formulating the draft proposal, the GNSO Council recommends that ICANN org consider changes to data protection law that may have affected the previous implementation of this Procedure in light of the contractual requirements, e.g., the General Data Protection Regulation. For example, should the identification of a new trigger to activate the procedure be considered given potential financial penalties under GDPR? 2. Following receipt of the proposal from ICANN org, the GNSO Council will consider the proposal and assess next steps, including seeking input from the community, if appropriate, given the substance of the proposal. Following the GNSO Council’s consideration, the GNSO Council may choose to adopt the proposal. 3. If the GNSO Council does not deem the proposal appropriate: a. the GNSO Council will recommend a small group of Council volunteers to review the WHOIS IAG draft charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-ica…> and confirm it is still fit for purpose; and b. Following confirmation of the Charter by the GNSO Council, the GNSO Council recommends launching the call for volunteers for the WHOIS IAG, taking into consideration the GNSO Council’s upcoming workload. For example, the call for volunteers may need to be postponed if no community bandwidth is available to immediately consider the issues. In the meantime, ICANN org, in conjunction with the EPDP Phase 1 IRT, will need to update relevant terminology pursuant to EPDP Phase 1, Rec. 27. 1. Should the GNSO Council consider the outcome developed from the WHOIS IAG unacceptable, the GNSO Council will consider initiating an EPDP to either change or repeal the Consensus Policy. 3.2 - Action Decision Radar<https://community.icann.org/download/attachments/40175174/program_managemen…> - Per the rationale circulated on 11 October 2020, Council agrees to launch a call for volunteers for a small team to develop both a draft charter and an EPDP scoping document for the IDN Policy Track 2. 3.3 - Following the GNSO Council’s consideration of the proposed immediate actions and subsequent steps as outlined here<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-pr…>, the GNSO Council directs: EPDP Phase 2a – Legal/natural and feasibility of unique contacts 1. The GNSO Policy Support Team communicate to the groups that have appointed members to the EPDP Team that the Council is expected to instruct the EPDP Team to further consider the topics of legal/natural and feasibility of unique contacts per the instructions above, as well as the expected timeframe, provided herein for reference, “[a]t the latest 3 months after reconvening, the Chair of the EPDP Team and GNSO Council Liaison to the EPDP will report back to the GNSO Council on the status of deliberations. Based on this report, which is expected to include an update on progress made and the expected likelihood of consensus recommendations, the GNSO Council will decide on next steps, which could include providing additional time for the EPDP to finalize its recommendations or termination of the EPDP if it is clear that no progress is being made or consensus is unlikely). Request groups to: a. Commence process of confirming members availability and/or re- appointing members to work on these topics. Proposed deadline: 15 November. b. Start developing proposals to address these topics, factoring in deliberations to date, that will allow the EPDP Team to kickstart deliberations on these topics when it reconvenes.” 1. The Council leadership to initiate an Expression of Interest Process to identify a new Chair. The EPDP Team shall recommence its deliberations upon selection and confirmation of a new Chair; however, should no suitable candidates be found or should the appointment process require significant time, Council leadership will inform the Council accordingly and recommend commencement of deliberations under the leadership of the GNSO Council liaison to the EPDP Team. Accuracy: 1. The GNSO Policy Support Team communicates to GNSO SG/Cs, as well as ICANN Advisory Committees that have expressed an interest in the topic of accuracy, the intent of the GNSO Council to launch a scoping team on this topic. Request groups to: a. Start thinking about members that have relevant knowledge and expertise that should join this effort once the scoping team launches. b. Start compiling relevant information and suggestions that would allow kickstarting the discussions on 1. and 2. once the scoping team is formed (see here<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-pr…> for resources already identified). 1. Council leadership to request ICANN Org to develop a briefing document that outlines both (i) existing accuracy requirements and programs and (ii) the corresponding impact that GDPR has had on implementing / enforcing these requirements and programs. The document, once delivered, will be provided to the scoping team to inform its deliberations. 2. GNSO Council to consider in the context of the Council Action / Decision Radar, the appropriate starting time for this effort, factoring in other projects that are in the pipeline. 3.4 - Confirmation of the Recommendations Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-epd…> to the ICANN Board regarding adoption of recommendations 1-22 contained in the Final Report from the EPDP Temporary Specification for gTLD Registration Data – Phase 2. 3.5 - Appointment of the GNSO Liaison to the Governmental Advisory Committee (motion<https://community.icann.org/x/OgebC>) Item 4: COUNCIL DISCUSSION - Discuss Draft Motion to Affirm intent of EPDP Phase 1 Recommendation 7 and Initiation of the Thick WHOIS Transition Policy EPDP (25 minutes) In adopting the Expedited Policy Development Process (EPDP) on the Temporary Specification Final Report and Recommendations, the Council requested that an informal Implementation Review Team (IRT) be established, which was done. After the recommendations were approved by the ICANN Board, the informal IRT transitioned to a formal IRT and has diligently been working to implement the policy recommendations. Within the IRT, there are diverging views amongst some IRT members on how to implement recommendation 7, especially in relation to the Thick WHOIS Transition Policy for .COM, .NET, and .JOBS The ICANN Board, taking note of the potential impasse, sent a letter<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> to the GNSO Council on 11 March 2020. The Council considered the letter and agreed that recommendation 7 did not explicitly overturn the Thick Whois Transition Policy; to do so will require the GNSO Council to initiate policy development. The Council sent a response<https://urldefense.com/v3/__https:/www.icann.org/en/system/files/correspond…> to the ICANN Board on 29 May 2020. The IRT has continued to try and implement recommendation 7 but has still been unable to reach agreement. As such and per the Council’s letter, the Council requested a briefing from, ”the GNSO Council liaison detailing the precise nature of the impasse so that the GNSO Council can make an informed determination on how to proceed.” During its September Council meeting, the Council received a briefing from the GNSO Council liaison to the IRT, Sebastien Ducos. The Council agreed to convene a small team of Councilors that was charged with establishing a path forward to try and resolve the impasse. That small team met to determine what the best practical path forward may be. Here, the Council will consider a draft motion that would do two things 1) Affirm the intent of EPDP Phase 1 Recommendation 7; and 2) initiate an EPDP on the Thick WHOIS Transition Policy. 4.1 - Introduction of topic (Council Vice-Chair, Pam Little) 4.2 – Council discussion 4.3 – Next steps Item 5: COUNCIL DISCUSSION - Draft Operational Design Phase for gTLD Policy Implementation (15 minutes) During the 23 September SO/AC Leaders call, the concept of an "Operational Design Phase" was introduced by Goran. The SO/AC Leaders had a preliminary discussion on the topic and Goran indicated that ICANN would produce a paper for community consideration and feedback. That paper<http://mm.icann.org/pipermail/council/attachments/20201005/2000130c/Design-…> was prepared and was shared with the Council on 5 October 2020. The objective for this new proposed design phase is to better prepare the Board by providing operational and resourcing information before making decisions on GNSO-approved policy recommendations. The paper notes that while the GNSO Council is the manager of the PDP and gTLD policy development is within the GNSO's remit, consensus policy making involves all stakeholders (including ACs who give advice to the Board). Further, the paper seeks to be clear that this design phase concept doesn't affect policy development or the Consensus Policy Implementation Framework. It recognizes that if policy issues are impacted, they rightfully go back to the GNSO for its consideration, rather than permitting ICANN Org or Board to make unilateral changes. The Stakeholder Groups and Constituencies were invited and encouraged to provide feedback to the paper. In addition, on a 6 October GNSO Council pre-ICANN working session, Karen Lentz from ICANN org provided additional information and rationale for the new concept. Here, Councilors will be invited to share their initial thoughts on the concept and the paper. 5.1 - Introduction of topic (Council leadership) 5.2 - Council discussion 5.3 - Next steps Item 6: COUNCIL DISCUSSION - Board Consultation Regarding Questions Surrounding the financial Sustainability of the System for Standardized Access and Disclosure (20 minutes) On 24 September 2020, the GNSO Council adopted the recommendations contained in the Expedited Policy Development Process (EPDP) on the Temporary Specification Phase 2 Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phas…>. Resolved clause 1b. states: b. [if 1a. is adopted] Noting some of the questions surrounding the financial sustainability of SSAD and some of the concerns expressed within the different minority statements, the GNSO Council requests a consultation with the ICANN Board as part of the delivery of the GNSO Council Recommendations Report to the ICANN Board to discuss these issues, including whether a further cost-benefit analysis should be conducted before the ICANN Board considers all SSAD-related recommendations for adoption. The request for a consultation with the ICANN Board is not usually an element of the transition of GNSO-approved recommendations from the GNSO Council to the ICANN Board. As such, the Council will need to consider how best to engage with the Board in seeking this consultation. Here, the Council will discuss next steps as it relates to resolved clause 1b, including whether the draft Transmittal Letter<https://gnso.icann.org/en/drafts/draft-transmittal-letter-icann-board-08oct…> accurately captures the agreed-upon approach of the Council. 6.1 - Introduction of topic (Council leadership) 6.2 - Council discussion 6.3 - Next steps Item 7: COUNCIL DISCUSSION - ADR Item - Council to Consider Delay of the Request for the Policy Status Report for the Expiration Policy(ies) (10 minutes) As indicated on the Action Decision Radar<https://community.icann.org/display/gnsocouncilmeetings/Action+Items?previe…>, the GNSO Council is to consider when to request a Policy Status Report to conduct a review of the two Expiration Policies, the Expired Domain Deletion Policy<https://www.icann.org/resources/pages/registars/accreditation/eddp-en> (EDDP) and the Expired Registration Recovery Policy<https://www.icann.org/resources/pages/errp-2013-02-28-en> (ERRP). Given the concerns about capacity, along with the circumstances that no known issues have presented themselves, Council leadership is suggesting that the request for Policy Status Reports for these two Consensus Policies can be delayed by a period of 24 months, assuming no substantive issues arise during that time. This would have the effect of deferring the request for a Policy Status Report on the EDDP and ERRP until at least November 2022, where it would then be discussed again to determine if a request is timely. Here, the Council will consider whether it agrees with this suggestion and if so, agree to include on the November consent agenda. 7.1 - Introduction of topic (Council leadership) 7.2 - Council discussion 7.3 - Next steps Item 8: ANY OTHER BUSINESS (20 minutes) 8.1 - Farewell to outgoing Councilors (Elsa Saade, Erika Mann, James Gannon, Julf Helsingius, Keith Drazek, Michele Neylon, Rafik Dammak and Scott McCormick.) 8.2 - 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. 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… References for Coordinated Universal Time of 11:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 04:00 San José, Costa Rica (CST) UTC-6 06:00 New York/Washington DC, USA (EDT) UTC-4 07:00 Buenos Aires, Argentina (ART) UTC-3 08:00 Rio de Janeiro, Brazil (BRST) UTC-3 08:00 London, United Kingdom (GMT) UTC+1 12:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 12:00 Paris, France (CEST) UTC+2 13:00 Moscow, Russia (MST) UTC+3 14:00 Singapore (SGT) UTC+8 19:00 Tokyo, Japan (JST) UTC+9 20:00 Melbourne, Australia (AEDT) UTC+11 22:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 25 of October 2020, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 01 of November 2020 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/y3nxs8rf Final GNSO Council Agenda 21 October 2020 - Part II (Admin) 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/OAebC This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5 updated on 24 October 2019 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. GNSO Council meeting held 15:15 CET (Hamburg time) Coordinated Universal Time: 13:15 UTC: https://tinyurl.com/yyor7bfj 06:15 Los Angeles; 09:15 Washington; 14:15 London; 16:15 Moscow; 22:15 Tokyo; (Thursday 22 October) 00:15 Melbourne GNSO Council Meeting Remote Participation: Not available until 24 hours before. ___________________________________ Item 1. Seating of the 2020 / 2021 Council (20 mins) 1.1 - Roll Call 1.2 - Statements of Interest INCOMING COUNCILORS: Kurt Pritz: SOI<https://community.icann.org/display/gnsosoi/Kurt+Pritz+SOI> Registries Stakeholder Group Kristian Ørmen - SOI<https://community.icann.org/pages/viewpage.action?pageId=66081213> Registrars Stakeholder Group Mark Datysgeld: SOI<https://community.icann.org/display/gnsosoi/Mark+Datysgeld+SOI> Business Constituency Stephanie Perrin: SOI<https://community.icann.org/display/gnsosoi/Stephanie+Perrin+SOI> Non-Commercial Stakeholder Group Wisdom Donkor: SOI<https://community.icann.org/display/gnsosoi/Wisdom+Donkor+SOI> Non-Commercial Stakeholder Group Tomslin Samme-Nlar - SOI<https://community.icann.org/display/gnsosoi/Tomslin+Samme-Nlar+SOI> Non-Commercial Stakeholder Group Olga Cavall- SOI<https://community.icann.org/display/gnsosoi/Olga+Cavalli+SOI> - Non-Voting NomCom Appointee Jeffrey Neuman - SOI<https://community.icann.org/display/gnsosoi/Jeff+Neuman+SOI> - GNSO Council Liaison to the GAC Thank you again to outgoing Councilors: Elsa Saade, Erika Mann, James Gannon, Julf Helsingius, Keith Drazek, Michele Neylon, Rafik Dammak and Scott McCormick. 1.3 - Review / Amend Agenda Item 2. Election of the Chair (20 mins) One nomination was received for this position from Philippe Fouquart of the Non Contracted Party House. The GNSO reviewed the candidate statement<https://gnso.icann.org/sites/default/files/file/field-file-attach/fouquart-…> and held a question & answer session with the candidate on 24 September 2020. Here the GNSO Council will proceed to hold the election for its Chair for 2020-2021, according to the GNSO Operating Procedures (note Section 2.2 of the GNSO Operating Procedures on Officer Elections: Chair and Vice-Chairs (see Appendix 1 below)). Item 3. Any Other Business (0 min) None Appendix 1: Excerpt from GNSO Operating Procedures (Section 2.2) 2.2 https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Officer Elections: Chair and Vice-Chairs The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows: 1. The GNSO Chair shall be elected by a 60 percent vote of each house. 2. Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a current or incoming member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair. a. All ballots will include the “none of the above” option. In the event that a 60 percent vote of each house selects the “none of the above” option, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be scheduled for no sooner than 30 days after the unsuccessful vote. b. In the case of a tie for the most votes between the two candidates, or between a candidate and “none of above,” a second election will be held no sooner than 30 days. The candidates shall remain the same for this second election. In the case this second election also results in a tie, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful vote. c. The leading candidate will be defined as the one with the highest score. The score is calculated by adding together the voting percentages attained from each house. The highest percentage attainable in each house is 100. Thus, the maximum score a candidate can achieve is 200 as a result of attaining 100 percent of the votes from the contracted party house and 100 percent from the non-contracted party house (100 percent + 100 percent = score of 200). In case neither candidate reaches the 60 percent of each house threshold, a second ballot will be held between the leading candidate and “none of the above.” d. In case neither candidate reaches the 60 percent of each house threshold and the candidates do not tie, a second runoff ballot will be held between the leading candidate and “none of the above.” e. If the single candidate does not reach the 60 percent of each house threshold in the runoff ballot, then each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful runoff ballot. 1. Each house shall select a Council Vice-Chair from within its respective house. 2. A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. 3. The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). 4. In the event that the GNSO Council has not elected a GNSO Council Chair by the end of the previous Chair’s term, the Vice-Chairs will serve as Interim GNSO Co- Chairs to jointly oversee the new Chair election and conduct Council business until a successful election can be held. In the event that one or both Vice-Chairs’ terms ends concurrently with the term of the previous Chair, the procedures described in Section 2.2.1 below shall apply. 5. The Council shall inform the Board and the Community appropriately and post the election results on the GNSO website within 2 business days following each election and runoff ballot, whether successful or unsuccessful. Appendix 2: GNSO Council Voting Thresholds (ICANN Bylaws,<https://www.icann.org/resources/pages/governance/bylaws-en/#article11> Article 11, Section 3) (i) Except as otherwise specified in these Bylaws, Annex A, Annex A-1 or Annex A-2 hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: (i) Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. (ii) Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (iii) Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority (as defined in Section 11.3(i)(xix)). (iv) Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (v) Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. (vi) Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under (iv) or (v) above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. (vii) Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. (viii) Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. (ix) Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, (x) Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xi) Modification of Approved PDP Recommendation: Prior to Final Approval by the Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. (xii) Initiation of an Expedited Policy Development Process ("EPDP"): requires an affirmative vote of a GNSO Supermajority. (xiii) Approve an EPDP Team Charter: requires an affirmative vote of a GNSO Supermajority. (xiv) Approval of EPDP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xv) Approve an EPDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xvi) Initiation of a GNSO Guidance Process ("GGP"): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (xvii) Rejection of Initiation of a GGP Requested by the Board: requires an affirmative vote of a GNSO Supermajority. (xviii) Approval of GGP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xix) A "GNSO Supermajority" shall mean: (A) two-thirds (2/3) of the Council members of each House, or (B) three-fourths (3/4) of the Council members of one House and a majority of the Council members of the other House. https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Appendix 1 GNSO Council Voting Results table Absentee Voting Procedures https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf 4.4 Absentee Voting 4.1.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. 1. Initiate a Policy Development Process (PDP); 2. Approve a PDP recommendation; 3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; 4. Fill a Council position open for election. 4.1.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting’s adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.1.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.1.4 Absentee balloting does not affect quorum requirements. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 1

Meetings today
by Novoa, Osvaldo Oct. 13, 2020

Oct. 13, 2020

Dear all, I am sorry but today I won't be able to join any call. I've had a death in my family and we have the burial arrangements and the burial itself today. Best regards, Osvaldo Ing. Osvaldo Novoa Sub Gerente General RIIC Antel Guatemala 1075, Nivel 22 Montevideo, Uruguay www.antel.com.uy Tel.: +598 2928 6400 Fax: +598 2928 6411 ________________________________ El presente correo y cualquier posible archivo adjunto est? dirigido ?nicamente al destinatario del mensaje y contiene informaci?n que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Est? prohibida cualquier utilizaci?n, difusi?n o copia de este e-mail por cualquier persona o entidad que no sean las espec?ficas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicaci?n que haya sido emitida incumpliendo nuestra Pol?tica de Seguridad de la Informaci?n This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

FW: *with correct date in body of email* : Final Proposed Agenda | GNSO Council Meetings part 1 and 2 | 21 October 2020 at 13:00 CET / 11:00 UTC
by philippe.fouquart＠orange.com Oct. 12, 2020

Oct. 12, 2020

Dear ISPCP colleagues, On behalf of Osvaldo and myself, please see the agenda for the next Council call. You will note the items on the next steps for the EPDP (both on its scope and its chair), the rec 7 & the Thick Whois Transition Policy issue, the draft Operational Design Phase that we discussed on this list, as well as the first discussion on how future exchanges on the financial sustainability of the SSAD should proceed. Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Nathalie Peregrine Sent: Sunday, October 11, 2020 10:15 PM To: council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: [council] *with correct date in body of email* : Final Proposed Agenda | GNSO Council Meetings part 1 and 2 | 21 October 2020 at 13:00 CET / 11:00 UTC Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 21 October 2020 at 11:00 UTC. Draft GNSO Council Agenda 21 October 2020 - Part I 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/OAebC This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019 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. GNSO Council meeting held 13:00 CET (Hamburg time) Coordinated Universal Time: 11:00 UTC: https://tinyurl.com/y3nxs8rf 04:00 Los Angeles; 07:00 Washington; 12:00 London; 14:00 Moscow; 20:00 Tokyo; 22:00 Melbourne GNSO Council Meeting Remote Participation: Not available until 24 hours before. ___________________________________ Item 1: Administrative Matters (10 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 <https://gnso.icann.org/sites/default/files/policy/2020/minutes/minutes-gnso…> of the GNSO Council meeting on 20 August 2020 were posted on 04 Sep 2020. Minutes<https://gnso.icann.org/sites/default/files/policy/2020/minutes/minutes-gnso…> of the GNSO Council meeting on the 24 September 2020 were posted on 9 October 2020. 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 <https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (10 minutes) 3.1 - Action Decision Radar<https://community.icann.org/download/attachments/40175174/program_managemen…> - Next Steps for WHOIS Conflicts Procedure Implementation Advisory Group The GNSO Council has considered the proposed immediate actions and subsequent steps as outlined in the WHOIS Conflicts Procedure IAG (WHOIS IAG) Small Team’s proposal<http://mm.icann.org/pipermail/council/attachments/20201006/2a0c0c3e/Summary…>. The proposal outlines recommended next steps to consider with respect to modifying the implementation of the WHOIS Conflicts Procedure, in light of public comments received and changes to data protection law that may have affected the implementation of the Procedure. Specifically, the GNSO Council requests: 1. ICANN org, in consultation with contracted parties, to draft a proposal for a modification to the existing Procedure based on its past experience with both the WHOIS Conflicts Procedure and the registrar data retention waiver process. In formulating the draft proposal, the GNSO Council recommends that ICANN org consider changes to data protection law that may have affected the previous implementation of this Procedure in light of the contractual requirements, e.g., the General Data Protection Regulation. For example, should the identification of a new trigger to activate the procedure be considered given potential financial penalties under GDPR? 2. Following receipt of the proposal from ICANN org, the GNSO Council will consider the proposal and assess next steps, including seeking input from the community, if appropriate, given the substance of the proposal. Following the GNSO Council’s consideration, the GNSO Council may choose to adopt the proposal. 3. If the GNSO Council does not deem the proposal appropriate: a. the GNSO Council will recommend a small group of Council volunteers to review the WHOIS IAG draft charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-ica…> and confirm it is still fit for purpose; and b. Following confirmation of the Charter by the GNSO Council, the GNSO Council recommends launching the call for volunteers for the WHOIS IAG, taking into consideration the GNSO Council’s upcoming workload. For example, the call for volunteers may need to be postponed if no community bandwidth is available to immediately consider the issues. In the meantime, ICANN org, in conjunction with the EPDP Phase 1 IRT, will need to update relevant terminology pursuant to EPDP Phase 1, Rec. 27. 1. Should the GNSO Council consider the outcome developed from the WHOIS IAG unacceptable, the GNSO Council will consider initiating an EPDP to either change or repeal the Consensus Policy. 3.2 - Action Decision Radar<https://community.icann.org/download/attachments/40175174/program_managemen…> - Per the rationale circulated on 11 October 2020, Council agrees to launch a call for volunteers for a small team to develop both a draft charter and an EPDP scoping document for the IDN Policy Track 2. 3.3 - Following the GNSO Council’s consideration of the proposed immediate actions and subsequent steps as outlined here<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-pr…>, the GNSO Council directs: EPDP Phase 2a – Legal/natural and feasibility of unique contacts 1. The GNSO Policy Support Team communicate to the groups that have appointed members to the EPDP Team that the Council is expected to instruct the EPDP Team to further consider the topics of legal/natural and feasibility of unique contacts per the instructions above, as well as the expected timeframe, provided herein for reference, “[a]t the latest 3 months after reconvening, the Chair of the EPDP Team and GNSO Council Liaison to the EPDP will report back to the GNSO Council on the status of deliberations. Based on this report, which is expected to include an update on progress made and the expected likelihood of consensus recommendations, the GNSO Council will decide on next steps, which could include providing additional time for the EPDP to finalize its recommendations or termination of the EPDP if it is clear that no progress is being made or consensus is unlikely). Request groups to: a. Commence process of confirming members availability and/or re- appointing members to work on these topics. Proposed deadline: 15 November. b. Start developing proposals to address these topics, factoring in deliberations to date, that will allow the EPDP Team to kickstart deliberations on these topics when it reconvenes.” 1. The Council leadership to initiate an Expression of Interest Process to identify a new Chair. The EPDP Team shall recommence its deliberations upon selection and confirmation of a new Chair; however, should no suitable candidates be found or should the appointment process require significant time, Council leadership will inform the Council accordingly and recommend commencement of deliberations under the leadership of the GNSO Council liaison to the EPDP Team. Accuracy: 1. The GNSO Policy Support Team communicates to GNSO SG/Cs, as well as ICANN Advisory Committees that have expressed an interest in the topic of accuracy, the intent of the GNSO Council to launch a scoping team on this topic. Request groups to: a. Start thinking about members that have relevant knowledge and expertise that should join this effort once the scoping team launches. b. Start compiling relevant information and suggestions that would allow kickstarting the discussions on 1. and 2. once the scoping team is formed (see here<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-pr…> for resources already identified). 1. Council leadership to request ICANN Org to develop a briefing document that outlines both (i) existing accuracy requirements and programs and (ii) the corresponding impact that GDPR has had on implementing / enforcing these requirements and programs. The document, once delivered, will be provided to the scoping team to inform its deliberations. 2. GNSO Council to consider in the context of the Council Action / Decision Radar, the appropriate starting time for this effort, factoring in other projects that are in the pipeline. 3.4 - Confirmation of the Recommendations Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-epd…> to the ICANN Board regarding adoption of recommendations 1-22 contained in the Final Report from the EPDP Temporary Specification for gTLD Registration Data – Phase 2. 3.5 - Appointment of the GNSO Liaison to the Governmental Advisory Committee (motion<https://community.icann.org/x/OgebC>) Item 4: COUNCIL DISCUSSION - Discuss Draft Motion to Affirm intent of EPDP Phase 1 Recommendation 7 and Initiation of the Thick WHOIS Transition Policy EPDP (25 minutes) In adopting the Expedited Policy Development Process (EPDP) on the Temporary Specification Final Report and Recommendations, the Council requested that an informal Implementation Review Team (IRT) be established, which was done. After the recommendations were approved by the ICANN Board, the informal IRT transitioned to a formal IRT and has diligently been working to implement the policy recommendations. Within the IRT, there are diverging views amongst some IRT members on how to implement recommendation 7, especially in relation to the Thick WHOIS Transition Policy for .COM, .NET, and .JOBS The ICANN Board, taking note of the potential impasse, sent a letter<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> to the GNSO Council on 11 March 2020. The Council considered the letter and agreed that recommendation 7 did not explicitly overturn the Thick Whois Transition Policy; to do so will require the GNSO Council to initiate policy development. The Council sent a response<https://urldefense.com/v3/__https:/www.icann.org/en/system/files/correspond…> to the ICANN Board on 29 May 2020. The IRT has continued to try and implement recommendation 7 but has still been unable to reach agreement. As such and per the Council’s letter, the Council requested a briefing from, ”the GNSO Council liaison detailing the precise nature of the impasse so that the GNSO Council can make an informed determination on how to proceed.” During its September Council meeting, the Council received a briefing from the GNSO Council liaison to the IRT, Sebastien Ducos. The Council agreed to convene a small team of Councilors that was charged with establishing a path forward to try and resolve the impasse. That small team met to determine what the best practical path forward may be. Here, the Council will consider a draft motion that would do two things 1) Affirm the intent of EPDP Phase 1 Recommendation 7; and 2) initiate an EPDP on the Thick WHOIS Transition Policy. 4.1 - Introduction of topic (Council Vice-Chair, Pam Little) 4.2 – Council discussion 4.3 – Next steps Item 5: COUNCIL DISCUSSION - Draft Operational Design Phase for gTLD Policy Implementation (15 minutes) During the 23 September SO/AC Leaders call, the concept of an "Operational Design Phase" was introduced by Goran. The SO/AC Leaders had a preliminary discussion on the topic and Goran indicated that ICANN would produce a paper for community consideration and feedback. That paper<http://mm.icann.org/pipermail/council/attachments/20201005/2000130c/Design-…> was prepared and was shared with the Council on 5 October 2020. The objective for this new proposed design phase is to better prepare the Board by providing operational and resourcing information before making decisions on GNSO-approved policy recommendations. The paper notes that while the GNSO Council is the manager of the PDP and gTLD policy development is within the GNSO's remit, consensus policy making involves all stakeholders (including ACs who give advice to the Board). Further, the paper seeks to be clear that this design phase concept doesn't affect policy development or the Consensus Policy Implementation Framework. It recognizes that if policy issues are impacted, they rightfully go back to the GNSO for its consideration, rather than permitting ICANN Org or Board to make unilateral changes. The Stakeholder Groups and Constituencies were invited and encouraged to provide feedback to the paper. In addition, on a 6 October GNSO Council pre-ICANN working session, Karen Lentz from ICANN org provided additional information and rationale for the new concept. Here, Councilors will be invited to share their initial thoughts on the concept and the paper. 5.1 - Introduction of topic (Council leadership) 5.2 - Council discussion 5.3 - Next steps Item 6: COUNCIL DISCUSSION - Board Consultation Regarding Questions Surrounding the financial Sustainability of the System for Standardized Access and Disclosure (20 minutes) On 24 September 2020, the GNSO Council adopted the recommendations contained in the Expedited Policy Development Process (EPDP) on the Temporary Specification Phase 2 Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phas…>. Resolved clause 1b. states: b. [if 1a. is adopted] Noting some of the questions surrounding the financial sustainability of SSAD and some of the concerns expressed within the different minority statements, the GNSO Council requests a consultation with the ICANN Board as part of the delivery of the GNSO Council Recommendations Report to the ICANN Board to discuss these issues, including whether a further cost-benefit analysis should be conducted before the ICANN Board considers all SSAD-related recommendations for adoption. The request for a consultation with the ICANN Board is not usually an element of the transition of GNSO-approved recommendations from the GNSO Council to the ICANN Board. As such, the Council will need to consider how best to engage with the Board in seeking this consultation. Here, the Council will discuss next steps as it relates to resolved clause 1b, including whether the draft Transmittal Letter<https://gnso.icann.org/en/drafts/draft-transmittal-letter-icann-board-08oct…> accurately captures the agreed-upon approach of the Council. 6.1 - Introduction of topic (Council leadership) 6.2 - Council discussion 6.3 - Next steps Item 7: COUNCIL DISCUSSION - ADR Item - Council to Consider Delay of the Request for the Policy Status Report for the Expiration Policy(ies) (10 minutes) As indicated on the Action Decision Radar<https://community.icann.org/display/gnsocouncilmeetings/Action+Items?previe…>, the GNSO Council is to consider when to request a Policy Status Report to conduct a review of the two Expiration Policies, the Expired Domain Deletion Policy<https://www.icann.org/resources/pages/registars/accreditation/eddp-en> (EDDP) and the Expired Registration Recovery Policy<https://www.icann.org/resources/pages/errp-2013-02-28-en> (ERRP). Given the concerns about capacity, along with the circumstances that no known issues have presented themselves, Council leadership is suggesting that the request for Policy Status Reports for these two Consensus Policies can be delayed by a period of 24 months, assuming no substantive issues arise during that time. This would have the effect of deferring the request for a Policy Status Report on the EDDP and ERRP until at least November 2022, where it would then be discussed again to determine if a request is timely. Here, the Council will consider whether it agrees with this suggestion and if so, agree to include on the November consent agenda. 7.1 - Introduction of topic (Council leadership) 7.2 - Council discussion 7.3 - Next steps Item 8: ANY OTHER BUSINESS (20 minutes) 8.1 - Farewell to outgoing Councilors (Elsa Saade, Erika Mann, James Gannon, Julf Helsingius, Keith Drazek, Michele Neylon, Rafik Dammak and Scott McCormick.) 8.2 - 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. 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… References for Coordinated Universal Time of 11:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 04:00 San José, Costa Rica (CST) UTC-6 06:00 New York/Washington DC, USA (EDT) UTC-4 07:00 Buenos Aires, Argentina (ART) UTC-3 08:00 Rio de Janeiro, Brazil (BRST) UTC-3 08:00 London, United Kingdom (GMT) UTC+1 12:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 12:00 Paris, France (CEST) UTC+2 13:00 Moscow, Russia (MST) UTC+3 14:00 Singapore (SGT) UTC+8 19:00 Tokyo, Japan (JST) UTC+9 20:00 Melbourne, Australia (AEDT) UTC+11 22:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 25 of October 2020, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 01 of November 2020 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/y3nxs8rf Final GNSO Council Agenda 21 October 2020 - Part II (Admin) 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/OAebC This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5 updated on 24 October 2019 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. GNSO Council meeting held 15:15 CET (Hamburg time) Coordinated Universal Time: 13:15 UTC: https://tinyurl.com/yyor7bfj 06:15 Los Angeles; 09:15 Washington; 14:15 London; 16:15 Moscow; 22:15 Tokyo; (Thursday 22 October) 00:15 Melbourne GNSO Council Meeting Remote Participation: Not available until 24 hours before. ___________________________________ Item 1. Seating of the 2020 / 2021 Council (20 mins) 1.1 - Roll Call 1.2 - Statements of Interest INCOMING COUNCILORS: Kurt Pritz: SOI<https://community.icann.org/display/gnsosoi/Kurt+Pritz+SOI> Registries Stakeholder Group Kristian Ørmen - SOI<https://community.icann.org/pages/viewpage.action?pageId=66081213> Registrars Stakeholder Group Mark Datysgeld: SOI<https://community.icann.org/display/gnsosoi/Mark+Datysgeld+SOI> Business Constituency Stephanie Perrin: SOI<https://community.icann.org/display/gnsosoi/Stephanie+Perrin+SOI> Non-Commercial Stakeholder Group Wisdom Donkor: SOI<https://community.icann.org/display/gnsosoi/Wisdom+Donkor+SOI> Non-Commercial Stakeholder Group Tomslin Samme-Nlar - SOI<https://community.icann.org/display/gnsosoi/Tomslin+Samme-Nlar+SOI> Non-Commercial Stakeholder Group Olga Cavall- SOI<https://community.icann.org/display/gnsosoi/Olga+Cavalli+SOI> - Non-Voting NomCom Appointee Jeffrey Neuman - SOI<https://community.icann.org/display/gnsosoi/Jeff+Neuman+SOI> - GNSO Council Liaison to the GAC Thank you again to outgoing Councilors: Elsa Saade, Erika Mann, James Gannon, Julf Helsingius, Keith Drazek, Michele Neylon, Rafik Dammak and Scott McCormick. 1.3 - Review / Amend Agenda Item 2. Election of the Chair (20 mins) One nomination was received for this position from Philippe Fouquart of the Non Contracted Party House. The GNSO reviewed the candidate statement<https://gnso.icann.org/sites/default/files/file/field-file-attach/fouquart-…> and held a question & answer session with the candidate on 24 September 2020. Here the GNSO Council will proceed to hold the election for its Chair for 2020-2021, according to the GNSO Operating Procedures (note Section 2.2 of the GNSO Operating Procedures on Officer Elections: Chair and Vice-Chairs (see Appendix 1 below)). Item 3. Any Other Business (0 min) None Appendix 1: Excerpt from GNSO Operating Procedures (Section 2.2) 2.2 https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Officer Elections: Chair and Vice-Chairs The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows: 1. The GNSO Chair shall be elected by a 60 percent vote of each house. 2. Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a current or incoming member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair. a. All ballots will include the “none of the above” option. In the event that a 60 percent vote of each house selects the “none of the above” option, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be scheduled for no sooner than 30 days after the unsuccessful vote. b. In the case of a tie for the most votes between the two candidates, or between a candidate and “none of above,” a second election will be held no sooner than 30 days. The candidates shall remain the same for this second election. In the case this second election also results in a tie, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful vote. c. The leading candidate will be defined as the one with the highest score. The score is calculated by adding together the voting percentages attained from each house. The highest percentage attainable in each house is 100. Thus, the maximum score a candidate can achieve is 200 as a result of attaining 100 percent of the votes from the contracted party house and 100 percent from the non-contracted party house (100 percent + 100 percent = score of 200). In case neither candidate reaches the 60 percent of each house threshold, a second ballot will be held between the leading candidate and “none of the above.” d. In case neither candidate reaches the 60 percent of each house threshold and the candidates do not tie, a second runoff ballot will be held between the leading candidate and “none of the above.” e. If the single candidate does not reach the 60 percent of each house threshold in the runoff ballot, then each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful runoff ballot. 1. Each house shall select a Council Vice-Chair from within its respective house. 2. A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. 3. The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). 4. In the event that the GNSO Council has not elected a GNSO Council Chair by the end of the previous Chair’s term, the Vice-Chairs will serve as Interim GNSO Co- Chairs to jointly oversee the new Chair election and conduct Council business until a successful election can be held. In the event that one or both Vice-Chairs’ terms ends concurrently with the term of the previous Chair, the procedures described in Section 2.2.1 below shall apply. 5. The Council shall inform the Board and the Community appropriately and post the election results on the GNSO website within 2 business days following each election and runoff ballot, whether successful or unsuccessful. Appendix 2: GNSO Council Voting Thresholds (ICANN Bylaws,<https://www.icann.org/resources/pages/governance/bylaws-en/#article11> Article 11, Section 3) (i) Except as otherwise specified in these Bylaws, Annex A, Annex A-1 or Annex A-2 hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: (i) Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. (ii) Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (iii) Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority (as defined in Section 11.3(i)(xix)). (iv) Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (v) Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. (vi) Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under (iv) or (v) above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. (vii) Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. (viii) Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. (ix) Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, (x) Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xi) Modification of Approved PDP Recommendation: Prior to Final Approval by the Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. (xii) Initiation of an Expedited Policy Development Process ("EPDP"): requires an affirmative vote of a GNSO Supermajority. (xiii) Approve an EPDP Team Charter: requires an affirmative vote of a GNSO Supermajority. (xiv) Approval of EPDP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xv) Approve an EPDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xvi) Initiation of a GNSO Guidance Process ("GGP"): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (xvii) Rejection of Initiation of a GGP Requested by the Board: requires an affirmative vote of a GNSO Supermajority. (xviii) Approval of GGP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xix) A "GNSO Supermajority" shall mean: (A) two-thirds (2/3) of the Council members of each House, or (B) three-fourths (3/4) of the Council members of one House and a majority of the Council members of the other House. https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Appendix 1 GNSO Council Voting Results table Absentee Voting Procedures https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf 4.4 Absentee Voting 4.1.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. 1. Initiate a Policy Development Process (PDP); 2. Approve a PDP recommendation; 3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; 4. Fill a Council position open for election. 4.1.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting’s adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.1.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.1.4 Absentee balloting does not affect quorum requirements. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 1

Re: [ispcp] Fwd: [council] Draft Operational Design Phase for gTLD Policy Implementation: For Initial Feedback.
by philippe.fouquart＠orange.com Oct. 8, 2020

Oct. 8, 2020

Thanks Wolf-Ulrich, As input to our discussion, please note the elements provided by Mary after yesterday's working session. I also understand from the answer provided by staff during that session that this framework, although not yet formalized, will be put in place as soon as the preparation for the board's vote on EPDP phase 2 recommendations. I think there's some recognition that this may be helpful but also some concerns relative to this adding an extra layer of complexity or on the risks of seeing this operational design phase address policy items that may have been overlooked by the PDP WG. Regards, Philippe -----Original Message----- From: ispcp [mailto:ispcp-bounces@gnso.icann.org] On Behalf Of wuknoben(a)gmail.com Sent: Thursday, October 08, 2020 12:14 AM To: 'Novoa, Osvaldo'; ispcp(a)gnso.icann.org Subject: Re: [ispcp] Fwd: [council] Draft Operational Design Phase for gTLD Policy Implementation: For Initial Feedback. Thanks Osvaldo and Philippe! Some observations: I recognize the necessity for the Board to have a complete picture of the impact of recommendations (cost, personal ressources etc.). The proposal adds another process (Design Phase) and working body (Design Feedback Group, DFG) to the existing ones which would build additional working load on the community. The work anyway is staff's obligation, not the community's one. How could this effort be minimized? The alternative option, described beginning on page 7, seems to be a possible solution and could be investigated a bit more in detail (engagement of the PDP-WG). Maybe this way the PDP-WG could cover the tasks of the DFG which otherwise would need a specific election process within the GNSO. Just some thoughts for your council debates. Best regards Wolf-Ulrich -----Ursprüngliche Nachricht----- Von: ispcp <ispcp-bounces(a)gnso.icann.org> Im Auftrag von Novoa, Osvaldo Gesendet: Dienstag, 6. Oktober 2020 02:07 An: ispcp(a)gnso.icann.org Betreff: [ispcp] Fwd: [council] Draft Operational Design Phase for gTLD Policy Implementation: For Initial Feedback. Hello all, Please see the attached mail, I would appreciate your comments. Best regards, Osvaldo Enviado desde mi iPhone Inicio del mensaje reenviado: De: "Drazek, Keith via council" <council(a)gnso.icann.org> Fecha: 5 de octubre de 2020, 18:35:06 UYT Para: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "stephanie(a)digitaldiscretion.ca" <stephanie(a)digitaldiscretion.ca>, "aheineman(a)godaddy.com" <aheineman(a)godaddy.com>, "bruna.mrtns(a)gmail.com" <bruna.mrtns(a)gmail.com>, "wolf-ulrich.knoben(a)t-online.de" <wolf-ulrich.knoben(a)t-online.de>, "claudia.selli(a)intl.att.com" <claudia.selli(a)intl.att.com> Asunto: Re: [council] Draft Operational Design Phase for gTLD Policy Implementation: For Initial Feedback. Responder a: "Drazek, Keith" <kdrazek(a)verisign.com> Hi all, During the 23 September SO/AC Leaders call with Goran, Maarten and Leon, the concept of an “Operational Design Phase” was introduced by Goran. We had a preliminary discussion on the topic and Goran indicated that ICANN would produce a paper for community consideration and feedback. That paper is attached here for your review, and Goran’s email to the SO/AC Leaders is below. I’ll highlight 3 points from Goran’s note and from the discussion on the call: * The objective for the design phase is to better prepare the Board by providing operational and resourcing information before making decisions on GNSO-approved policy recommendations. * While the GNSO Council is the manager of the PDP and gTLD policy development is within the GNSO's remit, consensus policy making involves all stakeholders (including ACs who give advice to the Board). * This design phase concept doesn't affect policy development or the CPIF. It recognizes that if policy issues are impacted, they rightfully go back to the GNSO for its consideration, rather than permitting ICANN Org or Board to make unilateral changes. (I made this point during the call) Please review the attached paper and work within your SGs and Cs to develop feedback. Also, Karen Lentz will touch on this during our Tuesday Council Working Session. To Goran’s last point about conducting a “fuller consultation on the gTLD policy lifecycle,” we’ll need to ensure that the GNSO Council and our SGs and Cs are prepared to engage where appropriate and in light of our ongoing PDP 3.0 work and the upcoming GNSO Review. Thanks and regards, Keith From: soac-chairs <soac-chairs-bounces(a)icann.org<mailto:soac-chairs-bounces@icann.org>> On Behalf Of Goran Marby Sent: Friday, October 2, 2020 3:19 PM To: soac-chairs(a)icann.org<mailto:soac-chairs@icann.org> Cc: Goran Marby <goran.marby(a)icann.org<mailto:goran.marby@icann.org>>; David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>>; Cassia Oliveira <cassia.oliveira(a)icann.org<mailto:cassia.oliveira@icann.org>> Subject: [EXTERNAL] [soac-chairs] Draft Operational Design Phase for gTLD Policy Implementation: For Initial Feedback. Cassia Oliveira on behalf of Goran Marby Dear SOAC leaders, Thank you again for taking the time to meet with Maarten and me last week. I am writing to follow up on one of ICANN org’s action items from that call, which was for me to finalize and circulate to you a proposal for a new Operational Design Phase relating to the implementation of approved gTLD policies. As we discussed, the objective for an additional design phase is to allow the Board to obtain relevant information about any operational and resourcing issues associated with certain policy implementation efforts. Accordingly, the Operational Design Phase is envisioned to take place prior to Board action on GNSO-approved policy recommendations, initiated through a Board request to ICANN org. Our expectation is that an Operational Design Phase will likely only be needed for complex, costly or other large-scale implementation efforts. I appreciate the thoughtful and substantive discussion we had on this topic during our call. While gTLD policy development work is managed by the GNSO, the other Supporting Organizations and the Advisory Committees play important roles in ensuring that ICANN consensus policies are developed through community consensus and are appropriately resourced. Thank you for the comments and suggestions you made on the call, which we have tried to address as much as possible in this initial draft paper. Please circulate the paper to your community groups for their review and further discussion. As I mentioned on our call, ICANN org will continue to refine the paper and welcome your feedback as part of this iterative process. After ICANN69, we plan to conduct a fuller community consultation on the gTLD policy lifecycle, to include an updated version of this paper and to gather community feedback on any updates we can make to improve the efficacy and efficiency of the policy making process. Best regards, Göran Marby President & CEO ICANN +1(310) 578 8690 Cássia Oliveira Sr. Manager, Office of the President & CEO cassia.oliveira(a)icann.org<mailto:cassia.oliveira@icann.org> +1(310) 578 8656 ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy. _______________________________________________ ispcp mailing list ispcp(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/ispcp _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

3 2

Fwd: [council] Draft Operational Design Phase for gTLD Policy Implementation: For Initial Feedback.
by Novoa, Osvaldo Oct. 7, 2020

Oct. 7, 2020

Hello all, Please see the attached mail, I would appreciate your comments. Best regards, Osvaldo Enviado desde mi iPhone Inicio del mensaje reenviado: De: "Drazek, Keith via council" <council(a)gnso.icann.org> Fecha: 5 de octubre de 2020, 18:35:06 UYT Para: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "stephanie(a)digitaldiscretion.ca" <stephanie(a)digitaldiscretion.ca>, "aheineman(a)godaddy.com" <aheineman(a)godaddy.com>, "bruna.mrtns(a)gmail.com" <bruna.mrtns(a)gmail.com>, "wolf-ulrich.knoben(a)t-online.de" <wolf-ulrich.knoben(a)t-online.de>, "claudia.selli(a)intl.att.com" <claudia.selli(a)intl.att.com> Asunto: Re: [council] Draft Operational Design Phase for gTLD Policy Implementation: For Initial Feedback. Responder a: "Drazek, Keith" <kdrazek(a)verisign.com> Hi all, During the 23 September SO/AC Leaders call with Goran, Maarten and Leon, the concept of an “Operational Design Phase” was introduced by Goran. We had a preliminary discussion on the topic and Goran indicated that ICANN would produce a paper for community consideration and feedback. That paper is attached here for your review, and Goran’s email to the SO/AC Leaders is below. I’ll highlight 3 points from Goran’s note and from the discussion on the call: * The objective for the design phase is to better prepare the Board by providing operational and resourcing information before making decisions on GNSO-approved policy recommendations. * While the GNSO Council is the manager of the PDP and gTLD policy development is within the GNSO's remit, consensus policy making involves all stakeholders (including ACs who give advice to the Board). * This design phase concept doesn't affect policy development or the CPIF. It recognizes that if policy issues are impacted, they rightfully go back to the GNSO for its consideration, rather than permitting ICANN Org or Board to make unilateral changes. (I made this point during the call) Please review the attached paper and work within your SGs and Cs to develop feedback. Also, Karen Lentz will touch on this during our Tuesday Council Working Session. To Goran’s last point about conducting a “fuller consultation on the gTLD policy lifecycle,” we’ll need to ensure that the GNSO Council and our SGs and Cs are prepared to engage where appropriate and in light of our ongoing PDP 3.0 work and the upcoming GNSO Review. Thanks and regards, Keith From: soac-chairs <soac-chairs-bounces(a)icann.org<mailto:soac-chairs-bounces@icann.org>> On Behalf Of Goran Marby Sent: Friday, October 2, 2020 3:19 PM To: soac-chairs(a)icann.org<mailto:soac-chairs@icann.org> Cc: Goran Marby <goran.marby(a)icann.org<mailto:goran.marby@icann.org>>; David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>>; Cassia Oliveira <cassia.oliveira(a)icann.org<mailto:cassia.oliveira@icann.org>> Subject: [EXTERNAL] [soac-chairs] Draft Operational Design Phase for gTLD Policy Implementation: For Initial Feedback. Cassia Oliveira on behalf of Goran Marby Dear SOAC leaders, Thank you again for taking the time to meet with Maarten and me last week. I am writing to follow up on one of ICANN org’s action items from that call, which was for me to finalize and circulate to you a proposal for a new Operational Design Phase relating to the implementation of approved gTLD policies. As we discussed, the objective for an additional design phase is to allow the Board to obtain relevant information about any operational and resourcing issues associated with certain policy implementation efforts. Accordingly, the Operational Design Phase is envisioned to take place prior to Board action on GNSO-approved policy recommendations, initiated through a Board request to ICANN org. Our expectation is that an Operational Design Phase will likely only be needed for complex, costly or other large-scale implementation efforts. I appreciate the thoughtful and substantive discussion we had on this topic during our call. While gTLD policy development work is managed by the GNSO, the other Supporting Organizations and the Advisory Committees play important roles in ensuring that ICANN consensus policies are developed through community consensus and are appropriately resourced. Thank you for the comments and suggestions you made on the call, which we have tried to address as much as possible in this initial draft paper. Please circulate the paper to your community groups for their review and further discussion. As I mentioned on our call, ICANN org will continue to refine the paper and welcome your feedback as part of this iterative process. After ICANN69, we plan to conduct a fuller community consultation on the gTLD policy lifecycle, to include an updated version of this paper and to gather community feedback on any updates we can make to improve the efficacy and efficiency of the policy making process. Best regards, Göran Marby President & CEO ICANN +1(310) 578 8690 Cássia Oliveira Sr. Manager, Office of the President & CEO cassia.oliveira(a)icann.org<mailto:cassia.oliveira@icann.org> +1(310) 578 8656 ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

3 2

RV: [Community-Finance] Planning and Financial Update at ICANN 69 Prep Week
by Novoa, Osvaldo Oct. 1, 2020

Oct. 1, 2020

For your information. Best regards, Osvaldo De: Community-Finance [mailto:community-finance-bounces@icann.org] En nombre de Planning Enviado el: jueves, 01 de octubre de 2020 03:12 p.m. Para: community-finance(a)icann.org CC: Planning Asunto: [Community-Finance] Planning and Financial Update at ICANN 69 Prep Week Dear ICANN Community: The Planning team in collaboration with the Finance team will host an ICANN69 prep week session on Oct 06, 2020 at 16:30 UTC. We look forward to your participation and invite you to share this information with other community members who would like to learn more about ICANN's Planning Process and Financial update. Please refer to the link below for more details of the session: https://69.schedule.icann.org/meetings/addHduMjKbH9Ezdbg#/?limit=10&sortByF… Best regards, ICANN Planning Team. ________________________________ El presente correo y cualquier posible archivo adjunto est? dirigido ?nicamente al destinatario del mensaje y contiene informaci?n que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Est? prohibida cualquier utilizaci?n, difusi?n o copia de este e-mail por cualquier persona o entidad que no sean las espec?ficas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicaci?n que haya sido emitida incumpliendo nuestra Pol?tica de Seguridad de la Informaci?n This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

Charter
by Novoa, Osvaldo Sept. 21, 2020

Sept. 21, 2020

Hello all, I was going to present my comments to the draft some time ago, but got distracted with my day to day work and couldn't make the time. On a general idea I think that our charter should be very specific so that it is very clear who can be a member and who cannot (which is not detailed in the draft). To be part of the ISPCP cannot be just a decision of the candidate but it must fulfill the specific requirements of the charter. The proposed requirements are very clear and specific so I agree with them. To see if we should consider any other requirements for our charter I checked the Business Constituency Charter and found some interesting considerations: 5.1.2 Ineligible Organizations. The purpose of the Business Constituency is to represent the interests of Business Users as described in §5.1.1. To avoid conflicts of interest, the following is a non-exhaustive list of entities which are not eligible to be a Member: a. Not-for-profit entities excepting trade associations or coalitions representing for-profit entities; b. Entities which derive more than 30 percent of annual revenue as a registry operator, registrar, or domain name reseller (collectively, "Contracted Parties"); c. Political organizations whose primary purpose is to elect government officials; d. Individuals or entities that represent governments in any way or in any capacity at ICANN; e. Other groups not chartered to support Business Users as described in §5.1.1. An entity which does not fall within the non-exhaustive criteria set forth above may nonetheless be ineligible to be a Member based upon a review and determination by the Credentials Committee in accordance with the provisions contained in §5.6. 5.1.3 Non-Voting Members: Any otherwise eligible Member according to §5.1.1 that votes in another Stakeholder Group or Constituency in either house of the GNSO, or is owned, controlled by, or under common ownership with any entity that votes in the Business Constituency or another Stakeholder Group or Constituency is ineligible for Voting status within the Business Constituency; however, such Member may be accorded Non-Voting status subject to the following: a. A representative of a Non-Voting Member may not hold an elected position, including Officer or GNSO Council Representative, within the Business Constituency; and b. With the exception of restrictions specified in §5.1.3, all other rights and privileges of membership apply to Non-Voting Members. 5.1.4 Representation. Whether Voting or Non-Voting, Members must agree to represent the interests of Business Users for all business and matters addressed inside the Business Constituency. I think we should consider if our Charter should include something in this line, I am worried in particular to the possibility of the same company participating in several Constituencies and obtaining some form of control over ICANN by their multiple votes. This is more possible if we are considering a Association of Companies directing the votes of its associates. If we don't insure the independence of the different constituencies we'll lose the multistakeholder model. Best regards, Osvaldo Ing. Osvaldo Novoa Sub Gerente General RIIC Antel Guatemala 1075, Nivel 22 Montevideo, Uruguay www.antel.com.uy Tel.: +598 2928 6400 Fax: +598 2928 6411 ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

Fwd: [council] FW: [gnso-secs] Call for volunteers: ccPDP4 on the (de)selection of IDN ccTLD strings
by Novoa, Osvaldo Aug. 3, 2020

Aug. 3, 2020

For your information and if anyone is interested. Best regards, Osvaldo Enviado desde mi iPhone Inicio del mensaje reenviado: De: "Drazek, Keith via council" <council(a)gnso.icann.org> Fecha: 3 de agosto de 2020, 17:42:50 UYT Para: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Asunto: [council] FW: [gnso-secs] Call for volunteers: ccPDP4 on the (de)selection of IDN ccTLD strings Responder a: "Drazek, Keith" <kdrazek(a)verisign.com> Hi all, The deadline for identifying GNSO representatives for the ccNSO’s policy development process on IDNs (ccPDP4) is this Friday, August 7. It will be important for the GNSO and ccNSO to understand our respective work in this area, so GNSO participation is encouraged. Please raise this with your SGs and Cs. Thanks, Keith From: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Sent: Monday, August 3, 2020 1:24 PM To: Drazek, Keith <kdrazek(a)verisign.com> Subject: [EXTERNAL] FW: [gnso-secs] Call for volunteers: ccPDP4 on the (de)selection of IDN ccTLD strings From: Gnso-secs <gnso-secs-bounces(a)icann.org<mailto:gnso-secs-bounces@icann.org>> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org<mailto:nathalie.peregrine@icann.org>> Date: Friday, 17 July 2020 at 15:02 To: 'Bruna Martins dos Santos' <bruna.mrtns(a)gmail.com<mailto:bruna.mrtns@gmail.com>>, Joan Kerr <joankerr(a)fbsc.org<mailto:joankerr@fbsc.org>>, Stephanie Perrin <stephanie.perrin(a)mail.utoronto.ca<mailto:stephanie.perrin@mail.utoronto.ca>> Cc: "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, Maryam Bakoshi <maryam.bakoshi(a)icann.org<mailto:maryam.bakoshi@icann.org>> Subject: [gnso-secs] Call for volunteers: ccPDP4 on the (de)selection of IDN ccTLD strings Dear GNSO Chairs, All, The ccNSO seeks volunteers for the Working Group which is tasked to develop policy recommendations for the (de)selection of IDN ccTLD strings, as part of the fourth ccNSO Policy Development Process (ccPDP4). In time, the results of this ccPDP will replace the IDN ccTLD Fast Track Process, which currently guides the selection process of IDN ccTLD strings. This Working Group is open to participants from other ICANN stakeholder groups and the ccNSO welcomes GNSO representatives to join this important policy development effort. The call for volunteers will close Friday, 7 August 2020 (23:59 UTC), however participants can join after this date as well. The Group is expected to kick off its work at the start of September. Members, participants, and experts commit to participate actively and regularly in the work of the WG and are expected to have at least a basic understanding of the reference material (see attachment and included below). Those that apply also commit to the charter<https://secure-web.cisco.com/1s65TC2OFJzEjPSt7DE9koA7dOnsArkM0C_QlVwk9bGQ40…> of the WG, including but not limited to the internal decision making and standards of behavior. Should there be interested parties that intend to join as a participants - once your respective SO/AC has completed its internal appoint procedure - please inform the ccNSO Secretariat (ccnsosecretariat(a)icann.org<mailto:ccnsosecretariat@icann.org>) about the names and email addresses, to add them to the mailing list. Read more * Detailed background information about ccPDP4 is included below. * Recently, the ccNSO Secretariat held a webinar to inform the community about the topics to be addressed and the working methods of the ccPDP4 WG. Consult the recording and slide deck here<https://secure-web.cisco.com/1EwMoKrr2C6iYXsCAli8ynCXGv3N0ury3Bh75_gXPCudvk…>. * On 16 July, the ccNSO Secretariat shared a call for volunteers with the ccNSO membership and broader ccTLD community, targeted at ccTLD managers as potential members of the Working Group. Please find the call for volunteers here [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/announcements/announc…>. You may find the information regarding who can join, the workload and working method and the background and reference materials useful. * In attachment you will be able to find information regarding the call for volunteers, that can be shared with your respective SO/AC. Kindly ensure to adjust the “how to apply” section. About ccPDP4 In September 2013, the ccNSO submitted the IDN country code policy development process (ccPDP2) Board Report to the ICANN Board of Directors. The recommended policy ccPDP2 contains two parts: 1. High-level proposals for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures. 2. Proposals to enable the inclusion of IDN ccTLDs in the ccNSO. By mutual understanding between the ccNSO and the ICANN Board, the Fast Track Process evolved, to test and gain more experience with the policy aspects pertaining to the introduction of IDN ccTLDs. The latest step in the evolution of the Fast Track Process was the introduction of the Risk Mitigation Panel and related process in case of confusing similarity of a requested IDNccTLD string in 2018. In March 2019 the ccNSO Council tasked a team (Preliminary Review Team or PRT) to review ccPDP2 in light of the impact of the following related processes on the recommended policies: * The evolved Fast Track Process, * The request of the ICANN Board of Directors with respect to IDN Variants and * Other relevant developments such as retirement of the (IDN) ccTLDs Based on its high-level analysis, the PRT identified various issues with the recommended policy for the selection of IDN ccTLD strings and advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address these issues, including the de-selection of IDN ccTLD strings. In January 2020, the ccNSO Council requested an Issue Report. In May 2020, after the Issue Report was submitted to Council, including the opinion of ICANN’s General Counsel, the ccNSO Council initiated the ccNSO Policy Development Process 4 to develop policy for the (de-)selection of IDN ccTLD strings. In addition, it was proposed to conduct ccPDP4 by way of a chartered working group, according to the proposed timeline. The Issue report will be published for comments shortly. The public comments, if any, will be used to inform the discussions of the WG. Reference Materials & Links * Issue report<https://secure-web.cisco.com/1gUcPYhKIK559glvrjKWDlRn-e39dSsgVGicFxTgGcwhCU…> * ccPDP4 section on ccNSO website: https://ccnso.icann.org/en/workinggroups/idn-cctld-strings.htm [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/workinggroups/idn-cct…> * ccPDP4 Workspace: https://community.icann.org/x/ZoBIC<https://secure-web.cisco.com/1S8wIMCBWer14yfW6q_qJ9iHS-4vqliC14UgYHKM9Aen_F…> Thank you. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]<https://urldefense.com/v3/__https:/twitter.com/ccNSO__;!!PtGJab4!oaAoZdUSgy…> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/ccnso/__;!!PtGJab4!oaAo…> http://ccnso.icann.org [ccnso.icann.org]<https://urldefense.com/v3/__http:/ccnso.icann.org__;!!PtGJab4!oaAoZdUSgyVj4…> _______________________________________________ Gnso-secs mailing list Gnso-secs(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-secs _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on._______________________________________________ Gnso-secs mailing list Gnso-secs(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-secs _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!PtGJab… ) and the website Terms of Service (https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!PtGJab4!o… ). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

Today's call
by Novoa, Osvaldo June 1, 2020

June 1, 2020

Dear all, Unfortunately I won’t be able to join today’s call. A new President of our Company has been designated, interim for now, and he has summoned me for a meeting with the Board today, at the same time of our call. I am really sorry. Best regards, Osvaldo ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

Transfer Policy
by Novoa, Osvaldo April 27, 2020

April 27, 2020

Dear all, Just to let you know that in the next Council we will be vote for a request for an Issue Report on the Report from the Transfer Policy Scoping Team<https://gnso.icann.org/sites/default/files/file/field-file-attach/transfer-…>. Best regards, Osvaldo ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0