NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Searchable, convenient, complete TCP/IP information.
The TCP/IP Guide

Google
Web TCP/IP Guide






Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  Name Systems and TCP/IP Name Registration and Name Resolution
           9  Name System Issues, Concepts and Techniques

Previous Topic/Section
Name System Functions: Name Space, Name Registration and Name Resolution
Previous Page
Pages in Current Topic/Section
12
3
Next Page
Name Registration Methods, Administration and Authorities
Next Topic/Section

Name Spaces and Name Architectures (Flat and Hierarchical)
(Page 3 of 3)

Comparing Name Architectures

As we will see in the next two topics, the architecture of the name space is intimately related to how names are registered and managed, and ultimately, how they are resolved as well. A flat name space requires a central authority of some sort to assign names to all devices in the system to ensure uniqueness. A hierarchical name architecture is ideally suited to a more distributed registration scheme that allows many authorities to share in the registration and administrative process.

All of this means that the advantages and disadvantages of each of these architectures are not a great mystery. Flat name spaces have the advantage of simplicity and the ability to create short and easily remembered names, as shown in Figure 232. However, they do not scale well to name systems containing hundreds or thousands of machines, due to the difficulties in ensuring each name is unique. For example, what happens if there are four people named John who all try to name their computers “John’s PC”? Another issue is the overhead needed to centrally manage these names.

In contrast, hierarchical name spaces are more sophisticated and flexible, because they allow names to be assigned using a logical structure. We can name our machines using a hierarchy that reflects our organization’s structure, for example, and give authority to different parts of the organization to manage parts of the name space. As long as each department is named uniquely and that unique department name is part of each machine name, we don’t need to worry about each assigned name being unique across the entire organization, only within the department. Thus we can have four different machines named with their department name and “John”, as Figure 233 demonstrates. The price of this flexibility is the need for longer names and more complexity in name registration and resolution.

Key Concept: The two most common types of name architecture are the flat name space and the hierarchical name space. Names in a flat name space are all peers with no relationship; in a hierarchical architecture, a multi-level structure is used to organize names in a specific way. The flat system is simpler and satisfactory for small networks, while the hierarchical name space is more flexible and powerful, and better-suited to larger networks and internetworks.



Previous Topic/Section
Name System Functions: Name Space, Name Registration and Name Resolution
Previous Page
Pages in Current Topic/Section
12
3
Next Page
Name Registration Methods, Administration and Authorities
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



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.