Alejandra, all.

My belated apologies for missing call.

Javier Rúa-Jovet

+1-787-396-6511
twitter: @javrua
skype: javier.rua1
https://www.linkedin.com/in/javrua 


On Jun 17, 2021, at 9:33 AM, Joke Braeken via Ccnso-council <ccnso-council@icann.org> wrote:



NOTES | ccNSO Council Meeting 174 | 17 June 2021 (12:30 UTC)

 

 

  1. Welcome and roll call

 

Welcome by chair Alejandra Reynoso.

We are quorate today.

 

2.                   Relevant Correspondence

 

New item, to regular agenda: Relevant for items to be discussed in the agenda. 

ccNSO website has a correspondence section.

 

3.                   Minutes & Action Items



a.                   Minutes Meeting 173, circulated 9 June  2021

b.                   Action items and To-do’s, if any

 

All completed. 

1 ongoing. See next meeting

 

4.                   Intermeeting Decisions (since 20 May 2021)



a.                   Separation of ccPDP 3 Part 1 and Part 2

b.                   Adoption Meeting Guideline

c.                   Extension CSC Membership selection process

d.                   Launch call for volunteers NomCom 2022

e.                   Adoption revised Terms of Reference of the ccNSO Outreach and Involvement Standing Committee (OISC ToR version 2)

 

CSC membership: Frederico Neves has been selected. See item 13.b on the agenda



5.                   Adoption ccPDP3 Retirement Final Report & Support Recommendation

 

Last time ccNSO took a similar decision: 2013. ccPDP2 was not adopted by the Board, by mutual agreement with ccNSO. 

Stephen Deerhake and Eberhard Lisse (ccPDP3-RET leadership team) will give an introduction. 

Any comments on the proposed manner to take this decision? 

Stephen: referring to the ccNSO policy session earlier this week. Appreciation for ICANN staff and WG members in contributing to this development and co-chair. 

Any comments or questions? ccPDP3 leadership is happy to answer any questions.

Alejandra thanks all. 

Eberhard: no additions. If and when council votes in favour, it needs to go to membership. Quorum requirements, and ⅔ of the quorum needs to vote in favour.

Alejandra: do councilors have questions?

Pablo: thanks to leadership team, participants and staff.

Nick: assuming we approve it and we get the quorum and necessary votes in favour, this policy becomes effective. Is there going to be a review process after a while? After it has been put in practice, what was the experience? 

Eberhard: good point. Put in diary, after the next retirement, we should review the process.

Stephen: echoes what Eberhard said. Once we see it in practice, it would make sense for those responsible in the future to have that review process take place. 

Bernard: ATRT3 review proposes to replace the SO/AC reviews with a continuous review programme. Includes the requirement of these reviews. Would be an opportunity for such a review.

Bart: if needed, Council can start another PDP. regarding the 5 or 10 year timeframe: you need a trigger event to occur. Currently I do not see one happening. You do not know when that will happen.

Nick: It might be 15 years from now. That is too long. All of the policies to be reviewed regularly by Council. 

Alejandra: first it needs to be put in practice, for a review to happen.

Jordan: Keeping our policies under continuous review is a new and interesting idea, thanks for raising it Nick

 

Move? Jordan

Second? Pablo 

 

Alejandra: Any questions regarding the resolution itself?

None

 

Do you support?

Ali: yes

Biyi: yes

Souleymane: yes

Ai-Chin: yes

Jiankang: yes

Jordan: yes

Giovanni: yes

Irina: yes

Nick: yes

Pablo: yes

Sean: yes

Stephen: yes

Javier: yes

Laura: yes

Marie-Noemie: yes

Demi: yes

Jenifer: yes

Alejandra: yes

 

Unanimous support. Thanks all. 

 

Stephen: thank you to council for the support

Javier: thanks. Honour to be part of this group.

Bart will circulate a members report for approval by Council. That will include the resolution and vote by Council. Afterwards it will be sent to members for voting. That will happen early next week.




 

6.                   GRC related items



a.                   Appointment Sean Copeland Vice-Chair of GRC

 

Vice-Chair will take over the role of Katrina by ICANN72

Pablo: Thanks to Sean.

 

Move: Pablo

Second: Stephen

 

Any questions on the resolution?

Resolution has been approved.

 

Eberhard: excuses himself. 



b.       Adjust role of GRC, update charter

 

See previous meetings and prep meeting

3 committees: 

  • Triage committee (workpload ccnso work plan and its execution)
  • OISC (how to keep community informed, recruit volunteers)
  • GRC (looking at overall governance and working methods of the ccNSO). 

GRC requested to review its own charter.

 

Move? Pablo

Second? Giovanni

All in favour

 

7.                   Adoption Work Plan 2021-2023



a.                   Adoption of Annual Work Plan

 

Bart: circulated. See email. Starting point is the mind map. Maps activities against the core purpose of the ccNSO:

  • ccNSO as Supporting organisation
  • Platform function
  • Decisional participant

Basework of the activities for the next 2 years. Any comments or questions? 

Jordan: hopes to present something easier to comprehend in future . Quarterly prioritisation will be more digestible. Jordan speaks on behalf of the Triage Committee and its new role.

 

Move? Javier

Second? Jenifer 

 

Any questions regarding the resolution?

None

All in favour 



b.       Progress expanded role Triage committee

 

Jordan: Triage Committee will have its 1st meeting on 6 July. will report back to Council on progress made

 

8.                   Confirmation overview status implementation of recommendations 2nd ccNSO Review

 

Table was not up to date. Some items were already completed, but not marked as such.

Any further actions required by the ccNSO? None. 

1 item is in ICANN org’s remit: ccNSO website update

Recommendation to subscribe future reviewers to the list. This is deferred to a potential future new review.

 

Move? Jenifer

Second: Pablo

Any questions on the decision in front of us?

None

All in favour



9.                   Council Election 2021

 

Timeline was shared with you. Election manager needs to be appointed.

Any questions or comments?

None

 

Move? Stephen

Second? Irina

 

Questions on the resolution?  None

All in favour

 

10.               ICANN Hybrid Meeting

 

Icann org survey results have been made available. Alejandra summaries the conversation from the prep meeting. Split opinions. 

Later today, ICANN plenary on the post-pandemic future of ICANN meetings. 

Alejandra was asked to share views.

Javier: move as fast and fair as possible, but here there is good vaccine flow.

Pablo: agrees with Javier. Complicated situation. There are some who are more ahead of the curve than others. Moving ahead as soon as possible. Support for hybrid meetings

Nick: difficult judgment. What is as fast as possible. You need a substantial proportion of attendees being able to attend. If this meeting was to be held in Europe, it would probably be illegal. What is the type of meeting? 

Jordan: opposed to this meeting in a hybrid meeting. Wrong signal to the global community to do this at this stage of the pandemic in North America, where ICANN has its headquarters. Division between those who have access and those who don’t. Will not be able to attend, will not have had my vaccine yet by the time of the meeting

Irina: i would support having a hybrid meeting, even though i cannot attend myself probably

Jenifer: Is there a possibility that ICANN can give people vaccines in Seattle?

Pablo: in PR when you enter the airport, you can get vaccinated. Would like to have a vaccination station at ICANN73. 

 

Any comments regarding those from community members attending todays meeting?

Byron: Question then - if not enough counties have had the vaccine yet, what is the benchmark that would be the trigger?  100% of countries?  80%?  70%?

Stephen: The Seattle meeting is the AGM, which might be a big itch for ICANN.  Jordan raises a very valid point however.

 

11.               Updates PDP3 Part Review Mechanism

 

See policy session at ICANN71



12.               IDN ccPDP4: Update

 

See policy session at ICANN71

 

13.               Update ECA & CSC



a.                   ECA (Informational) see written update

b.                   CSC (Informational) see written update

 

Frederico was appointed for the remainder of the term of Alejandra. 

But we need a volunteer starting in October too, for the full term

Any questions or comments?

Irina: typo on the date. 2019 

Bart: We will update the typos. 

 

Move? Laura

Second? Marie-Noemie

Any questions on the resolution? None

All in favour

No objections

 

14.               Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat

 

None



15.               Update WGs taken

(written updates, unless special developments Council needs to be aware off)



a.                   SOPC

b.                   IGLC

c.                   GRC

d.                   OISC

e.                   TLD-OPS

f.                    Technical WG

g.                   MPC

 

Any additional comments from Council liaisons?

Giovanni: SOPC had its meeting earlier today at ICANN71. Exchange of views with the ICANN planning team. They will start a prioritisation project. To help shape the strategic and operational plan. See how SOPC can support the icann planning. Follow-up meetings in the pipeline. 



16.               Update liaisons



a.                   Update ALAC Liaison (written update)

b.                   Update GNSO Liaison (written update to follow)

 

17.               Next Meetings

 

●     July 22 -12:00 UTC

●     September 16 – 20:00 UTC

●     October @ ICANN72 (23-28 October)

●     November 18 – 12:00 UTC

●     December 17 – 18:00 UTC

 

18.               AOB



  • No AOB by Other Councilors
  • DNS Abuse (additional item by Alejandra). See if ccNSO has a role? Attending ccTLD News, IGLC, Tech Day…. this topic comes back over and over. Alejandra was approached by several parties on the ccNSO View and to see whether there is a channel of communication for the ccNSO on this topic.  Discussion on the role of the ccNSO as an agenda topic during the July meeting. Please do give it some thought before our next Council meeting



19.               Closure

 

Thanking all volunteers, all committees and WGs. also liaisons and others.

Thanks to their commitment the ccnso can move forward with its work

Thanks to the secretariat 

 

 

 

Joke Braeken

ccNSO Policy Advisor

joke.braeken@icann.org

 

 

From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of ccnso-council <ccnso-council@icann.org>
Reply to: Joke Braeken <joke.braeken@icann.org>
Date: Thursday, 17 June 2021 at 13:40
To: ccnso-council <ccnso-council@icann.org>
Subject: [ccnso-council] Notes today's council meeting | 17 June (12:30 UTC)

 

Hello All,

 

Notes during today’s ccNSO council meeting will be taken here:

https://docs.google.com/document/d/1aTMtilufypzR71UOrHYHDFVW6wLGNuVgPfryHjxo20A/edit?usp=sharing [docs.google.com]

 

ccNSO Council Meeting 174 | 17 June 2021

 

14:30 CEST, 17 June 2021
12:30 UTC, 17 June 2021
ID# 12475 [71.schedule.icann.org]

 

Best regards.

 

 

Joke Braeken

ccNSO Policy Advisor

joke.braeken@icann.org

 

_______________________________________________
Ccnso-council mailing list
Ccnso-council@icann.org
https://mm.icann.org/mailman/listinfo/ccnso-council
_______________________________________________
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.