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!

Read offline with no ads or diagram watermarks!
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
1
2
3
Next Page
Name Registration Methods, Administration and Authorities
Next Topic/Section

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

Hierarchical Name Architecture (Hierarchical or Structured Name Space)

In this architecture, while names consist of a sequence of symbols, these symbols are assigned using a specific and clear structure. The name consists of discrete elements that are related to each other usually using hierarchical “parent/child” semantics. There are many naming architectures in various contexts that use this type of hierarchical structure; for example, consider how a large company might set up an organization chart and name the executives and officers in the organization. One hypothetical example of a hierarchical name architecture is illustrated in Figure 233.


Figure 233: Hierarchical Name Architecture (Structured Name Space)

This diagram contains the same devices as Figure 232, but they have been arranged using a hierarchical, structured name architecture. In this case, the organization has chosen to structure its device names first by facility location, and then by department. Each name starts with something like “USA-Service-” or “EU-Mfg-”. This provides immediate benefits by providing local control over device naming without risk of conflicts. If someone named John were hired into the USA sales force, his machine could be named “US-Sales-John” without conflicting with the machine owned by John of the European sales force (“EU-Sales-John”.) The structure also makes it easier to know immediately where a device can be found within the organization.

 


The best-known real world example of a hierarchical name space is the name space of the TCP/IP Domain Name System, which uses text labels separated by periods (“dots”) to form an internal structure. All the names in the system are organized into a structure, and a particular device's place in the structure can be determined by looking at its name. For example, “www.tcpipguide.com” refers to the World Wide Web server for The TCP/IP Guide, which is named under the umbrella of “COMmercial” companies.


Previous Topic/Section
Name System Functions: Name Space, Name Registration and Name Resolution
Previous Page
Pages in Current Topic/Section
1
2
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.