Summary

  • ICANN closed public comment on 10 August 2026 on draft UDRP and URS changes for complaints brought by intergovernmental organizations. Its summary and analysis report is due on 1 September.
  • The drafts create two different arbitration branches. A registrant may request arbitration before the domain-dispute decision, when the IGO may accept or decline. After specified favorable decisions or an immunity-based court order, a timely request invokes a commitment the IGO made when filing.
  • The mandatory branch has an express ten-business-day request window. The discretionary early branch has no stated deadline for the IGO's answer, no required response form and no default disposition.
  • Proposed UDRP Rules describe filing, fee, administrative review, notice and registrar-lock duties. They do not identify the record that closes an early request when the IGO declines or does not answer.
  • Proposed guidance says arbitration should not delay a dispute and does not automatically replace or interfere with an ongoing UDRP or URS case. That is an objective, not an execution clock.
  • ICANN should publish a thin early-request receipt showing request, intake, answer, deadline, underlying-case state, operational effect and termination, while keeping the mandatory post-decision route visibly separate.

A deliberate new window, not a drafting accident

The public-comment period is over, but the implementation record is not finished. ICANN asked the community to review draft changes to the Uniform Domain Name Dispute Resolution Policy, the Uniform Rapid Suspension system and their rules. The package implements four recommendations from a 2018 policy process and five from a 2022 expedited process. The ICANN Board adopted the combined package in April 2023.

The immediate news peg is procedural. Submissions closed on 10 August, sixteen appear in the public index, and ICANN's summary is due on 1 September. The consultation did not invite the community to retry the merits of IGO protection. It asked whether the drafts faithfully implement policy that has already been adopted.

One implementation choice came later. In January 2026, the GNSO Council confirmed that a respondent should be able to seek voluntary alternative dispute resolution after an IGO's UDRP or URS complaint begins, including before a determination. The Council said the policy recommendations should not be read to prevent that choice.

That makes the early window intentional. The question is not whether the drafter accidentally left a stray sentence in the redline. The Council authorized the branch; the implementation now has to make its state transitions usable.

The same word “arbitration” covers two different rights

The drafts distinguish two paths that must not be collapsed.

In the ordinary post-decision path, the registrant has ten business days after a UDRP panel decision or URS appeal decision favoring the IGO to initiate the new arbitral proceeding. A similar clock applies after a court declines to hear the merits on the basis of IGO privileges and immunities. In those circumstances, the IGO's agreement is not optional. It is a condition accepted when the IGO filed the complaint.

The early path works differently. Once the complaint has been transmitted, but before the UDRP decision or URS appeal decision, the registrant may request arbitration. The IGO “may, but is not required to,” agree. That is a request for consent, not the same review right that becomes available after the named decisions.

This boundary protects both sides of the policy bargain. The IGO retains discretion before the administrative process has produced an outcome. The registrant retains a mandatory alternative to court review when an IGO has won and immunity may obstruct the judicial route. Reporting the two branches as one would give the IGO a veto it does not have after the decision, or give the registrant a compulsory early route the text does not create.

The clocks expose the difference. The mandatory branch specifies when the registrant must act. The discretionary branch says the IGO may choose, but does not say when that choice must become known.

The UDRP draft starts a chain without naming its early ending

Proposed paragraph 20 of the UDRP Rules is operationally detailed at the beginning. The respondent sends the request electronically to an ICANN-designated arbitral institution, pays the applicable filing fee and copies the registrar. The institution checks administrative compliance. If the submission complies, it sends a Notice of Arbitral Proceeding to the IGO complainant and the other named actors.

The registrar also receives a direct instruction. Once it receives the respondent's request, it must maintain the domain lock and take no further action until it receives one of three things: evidence of a settlement, notice that the arbitral proceeding has terminated, or an arbitral decision.

Those records make sense when arbitration has been accepted and commenced. They are less clear in the discretionary branch. The draft does not state how many days the IGO has to accept or decline. It does not prescribe an answer form or say which parties must receive it. It does not say whether silence means decline, leaves the request pending, or triggers an institution's administrative closure. Nor does it explicitly identify the notice that lets the registrar distinguish a declined request from an active arbitration.

This is not proof that a domain will remain locked indefinitely. An arbitral institution's supplemental rules could supply a deadline or termination notice. ICANN could also revise the final instrument. The defensible finding is narrower: the public draft itself does not join the IGO's discretionary answer to the registrar's state machine.

That missing join matters because “request,” “administratively compliant,” “accepted,” “commenced” and “terminated” are not synonyms. If each actor uses a different one as the operative event, the procedure can be legally permitted yet operationally uneven.

URS repeats the answer-state gap without copying every UDRP effect

The proposed URS procedure uses the same policy distinction. Section 13.2.1.2 describes circumstances in which the IGO must participate: a timely request after a favorable URS appeal determination or after the qualifying court order. Section 13.2.1.3 covers other circumstances and says the IGO may accept or decline.

The URS text then identifies electronic filing, copying the registrar and registry operator, the filing fee, administrative review and notice. It also contains its own rules for suspension, resolution and communication. Those operational effects are not identical to a UDRP lock and should not be reported as though they were.

The common defect is smaller than a claim of identical procedure. In both draft paths, the early IGO choice lacks a published answer deadline and normalized disposition. A provider can know that a request arrived. An IGO can know that it has not consented. A registrar or registry operator can still need an authoritative record of what that means for the next action.

“Do not delay” cannot substitute for a clock

The proposed ICANN guidance recognizes the coordination problem. It says that initiating another arbitration or dispute-resolution process does not automatically affect, replace, supersede or interfere with an ongoing UDRP or URS proceeding. It also says arbitration should not be used to delay or prolong a dispute and should support efficient, coordinated resolution.

That is sound guidance, but it is expressly advisory. It imposes no requirements and does not amend the UDRP or URS rules. A statement of purpose cannot tell a registrar whether an early request is awaiting consent, has been declined, or has become a live arbitral proceeding.

Nor should the answer be inferred from silence. Default rules allocate power. Treating silence as acceptance would erase the IGO's discretion. Treating it as immediate decline would invent a deadline of zero. Treating it as permanently pending would convert a voluntary option into procedural uncertainty. The draft needs to choose and record a state rather than leave each administrator to construct one.

Publish an early-request answer receipt

The smallest repair is not a new policy debate. It is a thin operational receipt for the branch that the GNSO Council has already confirmed.

The receipt should identify the underlying UDRP or URS case, the early-request timestamp, delivery evidence, the arbitral institution, fee and administrative-intake state, and the date by which the IGO must answer. It should record accepted, declined or unanswered as distinct states, with an effective timestamp and the actor responsible for the next notice.

It should also show the continuing state of the underlying case. If the UDRP or URS timetable continues, say so. If an accepted arbitration produces a stay, lock or suspension effect under the applicable instrument, name it. If a request is withdrawn, deficient or terminated, publish the record that returns control to the ordinary path. Corrections and supersession should remain visible.

Most importantly, the receipt needs a branch flag. An early discretionary request and a mandatory request inside the ten-business-day window must never look alike. The same interface can display both, but the source of the right and the IGO's obligation are different.

Heng Lu's policy-mirror test applies here in a limited way: the record should describe the operational reality it coordinates. This is not an argument that ICANN lacks authority or that domain names are registry assets in the RIR sense. It is a demand that a procedural option expose who holds the next decision, by when, and with what effect. A thin ledger is enough; the merits and confidential filings can remain outside it.

Sources

  1. Heng Lu, The Policy Mirror
  2. ICANN public-comment proceeding
  3. Public submissions index
  4. Proposed UDRP policy redline
  5. Proposed UDRP Rules redline
  6. Proposed URS Procedure redline
  7. Proposed URS Rules redline
  8. Proposed policy guidance on IGO use of UDRP and URS
  9. GNSO Council resolutions, including 20260115-2
  10. 2022 IGO EPDP Final Report
  11. 2018 IGO-INGO Curative Rights PDP Final Report
  12. ICANN Board resolutions of 30 April 2023