Skip to main content

Furthering Government Participation in ICANN

Apac gac workshop

In my previous blogs (parts 1 and 2), I discussed the need for the Asia Pacific (APAC) region to participate in ICANN's multistakeholder model. I want to share a recent engagement to facilitate government participation and opportunities for our region to collaborate further.

In conjunction with the Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) 2018, we organized the first Governmental Advisory Committee (GAC) capacity-development workshop for Asian GAC members in Kathmandu, Nepal from 24-25 February 2018.

An initiative of the ICANN GAC Under-served Regions Working Group, this is the fifth workshop around the world, focusing on developing the capacity of GAC members to facilitate more effective participation in ICANN. The Asian GAC-focused workshop helped the 20 participants from 13 Asian economies better understand ICANN, our ecosystem, and participation model.

Since we were at APRICOT, community leaders who were in Nepal also participated. For example, we took the opportunity for Akinori Maemura, member of ICANN Board of Directors, who hails from the region - Japan - to share with participants and it turned out to be very interactive and engaging. Workshop participants also had opportunities to network with APAC Internet organizations like the Internet Society Asia Pacific Bureau, the Asia Pacific Top Level Domain (APTLD) and Asia-Pacific Network Information Centre (APNIC).

Overall, participants shared that the content was very good and particularly appreciated the interactivity of the sessions. They exchanged views, shared best practices and learned from one another. I'd like to take this opportunity to thank our GAC Vice Chair Guo Feng for his leadership in facilitating some of the discussions.

Some notable discussion points that open potential opportunities for collaboration include:

Further awareness building: Participants shared that awareness of ICANN and the Internet ecosystem was still relatively low in developing and least developed countries. As such, governments tend to prioritize other public policy issues. This is an area where the ICANN org regional team can partner with GAC members. We have partnered with governments to engage with their local communities in the past, and seen success in places such as Cambodia, Sri Lanka and the Maldives.

Coordination and collaboration with regional community: Participants agreed that it would be useful to engage more frequently as a region during ICANN meetings, and commit to explore leveraging regional fora such as the Asia Pacific Regional Internet Governance Forum (APrIGF). They were also impressed by the ICANN Readout sessions - organized by community members to provide ICANN meeting updates to fellow community members unable to attend the ICANN meeting in person - conducted in local communities as a model to explore with their own communities. Such platforms would allow GAC members to engage with other stakeholder groups and communities in the region.

The above are opportunities for us to work together as a region to foster participation in ICANN's multistakeholder model. I hope that we can collaborate as one region and learn from one another. For starters, join us at the next APAC Space in San Juan during ICANN61. APAC Space is a platform for our community to share views on ICANN policy issues and discuss how to better participate in ICANN.

Lastly, I'd like to thank my colleagues from the various ICANN org teams for contributing to the success of the workshop. This includes the teams from Government Engagement, Policy Development Support, and Office of the CTO.

If you'd like to see other photos of the GAC workshop in action, please visit my twitter handle.

Fun Fact: Since establishing the APAC regional office in 2013, we have facilitated 4 new GAC members - Cambodia, Palau, Timor Leste, and Nepal. The Oceania region has 100% GAC participation.

Comments

    Domain Name System
    Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."