FINAL VERSION 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.
DRAFT SUBMITTED FOR DISCUSSION
The first draft submitted will be placed here before the call for comments begins. The Draft should be preceded by the name of the person submitting the draft and the date/time. If, during the discussion, the draft is revised, the older version(S) should be left in place and the new version along with a header line identifying the drafter and date/time should be placed above the older version(s), separated by a Horizontal Rule (available + Insert More Content control).
First draft by Justine Chew, 24 July 2019:
As the ICANN constituency representing the views of individual Internet end users, the At-Large Advisory Committee (ALAC) considers the issue of Name Collision in the DNS an area of importance for the minimization of unintended consequences for end users. Name Collision occurs when a user, attempting to reach a private domain name, unintentionally reaches a misinterpreted public domain name, thus creating situations which not only undermines end user trust of the Internet but could also pose potential security issues.
In this respect, the ALAC supports the Security and Stability Advisory Committee (SSAC) in its continuing efforts to address the issue of Name Collision and notes the progress made in moving the Name Collision Analysis Project (NCAP) forward since the ICANN Board decisions of 2017-11-02, 2018.02.04.12 and 2019.03.14. And in particular, the ALAC notes the initiation of the NCAP Discussion Group (NCAP DG) in April 2019 and its facilitation of community participation in drafting the present Proposed Definition of Name Collision and Scope of Inquiry for the Name Collision Analysis Project (NCAP) dated 1 July 2019 for public comment.
We appreciate the need to have a Name Collision definition for purposes of scoping the inquiry for the NCAP, in order for the NCAP Study One to be manageable and on point. Therefore, the ALAC supports the Proposed Definition of Name Collision and Scope of Inquiry for the Name Collision Analysis Project of 1 July 2019. Of particular importance to us are:
(1) The recognition and inclusion of Type B situations (ie. B. In scope but not intended to be the subject of data studies) which provides built-in peripheral consideration of such situations with decision for examination through data analysis at a later stage if a compelling case were to arise within Study One; and
(2) The possibility of amending the Definition of Name Collision and Scope of Inquiry for the Name Collision Analysis Project should further pertinent information come to light at a later stage either through the ongoing work of the NCAP DG, NCAP Working Party and/or input obtained from the party/ies eventually contracted to undertake NCAP Study One.
2 Comments
Justine Chew
This Draft Definition of Name Collision and Scope of Inquiry for the Name Collision Analysis Project ("Draft Definition") is essentially an extract from the NCAP Study One Project Plan driven by SSAC, which is part of the NCAP's progress since its initiation in 2017 and following the ICANN Board's decisions of Nov 2017, Feb 2018 and Mar 2019. This Draft Definition also follows on from an earlier call for public comments to Draft Project Plan for the Proposed NCAP to which the ALAC voiced its support via a statement dated 18 Apr 2018.
I propose that At-Large supports this Draft Definition through the following draft statement:
As the ICANN constituency representing the views of individual Internet end users, the At-Large Advisory Committee (ALAC) considers the issue of Name Collision in the DNS an area of importance for the minimization of unintended consequences for end users. Name Collision occurs when a user, attempting to reach a private domain name, unintentionally reaches a misinterpreted public domain name, thus creating situations which not only undermines end user trust of the Internet but could also pose potential security issues.
In this respect, the ALAC supports the Security and Stability Advisory Committee (SSAC) in its continuing efforts to address the issue of Name Collision and notes the progress made in moving the Name Collision Analysis Project (NCAP) forward since the ICANN Board decisions of 2017-11-02, 2018.02.04.12 and 2019.03.14. And in particular, the ALAC notes the initiation of the NCAP Discussion Group (NCAP DG) in April 2019 and its facilitation of community participation in drafting the present Proposed Definition of Name Collision and Scope of Inquiry for the Name Collision Analysis Project (NCAP) dated 1 July 2019 for public comment.
We appreciate the need to have a Name Collision definition for purposes of scoping the inquiry for the NCAP, in order for the NCAP Study One to be manageable and on point. Therefore, the ALAC supports the Proposed Definition of Name Collision and Scope of Inquiry for the Name Collision Analysis Project of 1 July 2019. Of particular importance to us are:
(1) The recognition and inclusion of Type B situations (ie. B. In scope but not intended to be the subject of data studies) which provides built-in peripheral consideration of such situations with decision for examination through data analysis at a later stage if a compelling case were to arise within Study One; and
(2) The possibility of amending the Definition of Name Collision and Scope of Inquiry for the Name Collision Analysis Project should further pertinent information come to light at a later stage either through the ongoing work of the NCAP DG, NCAP Working Party and/or input obtained from the party/ies eventually contracted to undertake NCAP Study One.
Evin Erdogdu
Thank you Justine, I have updated the above "Draft for Discussion" accordingly.