AT-LARGE GATEWAY

At-Large Website

ALAC

RALOs

At-Large Regional Policy Engagement Program (ARPEP)

At-Large Governance

At-Large Reports

Policy Comments & Advice

Working Groups

ICANN Meetings

At-Large Summit (ATLAS III)

At-Large Review Implementation Plan Development

ALAC and RALO Elections, Selections, and Appointments

At-Large Priority Activities - 2021

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Comment Close
Date		Statement
Name 

Status

Assignee(s) and
RALO(s)

Call for
Comments		Call for
Comments
Close 		Vote
Announcement 		Vote OpenVote
Reminder		Vote CloseDate of SubmissionStaff Contact and EmailStatement Number
27.08.2013Proposal to Mitigate Name Collision RisksTBCTBCTBCTBCTBCTBCTBCTBCTBC

Cyrus Namazi
cyrus.namazi@icann.org

TBC
Comment / Reply Periods (*)
Comment Open Date: 
5 August 2013
Comment Close Date: 
27 August 2013 - 23:59 UTC
Reply Open Date: 
28 August 2013
Reply Close Date: 
17 September 2013 - 23:59 UTC
Important Information Links
Public Comment Announcement
To Submit Your Comments (Forum)
View Comments Submitted
Brief Overview
Originating Organization: 
ICANN
Categories/Tags: 
  • Security/Stability
  • Top-Level Domains
Purpose (Brief): 

To solicit community comment on proposed efforts to mitigate potential impact resulting from name collisions as New gTLDs are delegated into the root zone.

Current Status: 

ICANN engaged Interisle Consulting Group to prepare a study on the likelihood and potential consequences of collision between new public gTLD labels and existing private uses of the same strings. Interisle's study, entitled "Name Collision in the DNS" identifies three risk profiles, low risk (80% of the strings), uncalculated risk (20%) and high risk (2 strings). A proposal to mitigate the risks of name collisions for New gTLDs [PDF, 166 KB] has been developed and is presented for public comment.

Next Steps: 

Implementation of an agreed on solution for strings in each risk category; and the delegation of new gTLDs into the root.

Staff Contact: 
Cyrus Namazi
Email Staff Contact
Detailed Information
Section I: Description, Explanation, and Purpose: 

ICANN is pleased to announce the publication of the "Name Collision in the DNS" study report by Interisle Consulting Group, LCC (Interisle).

ICANN has undertaken a number of measures to assess and, where necessary, mitigate potential security and stability risks associated with the launch of new gTLDs. ICANN is presenting for public comment a proposal to mitigate potential risks of name collisions for new gTLDs as described in the "New gTLD Collision Risk Mitigation Proposal" [PDF, 166 KB]. Familiarity with the Interisle report and the document "Secure and Stable Introduction of New gTLDs" will be beneficial to understanding the proposal and contributing to the dialogue.

Section II: Background: 

On 31 January 2013, ICANN security team received the SAC 057: SSAC Advisory on Internal Name Certificates.

On 18 May 2013, the ICANN Board directed staff to commission a study on the use of TLDs that are not currently delegated at the root level of the public DNS in enterprises.

On 28 May 2013 ICANN announced the commissioning of two reports, one of them to the study potential security impacts of the applied-for new-gTLD strings in relation to name collisions with non-delegated TLDs that may be in use in private namespaces including their use in X.509 digital certificates. ICANN engaged Interisle Consulting Group to conduct the Name Collisions in the DNS Study and to provide options to mitigate the various risks.

Section III: Document and Resource Links: 

This announcement contains three documents published today.

Section IV: Additional Information: 

None

(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.

FINAL VERSION TO BE SUBMITTED IF RATIFIED

The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote. 

FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.

FIRST DRAFT SUBMITTED

The first draft submitted will be placed here before the call for comments begins.

 

  • No labels