Primary Domain
Internet Governance and Routing
Within the Primary Domain facet, Internet Governance and Routing intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
ICANN
Combining Marks Do Not Satisfy ICANN's Minimum of Two Category-L Code Points for an IDN
ICANN's 2026 IDN rule requires at least two Unicode General Category L code points and excludes Category M code points when determining whether the label is a single character.
ICANN
Language Meaning Does Not Decide Whether an IDN String Passes ICANN's RZ-LGR
ICANN's 2026 Guidebook treats an IDN as a technical DNS identifier before it treats the label as a word. Linguistic meaning and root-zone validity answer different questions.
ICANN
An Unsupported Script Cannot Enter ICANN's 2026 Round Through a Validation Challenge
ICANN's 2026 Applicant Guidebook draws a hard boundary between correcting a validation implementation error and adding support for a script that the applicable Root Zone Label Generation Rules do not contain.
CASE FILE
The Parody Began After the Address Bar: PETA v Doughney
A joke can be obvious on a page and absent from the address that brought the reader there. That timing problem sat at the centre of *PETA v Doughney*. Michael Doughney said his “People Eating Tasty Animals” site parodied People for the Ethical Treatment of Animals. The Fourth…
ICANN
An IDN Variant Depends on Its Primary String, but Not Every Variant Disqualification Ends the Application
ICANN's 2026 Applicant Guidebook gives the primary IDN string and its requested variants different disqualification consequences. That asymmetry matters when teams map application risk.
ICANN
ICANN’s Replacement String Option Expires After 14 Days
Under the 2026 Applicant Guidebook, a replacement string is designated with the application, elected during a 14-day period after Reveal Day, and cannot be reversed once the switch is made.
ICANN
Winning an ICANN Auction Does Not Guarantee Delegation
An auction result decides which directly contending application may advance. It does not itself award a delegated gTLD.
ICANN
Reveal Day Does Not Finalize an ICANN Contention Set
Reveal Day starts the contention record; it does not freeze it.
ICANN
Private Deals Cannot Resolve an ICANN Contention Set
From Reveal Day, applicants in the same contention set enter a communication boundary that covers private talks, public disclosures and indirect intermediaries.
ICANN
A .Brand String Change Can Add Words, But Cannot Create or Expand Contention
ICANN’s 2026 Round gives a qualifying .Brand applicant a narrow way to change a string when contention arises. It is not a general opportunity to rename an application.
ICANN
A Material Change to Public Application Content Opens 30 Days of Comment, Not Automatic Approval
When ICANN finds that a requested change materially affects public application content, the request enters a 30-day comment process but has not crossed the approval line.
Number Resource Society
An RPKI Cache Serial Is Not a Freshness Timestamp
Two RPKI caches can report perfectly accurate serial numbers and still tell an operator nothing about which cache holds newer global data. RFC 8210 scopes a serial to one cache session and protocol version. Treating the larger number as the fresher view manufactures a chronology…
ICANN
GAC Consensus Advice Starts a 21-Day Response Record, Not an Automatic Board Outcome
Formal GAC Consensus Advice changes the applicant's procedural position, but it does not itself supply the ICANN Board's decision.
ICANN
A GAC Early Warning Is a Signal, Not a Veto: The Applicant's Response Record
The 2026 Round gives a government representative a way to flag a concern without turning that notice into an automatic decision on the application.
ICANN
A Singular/Plural Risk Does Not Self-Execute: The 30-Day ICANN Notification Record
In the 2026 Round, a grammatical pair becomes a program decision only through a timely notification backed by verifiable dictionary evidence.
ICANN
An ICANN Objection Appeal Is Not a Retrial: What the Clearly Erroneous Standard Can Change
The 2026 Round appeal process reviews an identified objection error; it does not reopen the entire dispute from the beginning.
ICANN
Community Objection Is Not CPE: Two ICANN Procedures That Test Different Claims
The word “community” appears in both names, but the procedures ask different questions, involve different parties and create different records.
ICANN
What Evidence Record Should a Community Priority Evaluation Applicant Build?
A criterion-linked record is more useful than a pile of endorsements.
CASE FILE
Sixty Names Were Defendants; the Statute Still Defined the Claim: Harrods v Sixty Internet Domain Names
The caption did something unusual: it named sixty domain names as defendants. That procedural choice made a dispute over the Harrods name look, for a moment, like a dispute over things rather than people. The Fourth Circuit’s answer was narrower. The names could be before the…
ICANN
ICANN Checks Every Applied-for String for Geographic Meaning. What Must a Support Letter Prove?
ICANN’s 2026 Round checks every applied-for string for geographic meaning. Applicants need an authoritative, authentic and scope-correct support record—not merely a letter.