Dear All,
Please find included below some notes from today’s ccNSO Council meeting, held on Thu, 21 May 2020 at noon UTC.
Best regards,
Joke Braeken
To be quorate, we need 1 person per region.
Hope all are safe and well.
Calls are recorded and transcribed; recordings/transcripts posted on the public wiki: https://community.icann.org/x/V4HfBw.
2.
Minutes, Action Items & To-Do’s
Most of the action items have been completed
3.
Intermeeting ccNSO Council decisions & Actions (since 16 April 2020)
4.
ccPDP 3
a.
Part 1 Retirement – Update
Public comment has been opened on 5 May 2020 and will close 10 July 2020.
Last meeting was held yesterday. Upcoming: presentation by IANA, with ICANN legal
5.
IDN ccTLD related work items
a.
ccPDP4 Issue Report
We received input from ICANN legal on the issue report. Issue Report has been available for the oversight group since February. Was updated, based on their input. Was circulated
to ICANN general council. Is it within icann’s mission? Within the scope of the ccNSO policy? Does the policy have lasting impact? All confirmed.
IDN string selection would replace Fast Track Process. Also inclusion of IDN ccTLDs in the ccNSO: separate track (see 5.b. On today’s agenda). Council sent a letter with
proposed changes to the bylaws to icann. Board has responded that ICANN org will look at it, and will issue a public comment on the recommendations. Hopefully the process will be launched by ICANN68. The council as a start of the roadmap, first tasked a review
team, to look at areas that need to be updated in the proposed policy PDP2 (which was concluded in 2013). Fast track evolved, and other issues emerged in the meanwhile (e.g. confusing similarity). This PDP is an update of the proposals at the time, plus review
confusing similarity and introduce variant management. One major addition, at request of the ccPDP3-ret: this PDP should also define the trigger event for the de-selection and removal/retirement of IDN ccTLDs. Additional requirements for requesting an IDN
ccTLD string.
The group is quorate.
We can officially launch the work on this. Annex B, section 3 & 4. Development policy recommendations, then assemble a working group.
Secretariat to send out a call for volunteers, after ICANN68. Other stakeholders need to be invited to participate in the work as well. We need to formally inform the GAC
Chair, ask their advice/opinion. After publication, this decision is effective immediately.
Move? Giovanni
Second? Pablo
Questions or comments?
Bart: adding detail to 2 decisions.
All in favour.
We submitted the request to the Board, and received acknowledgement from the Board. Waiting for response from icann legal.
6.
ccNSO Board Seat 12 Nomination process
a.
Adoption Updated Guideline: ccNSO Board Seat 11 & 12 Nomination Process
We can move fwd with approval of the guideline. Major changes:
Decision into effect 7 days after publication
Move? Pablo
Second? Alejandra
No comments or questions
All in favour
Last year, when we went through the process, it turned out that the background checks lasted longer than expected. Additional layer of complexity to the selection process.
Need to start the process earlier.
First term of Nigel ends next year in October, AGM in 2021. He can be re-appointed, for 2 more terms.
Stephen: 6 month deadline prior to AGM (28 April 2021), specified in the ICANN Bylaws. Needs to be respected.
We will announce the nomination: start 9 June, close 30 June. Background checks follow, and Q&A at ICANN69 (Hamburg).
Move? Alejandra
Second? Giovanni
Questions/comments?
Joke Braeken appointed as Nomination Process Manager. Guideline was adopted today, timeline to be adopted as well.
Against? None
Abstain? None
All in favour
7.
NomCom Related Matters
a.
Review Implementation: Letter Chair of the Review WP
Asked us some questions. We missed the original deadline.
Google doc. Giovanni added some comments and suggestions.
2 parts:
They want to have our appointees already in June (see 7.b.)
See google doc:
https://docs.google.com/document/d/1u4yapu0rW72gg4vCzxIGkxlWfTZF4Rg2QcboDfMxSUs/edit?usp=sharing
Composition of NomCom should be more balanced, but the decision is not ours. (e.g. GNSO appoints 7, ccNSO appoints 1). Marie-Noemie supports gender and geographic diversity.
Suggest to be more critical. Constructive suggestion. Lengthy discussion with the Vice Chairs on this topic. If we appoint 1 person, diversity is impossible. It also depends on the number of volunteers. This year our representative to the NomCom is Annebeth
Lange (.eu). Should we then appoint next time a male person? From a different region? We only have 1 delegate, as ccNSO.
Response will be sent to Chair RP
Move? Giovanni
Second? Pablo
Comments/questions? None
Against? None
Abstain? None
All in favour
Annebeth is not term-limited.
Proposal to issue a call for volunteers, start 26 May and close 9 June. Council to select the preferred candidate between 10 and 17 June.
Selection procedure and timeline adopted
Against? None
Abstain? None
All in favour
8.
Closure of follow-up discussion CSC Effectiveness Review on potential gap between remit of CSC and RZERC.
Review was efficient. One of the ccTLDs asked us to request clarifications from ICANN. GAP analysis. Not clear what kind of gap analysis was meant. Clarification requested.
We reached out to the ccTLD repr that raised the issue. After numerous requests and reminders, so that we could go back to ICANN org, we still have not received that clarification.
Suggested not to take any further steps. Consider the item closed.
Against? None
Abstain? None
All in favour
Philippe: is the GNSO council cc-ed on the response letter to org? I'm just thinking maybe we should inform the GNSO council given that the CSC effectiveness review was
a "joint effort". Just as a "matter of courtesy"...
Bart: original correspondence needs to be checked. Will get back to Philippe on this.
9.
Approval updated Terms of Reference Internet Governance Liaison Committee (IGLC)
Updated Tor.
Selection Chair: groups nominates the chair, council appoints.
Move?
Alejandra seconded
Any questions? None
Abstain? None
All in favour
10.
Update ECA & CSC
a.
ECA
Phase 2 rejection action processes. Draft FY21-25 Operating and Financial Plan. Board approved the documents on 7 may. Notice 7 days later from ICANN Secretary. Could be
something that we propose to change in the bylaws.
Public comments period in December, and then the COVID-19 pandemic changed everything. Was responsible to review the projections and numbers. Budget was changed, reduced
in light of the pandemic. 2 webinars where the changes were represented. Those 2 webinars were referred to as “consultations with the community”. Question about the process? Was this an appropriate community consultation? No question about the fact that the
adjustments had to be made. What is the Council’s view? Should we react somehow? Or consider this as something inevitable?
Giovanni (SOPC Chair): sopc members also commented on the procedure by icann to approve the revised docs. Also other comments by SOPC members, about the fact that this
is a responsible decision. Blog entry by ICANN CEO and Board chair: they define the 2 webinars as having high levels of participation and engagement. ICANN could have reached out more and consulted more with the community. Nonetheless, this is a responsible
decision. Estimated funding reduced by 5 %. Estimated decline by 8%. 410 staff members, getting stable at 395. (revised projection at end of FY21). Formal call with Xavier Calvez, ICANN CFO, to point out that there are these concerns among some members of
the ccTLD community. He understood that communication was not optimal. However, pressure to complete this in a short timeframe. No-one questions the decision itself, but rather the process.
Stephen: Council to draft correspondence to Board that this should not set precedence.
Giovanni: agrees.
Katrina: consider expedited procedure, for instance with shorter comments period.
Draft letter will be shared with the full Council. Suggested to do so next week.
Rejection Action Period closes 4 June. We could submit it afterwards, as a statement, not as a rejection action.
b.
CSC
i. Update from CSC
PTI performance was 100%. SLA update, on the transfer and delegation of ccTLD is on the agenda of GNSO Council, consent agenda for today. Likely to be adopted. New SLA
will be implemented, as soon as CSC informs PTI.
ii. Appointment ccNSO Appointed Member on CSC, consultation with RySG and approval of full membership
CSC was informed that the procedure will be launched on 1 June. Council can take a decision to launch a process in anticipation of the upcoming CSC members selection, and
in anticipation of the role of the selection committee, which needs to be confirmed again.
Brett Carr has completed his 1st term. His term ends 1 october. He is vice chair, willing to stand again, he is not term-limited.
In the proposed timeline: correct typo. 2019 should read 2020.
Move? Stephen
Second? Pablo
Approve timeline with corrections, request secr to launch the call. We need the CSC Selection Committee, that will approve the full slate on behalf of the council, Council
will still approve the volunteers.
All in favour
11.
Council updates (Chair, Vice-Chairs, Councillors, Regional Organisations, Secretariat)
12.
WG/Committee Updates
a. GRC
Working on the same doc as last time: recall appointed board members. That doc covers also in case there is a request to recall a nomcom appointee, or the entire Board.
According to the bylaws, request can be submitted by any individual. Not sure when we will be ready to share it with the Council, Work ongoing.
b. SOPC
Had a call, planning to meet at ICANN68. At the same time, charter review will start. All committed to feedback that ICANN Finance provided to comment on the financial
and operating plan. Questions on what is next
c. TLD-Ops
none
d. Tech WG
Stephen: Tech WG is working on a Virtual Tech Day. DNSSEC oriented, some deferred presentations from Cancun
e. IGLC
Revised ToR. will meet at ICANN68, and contribute to ccNSO Members Meeting ICANN68
f. MPC
Update by Alejandra
·
Virtual ccTLD News session on 2 June 2020 | 11 UTC & 19 UTC
·
Council workshop: 3 June
·
GAC webinars: 3 and 4 June
·
9 and 11 June: ccTLD Community webinars for newcomers, and introducing the plans for ICANN68
2.
Draft ICANN68 ccNSO Schedule.
3.
Details on ccTLD News session and the 3 ICANN68 sessions as part of ccNSO Members Meeting.
Katrina: changes to usual ccNSO members meeting. Get members more engaged, even outside of the ICANN meeting. That is why the ccTLD News session is held virtually, ahead
of the icann68 schedule.
g. CCWG Auction Proceeds
leadership team now considers the Final Report complete. The next step in the process is for the Co-Chairs to make a designation of the level of consensus for the recommendations
in the report (see charter for detail, and to send the report to the Chartering organisations for adoption.
13.
Update liaisons
a.
Update ALAC Liaison (written update)
14.
Upcoming Meetings
a.
Update, if any, ICANN68
i. Schedule ICANN68 meetings
ii. Joint Meeting with GNSO Council
Is the joint meeting with GNSO Council happening? Pending confirmation
b.
Council virtual workshop
Some volunteers stepped forward.
c.
Meeting with the GAC
Webinar on update Policy development efforts & “DNS Abuse” and ccTLDs prior to ICANN68.
d.
Schedule upcoming webinars
e.
Next Council Meeting schedule
· ICANN68 (Virtual): Wednesday 24 June 2020, Block 5 (7 UTC, 15:00 Kuala Lumpur)
· August 20 – 12:00 UTC
· September 17 – 18:00 UTC
· October @ICANN69
· November 19 – 12:00 UTC
· December 17 – 18:00 UTC
15.
AOB
None
16.
Closure
Thank you, and
Bye all.
Joke Braeken
ccNSO Policy Advisor
Follow @ccNSO on Twitter: https://twitter.com/ccNSO
Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/