1.

4 ON ARCHITECTURES

Architectures cover many different aspects of networking environments. Service Architecture: The Basic framework of services by network . Protocol Stack Architecture: Service delivery functions and boundaries Router Architecture: specialized computer with hardware/software for packet processing , processing of routing protocols & configuration requirements. Network Topology Architecture: For efficient operation & service to its users, a network topology architecture is needed It is scalable and allows growth. NetworkManagement Architecture: Management plane handles the configuration responsibility of a network control plane addresses routing information exchanges.

1.5 SERVICE ARCHITECTURE

It is much like the postal delivery system. The three service models associated with IP networks are:

BEST-EFFORT SERVICE ARCHITECTURE

A packet or a datagram is forwarded from one router to another towards destination. For this IP network uses packet switching. The packet forwarding without worrying about reliable delivery. Two consecutive packets that belong to the same connection are to be treated independently by a router. IP makes its best effort to deliver packets. Because of this, the IP service paradigm is referred to as the best-effort service.

INTEGRATED SERVICES ARCHITECTURE

Developed in the early 1990s It allows functionalities for services that are real-time, interactive, and that can tolerate some loss, but require a bound on the delay , bandwidth guarantee and a dedicated path. For example, interactive voice and multimedia applications fall into this category. Note that the basic best-effort IP framework works on the notion of statelessness; that is, two consecutive packets that belong to the same connection are to be treated independently by a router. It require a connection or a session for a certain duration of time, duration. Since the basic IP architecture works on the notion of statelessness, and it was infeasible

DIFFERENTIATED SERVICES ARCHITECTURE

diff-serv architecture was developed to provide prioritized service mechanisms without requiring connection-level information to be maintained at routers. Specifically, this approach gives priority to services by marking IP packets with diffserv code points located in the IP header. Routers along the way then check the diff-serv code point and prioritize packet processing and forwarding for different classes of services. Diff-serv code points are identified through a 6-bit field in the IPv4 packet header; in the IPv6 packet header, the traffic class field is used for the same purpose.

SUPPLEMENTING A SERVICE ARCHITECTURE

In a realistic sense, and to provide acceptable quality of service performance, the basic concept can be supplemented with additional mechanisms to provide an acceptable service architecture, For example, although the basic conceptual framework does not require it, a router can be designed to do efficient packet processing for packets that belong to the same web-page requested by a user since they are going to the same destination. That is, a sequence of packets that belongs to the same pair of origination and destination IP addresses, to the same pair of source and destination port numbers, and to the same transport protocol (either TCP or UDP) can be thought of as a single entity and is identified as a micro flow. Thus, packets belonging to a particular microflow can be treated in the same manner by a router once a decision on forwarding is determined based on the first packet for this microflow. Another way to fine-tune the best-effort service architecture is through traffic engineering.

CONTINUED..

That is, a network must have enough bandwidth so that delay or backlog can be minimal, routers must have adequate buffer space, and so on, so that traffic moves efficiently through the network. In fact, both packet processing at a router and traffic engineering work in together for providing efficient services. Similarly, for both integrated-services and differentiatedservice architecture, packet handling can be optimized at a router. Furthermore, traffic engineering can be geared for integrated services or differentiated services architectures.

1.6 PROTOCOL STACK ARCHITECTURE 1.6.1 OSI REFERENCE MODEL

FIGURE: The OSI reference model and the IP reference model.

1.6 PROTOCOL STACK ARCHITECTURE

1.6 PROTOCOL STACK ARCHITECTURE

1.6 PROTOCOL STACK ARCHITECTURE

1.6 PROTOCOL STACK ARCHITECTURE

PROTOCOL LAYERING IN IP

ROUTER ARCHITECTURE: A FUNCTIONAL VIEW.

NETWORK MANAGEMENT ARCHITECTURE: DATA PLANE, CONTROL PLANE, AND

MANAGEMENT PLANE

Thanks