Summary
- The NRO notice prints the Community Forum deadline as "the 30th day after" 11 May 2026 and dates it 9 June 2026 — 29 days later, unless the anchor date counts as day one.
- The follow-up notice prints a 21-day Decision Period from 11 June to 2 July 2026 — exactly 21 days only if the anchor does not count — and labels that deadline PST while converting it as daylight time.
Take a calendar to the Empowered Community's approval of the Fundamental Bylaws amendments to Articles 17 and 18, and it returns two answers.
The Number Resource Organization's notice to the ASO community — a page dated 12 May 2026, last modified 12/05/2026 — prints that the ICANN Board approved the amendments on 3 May 2026 and fixes the Approval Action Board Notification Date at 11 May 2026. It then prints the outer edge of the Community Forum Period: "at 11:59 pm PDT on the 30th day after that date, 9 June 2026, or during the next scheduled ICANN Public Meeting, ICANN86, which will take place from 8–11 June 2026" (NRO notice).
From 11 May to 9 June 2026 is 29 calendar days. The 30th day after 11 May is 10 June. The printed date is the 30th day only if 11 May itself is day one — if the period counts inclusively from its anchor.
Now the second stage. The NRO's follow-up notice, dated 12 June 2026, prints that after the Forum concluded a new 21-day Approval Action Decision Period began and "will expire at 23:59 PST on Thursday, 2 July 2026. (3 July at 6:59 UTC)" (follow-up notice). The Forum sat on 11 June 2026, and the Empowered Community Administration ran the decision period from the Forum Period's 23:59 CEST expiry that day (EC Administration message).
From 11 June to 2 July 2026 is exactly 21 days, with the anchor excluded. Under the convention the first stage appears to use, a 21-day period running from 11 June would close on 1 July.
That subtraction is mine, not any publisher's. No reviewed page prints a counting rule, and no reviewed page acknowledges that one is needed.
The label that disagrees with its own conversion
23:59 in a UTC-8 zone is 07:59 UTC the next morning; 23:59 in a UTC-7 zone is 06:59 UTC. The follow-up notice labels its deadline PST and converts it to 6:59 UTC — the daylight-time answer, printed inside the standard-time label. The RIPE NCC's retrospective page of 7 July 2026 repeats "23:59 PST on Thursday, 2 July 2026" with no conversion and no recomputation (RIPE NCC). The EC Administration's May message prints the same PST label against the same July date.
Three publishers handle these dates: the NRO sets them, the EC Administration schedules the forum and runs the clock, and RIPE NCC republishes the result. None of the three shows the arithmetic; each shows the date. Repetition is not verification, and here it is not even independent — the same "PST" label travels from the May message to the June notice to the July retrospective without anyone asking what it converts to.
What the anchor is, and is not
The clock does not start from the Board's decision. The Board approved on 3 May; the notification date is 11 May; the Forum Period runs from the notification date. In the same EC Administration thread sits an earlier message printing delivery of the Secretary's Notice on 08 May — three days before the notification date that starts the 30-day count.
"Approval Action Board Notification Date" is printed with a value and defined in no reviewed page. That is the part of the clock a participant, a reader or an auditor cannot supply from outside: whether the anchor is the Secretary's delivery, the notice's publication, or a date the publisher selects. The count begins at a term, and the term is the gap.
There is a second date in the same file. The follow-up describes itself as a follow-up to a notice published on 29 May 2026. The notice page it belongs to is dated 12 May 2026. Seventeen days apart, both printed, neither reconciled.
The annex that would settle it
The instrument that should settle both questions is Annex D of the ICANN Bylaws, and it was not obtained in readable form in this review. ICANN's Bylaws page as retrieved identifies the Bylaws as amended 3 July 2026, and its table of contents lists "ANNEX D: EC MECHANISM" — but the retrieved text ended at Article 1 (ICANN Bylaws).
The only reproduction of the annex in this record is a GNSO-hosted PDF that did not yield readable text to the retrieval adapter. Its search excerpt attributes the 30th-day Forum Period to Section 1.3(c) and the 21st-day Decision Period to Section 1.4(a), and renders the operative day count in a form no typesetter would have set — "30 1 th day" — a scanning artifact sitting inside the number itself (GNSO reproduction).
ICANN's plain-language handbook on Empowered Community approval actions describes a 30-day community forum phase and a 21-day decision phase, both ending at 11:59 pm local time at ICANN's principal office, with a participant that does not communicate treated as abstaining (handbook). It summarises a procedure, and it rounds. A rounding summary cannot settle a counting rule, and a standard-time label cannot settle a conversion.
What the record does not say
Nothing here alleges that the approval was contested, that a participant missed a deadline, or that any period was miscalculated. No reviewed document says any of those things. What the record does print is the rule that gives the clock its teeth: the EC Administration states that a Decisional Participant which does not inform it of support or objection by the deadline "shall be deemed to have abstained", and that approval requires at least 3 Decisional Participants supporting and no more than 1 objecting. RIPE NCC records that the NRO Executive Council determined the ASO would support the Approval Action.
The arithmetic therefore has a consequence that is not arithmetic. Silence is not a neutral non-event; the publisher's own rule counts it as an abstention, in a decision where one objection is tolerated and three supporters are the floor.
Why one day matters
Counting is how a supermajority gate becomes auditable. A threshold with a printed denominator can be checked by anyone who can count, and that is the whole of its claim to legitimacy. A threshold with a printed clock can be checked only by subtraction, and subtraction requires the convention: does the anchor count as day one, or not?
The reviewed record gives opposite answers at its two stages and prints neither rule. One stage reconciles inclusively, the other exclusively. Until a counting rule is published and "Approval Action Board Notification Date" is defined, a participant who wants to be safe must act on the earlier of two readings — 1 July rather than 2 July — and a reader cannot tell whether the published dates were computed or inherited.
The fix is one sentence in an annex: state whether the anchor counts as day one. Everything else in this file — each publisher, each date, each period — follows from whether that sentence exists. The notice itself is indexed in BTW's directory (record).
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.






