Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
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.
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.
|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!|
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.