Idru - Mission Statement-a4-for Site

IDRU the Internationalized Domain Resolution Union MISSION Forthwith, IDRU begins to extend IDN to all societies of the world. We use ‘cross-patching’ – that is, we route to separate roots, for different linguistic scripts – which introduces a distributed root architecture. Control of local Internet futures then devolves to local linguistic communities. Those linguistic communities have opportunity to operate their root truly in the public interest. At the same time, a minimally-sized global team will offer necessary coordination, such as to prevent collisions in name space. Ultimately, IDRU knits a unified super-root, both distributed and coordinated. IDRU serves solely the public interest. HISTORY The technology to enable Internationalized Domain Names (IDN) was pioneered – innovated and implemented – twelve years ago by teams led by Tan, Tin Wee (Prof.), and Subbiah, S. (Prof.), both from Singapore. To vet it, all the prominent Internet authorities from a 10-nation region in Asia ran the new IDN through a test bed. At the time, this IDN was publicly available to the prevailing global authority; that body rejected it. Since that time, this technology became the basis for the present IETF IDNA standard for IDN, which is used by all – including now IDRU. Most of the world’s populace use non-Roman scripts. Without IDN they are blocked from Internet access. As far back as ten years ago, the need to implement IDN was compelling. When the prevailing authority failed to meet this most basic need over some years – so, disenfranchising billions of users – individual societies began to adopt IDN, on their own. Presently these are islands of IDN around the world. While delays from the prevailing authority continue, now is time to connect the islands. Now we begin to make IDN available to all societies. A DISTRIBUTED ROOT ARCHITECTURE The IDRU design for IDN – when applied across all the world’s scripts – produces a new architecture. That architecture brings key advantages; it also mandates management imperatives. In IDRU IDN, a browser’s request for a page is parsed. If a browser in, for instance, China seeks a domain in Chinese, the local root resolves it. If the domain request is not for Chinese, the Chinese root passes the request off to the appropriate root. When applied for all script groups, the root architecture becomes ‘distributed.’ Roots for

IDRU - page 2

different scripts either resolve a native incoming request or pass that request to the root that serves the appropriate script. The mechanical steps required to implement the distributed root are entirely trivial: ‘cross-patching.’ Software in the root for each script is patched to recognize, then route, requests for the other roots serving other scripts. The actual patching process is not likely to take more than ten minutes per patch for a given root – there is no mechanical impediment to implementation. ADVANTAGES AND MANDATES Technically, a distributed root is much less complex than a unitary root. The attempt, by others, to create one omnibus root introduces multiplying problems and concerns for stability. By contrast, a distributed root simply applies what is now long-tested and stable root technology, script by script.* More importantly, local language communities will be in charge of their own future on the Internet. A handful of Western, incumbent registries/registrars will not control the destiny and price of foreign domains. The management of each script root will have the opportunity to deliver a service that is demonstrably in the public interest – not corrupted to the interests of a few. At the same time, while devolution of the root to script groups decentralizes control, some global coordination will remain. A UNIFIED SUPER-ROOT We will also establish a minimally-sized central coordinating team. Its watchword will be a respectful hearing for all competing views, not decisions to favor a few. Coordination will include • •

Preventing collisions in namespace Security for the roots

Participants in IDRU will discuss prepared policy drafts, to seek agreed positions. Overall then, IDRU creates a unified super-root. That which should be distributed – both for good governance and for technical reasons – will be dealt locally. That which properly requires coordination will provide assurance of stability, around the world. IDRU IDRU both distributes and coordinates, judiciously, to offer a unified system that also respects local destinies – IDRU is a public service long sought around the world. *

Bona fides – does IDRU IDN work? • Our IDN technology is proven in multi-year implementations with about 400 million users. Our IDN was the inspiration for, then of course finalized to comply with, IETF RFC 3454, IDNA – and is • now the basis for IDRU.