Asia Pacific Top Level Domain Name Association: Difference between revisions
mNo edit summary |
|||
| Line 29: | Line 29: | ||
* To act as an interface with Internet coordination bodies and other bodies involved in the Internet domain name operation | * To act as an interface with Internet coordination bodies and other bodies involved in the Internet domain name operation | ||
== | == Workings of APTLD == | ||
APTLD works as the forum of information exchange regarding technological | |||
and operational issues of domain name registries in Asia Pacific region. Also, as an interface to other international Internet coordinating bodies, APTLD fosters and elevates participation of Asia Pacific based ccTLDs in these global fora, as well as acting in their best interest in global Internet policy | |||
making process. APTLD is based on membership, and its activities | |||
are funded by membership fees | |||
== Involvement in ICANN == | == Involvement in ICANN == | ||
Though APTLD is not a part of the ICANN structure, | Though APTLD is not a part of the ICANN structure, most APTLD members hold | ||
membership in the Country Code Names Supporting Organizations ([[ccNSO]]). | |||
The APTLD pledged its full support of the Joint Process Agreement ( | The APTLD pledged its full support of the Joint Process Agreement (JPA), which | ||
transitioned the handling of DNS responsibilities, earlier handled by the U.S | |||
Department of Commerce (DOC) on behalf of the U.S | |||
government, to a private organization such as Internet Corporation for Assigned | |||
Names and Numbers (ICANN). It also acknowledged the progress of ICANN in | |||
reaching the objective of fulfilling its limited mandate of technical | |||
coordination of the Internet’s naming and numbering resources. | |||
It had also supported the independent functioning of ICANN without the direct oversight of the U.S government after the expiry of the JPA on 30th September 2009 | It had also supported the independent functioning | ||
of ICANN without the direct oversight of the U.S government after the expiry of | |||
the JPA on 30th September 2009<ref name="link2">[http://www.aptld.org/pdf/APTLD%20submission%20to%20NTIA%20on%20JPA%20090608.pdf\ aptld.org]</ref> | |||
With the Asia-Pacific region being the most diverse region language-wise, APTLD has consistently advocated and promoted adoption of Internationalized Domain Names (IDN) and related technologies and instruments based on the use of non-Latin scripts | |||
and taken a proactive stance towards development of innovative technologies behind them. | |||
In 2007,APTLD also urged ICANN to implement a limited introduction of top level IDNs by taking some simple steps. The recommendations were : | |||
* Allow every existing ccTLD to manage one additional territory or country specific ccTLD in a recognized non-ASCII script of their territory or country. The task of determining the name of the ccTLD should be handed to the local Internet community. | * Allow every existing ccTLD to manage one additional territory or country specific ccTLD in a recognized non-ASCII script of their territory or country. The task of determining the name of the ccTLD should be handed to the local Internet community. | ||
* It also urged ICANN to manage a six-month comment period so that the international community would get a chance to comment on and object to the chosen IDN ccTLDs, if they seemed at all irrelevant to the ccTLD. This was mostly done to avoid spurious names for ccTLDs.<ref>[http://www.aptld.org/position/APTLD%20Position%20on%20Top%20Level%20Internationalised%20Domain%20Names%20-%20June%2021%202007%20v6.pdf aptld.org]</ref> | * It also urged ICANN to manage a six-month comment period so that the international community would get a chance to comment on and object to the chosen IDN ccTLDs, if they seemed at all irrelevant to the ccTLD. This was mostly done to avoid spurious names for ccTLDs.<ref>[http://www.aptld.org/position/APTLD%20Position%20on%20Top%20Level%20Internationalised%20Domain%20Names%20-%20June%2021%202007%20v6.pdf aptld.org]</ref> | ||
The region also see numerous cases of delegation and redelegation of country-code top | |||
level domains and representatives of the APTLD community vigorously contributed | |||
to the operation of the ccNSO Framework of Interpretation Working Group which set up guidelines for the ICANN community in this regard. | |||
== References == | == References == | ||
Revision as of 11:02, 22 December 2015
 | |
| Industry: | Internet / Top Level Domains |
| Founded: | 1988 |
| Headquarters: | APTLD Secretariat, Unit 2002-2005, 20/F ING Tower, 308 Des Voeux, Road Central, Sheung Wan, HONG KONG |
| Website: | aptld.org |
| Twitter: |  @APTLDnews
|
| Key People | |
| Lim Choon Sai (SGNIC), Chair Ting Chen (CNNIC), Vice Chair Leonid Todorov, General Manager | |
APTLD is an abbreviation for the the Asia Pacific Top Level Domain Name Association. It is an organization for the country-code Top Level Domain (ccTLD) registries in the Asia Pacific region, first established in 1988 and incorporated as a not-for-profit in Malaysia in 2003.[1] Presently, APTLD has 45 full and associate members.
Objectives[edit | edit source]
APTLD has the following objectives:
- To promote skills development and information exchange related to Internet domain names amongst members.
- To provide a forum to discuss policy matters affecting Internet domain name related entities
- To act as an interface with Internet coordination bodies and other bodies involved in the Internet domain name operation
Workings of APTLD[edit | edit source]
APTLD works as the forum of information exchange regarding technological and operational issues of domain name registries in Asia Pacific region. Also, as an interface to other international Internet coordinating bodies, APTLD fosters and elevates participation of Asia Pacific based ccTLDs in these global fora, as well as acting in their best interest in global Internet policy making process. APTLD is based on membership, and its activities are funded by membership fees
Involvement in ICANN[edit | edit source]
Though APTLD is not a part of the ICANN structure, most APTLD members hold membership in the Country Code Names Supporting Organizations (ccNSO).
The APTLD pledged its full support of the Joint Process Agreement (JPA), which transitioned the handling of DNS responsibilities, earlier handled by the U.S Department of Commerce (DOC) on behalf of the U.S government, to a private organization such as Internet Corporation for Assigned Names and Numbers (ICANN). It also acknowledged the progress of ICANN in reaching the objective of fulfilling its limited mandate of technical coordination of the Internet’s naming and numbering resources.
It had also supported the independent functioning of ICANN without the direct oversight of the U.S government after the expiry of the JPA on 30th September 2009[2]
With the Asia-Pacific region being the most diverse region language-wise, APTLD has consistently advocated and promoted adoption of Internationalized Domain Names (IDN) and related technologies and instruments based on the use of non-Latin scripts and taken a proactive stance towards development of innovative technologies behind them.
In 2007,APTLD also urged ICANN to implement a limited introduction of top level IDNs by taking some simple steps. The recommendations were :
- Allow every existing ccTLD to manage one additional territory or country specific ccTLD in a recognized non-ASCII script of their territory or country. The task of determining the name of the ccTLD should be handed to the local Internet community.
- It also urged ICANN to manage a six-month comment period so that the international community would get a chance to comment on and object to the chosen IDN ccTLDs, if they seemed at all irrelevant to the ccTLD. This was mostly done to avoid spurious names for ccTLDs.[3]
The region also see numerous cases of delegation and redelegation of country-code top level domains and representatives of the APTLD community vigorously contributed to the operation of the ccNSO Framework of Interpretation Working Group which set up guidelines for the ICANN community in this regard.