Summary

  • Verisign's two .NAME discontinuation requests did not match: ICANN's 28 July 2026 letter on the email-forwarding request records a one-year bar against re-registering second-level domains tied to deleted addresses, while its letter on the request that terminates the third-level names themselves records no equivalent bar.
  • Troy Rollo's Reconsideration Request 26-7 quotes that absence in his own words against a registration he says he has held since 30 July 2002 and builds a ranked ladder of remedies; Verisign then told ICANN on 5 November 2026 that it would withdraw both requests, and the protection now in writing lasts only as long as an accredited registrar keeps selling the two legacy services.

Verisign filed RSEP 2026013 on 15 April 2026 under the title "Removal of Third-Level Domain Name Registrations Service", and the operative sentence left nothing to construe: "Upon discontinuation, no new third level domain names will be registered and existing third level domain names will be terminated." (RSEP 2026013) A second request, RSEP 2026014, covered .NAME email forwarding and second-level email addresses, and described what happens to existing customers in the same breath as what happens to new ones (28 July 2026 letter on 2026014).

The letters that were not twins

On 28 July 2026 ICANN wrote to Verisign about each request. The letter on 2026013 records approval on 7 May 2026 and posting on 8 May 2026, tells Verisign it is free to discontinue the service, puts the estate at approximately 22,000 third-level registrations, and sets out 90 days' notice to registrars plus a 30-day reminder (letter on 2026013).

The letter on 2026014 carries a clause the other does not: second-level domains associated with deleted SLD email addresses would be withheld from re-registration for one year (letter on 2026014).

Read side by side, the two letters priced the same risk differently. The service whose discontinuation left a second level apparently free carried a twelve-month lock on that second level. The service that terminates the third-level names themselves — the ones people registered, renewed and printed on their correspondence — carried nothing of the kind.

The sentence Rollo quoted

Rollo did not have to argue this from inference. He quoted the record. His redacted request, dated 18 September 2026 and filed in his own name, states: "No such guarantee to prevent the re-registration of the second-level domain for any period is given in RSEP request 2016013." The digits are the document's own and are preserved here as printed; the request under challenge is 2026013 (Request 26-7).

He then sets out why the gap bites. Third-level registrations currently occupy the second level, so nobody else can register it. Once the third-level names are terminated, a second level whose email forwarding was never in play could be registered immediately, while one tied to discontinued email forwarding would sit out the year. Whoever registers it next controls every name and every email address beneath it. Request 26-7 cites second-level domains carrying many third-level registrations: "tanaka" with 51, "suzuki" with 45.

The registry-wide count in ICANN's letter is a different figure from a different document, and the two are not a fraction of one another.

That mechanism is why the request reads less like a plea and more like a fault report. Rollo says he has held troy.rollo.name since 30 July 2002, that it was sold as renewable for life, and that Verisign fixed 15 February 2027 for termination.

His relief is a ladder: reverse the approval and require Verisign to honour the "for life" promise, "with engineering such as an R-LDH encoding if needed"; failing that, offer the second level securely to the registrant holding the only or all third levels beneath it; failing that, treat the containing second level as permanently unavailable; failing that, build a mechanism for several third-level registrants to agree who takes it.

Four dates for one approval

The record does not agree on when the approvals happened, and the disagreement is not a matter of emphasis. ICANN's 28 July 2026 letters say approval on 7 May 2026 and posting on 8 May 2026. The Ombuds office's substantive evaluation of 31 July 2026 says both requests were approved on 8 May 2026 (Ombuds evaluation). Request 26-7 gives "7 or 8 May 2026, alternatively 28 June 2026". Verisign's letter of 5 November 2026 says ICANN approved the requests on 28 July 2026. Each is reported as printed; none is preferred here.

What the six became

ICANN consolidated Requests 26-2, 26-5, 26-6, 26-7, 26-9 and 26-10 on 14 October 2026 for joint consideration by the Board Accountability Mechanisms Committee and then the Board (notice of consolidation), and expanded the set on 28 October 2026 to take in Requests 26-11 through 26-13 (second notice). The only substantive holding in the file belongs to the earliest of them: on 24 August 2026 BAMC recommended that the Board deny Request 26-2, reasoning that the scope of ICANN's review under the Registry Services Evaluation Policy is limited to security, stability and competition, that ICANN knew about the termination of third-level registrations and the potential registrant impact, and that those impacts fell outside that review (BAMC recommendation; BAMC minutes).

That reasoning is the wall Request 26-7 runs into, and it is worth being exact about where it is written down. The scope statement is published by BAMC, not by the requester. The inspected portions of Request 26-7 contain no verified quotation of, or citation to, the answer given to 26-2.

Then the operator moved

On 5 November 2026 Verisign told ICANN two things. It would "continue to support all EPP transactions related to existing registrations for both services for as long as at least one ICANN-accredited registrar also continues to offer these services at the retail level", and it would withdraw both requests and resubmit replacements that seek discontinuation "only for new third-level registrations and new email-forwarding SLD email addresses" (Verisign letter).

ICANN acknowledged on 9 November 2026: "As requested, we have updated the original submissions to reflect a 'withdrawn' status and noted the Free to Discontinue letters as voided" (ICANN letter). ICANN's RSEP Process table, read on 20 November 2026, lists both requests as Withdrawn and the 28 July 2026 letter on 2026013 as VOIDED (RSEP Process table).

What the docket shows

The page for Request 26-7 identifies the request as dated 18 September 2026, lists attachments, correspondence dated 29 September through 7 November 2026, and the consolidation notice. It records no answer, no BAMC recommendation and no Board decision on the request (Request 26-7 docket). Those are the pages checked on 20 November 2026, not every channel ICANN might use.

What the withdrawal did and did not settle

The clause Rollo quoted has been voided along with the letter that carried it. The one-year bar against re-registering a second level existed in a free-to-discontinue letter; that letter is now marked VOIDED, and the request it approved is marked Withdrawn. The protection that replaced it is a sentence in a letter from the operator, and the sentence carries a condition: it holds for as long as at least one ICANN-accredited registrar keeps offering the two services at retail. That condition rests on registrar commercial decisions, not on a term any registrant can enforce and not on a rule ICANN administers.

Two consequences follow, both checkable. First, the termination date Request 26-7 names — 15 February 2027 — has not been withdrawn by any document read here; what changed is that the requests which set the wind-down in motion are gone, and the operator says replacements will seek discontinuation only for new registrations. Second, Request 26-7 remains on ICANN's docket, consolidated with five others and then with three more, challenging an approval its proponent has since withdrawn. ICANN's 9 November 2026 letter records the withdrawal and the voiding; it does not state that the underlying approvals were formally rescinded.

A reader who wants to test any of this needs three documents and no trust in this article: the letter on 2026014 for the year-long bar, the letter on 2026013 for its absence, and Request 26-7 for the sentence that puts the two next to each other. The corporate record behind the file sits in the ICANN directory entry.