Skip to main content

NGPC Progress on GAC Advice

The ICANN Board New gTLD Program Committee (NGPC) wishes to share with the ICANN community its progress in consideration of the GAC advice and what steps are still to be taken. The NGPC met on 8 May to consider a Plan for responding to the Governmental Advisory Committee's advice on New gTLDs, transmitted to the Board through its 11 April Beijing Communiqué. The Plan is in two parts: Part 1 shown below consists of actions for soliciting input from Applicants and from the Community.

  Item Resp. Start Date Compl. Date Status
1 Publish GAC Communiqué and notify applicants of 21-day GAC Advice Response Period Staff   18 April Complete
2 Applicants 21-day response period to GAC Advice Applicants 19 April 10 May In progress
3 Publish GAC Communiqué to solicit input on how the New gTLD Board Committee should address GAC advice regarding safeguards applicable to broad categories of New gTLD strings Staff   23 April Complete
4 Public comment period on how Board should address GAC Advice re: Safeguards Public 23 April Comment:
May 14
Reply:
4 June
In Progress
5 Collect and summarize applicant responses to GAC Advice Staff 11 May 31 May Not Started
6 Summarize and analyze public comments on how Board should address GAC Advice re: Safeguards Staff 5 June 12 June Not Started
7 Review and consider Applicant responses to GAC Advice and Public Comments on how Board should respond to GAC Advice re: Safeguards New gTLD Program Committee 13 June 20 June Not Started

Part 2 consists of actions for responding to each advice given by the GAC. In so doing, the NGPC is developing a GAC scorecard similar to the one used during the GAC and the Board meetings in Brussels on 28 February and 1 March 2011.

Each GAC scorecard item will be noted with a "1A", "1B", or "2":

  • "1A" indicates that the NGPC's proposed position is consistent with GAC advice as described in the Scorecard.
  • "1B" indicates that the NGPC's proposed position is consistent with GAC advice as described in the Scorecard in principle, with some revisions to be made.
  • "2" indicates that the NGPC's current position is not consistent with GAC advice as described in the Scorecard, and further discussion with the GAC is required following relevant procedures in the ICANN Bylaws.

Part 2 of the Plan is not yet finalized and, with respect to some of the advice, cannot be finalized until after the review of the Public Comments due to be completed on 20 June.

The NGPC will next meet in Amsterdam on 18 May and will provide a further update following that meeting.


More Announcements
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."