Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date: Tuesday, 15 October 19 November 2019

Time: 1819:00 - 1920:30 UTC  For the time in various time zones click here 

Meeting Number: AL.EU/CC.1119/1 

...

Zoom Room: https://icann.zoom.us/j/175517878

...

Dial-out Participants:  Olivier Crépin-Leblond, Anne-Marie Joly-Bachollet, Steinar Grotterod, Yrjo Lansipuro, Sebastien Bachollet, Roberto Gaetano, Lianna Galstyan, Natalia Filina, Wale Bakare, Ephraim Percy Kenyanito, Leon Sanchez, Oksana Prykhodko, Desaradushi, 

Apologies: Erich Schweighofer, Matthias M. Hudobnik , Annette Mühlberg, 

Staff: Heidi Ullrich, Silvia Vivanco, Gisella Gruber, Claudia Ruiz, Michelle DeSmyter

Call Management: TBC Michelle DeSmyter

...

Action Items: EN                        

Recording: EN EN

Transcript: EN

Zoom Chat: EN EN

...

AGENDA          

...

1. Roll call - staff
2. Review of AIs September- Olivier October Action Items - Sébastien (1 minute)
3. Update ALAC Public Consultations - Olivier (10 - Co-Chair CPWG and Sébastien (15 minutes)

Recently Ratified by the ALAC (since last EURALO Monthly Meeting)

Next Steps to Improve the Effectiveness of ICANN’s Multistakeholder Model
The ALAC summarized its comments as follows:

I. Strengthen ICANN’s bottom-up multistakeholder decision-making process and ensure that work gets done and policies are developed in an effective and timely manner.

Issue 1: Prioritization of work. ALAC feels this must be addressed (Category A). Some suggestions include: spreading the workload, increased outreach (ATLAS III, further incentives to keep contributing volunteers, adequate knowledge and resources (specified in II) The entire community,as well as ICANN.org must contribute to the resolution of this problem.

Issue 2: Precision in scoping the work. This issue may fall into Category A - must be addressed - or Category B -- might be partially addressed in current processes. We foresee scoping that is tight and smart and relevant to the process. It is impossible to say who should be responsible when so much activity around it is unresolved.

Issue 3: Efficient use of resources. This is a category A issue which must be addressed. We recognize that it might be partially addressed by current processes but cannot assess the situation until these processes are completed. We are concerned that PDP 3.0 may offer efficiency at the cost of inclusiveness which we feel would be a backwards step in the evolution of ICANN’s MSM.

Issue 4: Roles and responsibilities and a holistic view of ICANN. This is a category A issue although it will require further processes to resolve. ALAC seeks a bottom-up review of roles and responsibilities as an independent process. 

...

None

Public Comment for Decision

...

II. Support and grow active, informed and effective stakeholder participation.

Strategies to expand the concept of participation are offered as well as various resources and support needed to ensure informed participation. We consider this to be a Category A issue -- the model cannot evolve if it is not addressed. This is a major concern for At Large and other volunteer-based constituencies and all will need to be involved in addressing it. Support from ICANN,org and the Board will be necessary.

Issue 5: Representativeness and inclusiveness. Mentorship programs are a key part of ensuring that the MSM system remains representative and inclusive. Relevant constituencies as well as staff need to make sure these programs are working as they are intended and that they are reaching the right demographics. Inclusiveness at the leadership level needs to be improved through a bottom up process with staff assistance.

III. Sustain and improve openness, inclusivity, accountability and transparency.

Issue 6: Culture, trust and silos. This is a category A issue that needs to be addressed in this process. All constituencies need to reach across their boundaries, respect for other viewpoints must be reinforced. This is a problem in many large organizations and there are professional services available to help build trust and cooperation. By engaging some of these services, ICANN.org could help constituencies build a better working environment. 

Issue 7: Complexity. This is an inherent feature of ICANN work, but where it can be alleviated, ICANN.org should take the lead. Make sure information such as the website is well organized and understandable and closely monitor the internet governance environment for issues that will impact ICANN directly.

Issue 8: Consensus. Creating conditions that would facilitate consensus is the goal of the issues already listed. Preserving the voice of end users in the decision-making processes is crucial to ICANN’s MSM model -- a Category A issue in which all parties play a role but the role of the Board will be particularly important. 

Public Comment for Decision 

Proposed IANA SLAs for ccTLD Creation and Transfer 
Implementation Plan for the GNSO Consensus Policy Relating to the Protection of Certain Red Cross Names  
Proposal for Future Root Zone KSK Rollovers  

Current Statements (ALAC Advice, Comment or Correspondence)

Additional

  • Please see an ongoing workspace regarding CPWG SubPro Updates.
  • Post-ICANN66 Policy Report soon to be published.


4. EURALO Bylaws - Olivier (15 Next phase to be discuss at the EURALO GA - Sébastien (5 minutes)
5. Update on After ICANN 66 ATLAS III meeting - What next? - Olivier (10 minutes)
6. IGF Berlin 2019 Update - Olivier - Matthias and Natalia (10 15 minutes)
7. EURALO General Assembly 2019 - Olivier Sébastien (10 mins)
Agenda
8. AOB