Two Thousand Words Hold the Namespace. Since 1994.
Jon Postel's 1994 memo on domain delegation is neither law nor standard. Yet, it still decides how over 300 country endings, from .de to .io, live and die. Its secret is what it leaves out.
No signature on it.
No court behind it.
It says of itself: not a standard.
This text holds more than three hundred country endings today. One of them is where your company lives.
In March 1994, Jon Postel published a memo.
“Domain Name System Structure and Delegation.” Just over two thousand words. Filed as Informational — “This memo does not specify an Internet standard of any kind,” it says of itself, in its own opening.
What it says is stranger than what it is. The manager of a delegated domain is a trustee — for the nation and for the global internet community at once. Then the sentence the whole document turns on: “Concerns about ‘rights’ and ‘ownership’ of domains are inappropriate. It is appropriate to be concerned about ‘responsibilities’ and ‘service’ to the community.” The measure of a manager is set in four words: “equitable, just, honest, and competent.” And the one explosive question — what counts as a country — Postel refused to answer. “The IANA is not in the business of deciding what is and what is not a country.” He handed it to a list maintained elsewhere: ISO 3166.
The memo did not invent a practice. It wrote down one already running. Hungary’s .hu had been delegated on 7 November 1990 — nearly four years before the text that would supposedly govern it. Half the country codes on the internet predate their own rulebook.
Postel was the RFC editor, the “Numbers Czar,” and, in person, the IANA itself — the Internet Assigned Numbers Authority, the office that parceled out the internet’s names and numbers. When he died in October 1998, Vint Cerf’s memorial opened: “Jon, our beloved IANA, is gone.” He had, in his last weeks, completed the incorporation of a successor to carry the function — the body we now call ICANN.
One more line from the same memo, because it inoculates against reading this as scripture. In 1994 it predicted: “It is extremely unlikely that any other TLDs will be created.” After the 2012 round, more than 1,200 new generic endings entered the root zone.
The document failed as a prophecy and held as a constitution — because it was never kept for its prophecies.
The most durable legal construct on the internet is a text with no legal force.
Start with why it holds, because the answer is counterintuitive. Responsibility, not right. The trustee construction — as the ccNSO’s own later reading of it puts it — describes a duty of service to the community, not a legal relationship between the manager and the domain. Where the text hands out no right, there is nothing in it to sue over. No contract to breach. No property to claim back.
The delicate decisions are all pushed off the document. What counts as a country goes to ISO, a standards committee in Geneva. Who is a fit manager rests on the consent of the “significantly interested parties” — local consensus, in plainer words. Questions of equity, justice, and honesty are settled locally, under local law; the interpretation working group was explicit that IANA does not step into those.
And everything closes on consent. A transfer needs both the old and the new manager to agree. A revocation is a last resort, reserved for persistent failure of duty. The resting state of the whole system: no one can take anything from anyone by their own hand.
I read it as an operator, not a lawyer. The root zone is a register of responsibility. The IANA table does not list owners; it lists keepers. And the contracts outsiders assume must be there mostly are not: the Governmental Advisory Committee’s own 2005 principles say in writing that they are “not intended to be binding,” that they apply voluntarily, and that a registry’s refusal to adopt them cannot be held against it. A large part of the country-code world stands under no binding contract with ICANN at all.
The text allocates no rights, only responsibilities — so there is nothing in it to sue over.
Every attempt to replace it failed
In 1999 ICANN issued its own update, ICP-1. The ccNSO’s later analysis found it carried policy changes the ICANN Board had never approved by resolution — and that the country-code community had never accepted it. The interpretation group set it aside. In 2001 most country-code registries adopted RFC 1591 itself as their governing policy.
Then came the Framework of Interpretation. Three years of work, 2011 to 2014. Its charter forbade it from writing new rules; it could only interpret the old ones. The product of three years was a reading of the original text, not a revision of it.
The one real addition that ever cleared the full policy process is the 2022 retirement rule. Even that schedules only the death: a deletion from ISO 3166-1 triggers a Notice of Removal, then five years in the root, extendable by five more. It never touched the trust construction underneath.
And that rule was forced into being by a single case. As .yu was being wound down, the incoming registry itself — RNIDS — asked for clear and transparent rules, and an ICANN Board resolution of 30 September 2009 handed the question to the ccNSO to study. A case made the rule, twelve years on.
The text at work
.yu is the orderly death. Delegated in 1989, run first from Ljubljana, then carried after the breakup by YUNET in Belgrade. ISO changed the code from YU to CS in 2003; after Montenegro’s 2006 referendum, the September 2006 revision dropped CS and added RS and ME. On 11 September 2007 the ICANN Board delegated .rs to RNIDS and made the wind-down of .yu a condition; after one extension, .yu left the root zone on 1 April 2010. The numbers carry the drama on their own: Google indexed 69 million .yu pages in 2007, and 6.2 million by mid-2009; of 32,772 registered names, 4,266 were left. An entire country’s namespace went dark on a schedule, over two and a half years.
.su is the exception now meeting its first real test. Delegated on 19 September 1990, fifteen months before the Soviet Union ceased to exist. The code left the standard in 1992; the extension outlived its empire by more than three decades. According to press reports, the PTI — the body that now operates the IANA function — notified the manager, ROSNIIROS, in a private letter dated 6 February 2025 of a wind-down planned through 2030. No public announcement has followed, and 2030 is a plan, not a settled date.
.nu is where the trust construction meets the edge of law. Niue’s government sued in Sweden from 2018; the Södertörn district court in March 2024, and then the Svea Court of Appeal on 5 June 2025, rejected the damages claim. The district court held that the foundation had followed the existing framework and had no duty to seek Niue’s permission; the appeal court upheld the outcome. By the foundation’s account, the delegation itself rests with a separate body, IUSN. Read as my own structural inference: RFC 1591’s community-trustee idea was never enforceable before a Swedish court. The lawsuit over the trust construction was decided not by the rules of trust, but by local law — exactly as Postel’s text had arranged the world.
.io is the next test, still open. The Chagos sovereignty transfer was signed in May 2025; as these lines are written the IO code remains in the standard and the delegation is unchanged. If ISO ever removes it, the five-plus-five removal schedule begins. Earlier name changes ran the same way — Zaire became CD in 1997, East Timor became TL in 2002 — a new country, a new ending.
What this means if you decide
If your primary domain name lives on a country code, the top link in your chain of title is neither property nor contract. It is a trust mandate. There is no ownership behind it that a court protects, and no service contract you could cancel and re-sign somewhere else. Most corporate risk maps do not carry that line at all.
So three questions belong on the table when you choose an extension, or when you next audit the portfolio you already hold. Who runs the ending, and what is that body’s relationship to its own local community and government. Under what legal order the manager itself operates — which is the jurisdiction question a name inherits the day it is registered. And what happens if the country code’s status changes in the standard — because there is now a schedule for exactly that, and five years, plus five, is precisely as long as it was long enough for at .yu: time for an orderly move, for whoever starts in time.
The root zone records everything except ownership.
It does not note who owns an extension. It notes who answers for it.
That is the whole legacy of Postel’s two thousand words: at the very top of the internet, the concept of property does not exist. There is only service.
Magyar változat: [zona.hu/ketezer-szo-tartja-egyben-a-nevteret-1994-ota/]