Summary
- Doytchin Spiridonov told ICANN he holds three third-level .NAME names — DODO.DODO.NAME, GEORGE.DIMITROV.NAME and ASEN.ILIEV.NAME — and asked it to suspend two .NAME service discontinuations, to keep his registrations alive during reconsideration, and to grandfather or refund them if they were not. The Board Accountability Mechanisms Committee recommended denial on 24 August 2026.
- The committee closed two doors in its own words: RSEP review is "limited to ICANN's consideration of security, stability, and competition issues", and refunds, credits, grandfathering and compensation are "governed by contractual agreements between registrars and registrants, to which ICANN is not a party."
- His request then became the container for eight others — six .NAME requests consolidated on 14 October 2026, nine by 28 October 2026 — and the ICANN pages read for this article show no Board resolution on any of them, 170 days after he filed.
Three names and a paid-through date
The asset at the centre of this file never appears in a policy debate. In the committee's recommendation of 24 August 2026, staff are recorded asking on 10 June 2026 which third-level .NAME names the Requestor held, and the Requestor replying with three — DODO.DODO.NAME (to expire 17 February 2027), GEORGE.DIMITROV.NAME (to expire 5 November 2029) and ASEN.ILIEV.NAME (to expire 18 November 2026) — "and also identifying his associated email accounts" (BAMC Recommendation on Reconsideration Request 26-2). The wording of that recommendation is quoted here from the document text returned for the PDF at that address; its pagination and footnote numbering were not confirmed.
That last date is the whole case in miniature. One of the three registrations carried a paid-through date of 18 November 2026, the day before this was written. Nothing in the record read establishes that it lapsed, was renewed or was terminated, and this article does not say. It says that a docket and a paid-through date run on different clocks, and only one of them sends a notice.
The two proposals behind the file are the ones a registrant would feel. As the recommendation records, RSEP 2026013 concerns "the discontinuation of the third-level .NAME domain name registrations service" and RSEP 2026014 concerns "the discontinuation of the .NAME email forwarding service" — both approved by ICANN, both challenged by this one registrant (same recommendation).
What he asked for was specific. The recommendation summarises the relief as reconsidering and suspending the two approvals, providing more information on the approval process, opening a public comment process, and ensuring that no existing registrations are terminated during reconsideration. Further down, the same document quotes his list: disclosure of records relating to meetings between Verisign and ICANN, a full review of the factual basis for the approvals, a revised impact assessment addressing impact on registrants, an assurance that no existing registration or associated email service is terminated pending completion of reconsideration, and grandfathering through paid expiration dates or an equivalent refund (recommendation).
The two sentences that dispose of it
The committee did not pretend the harm was imaginary. It conceded the facts and denied their relevance, in a subsection headed, in the document as returned, "A. The Requestor Has Not Demonstrated that ICANN Failed to Consider Material Information When It Approved the RSEP Requests."
The first sentence: "While such considerations are understandably important to the Requestor and other registrants, the scope of ICANN's review of RSEP requests is narrow and is limited to ICANN's consideration of security, stability, and competition issues." The second does the arithmetic of that threshold: ICANN "was aware of the underlying facts regarding termination of third-level registrations and of the noted email services/addresses, as well as the potential impact on registrants", but those impacts "do not rise to the level of significant security, stability or competition issues under the RSEP and therefore fall outside the scope of ICANN's RSEP review" (recommendation).
Awareness granted. Standing denied. That is a cleaner piece of reasoning than most refusals ever get, and it is worth naming precisely: the committee is not saying ICANN ignored him. It is saying it heard him, and that the door he was knocking on does not open onto that room.
The third sentence is where the article lives. "Further, the potential remedies the Requestor has identified – such as refunds, credits, grandfathering, and compensation – are governed by contractual agreements between registrars and registrants, to which ICANN is not a party." And then, in case the point was too subtle: his claims about impacts on registration holders and about remedies against third parties "fall outside the scope of ICANN's review process under the RSEP" (recommendation).
The conclusion follows from those two moves, not from any finding about Verisign: the committee "concludes that ICANN's approval of RSEP 2026013 and RSEP 2026014 was appropriate and does not warrant reconsideration", and "recommends that the Board deny Request 26-2" (recommendation). The minutes of the committee's 24 August 2026 meeting record the same recommendation, and what happened next to it: it "will be published and shared with the Requestor, who will have 15 days to submit a rebuttal, if he chooses to do so, before the matter is submitted to the Board for consideration" (BAMC minutes, 24 August 2026).
Fifteen days to rebut an argument that your remedy belongs to somebody else's paperwork. That is the mechanism working exactly as written, and it is also, for a man with one registration paid through the day before this was written, a schedule measured in the wrong unit.
A file that became a container
The next move was administrative and consequential. By notice dated 14 October 2026, ICANN stated that Requests 26-2, 26-5, 26-6, 26-7, 26-9 and 26-10 "will be consolidated (Consolidated Requests) and will all be jointly considered in due course, first by the Board Accountability Mechanisms Committee (BAMC) and then the Board" (ICANN Notice of Consolidation, 14 October 2026). Two weeks later a second notice widened it: Requests 26-2, 26-5, 26-6, 26-7 and 26-9 through 26-13 "are being consolidated (Consolidated Requests) and will all be jointly considered in due course, first by the Board Accountability Mechanisms Committee (BAMC) and then the Board" (ICANN Notice of Consolidation, 28 October 2026). Counting the numbers printed in that second notice gives nine requests; the count is mine, not ICANN's.
Consolidation is a sensible way to handle nine filings about two Verisign proposals, and it changes who carries what. The first-filed request becomes the vehicle; the later ones ride behind it; and the committee's answer to the first one becomes the answer waiting for the rest. Whatever the Board eventually decides will land on nine dossiers at once, and until it does, none of them moves. His argument that a registrant's remedy sits in a registrar contract is now the settled reasoning of a consolidated file rather than the complaint of one man with three names.
The request's own docket page makes the queue visible. It lists the committee recommendation of 24 August 2026, the consolidation notice of 14 October 2026, correspondence from Pablo Rauzy dated 19 October 2026 and supplemental correspondence from Stefan Böck dated 7 November 2026 — and no Board decision (Request 26-2 docket page). Other people are now writing into his file. That is what a container looks like from the outside.
What the Board pages show, and what they do not
The absence claim here is narrow and it stays narrow. ICANN's status table dated 4 September 2026 lists Request 26-2 with the filing date 2 June 2026, a committee recommendation to the Board dated 24 August 2026, and the entry "Board Action: TBD" (2026 Reconsideration Requests Status Update, 4 September 2026). The approved resolutions of the Board's Regular Meeting on 18 October 2026 carry a reconsideration item for Request 26-4 only (approved resolutions, 18 October 2026). The preliminary report of the Board's Regular Meeting on 22 October 2026, held in Bali, records resolutions on an ERP provider renewal, a surplus transfer, a ccNSO policy item and thank-you items, and no reconsideration item at all (preliminary report, 22 October 2026).
ICANN's own Board calendar fills in the rest: a Regular meeting on 18 October, an Organizational and a Regular meeting on 22 October, then nothing but committee business — Audit on 3 November, Governance on 12 November — with a Finance Committee meeting listed as upcoming on 19 November (2026 Board Activities and Meetings). Add the docket page that lists no Board action, and the picture is consistent across five different artefacts produced by the institution itself.
Two limits belong in the same paragraph as the finding. ICANN has published a newer status update, dated 17 November 2026, whose landing page links a 138 KB PDF (status update page, 17 November 2026); the table inside that PDF could not be read here, so nothing in this article is drawn from it. And a written Board consent issued outside the published meetings listing cannot be excluded by reading that listing. What can be said is what the pages say: as of 19 November 2026, 170 days after the 2 June 2026 filing date printed in ICANN's own table, the record reviewed shows no vote on Request 26-2 or on the consolidated .NAME requests. The 170 days and the 83 days between filing and the 24 August recommendation are my arithmetic on printed dates.
A reader is entitled to ask why the missing vote matters when the answer is already written. It matters because of who can alter it. A committee recommendation is advice; the Board is the body that adopts or rejects it, and it is the only body in this chain that can say yes. Until it speaks, the committee's two sentences are the last word available to a registrant, and the last word is that the remedy is somewhere else.
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.






