ICANN66 - Montreal 2019

cc PDP on Retirement Working group
1. Welcome
2. Administrative matters
3. Presentation to the GAC
4. Final reading process document
5. Stress test / hypotheticals
   Break – out
   Next steps
6. Presentation to the community
7. AOB
8. Next meetings
  November 21 – 23:00 UTC
  December 5 – 05:00 UTC
  December 19 – 11:00 UTC –TBD

  January 9th – 17:00 UTC
  January 23 – 23:00 UTC
  February 6 – 05:00 UTC
  February 20 – 11:00 UTC

  March 8 @ICANN67

TLD Ops Standing Committee and Drafting Team
Agenda:
1. Opening and welcome
2. Action Point Review
3. DAAR update
4. ICANN66 Disaster Recovery Workshop Update
5.  AOB
6.  Closing

SOPC Workshop
Agenda:
SOPC meeting (60 minutes)
Overview of forthcoming strategic and operational presentation
Q&A on recent ICANN CEO and Board communiques on strategic priorities
Coordination with the GNSO

Workshop (120 mins in total)
Working methods
Review of Charter
Wrap-up and evaluation

Joint session:  ccNSO and ALAC
Agenda:
 Introduction to the ccNSO - Katrina Sataki

Tech Day AM
Agenda

Joint session:  ccNSO and GNSO
Agenda:

• Decision making on PTI SLA changes (request will be forthcoming): SLA IDN tables processing time
• Progress developing Joint procedure to initiate Special IAN Function Review ( required under the Bylaws).
• Coordination of policy development efforts pertaining to IDNs
• CCWG Auction proceeds: progress to date and anticipation of next steps required under the charter from the GNSO and ccNSO (Councils)
• Coordination comment efforts ICANN planning ( FY 21 Ops Plan and budget, other)
• Evolution of the MSM: are there any anticipated next steps from ccNSO and/or GNSO Council?
• AOB
• Closure

Tech Day PM
Agenda   

Joint session:  Board and ccNSO

 Questions to the ICANN Board:

Question 1

The ccNSO and GNSO Councils are working together to define a procedure for launching a Specific IANA Function Review (SIFR) after the Customer Standing Committee (CSC) has determined that a persistent and systemic PTI performance Issue exists and all three escalation steps - including the escalation to the ICANN Board - have failed to correct the issue (for more information see CSC Remedial Actions Procedures or RAP). When looking at the overall processes from RAP to SFIR to Separation process, the ccNSO Council notices that the timelines to deal with the unlikely - but highly impactful - situations are prohibitive and affecting the stability of the DNS negatively. What is the Board’s procedure to deal with issues raised by the CSC in a timely and efficient manner?

All together we have created procedural monsters which, due to their timelines, unknown and/or non-transparent processes do not allow for quick resolution of serious and potentially damaging issues. An IANA Naming Function service performance issue as described above is a very good example. What activities does the Board plan to make its own processes more efficient? What would the Board suggest to the Community to make sure that we can resolve issues efficiently?

Question 2

We have read with interest the recent blog post from ICANN CEO on the President & CEO’s FY20 priorities. Could the Board clarify how the priorities highlighted in the blog fit into the ICANN approved and published Strategic Plan?

Question 3

What, in the Board's view, is ICANN’s role regarding DNS Abuse? How could the ccNSO support ICANN in the fight against DNS abuse given that ccTLDs’ policy development is outside ICANN’s remit?