Public Comment CloseStatement
Name 

Status

Assignee(s)

Call for
Comments Open
Call for
Comments
Close 
Vote OpenVote CloseDate of SubmissionStaff Contact and EmailStatement Number

03 April 2020

ADOPTED

13Y, 0N, 0A

ADOPTED

Ratified by AFRALO & APRALO Leadership Teams (12Y, 0N, 0A)

See BigPulse Poll result

Drafting team volunteer(s):

Satish Babu

Seun Ojedeji

Raymond Selorm Mamattah (AFRALO)

Dr. T. V. Gopal (APRALO)

16 April 2020

20 April 2020

AL-RALO-ST-0420-01-01-EN

Hide the information below, please click here 

FINAL VERSION SUBMITTED (IF RATIFIED)

The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote. 



FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.

Please note the ratification vote for this statement was sent to the AFRALO and APRALO Leadership Teams. After the AFRALO-APRALO LT ratification, the ALAC will be able to endorse the statement.



DRAFT SUBMITTED FOR DISCUSSION

The first draft submitted will be placed here before the call for comments begins. The Draft should be preceded by the name of the person submitting the draft and the date/time. If, during the discussion, the draft is revised, the older version(S) should be left in place and the new version along with a header line identifying the drafter and date/time should be placed above the older version(s), separated by a Horizontal Rule (available + Insert More Content control).

02 April Draft - 

Joint Statement by AFRALO and APRALO on MEAC Regional Strategy (FY21-25)

AFRALO and APRALO appreciate the opportunity to comment on the MEAC Regional Strategy Document developed by the MEAC Regional Strategy Working Group (MEAC-SWG), based on ICANN's Strategic Plan for 2021-25.

We find the document to be largely consistent with the aspirations of the end-users of the MEAC region. We have the following comments to make the document better-adapted to the evolving Internet Governance ecosystem. These are classified under the four subheadings used in the original document:

A. Security

  1. DNS Abuse is one of the biggest threats for end-users. The MEAC Strategy needs to emphasize measures against DNS Abuse, as DNS consistent with the measures that the ICANN community has since recommended on aspects such as reporting, abuse thresholds, and tools for contract compliance.
  2. The last DNS study conducted in the region appears to be in 2015. We recommend that this be updated in order to better understand the state of the market, including security.
  3. The technologies of the future need a framework for Security which includes assuring quality of the mnemonic names in the region, different physical locations of the root name servers for the region, ascertaining the preparedness for DNSSEC at all levels in the region, performance monitoring and timely checking of the traffic flows.

B. ICANN's Governance

  1. We recommend that the strategy considers adopting some of the proposals recommended from the recent community work on Next Steps to Improve the Effectiveness of ICANN's Multistakeholder Model, for better effectiveness and higher throughput, reducing volunteer burn-out, and better use of resources.
  2. Scoping of the Computer Supported Collaborative Work tools in terms of a judicious mix of online and face-to-face meeting is necessary based on the region. Measures must be taken to include all stakeholders in the region, especially those that are remote and inaccessible, or bandwidth- or linguistically challenged, to articulate their opinions in the policy processes and discussions.
  3. Universal open standards with the applications offered on the edge devices need to be advocated.

C. Unique Identifier Systems

  1. We recommend more focus on academia and industry for the promotion of IDNs and UA in the Region, jointly with the UASG. Working with Academia is essential for producing technical solutions, including open source solutions, to UA problems, whereas industry's support is required to implement solutions from existing vendors.
  2. Inclusion of the Office of the Chief Technology Officer, ICANN is strongly suggested for arriving at a purposeful process for regulating the addition of the gTLDs.

D. Geopolitics

  1. In addition to the elements already proposed, we also recommend that ICANN carries out better advocacy with nationals Governments in the region so as to ensure that ICANN's strategy gets adopted. The advocacy needs to include the due appraisals on goal of universal accessibility through one internet with global navigation aids, services and appropriate use of technology.
  2. Continuing and increased attention to internationalized [I18N] domain names [IDNs] is necessary. 


30 March Draft - 

Joint Statement by AFRALO and APRALO on MEAC Regional Strategy (FY21-25)

AFRALO and APRALO appreciate the opportunity to comment on the MEAC Regional Strategy Document developed by the MEAC Regional Strategy Working Group (MEAC-SWG), based on ICANN's Strategic Plan for 2021-25.

We find the document to be largely consistent with the aspirations of the end-users of the MEAC region. We have the following comments to make the document better-adapted to the evolving Internet Governance ecosystem. These are classified under the four subheadings used in the original document:

  1. Security
    1. DNS Abuse is one of the biggest threats for end-users. The MEAC Strategy needs to emphasize measures against DNS Abuse, as DNS consistent with the measures that the ICANN community has since recommended on aspects such as reporting, abuse thresholds, and tools for contract compliance.
    2. The last DNS study conducted in the region appears to be in 2015. We recommend that this be updated in order to better understand the state of the market, including security.
    3. Emerging Technologies such as DoH/DoT may be considered amongst measures to enhance the security of the domain name system in the region.
  2. ICANN's Governance
    1. We recommend that the strategy considers adopting some of the proposals recommended from the recent community work on Next Steps to Improve the Effectiveness of ICANN's Multistakeholder Model, for better effectiveness and higher throughput, reducing volunteer burn-out, and better use of resources.
    2. Given that face-to-face meetings are likely to be reduced in the near future due to the ongoing pandemic, measures must be taken to ensure communities in the region, especially those that are remote and inaccessible, or bandwidth- or linguistically challenged, are able to articulate their opinions in the policy processes and discussions.
  3. Unique Identifier Systems
    1. We recommend more focus on academia and industry for the promotion of IDNs and UA in the Region, jointly with the UASG. Working with Academia is essential for producing technical solutions, including open source solutions, to UA problems, whereas industry's support is required to implement solutions from existing vendors.
  4. Geopolitics
    1. In addition to the elements already proposed, we also recommend that ICANN carries out better advocacy with nationals Governments in the region so as to ensure that ICANN's strategy gets adopted.






1 Comment

  1. I have seen the mail from Nadira Alaraj on the "UA and EAI for Arabic Script" and the online discussion meeting scheduled on June 8th. I am not

    joining this discussion.


    I am not an expert on Arabic Script. However, I wish to share the document included on Indic Scripts and Unicode that 

    one of the leading edge topics during early 2000. In my humble opinion, the script of any language is not merely a symbol that is

    encoded for its "machine representation". This paper provides some useful perspectives on Script of a Language as a focus for study.

    Arabic is no exception. It goes a long way in comprehending the Domain Name as a Model. 

    By the way, in my context, EAI is normally "Enterprise Application Integration". However, your usage of EAI as "E-Mail Address Internationalization" is new to me.

    I am sure that the discussions will look into the scope of the meeting call and possible pointers for other pertinent committees.