You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Date: Thursday, 19 December 2019

Time: 06:00 - 07:00 UTC (for the time in various time zones click here)

Meeting Number: AL.AP/CC.1019/1


How do I participate in this meeting?

English Conference ID = 1638

Chinese Conference ID = 2038


Zoom room: https://icann.zoom.us/j/451011612


Action Items: EN

Recording: EN, ZH

Transcript: EN, ZH

Chat: EN


Participants

EN: 

Apologies:  

Staff: 

ZH Interpreters: 

Call Management: 


Agenda   *****TO BE UPDATED*****

1. Roll call - Staff (2 min)

2. Welcome and APRALO Membership Matters (Satish, 3 min)


ALS

Individual

Newly Certified (1)None

Dr. T.V. Gopal

Pending ALAC Vote (1)#307 Internet Society Rural Development Special Interest GroupNone
Awaiting RALO Feedback (0)None

None

Processing Due Diligence (0)NoneNone
On Hold (3)

#299/308 China Internet Development Foundation - APRALO (Withdrawn and reapplied under new structure)

#267 Surabhi Softwares

#112 Arab Regional ISPs & DSPs Association (ARISPA) - APRALO 

None


3. Presentation on ALAC Policy Platform topics (former Hot topics)- 10 mins TBC Joanna Kulezka 

  

4. ALAC Policy Update -  Maureen/Holly/Kaili  (10 min)

Recently Ratified by the ALAC 

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. 

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. 

In addition, the ALAC submitted comments in response to:

Public Comment for Decision

Proposed IANA SLAs for Publishing LGRs/IDN Tables  

Current Statements (ALAC Advice, Comment or Correspondence)

5. ATLAS III Update (Maureen, 5 min)

6.APRALO Updates (12 min)

  • Update on UA-Tech Committee activities in ICANN66 under the Universal Acceptance program of ICANN – (Satish)
  • Update on Dot.Asia Board meeting (Maureen, Lianna, Satish Babu).
  • At-Large Outreach & Engagement Update (Ali AlMeshal)
  • GFCE Triple-I Workshop and inSIG2019 (Satish/Amrita)
  • Planning for APRALO group meeting/picture at ATLASIII (Satish)

7. APRALO RoPs Review Working Group update (5 mins)

Wiki: APRALO ROPs Review WG

8. Member of the Month (Lianna, 8 min)

9. NomCom Update (Nadira/Amrita, 3 min)

10. AOB (2 min)

  • IGF Berlin


  • No labels