Elastic and Inelastic Traffic

Internet traffic to an organization’s web page is a fundamental component of the company’s ability to conduct its business through the internet. It is a frustrating experience when a specific website is not reachable, or the access is slow (Zhang, 2012). Basically, there are two types of internet traffic: elastic and inelastic internet traffic. Elastic traffic can adjust, over wide ranges, to changes in delay and throughout across the internet and still meets the requirements of its application. On the other hand, inelastic traffic does not easily adapt, if at all, changes in delay and throughout across the internet. Currently, web traffic is about one trillion bits per second and surprisingly, it is on the rise, and soon it will hit three tbps.

Names are assigned to varied genres of devices in the modern networks, workstation, servers, and routers. A well-designed naming model should enable users to access the created device by name. The name of the sources indicates what to check while an address shows its location (Li & Chen, 2012). Most network protocols always require the parent device to obtain a network address, and the end user system must map this address to a name.

Developing an addressing and naming model for ten departments

For a company that consists of ten departments that have 1000 employees, there is a need to design 9 Local Area Network (LAN) with equal geographical separation. For the network to work effectively and efficiently, it would be prudent if each LAN can contain more than forty-five computers. The Information Technology unit of an entity bears the responsibility for developing an address and a name model in the organization (Ash, 2007). The organization should use a common data center of around twenty-five backed enterprise servers and routers. All these servers should have a single data center operation. For easy identification and avoidance of confusion, names of these servers should contain a location code. When a device has more than one interface, then all these devices should be mapped to a single common name.

Developing an addressing and naming model for equal separation by geography

Deploying multiple tenants in a shared infrastructure optimizes resources utilization at a lower cost but requires designs that address secure tenant separation to insecure end-to-end path isolation. The virtualized multi-tenant data center architecture should use a path isolation technique to divide a shared infrastructure logically into multiple virtual networks. The architectures should start by installing network layer 3 (L3) separations. L3 provides tenant isolation with separated dedicated per-tenant routing and forwarding avoiding inter-tenant traffic within the data unless configured (Ash, 2007). Separating network layer 2 (L2) will provide isolation and identification of tenant traffic across the L2 domain and across shared links. Moreover, by having network service separation will provide unique policies at the VLAN level of granularity.

Developing an addressing and naming model for a common data center

A good user experience depends on predictable performance within the data center network. By installing Ethernet networks, the company can bridge the performance and scalability gap between capacity-oriented clusters and purpose built custom systems architectures(Li & Chen, 2012).. This data center should be a home for one or more processors where to compute resources should be arranged into racks and allocated as clusters consisting of five hosts. These five hosts should be orchestrated to exploit thread-level parallelism central to most internet workloads through dividing incoming requests into parallel subtasks. The cluster-application model should be shared among multiple applications.

Analyzing the functional problems of throughput, delay and packet loss

Elastic Internet traffic can easily reconcile, over wide ranges, to changes in stall and throughput across the web and can still fulfill the needs of its applications. By installing TCP based internet, traffic on personal connection reconciles to congestion by decreasing the rate at which information is presented to the communication system (Zhang, 2012). The routers on the communication systems have a responsibility of receiving and forwarding packets. TCP notices packet loss and carries through retransmissions to ensure trusty messaging.

Analyzing how DNS works

The DNS would be used in the addressing and naming part of the plan. The DNS is a hierarchical distributed naming model for computing. The DNS will offer to support the internet infrastructure by providing a distributed and fairly robust mechanism that resolves Internet host names into IP addresses back into the host names. Moreover, the DNS will provide support to other internet directories like lookup capabilities to retrieve information pertaining to DNS name servers and mail exchangers.

Summary

Cyberspace is an enormous invisible world that connects millions of computer to each other. For effective and efficient operations of a ten department organization, designing 9 LAN with a backup of five enterprise servers and routers will ensure the free flow of data in the organization. For tenants who are geographically separated, implementation of the virtualized multi-tenant data center should ensure resource optimization (Zhang, 2012). Moreover, Ethernet networks installation will help bridge information gap in an infrastructure. However, designing of a good TCP will notice packet loss and carry through retransmissions which will ensure that there is trusty messaging within and without the organization. Notably, the DNS will provide robust mechanism to resolve all Internet host names. Poor internet traffic can be attributed to the absence of traffic infrastructure and low level of computer penetration.

References

Ash, G. (2007). Traffic engineering and QoS optimization of integrated voice & data networks. Amsterdam: Elsevier/Morgan Kaufmann Publishers.

Li, T. & Chen, S. (2012). Traffic measurement on the internet. New York, NY: Springer.

Zhang, J. (2012). ICLEM 2012. Reston, Va.: American Society of Civil Engineers.

Elastic and Inelastic Traffic