Dear all,

 

Please find below some high-level notes from the ccNSO Council Meeting, held on 26 April 2018, 18.00 UTC.

 

1) Welcome and Apologies

Attendance list is available at: http://ccnso.icann.org/about/council/attendance.htm

Bart confirmed we are quorate. All regions represented, and more than 10 councillors

 

Apologies received from Margarita, Leonid, Abibu, Demi

 

2) Minutes and Actions

Minutes sent on 03/04/2018. No comments received, so they are approved.

Action items: most are completed. Some included in the background material, some are still ongoing. E.g. selecting new Liaison to GNSO.

Summary received from our discussions in PR (ICANN61)

 

3) Overview inter-meeting Council decision

See agenda

 

4) Adoption Work Plan 2018-2020

Mindmap distributed. Also used during the council workshop.

Any questions, additions? None.

 

Draft resolution.

Move? Stephen Deerhake

Seconded? Peter Vergote

Against? None

Abstentions? None

All in favour.

 

5) Next steps discussion balancing workload and volunteer capacity

Also discussed in San Juan during Council workshop and at the ccNSO Members Meeting. See background material, summary was distributed.  We need a larger number of people that are willing to do the work.

Volunteers from the council are asked to step forward and help preparing the follow-up session in Panama.

 

Question from Peter Vergote: feedback from other SO/ACs : are they having the same issues? Have they identified solutions? Everyone seems to have the same issue, according to Katrina.  Difficult to find the right approach to get people involved.  We have to show the value of participating in the ccNSO.

 

Philip Fouquart: GNSO also lacks volunteers. However, sometimes there are too many volunteers. You need to make sure they are driven properly. Main challenge for some of the PDPs.

 

Suggestion by Bart:

Question to ask to the audience: why don’t you participate in WGs? Interesting question to ask in Panama. Mostly 120 people attending ccNSO Members Meetings, but only a handful participate in the council or the WGs.Prepare a session in Panama, and come up with a lightweight recommendation to move forward.

 

6) Structuring next steps of discussion of  ccTLD related Disaster Recovery planning

The secretariat will send out a call for volunteers to Council to assist in organising the participation and disaster recovery session. Follow-up session from San Juan.

Option: Involve TLD-OPS, to coordinate with Tech WG ? Important not only to approach this from a technical point of view but also keep in mind the “human” side. Not only focus on infrastructure.

 

Jacques Latour sent an email to the ccNSO members, with a summary of the latest TLD-OPS meeting. Clear that they are interested in a follow-up session, and will pay attention not only to the technical side.

 

Alejandra: sent out a call for proposals to the ccNSO Members and community mailing list, inviting the community to help shaping the session. Katrina welcomes this.

 

7) Study Group Emoji: Need for call for volunteers?

Discussed in San Juan, presentation from SSAC who did research on the subject. They shared their concerns.  2 ccTLDs offer emojis (.fm and .ws)

Study Group will not repeat the work done by SSAC. However, ask the ccTLDs that register emojis under the 2nd level, whether they are aware of the risks, and are willing to accept the risks. Advise them to revise the policy.

 

Proposal: We will have a Study Group, and issue a call for volunteers soon.

Inform SSAC and ICANN Org about the steps we plan to take. And invite SSAC to participate in the work of the Study Group.

 

Move? Byron

Seconded? Hiro

Against? None

Abstentions? None

All in favour

 

8) Update SSR 2

SO/AC chairs met on several occasions. New people were appointed to the group.

Next step: ICANN Board to find facilitators so that the group can be unpaused asap.

 

9) Special Elections European Region

Discussed previously in January/February.

Simplified timeline shared on screen.  

 

Q&A at face-to-face meetings. Either in Panama or in Barcelona.

Timelines presented include the voting and the timeline in case of run-off elections.

Pros and cons for both scenarios. Katrina believes the second scenario, to have the regular election and the special election at the same time, is preferable. Easier from an admin point of view. Have a Q&A in Barcelona for the European Region. After Panama = holiday season in Europe. Might not be favourable for the voting.

 

Stephen: ICANN Bylaws, 10.4.g. Not sure whether we can start in week 34 rather than week 17. We should stick to the rational interpretation of the bylaws, and he supports the first timeline (Q&A in Panama)

 

Alejandra: logistics for the elections. Will there be 2 concurrent elections for both seats?

Katrina: 1 election for the full term, 1 for the remaining term. E.g. same was done when Vika stepped down.

 

Bart: pasted the language from bylaws in the chat. You must establish a nomination and election schedule. It does not say anything however on when this needs to happen.

 

According to the bylaws sections : 10.3 (g)

A vacancy on the ccNSO Council shall be deemed to exist in the case of the death, resignation, or removal of any ccNSO Council member.



Vacancies in the positions of the ccNSO Council members selected by ccNSO members shall be filled for the unexpired term by the procedure described in Section 10.4(g) through (i).

Section 10.4 g

upon the occurrence of a vacancy in the seat of such a ccNSO Council member (i.e member appointed by the ccTLDs), the ccNSO Council shall establish a nomination and election schedule, which shall be sent to all ccNSO members within the Geographic Region and posted on the Website.

 

Stephen: European region underrepresented in the council. Nigel stepping down at the end of the Panama meeting.  

 

Vote now? On mailing list afterwards, with 1 week to express preference?

Peter: suggest to do this via mail. Not preferable to have the opinion of the collected via ZOOM.

 

Suggestion: Online voting. Katrina to send out email tomorrow, with 1 week deadline.

Against? None

Abstentions? Nigel

 

10) PDP Retirement

Update by Stephen. Met twice since council last met. Have used mindmaps. Closed to transitioning to written language in an outline form. Between now and Panama 2 more meetings. Substantive language to discuss in Panama. Stephen to reach out to GAC to have more participation/support from that side.

 

11) ECA, RZERC Update

11.1 ECA (Stephen Deerhake)

11.2 RZERC Update (placeholder)

12) ccNSO Organisational Review update

13) CSC related Topics

 

13.1 General CSC update (Byron)

Continued to hold regular meetings. PTI continues to meet its monthly metrics. The main additional element: adoption of the Remedial Action Procedures. Should there be systemic poor performance that requires a RAP. Agreed upon with PTI.

 

13.2 CSC Charter review

Preliminary report is now out. No substantial changes, but some elements that help the CSC to be more efficient. Public comment period: https://www.icann.org/public-comments/csc-charter-rt-initial-2018-04-11-en

Taking into account comments received, the Review Team will prepare a Final Report for consideration and adoption by the ccNSO and GNSO Councils. The Amended Charter will become effective following the adoption of the Final report.

The panama meeting will be used for adoption. That is the idea of the RT.

 

13.2.a Update current state of affairs (Abdalla)

 

Abdalla and Martin Boyle are the ccNSO appointed members from the RT. The main recommendations:

·         Not to change scope and remit of the CSC itself. Important to note with respect to future Reviews. The limited scope of the CSC is its strength.

·         Smaller change, but important: CSC to make minor changes to the Service Levels. This avoids to go through an extensive public comment period, to make minor changes to the SLAs.

·         When a member loses his/her affiliation during the membership period, there is a mechanism in place for confirmation that will be proposed.

 

Together with GNSO Council, each council according to its own procedures, we need to establish a small group to understand the process, and to organise the approval of the amendments.  We also need to select members to the CSC, approve full slate in September.  Call for liaisons and members.

 

13.2. b Next Steps:  Preparing for joint decision making.

 

To ensure continuity ICANN Org will initiate the process for a call for volunteers for the CSC at or around 1 May 2018. By sending an invitation to the ccNSO, RySG, SSSAC and GAC to start the selection process of members and/or liaisons according to their own rules and procedures. After the selection the ccNSO and GNSO Council need to approve the full slate of the CSC members and liaisons (envisioned mid-September 2018) Note that none of the current members or liaisons is term limited.

 

13.3 Upcoming CSC members Selection process

 

in October 2018 the term of the following members and liaisons of the CSC ends:

 

·         Jay Daley (ccNSO)(member)

·         Kal Feher (RySG)(member)

·         Lars-Johan Liman (RSSAC) (liaison)

·         Elise Lindberg (GAC)(Liaison)

 

13.4 Overlap CSC Effectiveness review and first IANA Function Review

14) Adoption Final Report ccNSO Meeting Strategy Review Team

Session held in San Juan. The final report is now out.

 

Alejandra: draft recommendations presented in Puerto Rico. Only 1 word added since then to the 5th recommendation.

 

1. Organise a ccNSO Members Meeting at every ICANN meeting

2. Ask the meeting programme WG to explore the possibility to organise a 1-day ccNSO

Members Meeting during the Policy Forum (i.e. the second ICANN meeting of the year)

3. Keep the ccNSO Members Meeting as 1 single stream, and do not organise parallel sessions.

4. Invite the meeting programme WG to keep in mind those priorities highlighted via the

survey, when putting together the agenda for the ccNSO Members meeting, being:

a. Developing relations between ccTLDs

b. Providing updates by and to the ccTLD community

Furthermore, the ccNSO Meeting Strategy Review Team recommends:

5. That the Meeting Programme Working Group attempts avoiding overlap or duplications with

regional organisations’ meetings.

6. That the ccNSO council ensures that the joint sessions with other supporting organisations

and advisory committees at public ICANN meetings are a valuable experience for all parties,

in terms of their objectives and timing.

 

Draft resolution presented

Move? Stephen

Second? Byron

Against? none

Abstentions? None

All in favour

 

15) ICANN 62  

 

15.1              ccNSO Council meetings

 

Monday, 25 June (Day 1)

12:15-13:30 – ccNSO Council Preparatory Meeting (lunch)

Monday, 25 June 2018 (Day 1)

17.00-18:30 – Joint ccNSO / GNSO (with cocktail)

Topics: CSC charter update, initiating CSC Effectiveness review,  progress cross-community groups (Auction Proceeds, Internet Governance)

Tuesday, 26 June 2018 (Day 2)

13.30:15-16:15 – Joint ccNSO / GAC

Topics meeting with GAC?

Wednesday 27 June 2018  (Day 2) 17:00-18:30 or Thursday 28 June 2018 (Day 4) 9.00-10.30: ccNSO Council Face to Face Meeting. Depends on topic session.

15.2               ICANN62 ccNSO Meetings Agenda (Alejandra)

 

4 days meeting

Monday: WG meetings, council prep, DNSSEC Workshop, Tech Day

Block 4&5 every day: cross-community topics. First proposal out on which session will be scheduled when.

Tue & Wed: ccNSO Members Meeting.

Thu: potentially council meeting. Or, during Wed, block 5. PDP-ret WG meeting, and kick-off planning for the Barcelona meeting

Draft agenda ccNSO Members Meeting.  Sessions highlighted in blue are the more interactive ones. Based on feedback received via the satisfaction survey.

Still to be determined what happens with the cross-community sessions. This will influence the scheduling of the ccNSO Members Meeting, and the council face to face meeting.

 

SO/AC leaders discuss the overall structure of the meetings. Request to submit cross-community topic proposals, followed via a vote. Sessions to be conflicted or not-conflicted. Decided upon by the majority.

ccNSO believes that none of the sessions should be non-conflicted.  

 

PDP-ret: block 1 &2 if the council face-to-face takes place on Wed, block 5.

 

ccNSO Council: increasingly difficult to get sponsors. Always the same ccTLDs offer sponsorship. Not enough funds collected, and unless a few more contributors step up, the cocktail will be cancelled.

 

16) Council Updates

 

Please submit them electronically

 

16.1    Chair Update

15.2    Vice-Chair Update

15.3    Councilors Update

15.4    Regional Organizations Update

15.5    Secretariat update

17) WG updates

 

Please submit them electronically

 

16.1 GRC update (Katrina)

16.2 CCWG Auction Proceeds (Peter Vergote)

16.3 CCWG Internet Governance (Young Eum)

16.5 ccNSO Meeting Strategy review

 

18) Liaison Updates

 

17.1 GNSO Update

17.2 ALAC update

 

19) Next meetings (2018)

 

24 May – 12:00 UTC

27 or 28 June – face to face, Panama City

23 August – 12:00 UTC (July and Aug combined)

20 September 18:00 UTC

October – face to face, Barcelona (date tbd)

15 November – 11:00 UTC

13 December – 17:00 UTC

20)  AOB

 

21)  Closure

 

Thank you. Follow-up of various issues on the mailing list.

 

 

Joke Braeken

ccNSO Policy Advisor 

joke.braeken@icann.org

 

Follow @ccNSO on Twitter: https://twitter.com/ccNSO

Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/

http://ccnso.icann.org