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).
Proposal for some text relating to this PC:
Ever since its Statement "Proposal to Mitigate Name Collision Risks" ( https://atlarge.icann.org/advice_statements/7231 ) of 27 Aug 2013, the ALAC has been supportive of work designed to identify, understand and mitigate risks associated with Name Collisions.
Such understanding of risks by ICANN has evolved a long way in the past 9 years and the ALAC is pleased to note that a great deal more is now understood and processes are in place to both understand the root cause of most name collisions and understand the impact of name collisions.
Thanking the authors of the NCAP studies, the ALAC reiterates its full support that this work continues in the future. Its position is unchanged from Aug 2013:
"In particular, the ALAC wishes to reiterate its previous Advice to the Board that, in pursuing mitigation actions to minimize residual risk, especially for those strings in the “uncalculated risk” category, ICANN must assure that such residual risk is not transferred to third parties such as current registry operators, new gTLD applicants, registrants, consumers and individual end users. In particular, the direct and indirect costs associated with proposed mitigation actions should not have to be borne by registrants, consumers and individual end users. The Board must err on the side of caution and ensuring that the DNS under ICANN's auspices remains highly trusted."