Computer network naming scheme: Difference between revisions
Content deleted Content added
OK, then, it's off to AfD |
Wikipedia:Articles for deletion/Computer network naming scheme closed as no consensus (XFDcloser) |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<!-- Please do not remove or change this AfD message until the discussion has been closed. --> |
|||
{{Article for deletion/dated|page=Computer network naming scheme|timestamp=20240427233726|year=2024|month=April|day=27|substed=yes}} |
|||
<!-- Once discussion is closed, please place on talk page: {{Old AfD multi|page=Computer network naming scheme|date=27 April 2024|result='''keep'''}} --> |
|||
<!-- End of AfD message, feel free to edit beyond this point --> |
|||
{{Refimprove|date=August 2018}} |
{{Refimprove|date=August 2018}} |
||
In [[computing]], '''naming |
In [[computing]], a '''naming scheme''' is a system for assigning and managing names of objects connected into [[computer network]]s. It typically consists of a [[namespace]] and processes for assigning, storing, and [[Name resolution (computer systems)|resolving]] names. |
||
==Naming schemes in computing== |
==Naming schemes in computing== |
||
Server naming is a common tradition. It makes it more convenient to refer to a machine by name than by its [[IP address]]. |
Server naming is a common tradition. It makes it more convenient to refer to a machine by name than by its [[IP address]]. |
||
| ⚫ | |||
The [[Central Intelligence Agency|CIA]] named their servers after states.<ref>{{cite web|url=http://www.itworld.com/offbeat/61750/would-server-any-other-name-be-functional|title=Would a server by any other name be as functional?|first=Josh|last=Fruhlinger|website=Itworld.com|accessdate=14 August 2018|archive-url=https://web.archive.org/web/20120411180054/http://www.itworld.com/offbeat/61750/would-server-any-other-name-be-functional|archive-date=2012-04-11}}</ref> |
|||
Naming systems have several other characteristics. The entities that assign and manage names can be [[Distributed computing|distributed]], [[centralized]], or [[hierarchical]]. Names can be human-readable or not human-readable.<ref>{{Cite journal |last1=Ahmed |first1=R. |last2=Boutaba |first2=R. |last3=Cuervo |first3=F. |last4=Iraqi |first4=Y. |last5=Tianshu Li |last6=Limam |first6=N. |last7=Jin Xiao |last8=Ziembicki |first8=J. |date=Third Quarter 2005 |title=Service naming in large-scale and multi-domain networks |url=https://ieeexplore.ieee.org/document/1610549 |journal=IEEE Communications Surveys & Tutorials |language=en |volume=7 |issue=3 |pages=38–54 |doi=10.1109/COMST.2005.1610549 |issn=1553-877X}}</ref> |
|||
Server names may be named by their role or follow a common theme such as colors, countries, cities, planets, chemical element, scientists, etc. If servers are in multiple different geographical locations they may be named by closest airport code. |
|||
Such as web-01, web-02, web-03, mail-01, db-01, db-02. |
|||
Airport code example: |
|||
lax-001 |
|||
lax-002 |
|||
arn-001 |
|||
City-State-Nation example: |
|||
3-character unique number |
|||
2-character production/development classifier |
|||
3-character city ID |
|||
2-character state/province/region ID |
|||
2-character nation ID |
|||
Thus, a production server in Minneapolis, Minnesota would be nnn.ps.min.mn.us.example.com, or a development server in Vancouver, BC, would be nnn.ds.van.bc.ca.example.com. |
|||
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". |
|||
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. |
|||
| ⚫ | |||
== See also == |
== See also == |
||
| Line 46: | Line 18: | ||
== External links == |
== External links == |
||
* {{IETF RFC|1178}} - "Choosing a Name for Your Computer" |
|||
* {{IETF RFC|2100}} - "The Naming of Hosts" |
* {{IETF RFC|2100}} - "The Naming of Hosts" |
||
* [http://namingschemes.com/ Naming schemes] |
|||
* [http://support.microsoft.com/kb/909264 Naming conventions in Active Directory] |
* [http://support.microsoft.com/kb/909264 Naming conventions in Active Directory] |
||
* [https://www.w3.org/TR/uri-clarification/ URIs, URLs, and URNs: Clarifications and Recommendations 1.0] |
* [https://www.w3.org/TR/uri-clarification/ URIs, URLs, and URNs: Clarifications and Recommendations 1.0] |
||
Latest revision as of 18:24, 21 May 2024
 | This article needs additional citations for verification. (August 2018) |
In computing, a naming scheme is a system for assigning and managing names of objects connected into computer networks. It typically consists of a namespace and processes for assigning, storing, and resolving names.
Naming schemes in computing[edit]
Server naming is a common tradition. It makes it more convenient to refer to a machine by name than by its IP address.
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 name (URN), uniform resource locator (URL), and uniform resource identifier (URI).
Naming systems have several other characteristics. The entities that assign and manage names can be distributed, centralized, or hierarchical. Names can be human-readable or not human-readable.[1]
See also[edit]
References[edit]
- ^ Ahmed, R.; Boutaba, R.; Cuervo, F.; Iraqi, Y.; Tianshu Li; Limam, N.; Jin Xiao; Ziembicki, J. (Third Quarter 2005). "Service naming in large-scale and multi-domain networks". IEEE Communications Surveys & Tutorials. 7 (3): 38–54. doi:10.1109/COMST.2005.1610549. ISSN 1553-877X.
External links[edit]
- RFC 2100 - "The Naming of Hosts"
- Naming conventions in Active Directory
- URIs, URLs, and URNs: Clarifications and Recommendations 1.0
 | This computer networking article is a stub. You can help Wikipedia by expanding it. |