Skip to main content

Webinars Scheduled to Explain Public Comment Enhancements

In addressing recommendations from the recent efforts of the second Accountability and Transparency Review Team (ATRT2), the ICANN staff has developed enhancements to the organization’s public comment proceeding processes. These enhancements will launch on 26 January 2015.

Two major changes will be implemented: 1) suspending the public comment reply cycle, and 2) launching an inquiry feature to allow for community feedback on staff summary reports of submitted comments. These improvements will be featured in redesigned landing pages for future public comment proceedings.

As part of these enhancements, the standard comment period will now be extended to a target of 40 days (minimum) and staff summary reports will be targeted for completion within two weeks of the comment period close date.

Two webinars will be held on Thursday 22 January 2015 at 10:00 UTC and 19:00 UTC to explain these changes in more detail. The two sessions are intended to be duplicates, scheduled to accommodate interested stakeholders in different time zones. Each session is scheduled for 60 minutes. During the course of the webinar, questions may be submitted using the chat function in Adobe Connect.

The presentation slides and recordings and transcripts of the webinars will be made available on the Public Comment Enhancements Webinar Reference Materials page. Additionally, ICANN staff is available to answer any questions about these changes via email at

In 2014, the staff Policy Development Support Team assumed day-to-day oversight of ICANN's public comment proceedings. The team spent considerable time reviewing the existing public comment infrastructure, processes, and procedures and gathering data on community comment activity to determine what changes inspired by the original recommendations of ATRT1 have been effective and to determine the best way to implement the ATRT2 recommendations.

Since then, the team has worked closely with the staff Online Community Services staff to evolve and enhance the existing infrastructure of the public comment pages on the ICANN website.

Public Comment Enhancements Webinars

Thursday, January 22, 2015 | 10:00 UTC and 19:00 UTC
Participation Details:

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"""" is not an IDN."