Versions Compared

Key

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

...

Recently Ratified by the ALAC (Since Last ALT-PLUS 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. 

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 

ALAC Advice to ICANN Board on DNS Abuse (submitted to the ICANN Board on 24 December 2019)

Implementation Plan for the GNSO Consensus Policy Relating to the Protection of Certain Red Cross Names
As a worldwide internationally recognized humanitarian aid organization, and one that has been regularly the target of those seeking to fraudulently extract donations, the ALAC believes that the International Federation of Red Cross and Red Crescent Societies (incorporating National Red Cross or Red Crescent Societies, and the International Committee of the Red Cross) should be given the benefit of protection to its various identifiers, designations and/or acronyms as intended by the policy changes proposed for implementation in the said updated consensus policy. This includes the proposed action to recognize changes to the official names of the Red Cross Society entities, including component names, in Eswatini and Macedonia, respectively, an action we view as necessary.

Registration Directory Service (RDS-WHOIS2) Review Team Final Report
The ALAC finds the report to include very useful information that should be used to guide the development of relevant policies, and appreciates the team's effort and supports the provided recommendations. 

The ALAC highlights the importance of the recommendations related to the accuracy of data, and it strongly advises its acceptance by the ICANN Board. In light of the GDPR, the ALAC noted the importance of several other recommendations in the WHOIS Report​ encouraging a more proactive position of contractual compliance, especially in regards to DNS Abuse, as well as the team's findings with regard to law enforcement needs.

DRAFT PTI and IANA FY21 Operating Plan and Budgets
The ALAC noted that the proposed PTI and IANA FY21 Operating Plan and Budgets are aligned with the ICANN Strategic Plan, and are also very similar to previous years' budgets. An adjustment in the PTI budget is noticeable, including adjustments in salaries, services and other administrative cross-charges from ICANN to PTI or IANA.

However, the ALAC pointed out that a change is in process in the Governance of the Root Server System, these changes are not reflected in the proposed PTI and IANA FY21 Operating Plan and Budgets. The ALAC asked several exploratory questions in their response.

In additional, informal ALAC feedback was given regarding:


Public Comment for Decision 

Proposed Amendment 3 to the .COM Registry Agreement 14 February 2020Proposal for Future Root Zone KSK Rollovers  

Current Statements (ALAC Advice, Comment or Correspondence)

Public Comment Name

Public Comment Close

Status

Penholder(s)

Invitation to Provide Input for PDP 3.0 Implementation

 

SUBMITTED

DRAFT PTI and IANA FY21 Operating Plan and Budgets

 

VOTE

ALAC Advice to ICANN Board on DNS Abuse

 

Due this week

COMMENT

Registration Directory Service (RDS-WHOIS2) Review Team Final Report

 

Deadline extended

COMMENT

Implementation Plan for the GNSO Consensus Policy Relating to the Protection of Certain Red Cross Names

 

COMMENT

ISOC Sells PIR
Potential ALAC Advice to ICANN Board

See Google Doc for ALAC Advice on ISOC/PIR Issue (Jan 2020)

 

TBD

Status
colourBlue
titleCOMMENT

 

Status
colourYellow
titleDRAFTING

As per 06 January Single Issue Call AI, a drafting team formed before assigning penholder(s):

Laurin Weissinger

Abdulkarim Ayopo Oloyede

Proposed Dates for ICANN Public Meetings 2024-2028 and Revised Dates in 2022

 

Status
colourBlue
titleCOMMENT

Proposed Final Report of the New gTLD Auction Proceeds Cross Community Working Group

 

Status
colourYellow
titleDRAFTING

 

Status
colourYellow
titleDRAFTING

Marita Moll (contributing to Multistakeholder portion of the Public Comment)

Justine Chew

At-Large Policy Platform
Post-ICANN66
ICANN67
COMMENT

Status

Jonathan Zuck

colour

Joanna Kulesza

ISOC Sells PIRTBD

COMMENT

Roberto Gaetano

Blue
titleCOMMENT

5.  Post ATLAS III/2020 At-Large Activities - Review and Development of Recommendations for the ALAC - Maureen Hilyard and Leads(25 minutes)

...