| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Name Registration Methods, Administration and Authorities (Page 1 of 2) It seems obvious that for our name system to be implemented, we need some method of assigning names to each of the devices that will use the system. Just as a name system has a name space that is comparable to an addressing system's address space, it also must implement a set of rules and procedures for assigning names, just as an addressing system assigns addresses. This is called name registration. In general, name registration encompasses the following concepts and tasks:
The complexity of the name registration process depends to a great extent on the size and complexity of the name system as a whole, and in particular the architecture of the name space. In a simple name system using a flat name space, registration is usually accomplished using a single authority. There is no structure, of course, and usually no delegation of authority, so there isn't much to registration. For hierarchical name systems, name registration is tied tightly to the hierarchy used for names. The central authority defines the structure of the hierarchy, and decides how the hierarchy is to be partitioned into subsets that can be independently administered by other authorities. Those authorities may in turn delegate subsets of their name spaces as well, creating a flexible and extensible system. This ability to delegate authority for name registration is one of the most powerful benefits of a hierarchical name space. For example, in the TCP/IP Domain Name System, a central authority is responsible for name registration as a whole; it is in charge of deciding what top-level domains, such as .com, .edu, .info and .uk are allowed to exist. Authority for managing each of these subsets of the worldwide hierarchy is then delegated to other organizations. These organizations continue the process of dividing the hierarchy as they see fit. Eventually each organization is able to decide how it will name its own internal systems independently; for example, IBM can register names in any way it sees fit within the ibm.com name.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||