Topic Five-Network Tandards and Protocols
Topic Five-Network Tandards and Protocols
NETWORK STANDARDS
Introduction
Standards ensure that the things we use every day work together reliably. As computer networks
have grown in size, importance, and popularity, a wide variety of standards have developed to
make it easier for network engineers to ensure that computers and networks will connect
together and communicate reliably and efficiently
• Defacto standards.
• Dejure standards.
De facto standards arise in the industry by virtue of wide spread commercial and
educational use. They are often proprietary and may be unpublished and unavailable to outside
vendors. Unpublished and unavailable standards are known as closed system standards.
Published and accessible standards are known as open standards; examples of de facto
standards such as IBM’s systems network architectures.
De jure standards are non-proprietary; no single company makes them or owns rights to them.
They are developed with the intent of providing for greater connectivity and interoperability by
making specifications public so that independent manufacturers can build to such specifications.
Examples of non-proprietary de jure standards are OSI reference model, TCP/IP protocol suite,
the IEEE 802 standard. Examples of non- proprietary de jure standards are OSI reference
model, TCP/IP protocol suite and the IEEE 802 standards
Apple Computer has historically relied on closed standards in its computing products;
if you wanted to use Macintosh computers, you had to get all your equipment and accessories
directly from Apple.
THE OPEN SYSTEMS INTERCONNECTION
(OSI) MODEL
To better understand how computer network works we will use a network model. This
model will help to understand and identify the various parts that make up the network
and understand how the parts work together. The OSI reference model is not a
protocol in itself, but rather a conceptual architecture with which to build
communication systems around. It does not promote any one vendor’s product or
technology. The model divides the communication process into seven interdependent
layers.
7 Application
6 Presentation
5 Session
4 Transport
3 Network
2 Data Link
1 Physical
Each layer is responsible for a specific function, and when combined with other layers,
enables data communications to take place. The grouping of these programs in the OSI
model is called the protocol stack. It is extremely important to understand what each
layer defines, and how the layers relate to other layers, and to the model as a whole.
The seven layers of the OSI model can be split into two halves, those which provide
interconnection services and those which provide internetworking services. Each layer
within the model provides a set of services to the layer above and enhances the service
provided by the layer below
The Interconnection Layers
Interconnection group of standards makes up the bottom four layers of the OSI model,
which are known as the physical, data link, network and transport layers.
The physical layer defines the functional, procedural and physical interfaces of
communication links between equipment. For example, plug specifications, and pin
allocations.
The data link layer adds error-checking information and formats data for physical
transmission.
The transport layer includes error detection and correction as well as multiplexing. Its
basic function is to enhance the quality provided by the network layer below, if this is
necessary.
The internetworking group includes the top three layers of the OSI model and basically
provides the support services for the user applications. They are known as the session,
presentation, and application layers.
The session layer provides the organization, synchronization and timing of the
exchange of the data between end systems.
The presentation layer is concerned with now the information to be exchanged. This
includes resolving character set differences, such as ASCII to EBCDIC, providing text
compression and encryption/decryption services.
The application layer provides support for the user applications, which wish to exchange
information. (i.e. file transfer
The function of each layer should be chosen with an eye towards defining
internationally standardized protocol
The layer boundaries should be chosen to minimize the information flow across the
interface.
The number of layers should be large enough that distinct function need not be thrown
together in the same layer out of necessity, and small enough that the architecture does
not become unwieldy
Advantages of Layered Network Architecture
A new layer can be introduced any time (if required) without interfering other layers.
Increases the address overhead in data packet as it travels from bottom layer to the top
layer.
LAYER FUNCTIONS
Physical layer
The data units at this layer are called bits. This layer defines the mechanical and electrical
definition of the network medium and network hardware. This includes how data is merged
onto the cable and retrieved from it. An example of the Physical layer is RS-232.
The main network device found at the Physical layer is a repeater. The purpose of a repeater (as
the name suggests) is simply to receive the digital signal, reform it, and retransmit the signal. It
should be easy to see that this has the effect of increasing the maximum length of a network,
which would have been reached due to signal degradation if a repeater was not available. It
should also be possible to anticipate the requirements of a repeater, it is simply regenerating
cleaner digital signal so doesn't have to understand anything about the information it is
transmitting, processing on the repeater is non-existent
Data link layer
The data link layer groups the bits that we see at Physical layer into Frames. Primarily
responsible for error-free delivery of data we see the DATA LINK layer as split into two, the
Logical Link Control and Media Access Control. Although this split may not be necessary for
the exam it is important to be aware if you see reference to the LLC that this is actually
part of the data link layer
The main network device found at the data link layer is a bridge. This device works at a
higher layer than the repeater and therefore is a more complex device. It has some understanding
of the data it receives and can make a decision based on the frames it receives as to whether it
needs to let the information pass, or can remove the information from the wire. This means
that the amount of traffic on the cable can be reduced and therefore the usable bandwidth
increased.
Network Layer
The unit of data at the network layer is called a packet. This layer is responsible for
ROUTING. It examines network addresses in the data instead of physical addresses seen in
the Data Link layer. It makes a decision as to where to route the packet based on information
and calculations from other routers, or according to static entries in the routing table.
The main device found at the Network layer is a router.
Transport Layer
The transport layer is responsible for the reliable delivery of data. The mechanism for this is
often a connection-oriented delivery where both communicating devices go through a process
where they come to expect data from the other. Once the transfer of data is complete they go
through a 'teardown' phase, which breaks the connection between the machines. There is more
overhead involved in this reliable delivery of data, but it ensures that errors are recognized and
recovered from
Some applications do not require this level of reliability and make use of connectionless
delivery where the above connection-building process is not performed. This in turn reduces the
level of overhead involved. For example, a file transfer over the Internet would probably make
use of reliable connection oriented delivery, whereas real time audio information (e.g. an
Internet radio show) can transmit using connectionless delivery. If some information is missed
the first time, then being realtime audio it is lost forever (you don't want it 5 seconds late and out
of sequence).
Session Layer
This layer is about establishing connections, authenticating access, co- ordination and
synchronization. The session layer is responsible for managing dialog between two devices,
for example the session layer determines whether the communication will be simplex, half-
duplex or duplex.
Presentation Layer
This layer is responsible for ensuring the data is in a format that is understood by both sender and
recipient. This layer is also responsible for data encryption and data compression
Application Layer
The Application layer is probably the most easily misunderstood layer of the model. This layer
deals with providing the network services to the end user, but is not the software running on their
machine (Word forinstance). Server messaging blocks (SMB s) exist at the application layer.
Each layer, with the exception of the physical layer, adds information to the data as it travels
from the application down to the physical layer. This extra information is called a header.
TCP/IP MODEL/ INTERNET MODEL
NETWORK PROTOCOLS
A Protocol suite (also referred to as protocol stack) is a hierarchical set of protocols that
coordinates to affect a communication process. Protocols are the agreed upon ways in
which computers exchange information. They are sets of basic steps that both parties must
perform in the right order. For example the sending computer must do the following: -
1. Break the data into packets
2. Addressing information to the packets identifying the destination computer
3. Deliver the data to the network card for transmission over the network
The receiving computer must -:
1. Accept the data from the network adapter
2. Remove the transmitting information that was added by the transmitting computer.
3. Reassemble the packets of data into the original message Protocol suite can be
perceived to as a software implementation of the OSI upper layer specification. Various set of
protocol implemented by different vendors exists. This includes TCP/IP,
NETWARE IPX/SPX,NWLINK etc.
The original goal behind the TCP/IP communications standard was to create an easy
method to establish connections between many dispersed computers. Back in the mid-1960s,
compute networks only existed in the minds of a few scientists. It was the scientists’ dream
to create a computer communication system that would facilitate collaborative research
across universities worldwide. In the late 1960s, the United States Defense Department’s
Advanced Research Project Agency funded a project to do just this.
When the concept of this connected network was first proposed, standards for computer to
computer communications did not exist. Therefore, it was necessary to develop a new protocol to
handle the diversity of the various computer languages. Because it was impossible to re-
engineer existing systems to a new standard, some compromises had to be made, especially in
relation to security. Also, because the primary long distance links would be voice grade
telephone systems, the protocol had to be as efficient as possible in order to keep
retransmission requirements to a minimum. Due to the many demands for a fast, efficient
low-overhead suite of protocols, Transmission Control Protocol / Internet Protocol, or simply
TCP/IP, was developed. Since its conception, TCP/IP has been improved and enhanced, and
is now considered by many the protocol of choice for today’s networks.
USED
File Transfer
Simple Mail
Domain Name
Dynamic
Configuration Protocol
69 UDP TFTP Trivial File Transfer
Protocol
80 TCP HTTP World Wide Web HTTP
110 UCP POP3 Post Office Protocol 3
.
• UDP
Provides connectionless communications and does not guarantee that packets will be delivered.
Applications that use UDP typically transfer small amounts of data at one time. Reliable delivery is
the responsibility of the application.
Like TCP, UDP is a transportation mechanism, but unlike TCP, UDP is unreliable. This is not to
say that UDP is a lower-class mechanism, but simply that the data it transports is not of the nature
that you need confirmation it has been delivered. UDP uses a best effort delivery method, and
does not inform the other protocols if a packet is undeliverable. The primary use for UDP
transmission is speed. Because error checking is omitted, there is very little overhead associated with
the UDP protocol. Among the services that use UDP are Trivial File Transport Protocol (TFTP),
Simple Network Management Protocol (SNMP), Domain Name Services (DNS), and Network File
Systems (NFS). A good example of UDP is live video and audio services on the Internet. If a datagram
is lost during video or audio trans-mission, there simply isn’t enough real time to retransmit the
dropped data and remain live.
Advantages of TCP/IP
(a) Broad connection among all types of computers and servers.
(b) Direct access to the global Internet.
(c) Strong support for routing.
(d) Includes simple networks management protocol support (SNMP)
(e) It support for (DHCP) to dynamically assign client IP address.
(f) Support for the windows Internet Name service (WINS) to allow name browsing among
Microsoft client server s.
(g) It has support for most other Internet Protocol such as HTTP. (h) It allows networking
between organisation.
Disadvantages of TCP/IP
(a) Difficult to setup
(b) Relatively high overheads to support connecting and routing
(c) Slower speed than IPX and NETBEUI
NWLINK
This is Microsoft’s implementation of Novell’s IPX/SPX protocol stack. Used in Novell
NetWare. Actually IPX is the protocol. IPX is included with each Microsoft Windows NT
to support connection totheNovellNetworkservers. This makes migration between platforms
very easily. It also makes need form a complete cut-over from one networking standard to
another very easily. NWlink does not allow file and print sharing and from NetWare
clients or servers.
Advantages
(a) Ease of setup
(b) Support for routing between networks
(c) Greater speed than for TCP/IP implementation
(d) Ease of connection to installed NetWare server and client s.
Disadvantages
(a) Slower than NetBEUI
(b) Doesn’t support NetWare management protocols
(c) It lacks an effective centralized network addressing scheme to ensure that the network don’t use
the same address numbers as where is with TCP/IP
NetBEUI
NetBEUI stands for NetBIOS Extended user interface. (Net Bios network Basic Input/output
System). NetBEUI was developed for work group of 20 -200 computers. IBM originally developed
NetBEUI for departmental LANS. It is extremely easy to configure requiring very little input from
the administrator. NetBEUI acceptance is limited to Microsoft and IBM personal computer
networks and s u f f e r s from one major problem. NetBEUI is not routable so all
communication using this protocol is limited to the local network. Hence, NetBEUI does not
scale at all. However, NetBEUI is fast. These parameters make this protocol ideal for small LANs.
Advantages
a) High speed on small networks
b) If easy to setup and implement if largely self-tuning (self-tuning features)
Disadvantages
a) It cannot be slotted between networks (unsuitable for large network)
b) Very few management and maintenance t ool s for NetBEUI which makes it difficult to
troubleshoot.
c) It offers very little class -plat form support.