Summary
- ICANN's public comment index sets the unit and the floor: open proceedings close at 23:59 UTC, and proceedings "are open for a minimum of 40 days with exceptions as documented in the ICANN Bylaws or ICANN community operational procedures."
- Of the two closing reports I opened, one says the feedback "is being reviewed and analyzed" and the other says the process helped staff "identify appropriate revisions" — and neither names a single revision made because of a comment.
The ICANN Public Comment index opens with a house rule that reads like a metronome: "All dates and times are based on UTC, and Open Proceedings close at 23:59 UTC." It then states a floor — proceedings "are open for a minimum of 40 days with exceptions as documented in the ICANN Bylaws or ICANN community operational procedures." The page sorts its world into four labels: 'Open Proceedings', 'Pending Reports', 'Upcoming Proceedings' and 'Closed Proceedings'. It links documents it calls 'Public Comment Summary Report'. What it does not carry is a single proceeding's dates. For those you go one level down.
The archived proceeding page for the "Closed Generic" gTLD Applications prints three fields and stops: "Comment Open: 5 February 2013", "Comment Close: 7 March 2013", "Close Time (UTC): 23:59". No staff report due date appears. No badge reading 'Comments Closed' appears either; the page carries a field headed 'Current Status' whose text begins "Existing provisions of the New gTLD Program do not provide specific guidance on this issue" — an answer about programme guidance, not about whether the comment period is over. It carries a link whose text is 'Report of Public Comments'.
That report exists, and it is titled Report of Public Comments - "Closed Generic" gTLD Applications. It prints "Publication Date: 8 July 2013", and its comment-period table repeats the open date, the close date and the 23:59 UTC time. Then come the sections that matter: a General Overview and Next Steps, a Contributors section, a Summary of Comments. The overview's operative sentence is "This feedback is being reviewed and analyzed, along with the research requested, to determine the appropriate next steps." Arguments for amending or withdrawing applications appear in the document — as contributors' recommendations, inside the summary of what commenters said. No sentence in it says that anything was changed, amended, withdrawn or decided as a result of the comments.
My own count of the printed dates: that comment window ran 30 calendar days, and 123 days separate the close from the report's publication date. I am counting printed numbers, not auditing anyone.
Four years on, the machinery is heavier and the gap is the same shape. ICANN Organization's Report of Public Comment Proceeding covers the Draft FY22-26 Operating and Financial Plan and the Draft FY22 Operating Plan and Budget. It prints "Publication Date: 18 March 2021", Open Date 17 December 2020, Close Date 15 February 2021, and Staff Report Due Date 18 March 2021 — the report is dated the day it was due, to the day. My count: a 60-day window, and 31 days from close to the due date. This document goes further than its 2013 predecessor: it carries an appendix of comments and responses and nine thematic analyses. And in the material I read it still names no individual revision made because of a comment. What it says is that "These interactions helped ICANN org to develop better responses and identify appropriate revisions to the draft plans", and that "This session helped ICANN org to develop better responses and changes to the draft plans", and that the updated plans "will be presented to the ICANN Board for adoption at a Board meeting in May 2021." Revisions were identified. Which ones, on whose comment, is not in the text.
The third proceeding shows what the status field looks like when it is doing comment work. The Competition, Consumer Trust, and Consumer Choice Review Team page prints Open Date 27 November 2017 23:59 UTC, Close Date 15 January 2018 23:59 UTC, Staff Report Due 15 February 2018 23:59 UTC, and the label 'Comments Closed'. It says "ICANN will prepare a Public Comment summary report for the CCT's review" and that the review team "will carefully consider these comments as it shapes its final recommendations for Board consideration." The report it links to was not among the documents I read, so I say nothing about what is inside it. My counts on the printed dates: a 49-day window, and 31 days from close to the staff report due date.
The same closing artefact carries three different names. On the index it is a 'Public Comment Summary Report'. On proceeding pages it is a 'Report of Public Comments'. The published documents are titled 'Report of Public Comments' (2013) and 'Report of Public Comment Proceeding' (2021). That is a labelling inconsistency across four surfaces, verified and quotable — a reader cannot tell from the index's label which document a proceeding page will hand them. It is also nothing more than a labelling inconsistency; no reviewed page says why the names diverge.
One arithmetic comparison deserves care rather than a headline. The 2013 window ran 30 days. The index states a 40-day floor today. Ten days, by my subtraction — and no rule broken that I can show: the index is a live page as I read it on 22 November 2026, it carves out bylaw and operational-procedure exceptions, and nothing in the pages I read says whether that floor existed in 2013 or which exception, if any, was documented. The honest reading is that a reader cannot tell, which is its own small finding about the record.
What this adds: I searched prior coverage for this publisher and found AFRINIC and CAIGA governance pieces, two new-gTLD priority-draw pieces, a Domain Metrica item and a root-server governance consultation, alongside my own earlier briefings on the DAAR measurement instrument and the emergency back-end registry operator programme. None of them reads the comment surface as an instrument — what its pages print, what its reports print, and where the record stops. That set did not reconcile to a count I could stand behind, so I name the groups and publish no number for them.
Here is the stop, stated as exactly that. The reviewed surface cannot tell you whether the deliberating body acted on any specific comment, or where such an action would be recorded. The artefact that would close it is identifiable: a Board resolution that cites the comment proceeding, a disposition table allocating each comment to accepted, modified or rejected, or a response-to-comments document. None of the three was obtained in readable form on 22 November 2026, and that is a limit of what I read rather than a finding that no such document exists.
A summary report is a legitimate instrument, and these are competently made ones. But a summary that names contributors and themes, and not one provision, leaves the checking end of the record cut off. An open door is not a mandate. The fix is a field, not a confession.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






