Computer network naming scheme: Difference between revisions

Content deleted Content added
m Reverted edits by 15.195.185.83 (talk) identified as spam (HG)
Citation bot (talk | contribs)
Removed URL that duplicated identifier. Removed parameters. | Use this bot. Report bugs. | Suggested by Abductive | Category:Naming conventions | #UCB_Category 41/44
 
(52 intermediate revisions by 35 users not shown)
Line 1:
{{Refimprove|date=August 2018}}
A '''naming scheme''' is a plan for naming objects. In [[computing]], naming schemes are often used for objects connected into [[computer network]]s.
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==
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 Names ([[Uniformuniform Resourceresource Namename]] |(URN]]), Uniform Resource Locators ([[Uniformuniform Resourceresource Locator|URLlocator]] (URL), and Uniform Resource Identifiers ([[Uniformuniform Resourceresource Identifieridentifier]] |(URI]]). For the technically inclined, the following article is worth perusing: http://www.w3.org/TR/uri-clarification/.
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 for a marketing department may be called "marwww01".
 
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 |journal=IEEE Communications Surveys & Tutorials |language=en |volume=7 |issue=3 |pages=38–54 |doi=10.1109/COMST.2005.1610549 |issn=1553-877X}}</ref>
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.
 
== Azure ==
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/.
On [[Microsoft Azure]] there is a naming convention to prefix applications with {{Mono|app-}}, functions app with {{Mono|func-}}, and service buses with {{Mono|sb-}}. The convention is to suffix the name with the environment {{Mono|-prod}} or {{Mono|-test}} and a number for the instance such as {{Mono|-001}}, {{Mono|-002}}, etc. Example {{Mono|app-navigator-prod-001.azurewebsites.net}}.<ref>{{cite web |title=Abbreviation recommendations for Azure resources - Cloud Adoption Framework |url=https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-abbreviations |website=learn.microsoft.com |publisher=Microsoft |access-date=12 May 2025 |language=en-us}}</ref><ref>{{cite web |title=Define your naming convention - Cloud Adoption Framework |url=https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming |website=learn.microsoft.com |publisher=Microsoft |access-date=12 May 2025 |language=en-us}}</ref>
 
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.
 
== See also ==
{{Portal|Internet}}
* [[Systematic name]]
* [[Geospatial network]]
* [[Naming convention]]
 
== References ==
{{reflist}}
 
== External links ==
* {{IETF RFC 1178|2100}} - "Choosing a NameThe forNaming Yourof ComputerHosts"
* [http://support.microsoft.com/kb/909264 Naming conventions in Active Directory]
* RFC 2100 - "The Naming of Hosts"
* [https://www.w3.org/TR/uri-clarification/ URIs, URLs, and URNs: Clarifications and Recommendations 1.0]
* [http://namingschemes.com/ Naming schemes]
 
[[Category:Naming conventions]]
[[Category:Network addressing]]
[[Category:Servers (computing)]]
 
 
{{network-stub}}