Summary

  • On 21 October the GNSO Council approved all 57 Latin Script Diacritics outputs in a 20–0 vote, sending 45 policy recommendations to the ICANN Board for consideration.
  • The 12 other outputs are implementation guidance. An Implementation Review Team is conditional on Board adoption; the Board’s 22 October IDN ccTLD vote belongs to another policy process.

Suppose a registry operator wants an accented form of a familiar ASCII top-level domain. The new GNSO vote matters to that plan, but it does not yet supply permission to operate the pair. The Council’s 21 October resolution closes one decision stage: it approves the working group’s entire package and asks the ICANN Board to adopt its policy recommendations. The Board’s judgment and any implementation still lie ahead.

The package has two kinds of output, a distinction lost when it is described simply as “57 recommendations.” There are 45 policy recommendations and 12 items of implementation guidance. The Council approved all 57, but its request to the Board concerns the 45 policy recommendations. It also asked ICANN org to convene an Implementation Review Team only if the Board adopts them. That conditional matters: there is no authorization in this motion to run implementation ahead of adoption.

The official vote recorder records 20 votes for the Latin Script Diacritics motion, none against, no abstentions and no absences. The working group had already reached full consensus. Those are substantial endorsements within the GNSO process, yet neither tally is a Board resolution. A unanimous room can recommend an exception; it cannot by itself make that exception an operative delegation rule.

The 31 August final report explains why an exception is being considered. An ASCII gTLD and a visually similar Latin-diacritic gTLD may not count as variants under existing rules. The working group drew a narrow path for a single registry operator to run qualifying strings together. The report’s detailed transition and exit arrangements have been examined separately; the news now is that the Council has voted to advance the package, not that those arrangements have gone live.

The timing invites a second possible mistake. In its 22 October resolutions, the ICANN Board adopted parts of a ccNSO IDN ccTLD policy and withheld others. That is a country-code process, not the GNSO’s Latin Script Diacritics gTLD package. The fact that both concern internationalized names does not transfer a Board decision from one track to the other.

For an applicant or registry operator, the immediate change is therefore narrower than the vote margin suggests. The GNSO has settled its recommendation; it has not supplied a Board adoption date, an effective rule or an implementation timetable. The next reliable signal is a Board decision specifically naming the Latin Script Diacritics recommendations, followed, if adopted, by an implementation process that states what qualified applicants can actually do.