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

Compare with Current View Page History

« Previous Version 15 Next »

Public Comment CloseStatement
Name 

Status

Assignee(s)

Call for
Comments Open
Call for
Comments
Close 
Vote OpenVote CloseDate of SubmissionStaff Contact and EmailStatement Number

18 April 2018

ADOPTED

13 April 2018

16 April 2018

18 April 2018

22 April 2018

18 April 2018


Hide the information below, please click here 


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.

As the principle voice of end users within the ICANN community, the At-large Advisory Committee (ALAC) supports the Security and Stability Advisory Committee (SSAC) in its efforts to address the issue of Name Collisions as it remains an area of some uncertainty. The ALAC urges the SSAC to proceed with the Name Collision Analysis Project (NCAP) Work Party's project plan and allocate enough time to do it right. We believe it is important to minimize the unintended consequences for end users. Name Collision occurs when a user, attempting to reach a private domain name, unintentionally reaches a public domain name and, as such, cut to the core of end user trust of the internet and could pose potential security issues.

The NCAP Work Party's project plan, as it currently stands, seems adequate without being excessive. We urge the SSAC to stay the course and not expedite the process for the benefit of any subsequent procedures. There is great anticipation, from parts of the community, for new applications but not only is a specific delay unlikely, given other factors, we believe it would be prudent for the SSAC to execute the project plan as submitted to provide the ICANN community with a holistic assessment of the risks.

Additionally, the ALAC seeks clarity on the SSAC's bidding process for work contemplated under this Draft Project Plan, as touched upon in sections 3.1 and 3.2. First, we appreciate the SSAC’s candour in disclosing that it will consider NCAP Work Party members’ bids (and that of their affiliates), but it remains unclear as to their overall status as compared to invited guests of the SSAC. Moreover, we see a potential issue with having only a select group of the SSAC community choosing with whom they will contract. The ALAC recommends that any decision with respect to contracting with either NCAP Work Party members and their affiliates or independent third-party contracting agents be taken by the whole SSAC (and excluding invited guests), and for SSAC to provide the ICANN community with adequate amount of notice with respect to any party with whom they wish to contract.

We believe that this recommendation will ameliorate concerns related to potential conflicts of interest that may arise.



FIRST DRAFT SUBMITTED

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

As the principle voice of end users within the ICANN community, the At-large Advisory Committee (ALAC) supports the Security and Stability Advisory Committee (SSAC) in its efforts to address the issue of Name Collisions as it remains an area of some uncertainty. The ALAC urges the SSAC to proceed with the Name Collision Analysis Project (NCAP) Work Party's project plan and allocate enough time to do it right. We believe it is important to minimize the unintended consequences for end users. Name Collision occurs when a user, attempting to reach a private domain name, unintentionally reaches a public domain name and, as such, cut to the core of end user trust of the internet.

The NCAP Work Party's project plan, as it currently stands, seems adequate without being excessive. We urge the SSAC to stay the course and not expedite the process for the benefit of any subsequent procedures. There is great anticipation, from parts of the community, for new applications but not only is a specific delay unlikely, given other factors, we believe it would be prudent for the SSAC to execute the project plan as submitted to provide the ICANN community with a holistic assessment of the risks.

We appreciate the opportunity to share our views on this matter. Thank you in advance for your time and consideration on this important issue.
 

  • No labels