Computer network naming scheme - Revision history

OAbot: Open access bot: url-access updated in citation with #oabot.

2025-05-28T12:24:45Z

Open access bot: url-access updated in citation with #oabot.

← Previous revision		Revision as of 12:24, 28 May 2025
Line 7:		Line 7:
	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).		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 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>		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\|url-access=subscription }}</ref>

	== Azure ==		== Azure ==

Frap: /* Azure */

2025-05-12T13:14:23Z

Azure

← Previous revision		Revision as of 13:14, 12 May 2025
Line 10:		Line 10:

	== Azure ==		== Azure ==
	On 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 ~~a.s~~ {{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>		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>

	== See also ==		== See also ==

Frap: Add text

2025-05-12T13:13:42Z

Add text

← Previous revision		Revision as of 13:13, 12 May 2025
Line 8:		Line 8:

	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>		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>

			== Azure ==
			On 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 a.s {{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>

	== See also ==		== See also ==
			{{Portal\|Internet}}
	* [[Systematic name]]		* [[Systematic name]]
	* [[Geospatial network]]		* [[Geospatial network]]

Rosguill: Wikipedia:Articles for deletion/Computer network naming scheme closed as no consensus (XFDcloser)

2024-05-21T18:24:24Z

Wikipedia:Articles for deletion/Computer network naming scheme closed as no consensus (XFDcloser)

← Previous revision		Revision as of 18:24, 21 May 2024
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]], 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.		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.

Citation bot: Altered url. URLs might have been anonymized. Add: authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_webform 22/3458

2024-05-09T05:49:51Z

Altered url. URLs might have been anonymized. Add: authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_webform 22/3458

← Previous revision		Revision as of 05:49, 9 May 2024
Line 11:		Line 11:
	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).		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 computing\|distributed]], [[centralized]], or [[hierarchical]]. Names can be human-readable or not human-readable.<ref>{{Cite journal \|~~last~~=Ahmed \|~~first~~=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=~~http~~://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>		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>

	== See also ==		== See also ==

Helpful Raccoon: qualification

2024-04-29T02:37:07Z

qualification

← Previous revision		Revision as of 02:37, 29 April 2024
Line 4:		Line 4:
	<!-- End of AfD message, feel free to edit beyond this point -->		<!-- End of AfD message, feel free to edit beyond this point -->
	{{Refimprove\|date=August 2018}}		{{Refimprove\|date=August 2018}}
	In [[computing]], a '''naming scheme''' is a system for assigning and managing names of objects connected into [[computer network]]s. It consists of a [[namespace]] and processes for assigning, storing, and [[Name resolution (computer systems)\|resolving]] names.		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==

Helpful Raccoon: more info

2024-04-29T02:35:56Z

more info

← Previous revision		Revision as of 02:35, 29 April 2024
Line 4:		Line 4:
	<!-- End of AfD message, feel free to edit beyond this point -->		<!-- End of AfD message, feel free to edit beyond this point -->
	{{Refimprove\|date=August 2018}}		{{Refimprove\|date=August 2018}}
	In [[computing]], a '''naming scheme''' is a system for assigning and managing names of 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 consists of a [[namespace]] and processes for assigning, storing, and [[Name resolution (computer systems)\|resolving]] names.

	==Naming schemes in computing==		==Naming schemes in computing==

Helpful Raccoon: /* External links */ This link isn't relevant either

2024-04-29T00:37:35Z

External links: This link isn't relevant either

← Previous revision		Revision as of 00:37, 29 April 2024
Line 22:		Line 22:

	== 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://support.microsoft.com/kb/909264 Naming conventions in Active Directory]		* [http://support.microsoft.com/kb/909264 Naming conventions in Active Directory]

Helpful Raccoon: /* External links */ removing irrelevant link

2024-04-29T00:36:41Z

External links: removing irrelevant link

← Previous revision		Revision as of 00:36, 29 April 2024
Line 24:		Line 24:
	* {{IETF RFC\|1178}} - "Choosing a Name for Your Computer"		* {{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]

Helpful Raccoon: Removing unsourced and poorly sourced material

2024-04-29T00:30:58Z

Removing unsourced and poorly sourced material

@@ Line 8: / Line 8: @@
 ==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 name]] (URN), [[uniform resource locator]] (URL), and [[uniform resource identifier]] (URI).