Hi Anne,
I will certainly take you up on that offer.
Kindly,
Sebastien Ducos
GoDaddy Registry | Senior Client Services Manager
+33612284445
France & Australia
From:
Aikman-Scalese, Anne <AAikman@lewisroca.com>
Date: Tuesday, 6 December 2022 at 7:00 pm
To: Steve Chan <steve.chan@icann.org>, Sebastien Ducos <Sebastien@registry.godaddy>, Terri Agnew <terri.agnew@icann.org>, council@gnso.icann.org <council@gnso.icann.org>, liaison6c@gnso.icann.org <liaison6c@gnso.icann.org>
Cc: gnso-secs@icann.org <gnso-secs@icann.org>, GNSO-Chairs <gnso-chairs@icann.org>
Subject: RE: [gnso-chairs] [council] Proposed Agenda | GNSO Council Meeting| Thursday, 15 December 2022
Caution:
This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious
emails to isitbad@.
Thanks Steve. I am happy to comment on Agenda Item 7 after Council Leadership introduction of the topic if that is desirable from Leadership’s point of view.
Anne
|
Anne E. Aikman-Scalese |
|
Of Counsel |
|
|
|
D. 520.629.4428 |
|
|
From: Steve Chan <steve.chan@icann.org>
Sent: Tuesday, December 6, 2022 9:51 AM
To: Sebastien@registry.godaddy; Aikman-Scalese, Anne <AAikman@lewisroca.com>; Terri Agnew <terri.agnew@icann.org>; council@gnso.icann.org; liaison6c@gnso.icann.org
Cc: gnso-secs@icann.org; GNSO-Chairs <gnso-chairs@icann.org>
Subject: Re: [gnso-chairs] [council] Proposed Agenda | GNSO Council Meeting| Thursday, 15 December 2022
[EXTERNAL]
Hi Sebastien, Anne,
The item has been added as agenda item 7 here:
https://community.icann.org/x/fAjVD. Hopefully it is captured correctly but if not, please let me know.
Best,
Steve
From: Gnso-chairs <gnso-chairs-bounces@icann.org> on behalf of Sebastien--- via Gnso-chairs
<gnso-chairs@icann.org>
Reply-To: "Sebastien@registry.godaddy" <Sebastien@registry.godaddy>
Date: Monday, December 5, 2022 at 2:00 PM
To: "Aikman-Scalese, Anne" <AAikman@lewisroca.com>, Terri Agnew <terri.agnew@icann.org>, "council@gnso.icann.org" <council@gnso.icann.org>,
"liaison6c@gnso.icann.org" <liaison6c@gnso.icann.org>
Cc: "gnso-secs@icann.org" <gnso-secs@icann.org>, GNSO-Chairs <gnso-chairs@icann.org>
Subject: Re: [gnso-chairs] [council] Proposed Agenda | GNSO Council Meeting| Thursday, 15 December 2022
Hi Anne,
We just had our Leadership meeting to review our agenda and I am afraid this was missed indeed. The good news is that contrary to last month, we have more time flexibility this time. We should be able to fit
it in.
Kindly
Sebastien Ducos
GoDaddy Registry | Senior Client Services Manager
+33612284445
France & Australia
From:
Aikman-Scalese, Anne <AAikman@lewisroca.com>
Date: Monday, 5 December 2022 at 10:41 pm
To: Terri Agnew <terri.agnew@icann.org>,
council@gnso.icann.org <council@gnso.icann.org>,
liaison6c@gnso.icann.org <liaison6c@gnso.icann.org>
Cc: gnso-secs@icann.org <gnso-secs@icann.org>, Sebastien Ducos <Sebastien@registry.godaddy>
Subject: RE: [council] Proposed Agenda | GNSO Council Meeting| Thursday, 15 December 2022
Caution:
This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious
emails to isitbad@.
Hi Terri,
In our pre-SPS webinar, Sebastien indicated we are free to add topics to the agenda for discussion. In the attached email, I asked for a brief discussion on the topic of ICANN priorities and
DNS Abuse and the relationship between ICANN Org work and Council work on this topic. This is in an email because I am not permitted to log in to Google docs. Can you or Sebastien please let me know what happened to that request?
Thank you,
Anne
|
Anne E. Aikman-Scalese |
|
Of Counsel |
|
|
|
D. 520.629.4428 |
|
|
From: council <council-bounces@gnso.icann.org>
On Behalf Of Terri Agnew via council
Sent: Monday, December 5, 2022 2:13 PM
To: council@gnso.icann.org;
liaison6c@gnso.icann.org
Cc: gnso-secs@icann.org
Subject: [council] Proposed Agenda | GNSO Council Meeting| Thursday, 15 December 2022
[EXTERNAL]
Dear all,
Please find below the final proposed agenda for the GNSO Council Meeting on
15 December
2022.
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/owjVD [nam10.safelinks.protection.outlook.com].
This agenda was established according to the
GNSO Operating Procedures [nam10.safelinks.protection.outlook.com] 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 on Thursday, 15 December 2022 at 21:00 UTC:
https://tinyurl.com/y4fkdfc3 [nam10.safelinks.protection.outlook.com].
13:00 Los Angeles; 16:00 Washington DC; 21:00 London; 22:00 Paris; (Friday) 00:00 Moscow; 08:00 Melbourne
GNSO Council Meeting Remote Participation:
https://icann.zoom.us/j/92399217049?pwd=WU1GZmlaOTh6NzJ1NndkRVF0MnJEUT09
[nam10.safelinks.protection.outlook.com]
Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call.
___________________________________
Item 1: Administrative Matters (10 minutes)
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
[nam10.safelinks.protection.outlook.com] of the GNSO Council meeting on 20 October 2022 were posted on 04 November 2022.
Minutes
[nam10.safelinks.protection.outlook.com] of the GNSO Council meeting on 17 November 2022 were posted on 01 December 2022.
Item 2: Opening Remarks / Review of Projects & Action List (0 minutes)
2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of
Projects List [nam10.safelinks.protection.outlook.com]and
Action Item List. [nam10.safelinks.protection.outlook.com]
Item 3: Consent Agenda (10 minutes)
-
Approval of Standing Selection Committee (SSC) leadership for 2022-2023
-
Confirmation of the Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Chair and GNSO Council representative to the WS2 Community Coordination Group
-
Acknowledgment of the GNSO Council liaison to the GNSO Guidance Process (GGP) for Applicant Support
-
Acknowledgment of the
Work Plan [nam10.safelinks.protection.outlook.com]for the GNSO Guidance Process (GGP) for Applicant Support
Item 4: COUNCIL VOTE - Adopting the Council Committee for Overseeing and Implementing Continuous Improvements (CCOICI)’s Work Stream
2 (WS2) Recommendations Report (15 minutes)
The Council received a brief update on WS2 from ICANN org during its September 2021 meeting and received a more detailed update in February
2022, to better understand the level of progress it has already made via already completed work (e.g., the development of guidelines and templates to support the GNSO as a Decisional Participant in the Empowered Community) and the limited set of remaining
WS2 tasks.
The Council then considered the best path forward to complete the remaining work and agreed to extend the CCOICI pilot to include the
WS2 work. The CCOICI has now completed this assignment and shared its
WS2 Recommendations Report [nam10.safelinks.protection.outlook.com] on 4 November 2022. The Council received a briefing from the former Chair of the CCOICI during its November meeting.
Here, the Council will vote to adopt the CCOICI’s WS2 Recommendations Report.
4.1 – Presentation of
motion [nam10.safelinks.protection.outlook.com] (Manju Chen, Chair of the CCOICI)
4.2 – Council discussion
4.3 - Council vote (voting threshold: simple majority)
Item 5: COUNCIL DISCUSSION - Expired Domain Deletion Policy and the Expired Registration Recovery Policy Next Steps (15 minutes)
In October 2020, the GNSO Council considered when to request a Policy Status Report to conduct a review of the two Expiration Policies,
the Expired Domain Deletion Policy (EDDP) and the Expired Registration Recovery Policy (ERRP). Given concerns about capacity, along with the general perception that no known issues have presented themselves, the Council agreed in November 2020 to delay the
request for the Policy Status Report (PSR) that had been identified by the Action Decision Radar as requiring consideration; the deferral was for a period of 24 months, necessitating consideration November 2022.
In July 2022, the Council agreed that it would be helpful to check with the registrars and ICANN Compliance to help determine if there
are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. A
report from Contractual Compliance [nam10.safelinks.protection.outlook.com] was shared with the Council on 1 November 2022 and feedback from the registrars has been shared in the past on previous Council calls. The Council received a briefing on the report
from ICANN Compliance and the Council briefly considered potential next steps. One suggestion may be to task a Councilor member to review the report from Contractual Compliance in detail and determine if any of the issues raised warrant further work at present.
That analysis will help inform the Council overall and allow the Council to formally record its determination as appropriate.
Here, the Council will consider appropriate next steps.
5.1 – Introduction of topic (Council leadership)
5.2 – Council discussion
5.3 – Next steps
Item 6: COUNCIL DISCUSSION - Debrief From Council-Specific SubPro Operational Design Assessment (ODA) Webinar and Q&A (35 Minutes)
On 12 September 2021 the ICANN Board
directed [nam10.safelinks.protection.outlook.com] the ICANN President and CEO to organize the resources required to begin work on the Operational Design Phase (ODP) for the GNSO’s New gTLD Subsequent Procedures
Final Report [nam10.safelinks.protection.outlook.com] and the Affirmations, Recommendations, and Implementation Guidance contained in that report. On 20 December 2021, ICANN org
announced [nam10.safelinks.protection.outlook.com] that the SubPro ODP had formally launched, starting at the beginning of January 2022. The ODP Team has shared numerous updates to the community and sent several sets of assumptions/questions to the GNSO
Council via the Council’s liaison to the ODP.
ICANN org is expected to publish the SubPro Operational Design Assessment (ODA) on 12 December. In advance of publication of the ODA,
the Council will receive a briefing during a webinar on 7 December. While it is unlikely that there is adequate time for Councilors to have reviewed the ODA in detail, there may be initial impressions from council-specific webinar. The ICANN org staff that
supported the SubPro Operational Design Phase (ODP) will be available to answer questions and engage in dialogue.
Here, the Council will hold a debrief from the council-specific SubPro ODA webinar and engage with ICANN org staff that supported the
ODP/ODA.
6.1 – Introduction of topic (Council leadership)
6.2 – Council discussion
6.3 – Next steps
Item 7: ANY OTHER BUSINESS (15 minutes)
7.1 - Vacant Council Liaison positions (TPR)
7.2 - Standing Committee on ICANN Budget & Operations (SCBO) new approach - any objections?
7.3 - Any suggested Additional Budget Requests (ABRs)?
7.4 - Update on RPMs IRT timeline.
_______________________________
Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i))
Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4)
References for Coordinated Universal Time of 21:00 UTC
Local time between November and March in the NORTHERN hemisphere
----------------------------------------------------------------------------
California, USA (PST) UTC-8 13:00
San José, Costa Rica (CST) UTC-6 15:00
New York/Washington DC, USA (EST) UTC-5 16:00
Buenos Aires, Argentina (ART) UTC-3 18:00
Rio de Janeiro, Brazil (BRT) UTC-3 18:00
London, United Kingdom (GMT) UTC+0 21:00
Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00
Paris, France (CET) UTC+1 22:00
Moscow, Russia (MSK) UTC+3 (Friday) 00:00
Singapore (SGT) UTC+8 (Friday) 05:00
Melbourne, Australia (AEDT) UTC+11 (Friday) 08:00
----------------------------------------------------------------------------
DST starts on Sunday 26 March 2023, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 12 March 2023 for the U.S.
DST ends on Sunday 29 October 2023 for EU countries, and on Sunday 05 November 2023 for the US.
----------------------------------------------------------------------
For other places see
http://www.timeanddate.com [nam10.safelinks.protection.outlook.com] and
https://tinyurl.com/y4fkdfc3 [nam10.safelinks.protection.outlook.com].
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message
or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying
to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message
or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying
to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.