Skip to main content
Resources

Upcoming Public Comment Proceedings

A vital element of ICANN's accountability and transparency is the opportunity for public comment on policy development work, implementation activities, and operations. This page provides information about potential upcoming public comment proceedings to help individuals and the community set priorities and plan future workloads. The topics and dates presented are offered as informed predictions and should not be considered as specific date announcements.

To view Open, Recently Closed, or Archived Public Comment Proceedings, please click the appropriate link.

Upcoming Public Comment Proceeding ICANN Staff Contact Estimated Timeframe
Proposed Registry Agreement Amendments to Release Country and Territory Names from Reservation Krista Papac Ongoing
Potential Proposed Registry Agreement Amendments to Implement Registry Services Krista Papac Ongoing
Phase 2 Assessment of the Competitive Effects Associated with the New gTLD Program Eleeza Agopian August 2016
ICANN – Post-Transition IANA Naming Function Contract Trang Nguyen August 2016
Proposal for Lao Script Label Generation Rule for the Root Zone Sarmad Hussain August 2016
International Governmental Organization/International Non-Governmental Organization Identifiers Protection Policy Implementation Krista Papac August 2016
Proposed Renewal of .TEL TLD Sponsored Registry Agreement Krista Papac August 2016
Proposed Renewal of .MOBI TLD Sponsored Registry Agreement Krista Papac August 2016
.WED Registry Agreement Amendment (Updated) – Introduction of Third Level Domain Sales Krista Papac August 2016
Internationalized Domain Names Implementation Guidelines Initial Recommendations Sarmad Hussain September 2016
Transition from Thin to Thick  Whois for .COM, .NET and .JOBS Krista Papac September 2016
Framework for Registries to Respond to Security Threats Krista Papac September 2016
FY18 Post-Transition IANA Operating Plan and Budget Xavier Calvez September 2016
GNSO Operating Procedures Proposed Amendments (as a result of the IANA Stewardship Transition) Julie Hedlund October 2016
Continuous Data-Driven Analysis of Root Stability Study Interim Report Eleeza Agopian October 2016
CCWG-Accountability Work Stream 2 Recommendations Karen Mulberry October 2016
Competition, Consumer Trust, and Consumer Choice Review Draft Report Margie Milam October 2016
ATRT2 Final Implementation Report Larisa Gurnick October 2016
GNSO International Governmental Organizations/International Non-Governmental Organizations Access to Curative Rights Policy Development Process Initial Report Mary Wong October 2016
ICANN57 | 3-9 November 2016 | Hyderabad, India
ccTLD Delegation, Revocation, and Retirement Review Mechanism Policy Development Process Initial Report Joke Braeken November 2016
Proposal for Thai Script Label Generation Rule for the Root Zone Sarmad Hussain November 2016
Study on Internationalized Domain Name Variant Top-Level Domain Implementation Sarmad Hussain December 2016
At-Large Review 2 Independent Examiner Draft Report Larisa Gurnick December 2016
CCWG on the Use of Country and Territory Names as Top-Level Domains Initial Report Joke Braeken January 2017
Next Generation Registration Directory Services Policy Development Process Initial Report – Phase I Marika Konings January 2017
Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process Initial Report – Phase I Mary
Wong
January 2017
Label Generation Rules for the Root Zone Version 2 Sarmad Hussain January 2017
New gTLD Subsequent Procedures Policy Development Process Initial Report Steve
Chan
January 2017
Proposed Renewal of .ASIA TLD Registry Agreement Krista Papac January 2017
CCWG-Accountability Work Stream 2 Recommendations Karen Mulberry February 2017
Internationalized Domain Names Implementation Guidelines Recommendations Sarmad Hussain February 2017
FY18 ICANN Operating Plan and Budget and Five-Year Operating Plan Xavier Calvez February 2017
ICANN58 l 11-16 March 2017 l Copenhagen, Denmark
Continuous Data-Driven Analysis of Root Stability Study Final Report Eleeza Agopian April 2017
ICANN59 l 26-29 June 2017 l Johannesburg, South Africa
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."