WO2016144339A1

WO2016144339A1 - Generate network name based on network naming standard

Info

Publication number: WO2016144339A1
Application number: PCT/US2015/019840
Authority: WO
Inventors: Niraj NAIDU; Frederick KOTZE
Original assignee: Hewlett Packard Enterprise Development Lp
Priority date: 2015-03-11
Filing date: 2015-03-11
Publication date: 2016-09-15

Abstract

Some examples provide for generating a network name for a network device based on a network naming standard that defines a structure for the network name in view of the device information, and associating the network name to a set of network addresses associated with the network device. For some examples, associating the network name to the set of network address may comprise configuring the network name to resolve to the set of network addresses.

Description

GENERATE NETWORK UAME BASED ON NETWORK AM!NG STANDARD

BACKGROUND

[Θ001] Generally, a network name is a human-readable string that can be configured to resolve (e.g., convert) to a set of network addresses. Once such a relationship is established, the network name can identify the set of network addresses and be used in place of the set of network addresses. A commonly- used example of a network name include a domain name, which may be configured to resolve to a set of Internet Protocol addresses associated with (e.g., utilized by) a set of network devices, such as server computer systems. Benefits of using network names include that they provide a layer of abstraction (which can be useful in network redirection), they may be shorter than the set of network addresses they identify, and they may be easier for an individual remember than the set of network addresses they identify.

BRS EF DESC ! PTSO OF THE DRAW! GS

[0002] Certain examples are described in the following detailed description in reference to the following drawings.

[0003] FIGs. 1 and 2 illustrate example computer systems for generating a network name.

[0004] FIGs. 3-6 illustrate example methods performed by an example computer system to facilitate generation of a network name.

DETAILED DESCRSPTIO

[0005] Traditional methods of creating, configuring, and managing network names can be tedious and inefficient, particularly when the network names are created, configured, and managed for a large set of network devices (e.g., virtual network devices, such as cloud computer instance). Traditional methods usually involve a user (e.g., an administrator) having to separately interact with different systems (e.g., Domain Name System [DNS] server, Dynamic Host Control Protocol [DHCP] server, etc.) and having to perform several operations manually (e.g., management of network addresses, manual generation of network names, configuration of network names, optional adherence to a naming convention, etc.). As a consequence, traditional methods consume an unreasonable amount of user time, and often result in arbitrary network names being created by users (i.e., based on no naming standard), or inconsistent application of naming standards by users when creating network names.

[0006] Various examples described herein generate a network name for a network device based on device information associated with the network device and based on a network naming standard, and associate the network name to a set of network addresses associated with the network device. According to some examples, a network name for a network device is generated based on a network naming standard that defines a structure for the network name in view of device information associated with the network device. Additionally, for some examples, associating a network name to a set of network address may comprise configuring the network name to resolve to the set of network addresses.

[0007] As used herein, a network naming standard includes a group of segments (e.g., series of segments), where each segment comprises a set of characters (e.g., a single character or a plurality of characters) and the group defines the structure of a network name according to the network naming standard. As used herein, a string value will be understood to be a set of characters. The group of segments may include a segment having a static string value (hereinafter, "static segment"). The group of segments may include a segment having a string value that is auto-generated string value (hereinafter, "auto-generated segment"), which may comprise an alpha character, a numeric character, or a symbolic character. For some examples, the auto-generated string value may be generated such that the resulting network name is unique from other network names. For instance, a particular network name standard may be defined by a series of segments including a first segment that is a static segment and having a static value of "ABC," and a second segment that is an auto-generated segment having an auto-generated numeric value. Based on this particular network naming standard, a network name generated for a first network device may comprise "ABC0001 ," a network name generated for a second network device may comprise "ABC0002," a network name generated for a second network device may comprise "ABC00Q3," and so on. if for some reason the allocation of the network name "ABC0002" is ever relinquished (e.g., deleted), and the next request for a network name for another network device based on the particular network naming standard may result in "ABC0002" being regenerated for another network device (or reallocated to the other network device if the network name has not been deleted),

[00Θ8] The group of segments may include a segment associated with a set of pre-defined string values (hereinafter, "pre-defined segment"), where the predefined segment has a string value selected (and therefore assigned) from a set of pre-defined string values. When a network name is generated for a network name based on the group of segments, for the pre-defined segment, the string value may be selected from the set of pre-defined string values. For some examples, the string value is selected based on device information associated with the network device. Accordingly, the set of pre-defined string values may relate to geographical information associated with the network device (e.g., building, company site, continent, country, state, city, etc.), an operating system associated with the network device (e.g., UNIX, Linux, Windows©, etc.), an environment of use (hereinafter, "use environment") associated with the network device (e.g., development, alpha testing, beta testing, production, etc.), or a service provided by the network device (e.g., a web service, an application service, database service, messaging service, email service, etc.). Depending on the example, each pre-defined segment may have a static length requiring a certain number of characters (e.g., 3 characters with zero filling where less than 3 characters are provided), have a length range (e.g., 2 to 3 characters), or have a variable length (e.g., 1 to the length of the largest pre-defined string value provided).

[00Θ9] Illustrated below in Table 1 is an example group of segments that defines a structure for network names. As shown, the group of segments first includes a static segment to indicate that the example network naming standard is associated with "Customer 3," then includes pre-defined segments to indicate a country, a city, a use environment, an operating system, and a service associated with the network device (for which a network name is being generated), and then includes an auto-generated segment having a numeric value to distinguish it from other network names having the same value for segments 0 through 4. With regard to the pre-defined segment for a country, the "AU" represents Australia, "US" represent United States, and "DE" represents Germany. With regard to the pre-defined segment for a city, "SYD" represents Sydney, "MEL" represents Melbourne, "SFO" represents San Francisco, "LAX" represent Los Angeles, "BER" represents Berlin, and "MUN" represents Munich. With regard to the pre-defined segment for a use environment, "PROD" stands for production environment, "ALPH" represents alpha testing environment, "BETA" represents beta testing environment, and "DEV" represent development. With regard to the pre-defined segment for operating system, "W" represents Windows©, "U" represents UNIX, and "L" represents Linux. With regard to the pre-defined segment for a service, "APP" stands for an application service, "WEB" stands for a web-based service (e.g., web pages), "EML" stands for e-mail service, and "DB" stands for database service.

An Example Network Naming Standard

[0010] Table 2 illustrates an example network name generated for an example network device based on the example network naming standard illustrated in Table 1 and in view of device information associated with the example network device. For the example network name illustrated in Table 3, the device information indicates that the example network device: is associated with Customer 3, is associated with (e.g., located in) the United States and the city of Los Angeles; is being used for beta testing; is running a Linux operating system; is providing a database service; and is at ieast the fourth network device to have received a similar network name. Accordingly, the resulting example network name is "CUS3USLAXBETALDB004."

Example Network Name

[0011] As used herein, device information associated with a network device can include, without limitation, geographical information relating to the network device, a service provided by the network device, hardware information relating to the network device (e.g., model number, central processing unit [CPU] type, network device type, etc.), software information relating to the network device (e.g., an operating system or software application installed), and the like. A network device can include a desktop, laptop, hand-held computing device (e.g., personal digital assistants, smartphones, tablets, etc.), workstation, or other device capable of network communication. A network can include an internet protocol (IP) network and, as such, a network address can include an IP address. A network name can include a domain name, such as an internet domain name, implemented using a Domain Name System (DNS). A network name can include a NetBIOS name implemented using a NetBIOS name service.

[0012] Various examples are implemented as a software on a computer system that automates generation of a unique or non-unique network name (e.g., domain name) for a network device based on a network naming standard, which may be user definable. The software may be implemented on a cloud-based computer system and may provide a web-based interface or an interface for an application programming interface (API).

[0013] The software may permit a set of network naming standards to be defined, which are then used to provision a network name for a network device (e.g., generate a network and associate with the network device). The network device may be a physical network device or a virtual network device (e.g., cloud- based device). The software may permit definition (e.g., identification) of networks (e.g., Internet protocol [IP] networks) from which one or more available network addresses will be associated with (e.g., allocated to) generated network names and associated with the network device. A given network may be defined by a set of available network addresses (e.g., pool of available network addresses), a set of reserved network addresses (e.g., pool of reserved network addresses), a set of allocated network addresses (e.g., pool of allocated network addresses), or some combination thereof. A given network may also be defined by type of network (e.g., class A, B, or C IP network) and be a set of network parameters associated with the network, such as Virtual Local Access Network (VLAN) identifier, port group, gateway address, Domain Name System (DNS) server address, subnet network address, gateway network address, Network Time Protocol (NTP) server address, and the like.

[0014] Operations performed by the software may cause the storage of data (e.g., values) regarding network naming standards, network names generated, associations between network names and network devices, associations between sets of network addresses and network names, associations between sets of network addresses and network devices, associations between sets of network addresses and networks, or some combination thereof. The software may provide the stored data (e.g., stored values) to a user through a web-based interface) or may provide the stored data to third party systems (e.g., Cloud Service Automation (CSA) systems, Operations Orchestration (00) systems, DNS servers, DHCP servers, or network devices network devices themselves) through a web-based interface or an application program interface (API). Third party systems may act on the stored data to automate allocation of network names and network addresses to network devices.

[0015] in certain implementations, a system is provided comprising: an interface layer that provides a web-based user interface (e.g., provided by a web server), or an application program interface (API), or both; an application layer; and a database layer. As described herein, the system may be implemented using a set of cloud-based resources. The interface layer may serve to interface users or third party systems with the application layer of the system. For instance, a user may utilize a web-based user interface to interact with the system, and cause the system to perform various operations described herein, such as generating network names based on a network naming standard, associating a generated network name with a set of network addresses, and associating a set of network addresses with a network device. Similarly, a third party system may utilize an API provided by the interface layer to interact with the system, and cause the system to perform various operations described herein. In connection with performing various operations described herein, a user or a third party- system may utilize the interface layer to manage (e.g., add, remove, edit, etc.) customers, network naming standards, network devices, or networks. For instance, with respect to network devices, the interface layer may permit a user or third party system to create or modify information regarding the network device (hereinafter, "device information"). With respect to the network naming standards, the interface layer may permit a user or third party system to create or modify a group of segments that define the structure of a network name according to the network naming standard. With respect to the network, the interface layer may permit a user or third party system to create or modify information regarding a network, including information regarding the type of network (e.g., class A, B, or C internet protocol [I P] network), a set of available network addresses in the network, a set of reserved network addresses in the network, or network parameters associated with the network (e.g., Virtual Local Access Network [VLAN] identifier [I D], port group, gateway address, Domain Name System [DNS] server address, subnet network address, gateway network address, Network Time Protocol [NTP] server address, etc.).

[0016] The application layer may comprise computer-readable instructions executable to cause the system to use values provided through the interface layer to perform operations described herein. For instance, the application layer may cause the system to generate a network name for a network device based on a request received through the interface layer, generate the network name based on a network naming standard selected or defined through the interface layer, or generate the network name based on the network naming standard in view of device information (associated with the network device) defined or modified through the interface layer. [0017] The database layer may comprise a datastore to store, and provide subsequent access to various values defined in the system through by the interface layer (e.g., by user requests) and by the application layer (e.g., network names generated, associations stored between network names and network addresses). Depending on the example, the system may utilize stored values to cause other systems, such as Cloud Service Automation (CSA) systems, Operations Orchestration (00) systems, DNS servers, DHCP servers, and network devices themselves, to implement configurations in accordance with the stored values. For instance, based on the stored values, the system may cause a network name generated at the system to be implemented at a DNS server and to be implemented such that the network name resolves to a set of network addresses to which the network name is associated on the system. The system may cause a DHCP server to allocate to the network device the set of network addresses to which the network device (and the network name) is associated on the system. Additionally, the system may cause a CSA system to invoke a network device instance that is configured network settings according to stored values on the system that indicate the network name associated with the network device, the set of network addresses associated with the network device, and with a set of network parameters associated with a network to which the set of network addresses is associated. For some examples, the system may cause other systems, such as CSA systems, 00 systems, DNS servers, DHCP servers, and network devices themselves, to automatically access the stored values from the system and configure themselves according to those stored values.

[0018] The following provides a detailed description of the examples illustrated by F!Gs. 1 -2.

[0019] FIG. 1 illustrates an example computer system 100 for generating a network name. As shown, the computer system 100 includes a network name generation module 102, a network name management module 104, a network address management module 106, a data access module 108, and a communications module 1 10. Depending on the example, the computer system 100 may comprise a desktop, laptop, hand-held computing device (e.g., personal digital assistants, smartphones, tablets, etc.), workstation, or other device that includes a processor. Additionally, in some examples, the computer system 100 may comprises one or more servers, which may be operating on, or implemented, using one or more cloud-based resources, such as a Software-as-a-Service (SaaS), Piatform-as-a-Service (PaaS), or Infrastructure-as-a-Service (laaS). In various examples, the components or the arrangement of components in the computer system 100 may differ from what is depicted in FIG. 1 .

[0020] As used herein, modules and other components of various examples may comprise, in whole or in part, machine-readable instructions or electronic circuitry. For instance, a module may comprise computer-readable instructions executable by a processor to perform one or more functions in accordance with various examples described herein. Likewise, in another instance, a module may comprise electronic circuitry to perform one or more functions in accordance with various examples described herein. The elements of a module may be combined in a single package, maintained in several packages, or maintained separately.

[0021] The network name generation module 102 may facilitate generation of a network name for a network device based on a network naming standard, which may define a structure for the network name in view of device information associated with the network device. The network name may be generated in response to a request or instruction received by the computer system from a user at a client system. The request may be for generating a network name for a network device using a selected network naming standard, or may be for creating a new record for a network device. As described herein, the network device may be a physical network device or a virtual network device (e.g., cloud-based network device instance). As described herein, the network naming standard may be define a structure by a group of segments (e.g., series of segments), where each segment may be a static, pre-defined, or auto-generated segment. For the pre-defined segments, the device information associated with the network device may determine the pre-defined string value selected from the set of predefined string values associated with the pre-defined segment.

[0022] The network name management module 104 may facilitate storing an association (e.g., data representing the association) between the network name generated by the network name generation module and a set of network addresses. As described herein, ihe set of network address may be those to be associated with (e.g., to be allocated to), or those already associated with (e.g., already allocated to), the network device for which the network name was generated by the network name generation module 102. For some examples, storing an association between the network name and the set of network addresses can result in the network name being configured to resoive to the set of network addresses. For instance, where the network name is a domain name and the set of network address is a set of Internet protocol (IP) addresses, a Domain Name System (DNS) server reading the stored association between the domain name and the set of IP addresses may configure the domain name to resolve to the set of IP addresses.

[0023] The network address management module 106 may facilitate storing an association (e.g., data representing the association) between a set of network addresses and the network device for which the network was generated by the network name generation module 102. The network address management module 106 may associate the set of network addresses with the network device before or after the network name is associated with the network device by the network name management module 104. For some examples, storing an association between the network device and the set of network addresses can result in the set of network addresses being reserved for or assigned (e.g., allocated) to the network device. For instance, where the set of network address is a set of internet protocol (IP) addresses, a Dynamic Host Control Protocol (DHCP) server reading the stored association between the network device and the set of IP addresses may reserve that set of IP addresses for the network device (i.e., not allocate that set of IP addresses to any other network device) and may assign that set of IP addresses to the network device when the network device makes a DHCP request.

[0024] The data access module 108 may facilitate providing another computer access to data regarding the associations created by the network name management module 104 and the network address management module 106. Additionally, the data access module 108 may facilitate providing data regard the generated network name to another computer. The other computer to which data is provided can include the network device itself or a computer system serving as a Cloud Service Automation (CSA) system, an Operations Orchestration (00) system, a DNS server, a DHCP server, or the like. The data provided by the data access module 108 may be stored on and retrieved from a datastore (e.g., database or fiat file), which may be included by or separate from the computer system 100.

[0025] The communications module 1 10 may facilitate data communication between the computer system 100 and the another computer system, such as a client computer system from which a user can interact with the computer system 100, a network device for which a network name is generated, or a computer system serving as a Cloud Service Automation (CSA) system, an Operations Orchestration (OO) system, a DNS server, a DHCP server, or the like. The data communication may be over a communications network, which may comprise one or more local or wide-area communications networks, such as the Internet, WiFi networks, cellular networks, private networks, public networks, and the like. Through the communications module 1 10, the computer system 100 may receive a request for a network name for a network device, receive a request to associate the network name to the set of network addresses, receive a request to associate the network device to the set of network addresses, or provide related data to other computer systems external to the computer system 100.

[0026] FIG. 2 illustrates an example computer system 200. As shown, the computer system 200 includes a computer-readable medium 202, a processor 204, and a communications interface 208. in various examples, the components or the arrangement of components of the computer system 200 may differ from what is depicted in FIG. 2. For instance, the computer system 200 can include more or less components than those depicted in FIG. 2.

[0027] The computer-readable medium 202 may be any electronic, magnetic, optical, or other physical storage device that stores executable instructions. For example, the computer-readable medium 202 may be a Random Access Memory (RAM), an Electrically-Erasable Programmable Read-Only Memory (EEPROM), a storage drive, an optical disc, or the like. The computer-readable medium 202 can be encoded to store executable instructions that cause the processor 204 to perform operations in accordance with various examples described herein, in various examples, the computer-readable medium 202 is non-transitory. As shown in FIG. 2, the computer-readable medium 202 includes network name generation instructions 208, network name association instructions 210, and network address association instructions 212.

[0028] The processor 204 may be one or more centra! processing units (CPUs), microprocessors, or other hardware devices suitable for retrieval and execution of one or more instructions stored in the computer-readable medium 202. The processor 204 may fetch, decode, and execute the instructions 208, 210, and 212 to enable the computer system 200 to perform operations in accordance with various examples described herein. For some examples, the processor 204 includes one or more electronic circuits comprising a number of electronic components for performing the functionality of one or more of the instructions 208, 210, and 212.

[0029] The communications interface 206 may facilitate communication between the computer system 200 and a remote network entity, such as another computer system, instructions 208, 210, and 212 can cause the processor 204 to send or receive network traffic through the communications interface 206.

[0030] The network name generation instructions 208 may cause the processor 204 to generate a network name for a network device based on a network naming standard that defines a structure for the network name in view of device information associated with the network device. The network name association instructions 210 may cause the processor 204 to store an association between the network name and a set of network addresses. The network address association instructions 212 may cause the processor 204 to store an association between the set of network addresses and the network device.

[0031] FIG. 3 illustrates an example method 300 performed by an example computer system to facilitate generation of a network name. The method 300 may be implemented in the form of executable instructions stored on a computer- readable medium or in the form of electronic circuitry.

[0032] in FIG. 3, the method 300 begins at block 302, with the computer system generating a network name for a network device based on a network name standard that defines a structure for the network name in view of device information associated with the network device, in various examples, generating the network name for the network device comprises obtaining the device information associated with the network device from a record corresponding to the network device. Alternatively, the device information may be provided as pail of a request to the computer system to generate the network name for the network device. For some examples, the structure defined by the network naming standard includes a group of segments having a segment having an auto- generated string value. Depending on the example, the auto-generated string value may be generated according to a constraint that determines how the auto- generated string value is generated (e.g., value limits, character restrictions, increment amounts, etc.).

[0033] Additionally, for some examples, the structure includes a group of segments having a segment associated with a set of pre-defined string values, where the segment has a string value selected from a set of pre-defined string values. For some such examples, generating the network name for the network device comprises the computer system selecting the string value, from the set of pre-defined string values, based on the device information. Depending on the example, the set of pre-defined string values may relate to geographical information associated with the network device, an operating system associated with the network device, an environment of use associated with the network device, a service provided by the network device, or hardware information associated with the network device (e.g., hardware model number, serial number, processor type, etc.).

[0034] At block 304, the method 300 continues with the computer system associating the network name, generated at block 302, to a set of network addresses associated with the network device. For some examples, associating the network name to the set of network addresses comprises configuring the network name to resolve to the set of network addresses.

[0035] FIG. 4 illustrates an example method 400 performed by an example computer system to facilitate generation of a network name. The method 400 may be implemented in the form of executable instructions stored on a computer- readable medium or in the form of electronic circuitry.

[0036] in FIG. 4, the method 400 begins at block 402, with the computer system receiving data regarding selection of a network naming standard. For some examples, the data received is pail of a request from a user at a client system (e.g., via a web user interface) or a request from a third party system (e.g., via an application programming interface [API]) to use a network naming standard when generating a network name for a network device. Additionally, in some examples, the data received is part of a request to generate a network name for a network device.

[0037] At block 404, the method 400 continues with the computer system generating a network name for a network device based on the network naming standard selected at block 402. As described herein, the network naming standard selected may define a structure for the network name in view of device information associated with the network device. The method 400 continues to block 408, which may be similar to block 304 of the method 300 described with respect to FIG. 3.

[0038] FIG. 5 illustrates an example method 500 performed by an example computer system to facilitate generation of a network name. The method 500 may be implemented in the form of executable instructions stored on a computer- readable medium or in the form of electronic circuitry.

[Θ039] in FIG. 5, the method 500 begins at block 502, with the computer system receiving data regarding selection of a network, which may be utilized with a network device. For some examples, the data received is part of a request from a user at a client system (e.g., via a web user interface) or a request from a third party system (e.g., via an application programming interface [API]) to use a particular network with a network device. Additionally, in some examples, the data received is part of a request to generate a network name for a network device.

[0040] At block 504, the method 500 continues with the computer system selecting a set of network address from a set of available network address associated with the network selected at block 502. At block 506, the method 500 continues with the computer system associating the set of network addresses with the network device. As described herein, associating the set of network addresses with the network device may result in the set of network addresses being reserved for or ai!ocated to the network device (e.g., by a Dynamic Host Control Protocol [DHCP] server). The method 500 continues to blocks 508 and 510, which may be respectively similar to blocks 302 and 304 of the method 300 described with respect to FIG. 3.

[0041] FIG. 6 illustrates an example method 600 performed by an example computer system to facilitate generation of a network name. The method 600 may be implemented in the form of executable instructions stored on a computer- readable medium or in the form of electronic circuitry.

[0042] In FIG. 6, the method 600 begins at block 602 and continues to block 604, where block blocks 602 and 604 may be similar to blocks 302 and 304 of the method 300 described with respect to FIG. 3. At block 608, the method 600 continues with the computer system providing another computer system a set of network parameters associated a network to which the set of network addresses is associated. As described herein, a network parameter associated with a network can include a Virtual Local Access Network (VLAN) identifier, a port group, a gateway address, a Domain Name System (DNS) server address, a subnet network address, a gateway network address, a Network Time Protocol (NTP) server address, and the like. The network parameters may be provided to another computer system that can implement the network parameter as part of the settings for the network device. The other computer system may be the network device itself or a computer system serving as a Cloud Service Automation (CSA) system, an Operations Orchestration (OO) system, a DNS server, or a DHCP server, which may receive a network parameter provided by the computer system at block 608, and utilize it with enabling network operation of the network device.

[0043] in the foregoing description, numerous details are set forth to provide an understanding of the subject disclosed herein. However, various examples may be practiced without some or all of these details. Some examples may include modifications and variations from the details discussed above, it is intended that the appended claims cover such modifications and variations.

Claims

1 . A computer system, comprising:

a network name generation module to generate a network name for a network device based on a network naming standard that defines a structure for the network name in view of device information associated with the network device;

a network name management module to store a first association between the network name and a set of network addresses;

a network address management module to store a second association between the set of network addresses and the network device: and

data access module to provide another computer system access to data regarding the first association and data regarding the second association.

2. A non-transitory computer readable medium having instructions stored thereon, the instructions being executable by a processor of a computer system, the instructions causing the processor to:

generate a network name for a network device based on a network naming standard that defines a structure for the network name in view of device information associated with the network device;

store a first association between the network name and a set of network addresses; and

store a second association between the set of network addresses and the network device.

3. A method, comprising:

generating, by a computer system, a network name for a network device based on a network naming standard that defines a structure for the network name in view of device information associated with the network device; and associating, by the computer system, the network name to a set of network addresses associated with the network device.

4. The method of claim 3, wherein associating the network name to the set of network addresses comprises configuring the network name to resolve to the set of network addresses.

5. The method of claim 3, wherein the structure includes a group of segments having a segment associated with a set of pre-defined string values, and the segment has a string value selected from a set of pre-defined string values.

6. The method of claim 5, wherein generating the network name for the network device comprises selecting the string value from the set of pre-defined string values based on the device information.

7. The method of claim 6, wherein the set of pre-defined string values relates to geographical information associated with the network device.

8. The method of claim 6, wherein the set of pre-defined string values relates to an operating system associated with the network device.

9. The method of claim 6, wherein the set of pre-defined string values relates to a use environment associated with the network device.

10. The method of claim 6, wherein the set of pre-defined string values relates to a service provided by the network device.

1 1 . The method of claim 3, wherein the structure includes a group of segments having a segment having an auto-generated string value.

12. The method of claim 3, comprising receiving, at the computer system, data regarding a selection of the network naming standard.

13. The method of claim 12, wherein the data includes data regarding a second selection of the set of network addresses to be associated with the network device.

The method of claim 3, comprising receiving, at the computer system, data regarding a selection of a network;

selecting the set of network addresses from a set of available network addresses associated with a network; and

associating the set of network addresses to the network device.

15. The method of claim 3, wherein the set of network addresses is associated with a network having a set of network parameters, and the method comprises providing another computer system with the set of network parameters in association with the network device.