Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Invalid Top Level Domain Queries at the Root Level of the Domain Name System

Service Expectations of Root Servers (R1)


Date IssuedDocumentReference IDCurrent Phase

15 2010 

Invalid Top Level Domain Queries at the Root Level of the Domain Name System Service Expectations of Root Servers (R1)SAC045RSSAC001

Status
colourGreen
titleClosed



Description:

ICANN should educate users so that, eventually, private networks and individual hosts do not attempt to resolve local names via the root system of the public DNSA defined set of service expectations that root server operators must satisfy including Infrastructure, Service Accuracy, Service Availability, Service Capability, Operational Security, Diversity of Implementation, Monitoring and Measurement, and Communication (both Inter-Operator and Public Communication).


STATUS UPDATES

This item has been processed as much as is relevant and is considered complete; no work is outstanding from the perspective of Board Advice (note that related implementation work may have been integrated into ICANN’s ongoing operations or other initiatives).

Status provided in 19 October 2016 letter from ICANN Board Chair to SSAC Chair: https://www.icann.org/en/system/files/correspondence/crocker-to-faltstrom-19oct16-en.pdf.

The ICANN Board New gTLD Program Committee (NGPC) resolutions on name collision adopted on 7-Oct-2013 and 30-Jul-2014 addressed the issues related to invalid top-level domain queries at the root level of the DNS: http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-07oct13-en.htm; https://www.icann.org/resources/boardmaterial/resolutions-new-gtld-2014-07-30-en.

As part of the 30 July 2014 Board Resolution, a Name Collision Occurrence Management Framework was also published, which can be found here: https://www.icann.org/en/system/files/files/name-collisionframework-30jul14-en.pdf. It should be noted however that invalid TLD query data has not yet been studied and such a study would be required for future "subsequent procedures" for new gTLDs.

ICANN has also developed materials to help IT Professionals understand and address the root cause of name collision: https://www.icann.org/resources/pages/name-collision2013-12-06-en#resources. Materials include a guide for IT departments to identify and manage the name collision risks in their networks among other measures towards that end: https://www.icann.org/en/system/files/files/name-collisionmitigation-01aug14-en.pdf.
DatePhaseTypeStatus Updates

 

ClosedBoard Update