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

Compare with Current View Page History

« Previous Version 4 Next »

Comment Close
Date
Statement
Name 

Status

Assignee(s)

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

Universal Acceptance of TLDs Draft Roadmap

DRAFTINGSatish BabuTBCTBCTBCTBCTBCTBCTBC
Francisco Arias
TBC

For information about this PC, please click here 

Contents

Brief Overview

To solicit community comment on proposed roadmap for the Universal Acceptance Initiative[PDF, 117 KB].

Comment Period: 18 Jun 2014 - 18 Jul 2014 23:59 UTC
Reply Period: 19 Jul 2014 - 8 Aug 2014 23:59 UTC

Section I: Description, Explanation, and Purpose

The goal of "domain names in a TLD must be useable in applications regardless of the written script, and length or newness of the TLD" roughly captures the observed issues and obstacles driving the discussion of universal acceptance. The Universal Acceptance initiative is aimed to address technical acceptance issues with the use of domain names and related Internet Identifiers. For example, in some applications URLs using some TLDs are confused with search strings, email addresses using non-ASCII scripts are rejected (which limits the usefulness of a non-ASCII TLD name), and some applications do not present the native written form, instead only presenting the internal DNS label format.

ICANN is looking for input on the proposed roadmap for the Universal Acceptance initiative[PDF, 117 KB]. Particularly, ICANN is interested in learning what the community thinks about the goal, scope, and approach in the proposal.

Section II: Background

On 15 November 2013 the Joint ccNSO‐GNSO IDN Group (the JIG) published the JIG Final Report on Universal Acceptance of IDN TLDs recommending ICANN to take action in promoting the universal acceptance of new TLDs and IDNs.

Section III: Relevant Resources

Section IV: Additional Information

Staff Contact

 

FINAL VERSION TO BE 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.



FIRST DRAFT SUBMITTED

 

AT-LARGE ADVISORY COMMITTEE

ALAC Draft Statement on
the Proposed Roadmap for Universal Acceptance Initiative

 

Preamble

Universal Acceptance refers to the universal and consistent ability to use TLDs, whether existing, IDN ccTLDs, or new gTLDs, “...regardless of the written script, and length or newness of the TLD”. Universal Acceptance is a critical factor to foster and ensure competition, consumer trust and choice in the DNS marketplace.

The Universal Acceptance Initiative (UAI) is an internal initiative of ICANN that attempts to address these concerns using ICANN's multistakeholder constituencies in a collaborative and co-ordinated manner, applying additional resources as required. UAI focuses not only on IDNs, but all TLDs.

On 18 June 2014, ICANN Staff released a draft document on the proposed roadmap for the Universal Acceptance Initiative which was based on past work, including the final JIG Report on Universal Acceptance of IDN TLDs.

 

The ALAC Response to the Draft Roadmap

  1. From an end-user perspective, Universal Acceptance is very important for upholding the public trust in the evolving Domain Name Ecosystem, and for facilitating the participation of large sections of populations in the world hitherto excluded from utilizing DNS because of the lack of support for their scripts.

  2. ALAC places on record its appreciation for ICANN for the efforts taken to release the draft roadmap. The roadmap, when implemented, will be of significant benefit to end-user communities that ALAC represents.

  3. Given the large number of stakeholders who need to work together to achieve Universal Acceptance—including DNS operators, software vendors, service providers, protocol & standard bodies, system & network operators, security practitioners and end users—it is important to ensure that there is frequent and free-flowing interactions between these stakeholders.

  4. ALAC recommends the creation of a intermediate-term, cross-community mechanism that not only provides facilitation for stakeholder interactions, but also allows organizational retention of issues as well as learnings, acting as a knowledge base for all aspects of Universal Acceptance

  5. ALAC also recommends monitoring of progress of the UAI based on progress indicators that are jointly identified as part of the above mechanism, so that there is a shared

  6. ALAC reiterates the need for ongoing advocacy with all stakeholder communities, and particularly end-user communities, for the dissemination of information on Universal Acceptance.

  7. When targeting end-users, these advocacy and outreach efforts need to be undertaken in consultation with the At-Large community

 


  • No labels