Multi-root domain system

Introduction

Current root domain system is controlled by single organization ICANN. This organization decides which top-level domains will exist and sell rights for those domains to other organizations which serve as registrars for end users. ICANN is US based and can decide about blocking of particular domains which are against US laws. It is central authority and has power to censor selected domains. This centralized system is not problem just for countries with different policies but will be also problematic for inter-planetary domain system where managing one centralized domain system across multiple planets or solar systems would be too problematic due long delays for transfer of information.

Requirements

• Root namespaces need to be managed decentralized way (For censor resistance and inter-planetary independence)
• Collisions in registered namespaces should expected and resolution process have to be defined
• Allow user and network providers to define their own namespaces
• Support public and private namespaces
• Free of charge domains should be possible
• Namespaces should be optional

Root namespaces

URL format needs to be extended to support additional optional domain namespace identification:

scheme:[//[user[:password]@]host[^namespace][:port]][/path][?query][#fragment]

Examples:

• http://www.domain.org^earth/
• http://www.search.com^moon/
• http://www.public.gov^mars/
• http://ds74gfd374gds4gki^onion/
• http://www.something.net^opennic/
• https://www.domain.com^icann:443/
• http://display.system.config^localhost/
• http://router12.area2.nodes^localnet/
• http://mydomain.global^virtualnetwork/

By default each network device is located in one of existing namespace and should have set default namespace. Default namespace would be used to determine to which root servers should network node connect. So in case of mars namespace any domain without namespace identification should be considered as mars namespace. To address earth namespace user needs to specify earth namespace explicitly.

• Some of names should be reserved for special usage. For example for private non-public domain names.
• From HTML page if page links domain without namespace then it should refer to same namespace.

Registry

For each namespace set of root servers needs to be defined. There should be possible to have several root namespace registries with different approach to manage registered names. It is expected that such registries would have several namespaces same. But there should be method designed to decide which namespaces are legitimate and which are registered by domain speculators.

Names uniqueness

Registration of names for root namespace need to be free of charge. Currently high price is charged for domains assignments and this high price is partially justified by need to limit number of registered names to avoid high abuse of registry by domain speculators. But there should be another way to solve this problem. For example by checking if domain is really used. As there should be multiple root namespace registries then consequently system should iterate to one registry with best process of managing names. There should be easy way to switch to different registry.