Summary

  • ICANN’s open consultation on the Technical Study Group report for gTLD integrations with alternative naming systems lists 11 submissions. One row is marked “Submission Retracted” and says its content has been removed.
  • Public application data confirms the row has retracted: true and records when it was originally submitted. The reader-facing page does not show a separate retraction time, the actor behind the transition, a governing rule class, a replacement or its future report treatment.
  • ICANN’s user guide permits a submitter to retract a published comment while a proceeding is open. Its Terms of Service separately permits ICANN to refuse or remove content. The tombstone does not say which authority path applied.
  • A 2023 ICANN proceeding counted six received submissions but said one removed submission would not be considered further. That precedent makes disposition and denominators part of the governance record, not a cosmetic detail.
  • The missing fields do not justify restoring removed material or disclosing protected case facts. They justify a privacy-preserving state receipt that identifies actor class, transition time, rule version, replacement status and counting treatment.
  • Participation is input, not mandate. Preserving who withdrew or removed an input—and how the institution handled it—protects both the contributor’s agency and the integrity of the later summary report.

Eleven submissions, one blank record

ICANN opened its Public Comment on the initial report of the Technical Study Group on gTLD integrations with alternative naming systems on 10 August. The submission window closes on 21 September, and a report is due on 5 October. The underlying question is consequential: whether a global DNS gTLD can be associated with the same string in an alternative naming system without compromising DNS security and stability.

This article is not about the answer. It is about one visible state transition inside the process collecting the answers.

At the evidence cutoff, the all-submissions page said “1–11 of 11 submissions”. Its first row carried the organization label Krypto@Recht on X, the date 1 September 2026, the heading “Submission Retracted” and no public body. In its place was one sentence: “This Submission has been removed.” The proceeding’s main page showed the same tombstone among recent submissions.

The HTML delivered by ICANN contains a little more machine-readable state. It marks the entry retracted: true, supplies a public slug and records the original submissionTime as 1 September at 10:53:08 UTC. That timestamp describes submission, not necessarily retraction. The public presentation does not expose another time for the state change.

The system has therefore done better than silent deletion. It preserves that an entry occupied the consultation record and has ceased to be publicly available. What it does not preserve for readers is the authority-bearing event between those states.

“Retracted” and “removed” cover different powers

ICANN’s Step-by-Step Submission Guidelines give a contributor a direct retraction power. While a proceeding remains open, a signed-in user can open a published submission, choose “Retract Submission” under Document Actions and confirm. The guide says the submission will no longer be publicly available and a note will appear indicating that it has been removed. A published submission can also be retracted, edited and published again while the window remains open.

That is one path: the contributor withdraws or revises the contributor’s own input.

ICANN’s Terms of Service creates another. ICANN reserves the right, though not the obligation, to refuse or remove content that in its reasonable opinion violates a policy or procedure or is harmful or objectionable. The terms also place contributor responsibilities around rights, privacy, spam, harmful material and expected behavior.

That is a different path: the platform operator exercises institutional authority over public material.

Both paths can legitimately end with content no longer visible. They should not end with the same public meaning. A self-retraction records contributor agency. An institutional removal records an administrative act governed by a rule. A legal or privacy response may require still another disclosure boundary. The current tombstone establishes none of those explanations, so this article assigns none of them.

It would be irresponsible to call the entry censored. It would be equally irresponsible to assume the submitter withdrew it. “Submission Retracted” describes the present state. “This Submission has been removed” describes the display result. Neither sentence identifies the actor or the public rule by which the state changed.

A denominator is also a decision

ICANN describes Public Comment as a process in which anyone may submit, all submissions are public and archived, ICANN org identifies themes in a summary report, and the group that opened the proceeding addresses the input and proposes next steps. Its employee-practices page says ICANN org is neutral in managing a consistent and transparent mechanism and that submissions remain readily available in an organized archive.

A retraction creates a necessary exception to the ordinary description of public availability. The exception need not expose the removed text. It does need a legible disposition.

The current all-submissions interface counts the tombstone inside “11 submissions”. Does that mean 11 received, ten publicly substantive, and an as-yet-undecided number considered? The page does not say. It would be a mistake to derive the future report’s denominator from the live list alone.

An older official outcome shows why. In a 2023 consultation on a ccTLD review mechanism, ICANN reported that six submissions had been received, one had been removed, and the latter would not be considered further. The institution thereby separated receipt from consideration. That example proves that removal can affect the analysis set. It does not prove what will happen in the 2026 TSG proceeding.

Another public submissions page, for a 2025–2026 GNSO consultation, also used a dated “Submission Retracted” heading and the same removed-content notice. The interface already knows how to preserve a tombstone. What is missing is a stable vocabulary for the transition and the item’s downstream treatment.

The distinction matters because published totals travel. Journalists cite them. Working groups use them to describe participation. Later reviewers compare support, opposition and regional reach. A number that mixes active comments, contributor-withdrawn comments and institution-removed material without a state breakdown invites a false inference about the evidence before the decision-maker.

Preserve the act without restoring the content

The remedy can be narrow. A public state receipt need not reveal the removed submission, a protected complaint, legal advice, personal data or moderation detail. It should disclose only what is needed to understand the governance transition:

  1. the stable submission identifier and original submission time;
  2. the current state and the time that state began;
  3. a safe actor class, such as submitter retraction or ICANN administrative removal, without naming a staff member;
  4. the governing procedure or terms version and, where safe, a broad reason class;
  5. a link to a republished or superseding submission, if one exists;
  6. separate treatment in received, publicly available and considered counts;
  7. the route for correction, appeal or restoration where such a route applies; and
  8. an integrity reference that proves which record changed without republishing its body.

The receipt must be allowed to say not public when a field cannot safely be disclosed. The point is not maximal disclosure. It is to prevent silence from collapsing several different powers into one ambiguous label.

ICANN’s Bylaws already supply the relevant direction. They commit the institution to open and transparent processes, consistent and fair application of documented policies, responsive consultation and public disclosure of comments. The Expected Standards of Behavior likewise ask participants to support robust mechanisms for input, accountability and transparency. A typed state change is a modest implementation of those commitments, not a demand to expose everything.

Input has an owner; decisions have another

Lu Heng’s critique of the multistakeholder model is useful here because it separates participation from mandate. A public comment can supply knowledge, interest, warning or dissent. It does not become institutional authority merely by appearing in the consultation. The body that summarizes and acts on the record has a different role.

The same separation applies when an input disappears. The submitter owns the choice to retract under the user procedure. ICANN owns any decision to remove content under platform rules. ICANN org also owns the administrative construction of the summary report, while the TSG and the proceeding opener own their response to the input. None of these signals should silently substitute for the others.

That is why the actor field matters even when the removed words must remain unavailable. It tells the reader whether the transition expresses the contributor’s agency, the institution’s enforcement, or a protected process whose public classification is necessarily limited. The report-disposition field then tells the reader what the institution did with the resulting record.

ICANN has already preserved the outline of an event: a named public slot, a submission date, a retracted state and an absent body. The next step is not to reopen the body. It is to finish the public grammar of the event. A consultation cannot make every fact public, but it can say which authority changed the state and what that change means for the evidence it will later claim to have considered.

Sources

  1. ICANN — Initial Report of the TSG on gTLD Integrations with Alternative Naming Systems
  2. ICANN — all submissions to the TSG proceeding
  3. ICANN — About Public Comment
  4. ICANN — Public Comment Step-by-Step Submission Guidelines
  5. ICANN — Terms of Service
  6. ICANN — Expected Standards of Behavior
  7. ICANN — Organization Employee Practices and Resources
  8. ICANN — Bylaws
  9. ICANN — 2023 ccNSO review-mechanism Public Comment
  10. ICANN — submissions on the proposed GNSO Board-reversal process
  11. Lu Heng — The Multi-Stakeholder Mirage