Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
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

Status
colourGreyYellow
titleTBCDrafting
TBCTBCTBCTBCTBCTBCTBCTBC
Francisco Arias
TBC

For information about this PC, please click here 
Toggle Cloak

Cloak
visibletrue
Alicebluedashedbluedefrance2

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

 

...