Summary

  • The ccNSO says ICANN may seek relevant statements when there is a reasonable basis to suspect a change affecting an IDN ccTLD. That is different from routinely policing compliance.
  • The Council adopted the answer in July. The Board’s 4–6 September workshop is due to consider ccPDP4 next steps, not announce a predetermined outcome.

ICANN’s forthcoming Board workshop puts a small but consequential question back in view: when may an administrator ask a country-code domain manager to prove that a name still qualifies?

The 2 September workshop preview says the Board will consider next steps recommended by its ccPDP4 Caucus. The recommendations concern internationalised country-code top-level domains, or IDN ccTLDs. These let country-code names use different writing systems. The workshop runs from 4 to 6 September in Los Angeles; the preview does not establish adoption.

One part of the preparatory work is already public. In its response to question 3, the ccNSO explains that language assigning ICANN a passive role was intended to prevent active compliance policing. It nevertheless accepts follow-up where there is a reasonable assumption that something relevant has changed.

Permission to ask is not a finding

The question concerns changes to a designated language, its script, or a territory’s name in that language. A follow-up may request a statement about the name association, the language’s status or the referenced script, depending on the issue.

The response gives examples involving French or English transliteration in the ISO 3166 list and the GAC accreditation process. It does not turn either example into an automatic finding that a domain name has become ineligible. Nor does it supply an exhaustive test for what makes an assumption reasonable.

This is not merely an unanswered proposal from ICANN staff. The 16 July Council minutes record adoption of the response under resolution 231-04. The August meeting notes mark its dispatch complete and describe staff incorporating the answers into their assessment. Council agreement on interpretation is, however, distinct from a Board decision on the policy.

The document has to fit the question

The June 2024 Board Report separates three matters: whether a string still represents the territory’s name, whether the language retains the relevant status, and whether the script remains in use for that language. A designated language, for this purpose, has legal status in the territory or serves its administration.

These are not interchangeable claims. A changed spelling in an external reference might justify asking for clarification; it does not by itself establish that a language has lost its administrative role.

The report also shows why a request is more than harmless correspondence. In section 12.4’s particular scenario—a valid new application in the same designated language but another script—the earlier applicant or manager must obtain a script statement from a comparable relevant public authority. That procedure includes a three-month response interval after notification and possible retirement consequences. The July answer does not create a new, universal three-month inspection cycle.

For managers, the practical issue is therefore the scope and basis of the enquiry before any eventual eligibility decision. A narrow request can resolve stale or inconsistent evidence. An open-ended demand can consume administrative effort without making clear what would settle the matter.

As of 3 September, the reviewed record identifies no particular string investigated or retired under this clarification. The next question is how its distinction will be carried into any approved implementation: a reason to ask for evidence must not silently become a conclusion about what that evidence will prove.

Sources

  1. September Board workshop preview
  2. Council response, question 3, page 5
  3. July Council minutes, resolution 231-04
  4. August Council notes
  5. ccPDP4 Board Report, sections 12.2–12.4