GNSO votes 20–0 on Latin diacritics policy

Twenty votes, zero dissent: ICANN’s accent policy reaches the Board’s desk

Why it matters

The GNSO Council gave a unanimous push to 57 Latin-script diacritics outputs. The next signature belongs to a different room.

Daniel Kade23 October 2026 at 17:36 UTCReading Time 2 minLast update: 23 October 2026

أقر مجلس GNSO المخرجات بعشرين صوتاً وأحال 45 توصية إلى مجلس إدارة ICANN.

Summary

On 21 October, all 20 voting GNSO councillors backed the Latin Script Diacritics final report: 45 policy recommendations and 12 implementation-guidance items.
The Council recommended the 45 policy recommendations to the ICANN Board; a review team follows only if the Board adopts them.

The accent mark has cleared one of ICANN’s larger rooms. In its 21 October resolution, the GNSO Council approved all 57 outputs from the Latin Script Diacritics working group and sent 45 policy recommendations to the Board with a recommendation to adopt. The motion’s original vote recorder shows 20 yes, no opposing vote, no abstention and no absence. Seven votes came from the Contracted Parties House and thirteen from the Non-Contracted Parties House. This is as tidy a Council tally as a policy author could order.

The arithmetic matters because the outputs have different destinations. Forty-five are policy recommendations on the exceptional pairing of an ASCII top-level-domain string with a related Latin-script string bearing diacritics. Twelve are implementation guidance. The Council approved both sets; its formal recommendation to the Board concerns the 45 policy items. The working group’s final report records full consensus on all 57 on 6 August and submission to the Council on 31 August. Wednesday’s vote promoted that work from group agreement to a Council position.

The next desk has its own pen. The resolution asks ICANN to convene an Implementation Review Team if the Board adopts the recommendations. That conditional wording sets the sequence: Council approval, Board consideration, then implementation design. Operators interested in paired strings now have a clear policy signal and a concrete record to inspect, while the final decision remains on the Board agenda.

A unanimous vote can make a complicated file look effortless. It also fixes responsibility. If the Board alters the course, the Council’s twenty-name record and its split between policy and guidance give readers a precise starting point for asking why. The accent has a passport from the Council; the Board controls the next stamp.