Summary

  • Mark Atwood's Reconsideration Request 26-14, dated 5 November 2026, challenges two Verisign registry-service approvals affecting .NAME and concedes in its own text that it arrived outside a thirty-day window.
  • ICANN's docket page for the request lists the request and Exhibits A and B and no disposition, while the Board's 18 October 2026 denial of Request 26-4 shows what a closed entry on the same docket looks like.

The page carries a title and a two-item list. "Request 26-14: Mark Atwood" is followed by Request 26-14, dated 5 November 2026, and Exhibits A and B, also dated 5 November 2026, on the docket page itself. That is the entire index. A docket is not a diary; it exists to show what has been posted against a file, and what has been posted against this one is the filing plus its evidence.

The filing is a redacted PDF dated 5 November 2026 (Request 26-14), published under Mark Atwood's name with his contact details removed. By its own text it challenges ICANN staff approval of two Verisign registry-service evaluations: RSEP 2026013, concerning discontinuation of third-level .NAME registrations, and RSEP 2026014, concerning discontinuation of .NAME email forwarding.

The harm is stated in the first person. "I have held mark.atwood.name continuously since December 2004 -- nearly 22 years," reads the excerpt printed for this article. The request describes the domain and its email address as his primary digital identity, tied to banking, healthcare, government and two-factor recovery accounts. That is the filer's own account of what is at stake, and it is the reason the rest of the document is worth reading closely.

Then comes the sentence that makes this a different kind of brief. The request's timeliness section states that it was filed more than thirty days after the formal approval it challenges, and asks ICANN to accept it on lack-of-notice and good-faith grounds. Two things need saying plainly beside that number. First, the thirty-day period is the request's own characterisation of the window, not a clause read for this article: the Bylaws text that sets any reconsideration deadline is not in the record examined here.

Second, whether such a window can be waived by the body that sets it, or instead closes the matter, is precisely what the unread clause would settle. A deadline that ends a matter and a window a body may open are two different instruments, and this article does not pretend to know which one it is looking at.

The relief tells you which one the filer thinks he is facing. He asks for acceptance for consolidation with pending Requests 26-2, 26-5, 26-6, 26-7 and 26-8; reconsideration of the two RSEP approvals; priority registration and reservation protections for affected registrants; and a recommendation for policy review of registrant security harm in the RSEP process. The request also states that the consolidated matters remain pending before the Board. He is not asserting a right. He is asking for a discretion, and asking to be folded into a set that is still open.

Now the contrast that keeps the piece honest. On 18 October 2026 the Board closed a file in writing: "Resolved (2026.10.18.01), the Board adopts the BAMC Recommendation on Reconsideration Request 26-4 and denies Reconsideration Request 26-4," the approved resolutions record. The same resolution determined that future reconsideration requests relating to Nameshop Application ID 1-1873-71868 would be deemed frivolous under Article 4, Section 4.2(k) of the Bylaws — a clause named here as the resolution cites it, not read for this article and not paraphrased. Request 26-4 was submitted by Sivasubramanian Muthusamy on behalf of Nameshop and concerned termination of the .IDN application and alleged Board inaction, according to the reported summary of that record. Two postures, one docket: one filed in a person's own name, one filed on a company's behalf.

So the contrast is not a mood. The machinery demonstrably produces a dated, numbered, public ending, and it did so six weeks before Atwood filed. Which makes the 26-14 page legible in a specific way: the page does not show an ending, and the page is dated 16 November 2026 — eleven days after the filing it indexes.

As it stood on 19 November 2026, it carried no BAMC recommendation, no Ombuds evaluation and no Board action entry. That is a statement about one page on one day. It is not a statement about the world, and it is not a claim that nothing happened.

ICANN has published a 2026 Reconsideration Requests Status Update dated 17 November 2026 (status update), and its landing page links a PDF of roughly 138 KB. The table inside that PDF was not readable in the copy examined for this article, so no entry from it is quoted, dated or attributed here. That is a limit of the copy. If the table carries a disposition for this request, the finding below changes and should change.

The directory settles nothing either. ICANN's central reconsideration index lists Request 26-14 under Mark Atwood and Request 26-4 under Sivasubramanian Muthusamy, and links the status update. It is a register of requests, not a determination of any of them.

This desk read Request 26-2 and the two worked responses applying the consolidated recommendation in a 19 November 2026 briefing, and left one gap open: the 17 November status table.

This article walks at the same table through a different door — a new named filer who concedes his own lateness and asks to be folded into the set that is still open.

What remains is a distinction between logged and weighed. The reconsideration route gives a registrant a form, a docket and a discretionary door. The published record shows the filing; the institution's own practice shows it can show more when it decides to. Until the docket prints three things — a receipt, an acceptance decision and a disposition — a stranger cannot tell which of the two happened. Neither, on this record, can the filer.

The five records behind this article were read as provider-reported excerpts rather than as documents inspected line by line.

Layout, letterhead, pagination and signature blocks are unverified, and that caveat bites hardest on the request, the only one of the five whose argument lives inside the document rather than in its index line.

Nothing here alleges that a request was wrongly accepted or wrongly refused, that any staff registry-service approval was proper or improper, that a registrant's domain was taken, that a filing period was misapplied, or anything about the conduct of any director, officer, employee or filer that these documents do not state themselves.

A docket is the institution's own instrument and it is free to be complete. For Request 26-14, as of 19 November 2026, it is not. The filer has already done the harder thing: he conceded the lateness in writing, set out nearly twenty-two years of dependent identity, and asked anyway. ICANN's directory entry carries the institutional identifiers used across this desk's coverage.