Introduction
As organizations became larger in number of employees and geographical distribution, efficiency in communication became a key technological focus. Traditionally, most communication across organization was conducted through voice transmitted through intercom systems and in writing transmitted through fax systems. The advent of computers resulted in the creation of intranet systems that ably enable secure multimedia communication between members of the same organization spread across a wide geographical area, sometimes national or global in scope (Shen et al., 2017). However, the nature of data has continued to grow, including voice, video and other data formats thus complicating transmission. This has resulted in elastic and inelastic data. Elastic data is the kind of data whose transmission is not affected by delays in transmission (Shen et al., 2017). A recorded voice message in Mp3 format is an example of elastic data. Inelastic data on the other part is the kind of data that cannot be transmitted efficiently if there is any delay or interruption in the transmission (Shen et al, 2017). A video conference transmission is an example of inelastic data. Further, the need for privacy and efficiency has also created a requirement of limiting transmission of information at an individual level (Shang et al, 2016). The above listed conditions have resulted in a scenario where intranet settings require a consideration of complex variables and it is these variables that form the essence of this research paper.
Outline of an Addressing and Naming Model
A data communications network (DCN) is made up of a collection of nodes, which are devices being utilized by the individual users of the network (Shang et al., 2016). A simple DCN will only have a few users making identification of specific users easier. However in the instant case, there are 1000 employees spread across 10 departments and without a geographical limitation in scope. This complicates the process of identification yet every message must be sent to the exact person out of the 1000 and also have an exactly marked point of origin. An address is a specific identifier of each and every node in a DCN and normally entails a numeric figure for ease of transmission into binary code (Shang et al., 2016). Addressing is therefore the process of creating and establishing these identifiers. On the other hand, naming is the process of using alphabetical or a combination of alphabetical and numerical derivatives to create easily recognizable titles for the addresses of a DCN (Shang et al., 2016). This is because addresses in numerical figures would be difficult to recognize and identify for most humans more so in a DCN that has many users such as the instant case.
Delegate your assignment to our experts and they will do the rest.
The addressing plan can be developed using the 20 backend enterprise servers. The servers can be bequeathed a two numerical derivative from number 01 to number 20. Each and every node on the system including the ones used by the employees, the ten departmental headquarters and the sub-departments will fall within any of the 20 servers. With an employee base of 1000 employees, the number of nodes will normally be a five figure number. The nodes can therefore be set chronologically as and when they are made for example the first node can be 00001 with the five thousandth node being 05000. The address of the node, a singular node will have the number of the server it is connected to first, a decimal point then the actual node number. For example if a computer is connected marked as number 00867 and connected to server number 15 then its address will be 15.000867.
Naming on the other hand focuses on creating ease of identification (Shang et al, 2016). Easiest way to identify an employee is through their names and the department they operate under. Therefore, nodes connected to specific employees should be named after the employees and their respective departments. However to avoid the name being long, the 10 departments of the organization can be given number 01 to 10 then attached to the actual name of the employee. If an employee is using more than one node, then another number can be added after using hyphenation. For example if the employee is Tony Maxwell and works in department number 07 the name will be TonyMaxwel.07 and if he has two nodes the second one will be TonyMaxwel.07-2.
Functional Problems
Throughput refers to the amount of information going through the system at any given time and varies exponentially from time to time. Delay is in two major forms to wit End-to-end delay or one-way delay (OWD) (Shen et al., 2017). It refers to the amount of time it takes for data to travel from one node in a network to the other and is measured in fractions of a second (Shen et al., 2017). Packet loss on the other hand refers to when due to network congestion one or more packets of data fail to reach its destination (Shen et al., 2017). There is a functional correlation between throughput, delay and packet loss in the network. With variables as high as 1000 employees many of them communicating within and without the system at any given time, throughput can rise and fall exponentially. A chronic rise can result in congestion which will increase the delay and in extreme cases cause pocket loss.
With regard to elastic data traffic, higher delays may not affect the efficiency of the system but with inelastic data traffic, delays will render the system ineffective (Shen et al., 2017). Packet loss however means that part of the information sent will not arrive at its destination and therefore will affect both elastic and inelastic data traffic. Indeed, if the network develops a high propensity of packet loss it will be obsolete (Shen et al., 2017). The solution to the problems caused by high throughput, delays, and packet loss is either having servers powerful enough to handle any amount of data that the system can produce or have a system to regulate the amount of data that goes through the system at any given time.
How DNS can be used in the Plan
A domain name system (DNS) changes the naming and addressing system from being based on the hardware to being based on the users of the hardware (Byrnes & Turner, 2016). This makes the hardware anonymous and can be used by anyone with the necessary permissions to use it. To use DNS in the system, a Domain name space with 20 tree sub-divides into zones each supported by one of the backend enterprise servers. Under this system, addressing would be based on hardware and the servers they are connected to and naming based on the users themselves (Byrnes & Turner, 2016). Through a customized graphical user interface (GUI), a username would connect any device directly to the domain space. Any information sent will therefore reflect the username of the source as opposed to the hardware node where the information has emanated from. DNS will also reduce one user to one node creating ease of addressing and naming (Byrnes & Turner, 2016).
Executive Summary
This is a plan for the addressing and naming of users and nodes in a DCN of an organization with 1000 employees spread across ten departments. The plan is premised on the need for ease of identification of the information transmitted from one user to the other both electronically and by the users themselves. Being a DCN limited to use by employees only, the plan operates on the understanding that the employees operate and utilize specific and assigned hardware either stationary or mobile. The addressing and naming will therefore combine the users and their respective hardware devices as connected to the system using 20 devices.
The addressing will be premised on the hardware assigned to each individual or department. With there being 1000 employees and 10 departments, the number of devices in use will definitely be over 1000. This is premised on an understanding that in the contemporary information age, each employee has a computerized device in their workstation or on their person. Each server will be given a two figure number between 01 and 20 with each gadget getting a 5 figure number. The addressing will be based on the combination of the two numbers divided by a decimal point. The naming on the other hand will be based on the names of the users themselves followed by a departmental number. With there being 10 departments the departmental number will be between 01 and 10. The name will therefore be two names of the employee and the departmental number separated by a decimal point.
References
Byrnes, T. L., & Turner, F. (2016). "Domain Name System Based VPN Management." U.S. Patent Application No. 15/087,493 .
Shang, W., Bannis, A., Liang, T., Wang, Z., Yu, Y., Afanasyev, A., & Zhang, L. (2016, April). Named data networking of things. In Internet-of-Things Design and Implementation (IoTDI), 2016 IEEE First International Conference on (pp. 117-128). IEEE.
Shen, B., Rho, S., Zhou, X., & Wang, R. (2017). A delay-aware schedule method for distributed information fusion with elastic and inelastic traffic. Information Fusion , 36 , 68-79.
