Computer network naming scheme: Difference between revisions
Line 3: | Line 3: | ||
==Naming schemes in computing== |
==Naming schemes in computing== |
||
Large networks often use a systematic naming scheme, such as using a location (e.g. a department) plus a purpose to generate a name for a computer. |
Large networks often use a systematic naming scheme, such as using a location (e.g. a department) plus a purpose to generate a name for a computer. |
||
For example, a web server in NY may be called "nyc-www-04.xyz.net". |
|||
⚫ | |||
Common Network Naming Convention: |
|||
⚫ | Network naming can be hierarchical in nature, such as the [[Internet]]'s [[Domain Name System]]. Indeed, the Internet employs several universally applicable naming methods: Uniform Resource Names ([[Uniform Resource Name |URN]]), Uniform Resource Locators ([[Uniform Resource Locator|URL]]), and Uniform Resource Identifiers ([[Uniform Resource Identifier |URI]]). For the technically inclined, the following article is worth perusing: http://www.w3.org/TR/uri-clarification/. |
||
(city-function-number.domain.name) |
|||
The choice of names may be limited by a length limitation (such as 15 character flat name space for [[NetBIOS]]), or may be limited by a character set limitation. |
|||
[[List_of_airports_by_IATA_code|City Code IATA]] |
|||
nyc-pdc-201.xyz.net |
|||
lon-rtr-103.xyz.net |
|||
hkg-san-541.xyz.net |
|||
mos-gpc-999.xyz.net |
|||
If you have many offices in a city distinguish the offices designate |
|||
100-200 ABC location |
|||
200-300 CDE location |
|||
⚫ | |||
⚫ | Network naming can be hierarchical in nature, such as the [[Internet]]'s [[Domain Name System]]. Indeed, the Internet employs several universally applicable naming methods: Uniform Resource Names ([[Uniform Resource Name |URN]]), Uniform Resource Locators ([[Uniform Resource Locator|URL]]), and Uniform Resource Identifiers ([[Uniform Resource Identifier |URI]]). For the technically inclined, the following article is worth perusing: http://www.w3.org/TR/uri-clarification/. |
||
== See also == |
== See also == |
Revision as of 07:38, 13 September 2011
A naming scheme is a plan for naming objects. In computing, naming schemes are often used for objects connected into computer networks.
Naming schemes in computing
Large networks often use a systematic naming scheme, such as using a location (e.g. a department) plus a purpose to generate a name for a computer.
For example, a web server in NY may be called "nyc-www-04.xyz.net".
Common Network Naming Convention:
(city-function-number.domain.name) City Code IATA nyc-pdc-201.xyz.net lon-rtr-103.xyz.net hkg-san-541.xyz.net mos-gpc-999.xyz.net
If you have many offices in a city distinguish the offices designate 100-200 ABC location 200-300 CDE location
However, smaller networks will frequently use a more personalized naming scheme to keep track of the many hosts. Popular naming schemes include trees, planets, rocks, etc. (aniquated)
Network naming can be hierarchical in nature, such as the Internet's Domain Name System. Indeed, the Internet employs several universally applicable naming methods: Uniform Resource Names (URN), Uniform Resource Locators (URL), and Uniform Resource Identifiers (URI). For the technically inclined, the following article is worth perusing: http://www.w3.org/TR/uri-clarification/.
See also
External links
- RFC 1178 - "Choosing a Name for Your Computer"
- RFC 2100 - "The Naming of Hosts"
- Naming schemes