Summary

  • ICANN's public comment page states that proceedings stay open for a minimum of 40 days, with exceptions documented in the Bylaws or in community operating procedures. The Bylaws' own comment clause states no number of days at all.
  • The twenty-one-day figure in Article 3 §3.6(a)(i) is advance notice of Board action, not the length of a comment period. What closes a proceeding is a theme report, published on a date each proceeding states for itself.

A proceeding with three dates on it

The DNSSEC DS Automation: Security & Stability Assessment proceeding has been open for submissions since 12 October 2026. It closes for submissions on 23 November 2026 at 23:59. The report is due on 7 December 2026 at 23:59, and the page calls that document a "Public Comment Summary report". The timeline is stated in UTC, the sort of precision that appears only where a deadline has bitten someone.

That is forty-two days between opening and closing — my subtraction from ICANN's own two dates, not a figure ICANN publishes as a rule — four days above the published forty-day minimum. From close to stated report date, fourteen days. Hold those three dates in view, because they are the whole architecture of a proceeding in miniature: an intake window, a close, a promised reckoning. Now ask where the numbers come from. The answers do not live where most people assume.

Where the forty days actually live

"Proceedings are open for a minimum of 40 days with exceptions as documented in the ICANN Bylaws or ICANN community operational procedures." That sentence is on ICANN's public comment page, read on 13 November 2026, and it is the only standing minimum-duration figure I located anywhere in the documents this article rests on. It is not decoration: forty days is what a commenter, a contracted party or a competing applicant can plan against without reading anything else.

It is also a sentence on a web page describing the process, not a clause in the instrument that constitutes the process. That difference matters less than it sounds and more than it looks. The Bylaws, on the page stated as amended 3 July 2026, require ICANN to "provide a reasonable opportunity for parties to comment" — §3.6(a)(ii) — a standard with no figure attached. A reasonable opportunity is a judgement. Forty days is a number. Both do work, and they are not doing the same work.

I put the sharper version of this question to my own editorial discipline before drafting: has the enforceable number and the binding instrument, in effect, traded places? The answer came back that the framing overreaches. The charter layer fixes process — notice, opportunity, who acts. The practice layer supplies the duration and the reporting template. The two layers govern different objects, which is a division of labour, not a transfer of authority. What would have to change to move the forty-day floor is genuinely not established by anything I read, and I am not inventing it for the tidier sentence.

Twenty-one days is a different clock

Here is the number that travels. Article 3 §3.6(a)(i) provides for notice "at least twenty-one days (and if practical, earlier) prior to any action by the Board". Twenty-one days, in the Bylaws, in an instrument with actual legal force, attached to a real obligation.

It is not the comment period. It is the notice that must precede Board action — a separate commitment, on a separate timetable, serving a separate purpose. Anyone reporting that ICANN's comment periods run twenty-one days has taken a genuine number out of its genuine clause and rehoused it. The Bylaws' actual comment provision contains no day count; it reached this review as a fragment, and I attach no number to it.

That is the trap this subject sets, and it is worth naming: the charter's number is not the practice's number, and the practice's number is not in the charter. Two instruments, two figures, forty days of difference in what they govern. My own desk has spent the week reading ICANN instruments where the operative number sat one document down from where the right was created. Same shape here, with a twist — the number people rely on is not one document down, it is one document across.

Four bodies can open a proceeding

"The ICANN Board, Supporting Organizations, Advisory Committees, or ICANN organization (org) can open proceedings." That is from the about page, step one of the process infographic, in the publisher's own wording.

Four kinds of actor, one of which is the organization that also writes the closing report. I tested whether the record supports saying the gate is real for the commenter while the disposition is formatted rather than adjudicative for the decision-maker. It does — provided the description stays on structure rather than motive, and provided I do not slide into the claim that comments are ignored. Nothing in these documents supports that claim.

The practical consequence of the plural opener is not cynicism but arithmetic: a party watching for a proceeding has four possible queues to watch, not one, and a party assuming a single announcement channel will simply miss proceedings opened elsewhere.

What closes it, and on whose date

When a submission period ends, the closing instrument is a report. ICANN's organization practices state it directly: "When the submission period for a Public Comment proceeding ends, ICANN org develops a summary report using a template." The described report identifies and analyses common themes, records the proceeding's outcome, the resulting document changes and next steps. The infographic's step four says it in fewer words: "ICANN org summarizes submissions and identifies themes into a published report."

Themes, an outcome, changes, next steps. That is a format for disposition, and it is demanding — it obliges someone to say what happened and what moved. It is not a ruling on each submission, and no document I read promises one. File a comment expecting a paragraph addressed to your point and you are expecting a document this procedure does not describe. File one written to be legible to thematic summarisation — one problem, stated once, with the consequence spelled out — and you are writing to the instrument that exists.

The date is the quietly interesting part. The report has a due date, published per proceeding, not a standing interval in the charters. For the DNSSEC assessment that date is 7 December 2026. A dated commitment per proceeding is a stronger thing to hold an institution to than a general aspiration, and a weaker thing than a rule that every proceeding closes its record within a fixed number of days of intake. ICANN has chosen the former.

It has not always. A policy update dated 21 November 2014 announced that "staff will be expected to produce a summary report of comments submitted within two weeks of the closing date of the proceeding." That is history and I treat it as history: not the current rule, and I compute nothing from it. But it is a useful dated marker of what the institution once said out loud about its own turnaround, and the current public record states the interval per proceeding instead.

What this review did not obtain

Three gaps, each stated where it bites rather than as a closing caveat.

No sentence naming a single office or role that opens, extends and closes a public comment proceeding appeared in the documents I read. Opening authority is stated in the plural. Extension authority I did not find at all. That is a fact about my reading, not a finding that no such provision exists — and the practical difference is large, because a party who needs more time has, on this record, no identified addressee.

The forty-day minimum is stated to have exceptions "as documented in the ICANN Bylaws or ICANN community operational procedures". I did not read those exception documents. So I enumerate no exception and describe no proceeding as exceptional, and the floor is a floor as published rather than a floor as tested.

An archived page titled "How Public Comment Works" could not be retrieved at all: two attempts timed out and only a search preview was available. Nothing from it appears here.

What a reader should do with this

Three dates, not one. A proceeding publishes when it opens, when it closes, and when its report is due. Diarise the third. Most parties diarise the second and then treat silence as an answer.

Write to the format that exists. A theme report rewards a submission whose theme is unmistakable and whose consequence is stated in the first paragraph. It cannot reward a submission whose argument is spread across four screens and depends on the summariser reconstructing it.

And know which clock you are reading. Forty days is the intake floor. Twenty-one days is Board notice. Neither is the other, and a party planning against the wrong one will be late in a way no extension can fix, because the extension route is exactly the one this review could not locate.

ICANN's own pages are the institution describing its own process, and that is the status of every quotation above — recorded at the ICANN Public Comment entry. What would change the picture is not a better summary of those pages but two missing documents: the exception procedures that qualify the forty-day floor, and any record of a period extended. Until one of those surfaces, the honest description of this gate is that the entrance is measured to the day and the exit is dated per proceeding.