Historical Resolution Tracking Feature » SAC045: SSAC Advisory on Invalid Top Level Domain Queries at the Root Level of the Domain Name System (DNS)
Important note: The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.
SAC045: SSAC Advisory on Invalid Top Level Domain Queries at the Root Level of the Domain Name System (DNS)
Whereas, on 2 November 2010, the ICANN Board passed a Name Collision related Resolution, requesting ICANN's Security and Stability Advisory Committee (SSAC) to develop a plan for Board approval setting out studies of the issue of name collision, with many elements detailed.
Whereas, on 15 November 2010 the SSAC Advisory, SAC045: SSAC Advisory on "Invalid Top Level Domain Queries at the Root Level of the Domain Name System" was received by ICANN org.
Whereas, on 10 December 2010, the ICANN Board passed Resolution 2010.12.10.22, which directed ICANN org's Chief Executive Officer (CEO) to implement SAC045.
Whereas, on 2 November 2017, developments in the New Generic Top Level Domain (gTLD) Program caused the ICANN Board to request, through resolutions 2017.11.02.29 and 2017.11.02.31, that SSAC develop a new plan for Board approval setting out studies of the issue of name collision.
Whereas, in January 2018, the SSAC Name Collision Analysis Project (NCAP) Work Party ("NCAP WP") was formed and prepared a plan calling for three studies.
Whereas, on 28 February 2018, SSAC published "SSAC Proposal for the Name Collision Analysis Project", which proposed three consecutive studies to address the Board's request.
Whereas, the Office of the Chief Technical Officer (OCTO) proposed minor changes to the proposal and, after discussion between SSAC and OCTO, an updated version of the proposal was published in February 2019.
Whereas, in June 2018, after input from the Board, the ICANN org CEO assigned OCTO to be responsible for completing the NCAP studies.
Whereas, in November 2019, during a meeting with representatives of OCTO and SSAC, the SSAC representatives agreed that the remaining actions called for by SAC045 are covered by the NCAP.
Resolved (2021.05.12.07), the Board finds that the actions called for in SAC045 can be considered resolved by the NCAP and that the remaining item related to SAC045 being tracked in the ICANN org Action Request Registry may therefore be completed.
1. Why is the Board addressing the issue?
On 2 November 2010, the ICANN Board passed a Name Collision related Resolution, requesting ICANN's Security and Stability Advisory Committee (SSAC) to develop a plan for Board approval setting out studies of the issue of name collision, with many elements detailed.
On 15 November 2010 the SSAC Advisory, SAC045: SSAC Advisory on Invalid Top Level Domain Queries at the Root Level of the Domain Name System was received by ICANN org. The Security and Stability Committee (SSAC) identified certain technical considerations of strings that they proposed for use by applicants and recommended specific actions with regard to applications for those strings.
On 10 December 2010, the ICANN Board immediately directed implementation of SAC045 with Resolution 2010.12.10.22,:
The Board directs the Chief Executive Officer (CEO) to:
Analyze and amend the Domain Name System (DNS) Stability Review described in the Applicant Guidebook to allow the option to prohibit the delegation of problematic strings, as appropriate, to address the potential technical and stability issues discussed in SAC045; and,
Develop a mechanism to alert potential applicants for new generic top-level domains (gTLDs) about the issues raised in SAC045.
Due to further developments on the new gTLD program, on 02 November 2017, the ICANN Board passed resolutions (2017.11.02.29 - 2017.11.02.31)
requesting SSAC to develop a new plan for Board approval setting out studies of the issue of name collision, with many elements detailed.
Following the Board resolution, SSAC began project planning in December 2017 for the work necessary to address the Board's request. In January 2018, the SSAC Name Collision Analysis Project (NCAP) Work Party ("NCAP WP") was formed and prepared a plan calling for three studies. The NCAP Administration ("NCAP Admin"), a smaller group comprising the NCAP WP leadership and SSAC leadership, was also created to guide the NCAP effort both within SSAC and in the larger ICANN community.
On 28 February 2018, SSAC published "SSAC Proposal for the Name Collision Analysis Project", which proposed three consecutive studies to address the Board's request.
In June 2018, after input from the Board, the ICANN org CEO assigned the Office of the Chief Technical Officer (OCTO) to be responsible for completing the NCAP studies since SSAC does not have the administrative infrastructure to undertake and manage such a large project. OCTO proposed minor changes to the proposal and, after discussion between SSAC and OCTO, an updated version of the proposal was published in February 2019.
As the NCAP studies encompass all of the elements within SAC045, during ICANN66 in November 2019, SSAC agreed with OCTO that SAC045 could be closed.
This Board Paper demonstrates ICANN org's completion of work on SAC045's recommendations. As a result, the Board is now directing that the remaining items related to SAC045 being tracked in the ICANN org Action Request Registry may be closed, at the recommendation of the Board Technical Committee (BTC).
2. What is the proposal being considered?
The Board is considering a recommendation from the BTC that the ICANN Board direct that the remaining items related to SAC045 being tracked in the ICANN org Action Request Registry may be closed.
3. Which stakeholders or others were consulted?
The SSAC agreed that ICANN org has fulfilled its role in implementing the Recommendations of this Advisory.
4. What concerns or issues were raised by the community?
None.
5. What significant materials did the Board review?
In determining that the remaining items related to SAC045 being tracked in the ICANN org Action Request Registry may be closed, the Board considered the recommendation of the BTC and the rationale from ICANN org demonstrating that work on these remaining items is now complete.
6. Are there positive or negative community impacts?
This Board resolution confirms that the Advisory's recommendations were completed by ICANN org and does not assess the impacts of the implementation of the recommendations.
7. Are there fiscal impacts or ramifications on ICANN (strategic plan, operating plan, budget); the community; and/or the public?
No fiscal impacts or ramifications on ICANN, the community, or the public are expected as a result of closing these remaining SAC045 items.
8. Are there any security, stability or resiliency issues relating to the DNS?
No security, stability, or resiliency issues relating to the DNS are expected as a result of closing these remaining SAC045 items.
9. Is this decision in the public interest and within ICANN's mission?
Yes. Confirming the completion of the implementation of an Advisory provides an accountability mechanism for ICANN's work, which is in the public interest and within ICANN's mission.
10. Is this either a defined policy process within ICANN's Supporting Organizations or ICANN's Organizational Administrative Function decision requiring public comment or not requiring public comment?
This action does not require public comment.