Skip to main content

New GNSO Council Work Prioritization Process Recommendations

Open: 23 April 2010
Closed: 16 May 2010

Explanation/Background: At its 21 April 2010 meeting, the GNSO Council approved the use of a set of recommended new operating procedures designed to enable GNSO Councilors to begin categorizing and prioritizing their major work projects so that the Council can fulfill its new role as a strategic manager and coordinator of policy development activities within the GNSO. The ICANN community is invited to provide comments on those recommended new procedures.

One of the fundamental tenets of the GNSO Improvements efforts has been to move the GNSO Council away from being a legislative body concerned primarily with voting towards becoming a more focused strategic entity with strengthened management and oversight of the policy development process. As part of that effort a newly restructured GNSO Council was seated at the Seoul ICANN meeting in October 2009.

One of the new Council's first items of business was to organize a Drafting Team (the GNSO Work Process Model Drafting Team – "WPM-DT") to develop a methodology for prioritizing the GNSO's project work. On 9 April 2010, the WPM-DT delivered a recommended model methodology and set of new procedures to help the Council prioritize its work. The WPM-DT's intent was to ensure that the recommended process:

  • is user-friendly, unambiguous, and straightforward to execute;
  • produces realistic outputs that will help the Council to make effective management decisions; and
  • is structured as an on-going task that accommodates change including the introduction of new projects as they are proposed in the future.

At its 21 April meeting the Council accepted the deliverable of the WPM-DT and approved the use of a new Operating Procedures Chapter 6 and ANNEX [PDF, 137 KB] to conduct its first Work Prioritization effort - scheduled for June 2010 in Brussels, Belgium.

In addition to directing the opening of this Comment Forum, the Council approved a timetable for conducting its initial work prioritization effort. The full GNSO Council Resolution approving the use of the recommended new procedures (linked below) contains a timeline for that initial effort. The Council said it reserves the right to modify the procedures described in Chapter 6 and the ANNEX after the conclusion of both the public comment period and the first prioritization effort. Community members are invited to review and comment on these new procedures.

Document Links:

Deadline and How to Submit Comments:

At the direction of the GNSO Council, the Staff is opening a 21-day public consultation forum, from 26 April through 16 May 2010 and invites community comments concerning the Drafting Team's deliverable.

To submit comments:

To view comments:

For a copy of the public announcement of this forum please see:

Staff Responsible: Robert Hoggarth

Staff member responsible: Robert Hoggarth

Announcement | Comments | Summary/analysis of 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"""" is not an IDN."