The development of a specific addressing and naming model for an organization with one thousand employees can be a challenging task. However, while referring to the structured model according to which addresses and names are assigned systematically, it is possible to respond to potential issues. This paper aims to provide outlines of plans for the addressing and naming model that can be used in a large organization, in the environment based on the separate geographical locations, and in the environment with the common data center and several servers. The paper also discusses the potential problems associated with the development of the plan and the specifics of using the domain name system (DNS) while proposing the plan.
Plan for the Development of an Addressing and Naming Model in a Large Organization
If the organization employs one thousand workers with ten departments, it is important to develop a structured model for the utilized network. The focus is on distributing addresses and names in departments as the main components of the hierarchy (Oppenheimer, 2010). The plan should include the following main steps:
- to design the appropriate hierarchy for addressing ten departments and associated sub-networks;
- to determine and distribute the authority for addressing and naming in ten departments;
- to assign addresses and names that are selected systematically;
- to determine the principles of the route summarization.
Plan for the Development of an Addressing and Naming Model: Equal Separation by Geography
If there is a condition that the equal separation by geography is observed, the plan for the organization can be modified to address this detail. The focus should be on reflecting the geographical locations in names and the perfect route summarization (Khoury & Abdallah, 2012). The proposed major steps are the following ones:
- to design the hierarchy and determine sub-networks;
- to distribute the authority for addressing and naming according to separate geographical locations;
- to assign addresses and names that are meaningful and easy to be managed;
- to determine the effective route summarization;
- to concentrate on mapping the geographical locations according to addresses and names.
IP addresses can include meaningful prefixes, and names can be related to the local area.
Plan for the Development of an Addressing and Naming Model: Common Data Center
If the organization has twenty backend servers, each server will cover the addresses for computers of fifty employees. In this context, the focus is on distributing the authority to departments and developing effective route summarization to cover these sub-networks. In this case, the number of routes should be reduced, and node IDs should be determined for each server (Oppenheimer, 2010). Therefore, the plan will include such steps as:
- the design of the hierarchy;
- the focus on the authority;
- the assignment of addresses and names;
- the route summarization and the process of determining node IDs to build the effective network.
Analysis of Functional Problems
The proposed plan is effective to address such possible problems as the delay, throughput, and even packet loss. The reason is that the elastic traffic associated with the TCP protocol used in this system does not depend on delays. Moreover, the application of the TCP protocol means that the system also addresses the problem of the throughput (Chodorek, Chodorek, & Krempa, 2008). Even though the high throughput is expected, there are no limits or stated minimum criteria regarding the throughput in this network. The packet loss problem is also addressed as the TCP protocol works to respond to this issue as the connection-oriented protocol (Chodorek et al., 2008, p. 874). The packet loss can become a result of only intended operations.
Analysis of Using the DNS
The domain name system or DNS allows arranging names assigned to devices according to the domain hierarchy principles. The DNS is used for the static addressing and naming that applies to the discussed organization’s network. If ten departments are located in ten different states or cities, it is possible to use ten domain names (Oppenheimer, 2010). Thus, while having ten local area networks, it is possible to reflect the names of states or cities in the domain names to make them recognizable and meaningful. In this enterprise, the DNS is utilized to make the network more systematic and organized.
Summary Highlighting the Main Points of the Plan
To develop the appropriate plan for the large organization that has ten departments which employ a thousand of employees and which are located separately, it is necessary to design the desired system hierarchy with the focus on determined sub-networks, distribute the authority according to separate geographical locations, and assign addresses and names associated with locations. It is also important to determine the route summarization and state node IDs to guarantee the servers.
The proposed plan can be discussed as effective in addressing the organization’s needs since it is based on the TCP protocol. As a result, the probability of functional problems is minimal. The DNS’s focus is also important as it allows systematizing all the addresses and names used in the organizations’ network and sub-networks.
References
Chodorek, A., Chodorek, R. R., & Krempa, A. (2008). An analysis of elastic and inelastic traffic in shared link. Human System Interactions, 5(1), 873-878. Web.
Khoury, J. S., & Abdallah, C. T. (2012). Internet naming and discovery: Architecture and economics. New York, NY: Springer Science & Business Media. Web.
Oppenheimer, P. (2010). Top-down network design. New York, NY: Cisco Press. Web.