Internet Corporation for Assigned Names and Numbers
| Subscribe: Newsletters & News Alerts | ICANN Blog | Public Comment
A vital part of ICANN's processes is the opportunity for there to be public comment on each substantial piece of work before it is put forward for final approval. This is an archive of one month's public comment periods, arranged according to the month in which the comment period was closed.
Each box below provides a brief explanation of what the comment period hoped to achieve, as well as: links to relevant reports and/or webpages; a link to the official announcement of the comment period; a link to where all existing comments can be found; and an email link for anyone that wished to send in a comment. A "summary/analysis" objectively reviews the comments.
| Forums closing this month | Public comment | Archived forums: |
| Return to main public comment page |
Closed forums
| Registry failover plan | ||||||
|
Explanation: A revised draft [PDF, 41K] is being posted which incorporates feedback received following the ICANN meeting in Los Angeles. Comments may be submitted until 15 December 2007. With the expected expansion of new generic top-level domains, the possibility of a registry failure is greatly increased. In order to pre-empt a possible future problem, ICANN has worked with gTLD and ccTLD registry representatives to devise a way of dealing with the failure of an arm of the domain name system. The draft Failover Plan [pdf] (here as a flow chart) comes with a Best Practices [pdf] document. The Failover Plan identifies the process and procedures to be undertaken when a specific set of events indicating a potential gTLD registry failure. It is designed to protect the interests of registrants and provide the best opportunity for continued registry operations. The Best Practices document intends to be the source of contractual terms that will become part of every new registry agreement. These terms are intended to provide registries a tool for ensuring ongoing operations and also to provide a backstop process in the case of failure. This is a complex and important topic and so ICANN is putting it out for review by the wider community. You can find more summary information on the official announcement.
|
|||||
| Staff member responsible: Patrick Jones | ||||||
| Single-letter domains | ||||||
|
Explanation: ICANN is looking for ideas and suggestions on ways to allocate single-letter domains, such as a.com, i.info, 4.mobi or 8.org. Currently, it is not possible to register single-letter domains in all 16 generic top-level domains, from .aero to .travel - a policy stretching back to pre-ICANN days. However, a recent report [pdf] by a working group of the GNSO recommended that single-letter domains be made available now and into the future, with the proviso that an appropriate allocation method was devised. This forum is therefore asking the community for suggestions on what allocation methods it feels would be best. ICANN will synthesize responses and then present proposed methods for allocation for community consideration. For more information and background, see the official announcement of this forum. |
|||||
| Staff member responsible: Patrick Jones | ||||||
| ALAC bylaw change | ||||||
|
Explanation: A proposed bylaw change for the At-Large Advisory Committee (ALAC) - the part of ICANN that represents ordinary Internet users - is designed to allow the regional bodies (RALOs) to take a greater role in the approval of "At Large Structures" (ALSes), which form the base component part of the ICANN structure. The change is also designed to improve transparency of ALS application reviews and approvals. You can find more information on the exact change in the official announcement for this public comment period.
|
|||||
| Inter-Registrar Transfer Policy | ||||||
|
Explanation: The GNSO Council, in the process of reviewing the Inter-Registrar Transfer Policy, formed a working group to review the effectiveness of the policy and identify areas where future policy work might be beneficial. One of the working group's outputs was a draft advisory containing certain reminders and clarifications relevant to the policy. In accordance with the GNSO Council's resolution of 20 September 07, this draft Advisory is being posted for constituency and community review and comment. The input received will be reviewed and analyzed by the GNSO Council, pursuant to which this or an amended form of the draft may be released as a community advisory.
|
|||||
Announcement | Comments | Summary/analysis of comments |
||||||
| RSSAC review terms of reference | ||||||
|
Explanation: As part of the ongoing independent review of ICANN's supporting organisations and advisory committees, we are seeking comment on the proposed "terms of reference" for the DNS Root Server System Advisory Committee (RSSAC). You can see the full scope and guiding questions on the official announcement page for this review. The results will be posted for a second period of public review and comment, and then put in front of the Board for review. Consideration by the Board includes the ability to revise the structure or operation of the RSSAC by a two thirds vote of all members. Comments will be taken until 1 December 2007.
|
|||||