Académique Documents
Professionnel Documents
Culture Documents
Network computer devices that originate, route and terminate the data are called network
nodes.[1] Nodes can include hosts such aspersonal computers, phones, servers as well
as networking hardware. Two such devices can be said to be networked together when one device
is able to exchange information with the other device, whether or not they have a direct connection
to each other.
Computer networks differ in the transmission medium used to carry their signals,
the communications protocols to organize network traffic, the network's size, topology and
organizational intent.
Computer networks support an enormous number of applications such as access to the World Wide
Web, video, digital audio, shared use of application and storage servers, printers, and fax machines,
and use of email and instant messaging applications as well as many others. In most cases,
application-specific communications protocols are layered (i.e. carried as payload) over other more
general communications protocols.
Network Management
Network management refers to the broad subject of managingcomputer networks. There exists a wide variety
of software andhardware products that help network system administrators manage a network. Network
The Open Systems Interconnection model (OSI model) is a conceptual model that characterizes
and standardizes thecommunication functions of a telecommunication or computing system without
regard to their underlying internal structure and technology. Its goal is the interoperability of diverse
communication systems with standard protocols. The model partitions a communication system
into abstraction layers. The original version of the model defined seven layers.
A layer serves the layer above it and is served by the layer below it. For example, a layer that
provides error-free communications across a network provides the path needed by applications
above it, while it calls the next lower layer to send and receive packets that comprise the contents of
that path. Two instances at the same layer are visualized as connected by a horizontal connection in
that layer.
The model is a product of the Open Systems Interconnection project at the International
Organization for Standardization (ISO), maintained by the identification ISO/IEC 7498-1.
History[edit]
In the late 1970s, one project was administered by the International Organization for Standardization
(ISO), while another was undertaken by the International Telegraph and Telephone Consultative
Committee, or CCITT (the abbreviation is from the French version of the name). These two
international standards bodies each developed a document that defined similar networking models.
In 1983, these two documents were merged to form a standard called The Basic Reference Model
for Open Systems Interconnection. The standard is usually referred to as the Open Systems
Interconnection Reference Model, the OSI Reference Model, or simply the OSI model. It was
published in 1984 by both the ISO, as standard ISO 7498, and the renamed CCITT (now called the
Telecommunications Standardization Sector of the International Telecommunication Union or ITU-T)
as standard X.200.
OSI had two major components, an abstract model of networking, called the Basic Reference Model
or seven-layer model, and a set of specific protocols.
The concept of a seven-layer model was provided by the work of Charles Bachman at Honeywell
Information Services. Various aspects of OSI design evolved from experiences with the ARPANET,
NPLNET, EIN, CYCLADES network and the work in IFIP WG6.1. The new design was documented
in ISO 7498 and its various addenda. In this model, a networking system was divided into layers.
Within each layer, one or more entities implement its functionality. Each entity interacted directly only
with the layer immediately beneath it, and provided facilities for use by the layer above it.
Protocols enable an entity in one host to interact with a corresponding entity at the same layer in
another host. Service definitions abstractly described the functionality provided to an (N)-layer by an
(N-1) layer, where N was one of the seven layers of protocols operating in the local host.
The OSI standards documents are available from the ITU-T as the X.200-series of
recommendations.[1] Some of the protocol specifications were also available as part of the ITU-T X
series. The equivalent ISO and ISO/IEC standards for the OSI model were available from ISO, but
only some of them without fees.[2]
OSI Model
Protocol
data
Layer Function[3] Examples
unit (PDU
)
1. Physic Transmission and reception of raw bit DOCSIS, DSL, Ethernet physical
Bit
al streams over a physical medium layer, ISDN, RS-232
At each level N, two entities at the communicating devices (layer N peers) exchange protocol data
units (PDUs) by means of a layer N protocol. Each PDU contains a payload, called the service data
unit (SDU), along with protocol-related headers and/or footers.
1. The data to be transmitted is composed at the topmost layer of the transmitting device
(layer N) into a protocol data unit (PDU).
2. The PDU is passed to layer N-1, where it is known as the service data unit (SDU).
3. At layer N-1 the SDU is concatenated with a header, a footer, or both, producing a layer N-1
PDU. It is then passed to layer N-2.
4. The process continues until reaching the lowermost level, from which the data is transmitted
to the receiving device.
5. At the receiving device the data is passed from the lowest to the highest layer as a series
of SDUs while being successively stripped from each layer's header and/or footer, until
reaching the topmost layer, where the last of the data is consumed.
Some orthogonal aspects, such as management and security, involve all of the layers (See ITU-
T X.800 Recommendation[15]). These services are aimed at improving the CIA triad -
confidentiality, integrity, and availability - of the transmitted data. In practice, the availability of a
communication service is determined by the interaction between network design and network
management protocols. Appropriate choices for both of these are needed to protect against denial of
service.[citation needed]
It defines the electrical and physical specifications of the data connection. It defines the
relationship between a device and a physical transmission medium (e.g., a copper orfiber optical
cable, radio frequency). This includes the layout of pins, voltages,
line impedance, cable specifications, signal timing and similar characteristics for connected
devices and frequency (5 GHz or 2.4 GHz etc.) for wireless devices.
It is responsible for transmission and reception of unstructured raw data in a physical medium.
It defines transmission mode i.e. simplex, half duplex, full duplex.
It defines the network topology as bus, mesh, or ring being some of the most common.
It mostly deals with raw data.
The physical layer of Parallel SCSI operates in this layer, as do the physical layers of Ethernet and
other local-area networks, such as Token Ring, FDDI, ITU-T G.hn, and IEEE 802.11 (Wi-Fi), as well
as personal area networks such as Bluetooth and IEEE 802.15.4.
IEEE 802 divides the data link layer into two sublayers:[16]
Media Access Control (MAC) layer - responsible for controlling how devices in a network gain
access to medium and permission to transmit it.
Logical Link Control (LLC) layer - responsible for identifying Network layer protocols and then
encapsulating them and controls error checking and frame synchronization.
The MAC and LLC layers of IEEE 802 networks such as 802.3 Ethernet, 802.11 Wi-Fi,
and 802.15.4 ZigBee, operate at the data link layer.
The Point-to-Point Protocol (PPP) is a data link layer that can operate over several different physical
layers, such as synchronous and asynchronous serial lines.
The ITU-T G.hn standard, which provides high-speed local area networking over existing wires
(power lines, phone lines and coaxial cables), includes a complete data link layerthat provides
both error correction and flow control by means of a selective-repeat sliding-window protocol.
Message delivery at the network layer is not necessarily guaranteed to be reliable; a network layer
protocol may provide reliable message delivery, but it need not do so.
The transport layer controls the reliability of a given link through flow
control, segmentation/desegmentation, and error control. Some protocols are state- and connection-
oriented. This means that the transport layer can keep track of the segments and retransmit those
that fail. The transport layer also provides the acknowledgement of the successful data transmission
and sends the next data if no errors occurred. The transport layer creates packets out of the
message received from the application layer. Packetizing is a process of dividing the long message
into smaller messages.
OSI defines five classes of connection-mode transport protocols ranging from class 0 (which is also
known as TP0 and provides the fewest features) to class 4 (TP4, designed for less reliable networks,
similar to the Internet). Class 0 contains no error recovery, and was designed for use on network
layers that provide error-free connections. Class 4 is closest to TCP, although TCP contains
functions, such as the graceful close, which OSI assigns to the session layer. Also, all OSI TP
connection-mode protocol classes provide expedited data and preservation of record boundaries.
Detailed characteristics of TP0-4 classes are shown in the following table:[18]
An easy way to visualize the transport layer is to compare it with a post office, which deals with the
dispatch and classification of mail and parcels sent. Do remember, however, that a post office
manages the outer envelope of mail. Higher layers may have the equivalent of double envelopes,
such as cryptographic presentation services that can be read by the addressee only. Roughly
speaking, tunneling protocols operate at the transport layer, such as carrying non-IP protocols such
as IBM's SNA or Novell's IPX over an IP network, or end-to-end encryption with IPsec.
While Generic Routing Encapsulation (GRE) might seem to be a network-layer protocol, if the
encapsulation of the payload takes place only at endpoint, GRE becomes closer to a transport
protocol that uses IP headers but contains complete frames or packets to deliver to an
endpoint. L2TP carries PPPframes inside transport packet.
Although not developed under the OSI Reference Model and not strictly conforming to the OSI
definition of the transport layer, the Transmission Control Protocol (TCP) and theUser Datagram
Protocol (UDP) of the Internet Protocol Suite are commonly categorized as layer-4 protocols within
OSI.
This layer provides independence from data representation (e.g., encryption) by translating between
application and network formats. The presentation layer transforms data into the form that the
application accepts. This layer formats and encrypts data to be sent across a network. It is
sometimes called the syntax layer.[19]
The original presentation structure used the Basic Encoding Rules of Abstract Syntax Notation
One (ASN.1), with capabilities such as converting an EBCDIC-coded text file to anASCII-coded file,
or serialization of objects and other data structures from and to XML.
The TCP/IP reference model is the network model used in the current Internet
architecture [19]. It has its origins back in the 1960's with the grandfather of the
Internet, the ARPANET. This was a research network sponsored by the Department of
Defense in the United States. The following were seen as major design goals:
The reference model was named after two of its main protocols, TCP (Transmission
Control Protocol) [12] and IP (Internet Protocol).
The application forms its request, then passes the packet down to the lower layers,
which add their own control information, either a header or a footer, onto the packet.
Finally the packet reaches the physical layer and is transmitted through the cable onto
the destination host. The packet then travels up through the different layers, with each
layer reading, deciphering, and removing the header or footer that was attached by its
counterpart on the originating computer. Finally the packet arrives at the application it
was destined for. Even though technically each layer communicates with the layer
above or below it, the process can be viewed as one layer talking to its partner on the
host, as figure 2.1 shows.
Different type of encryption techniques are used to protect the data or any other information
from leaking and from illegal use. So another important technique is used to protect the data
during transmission is called as data encapsulation. Literally encapsulation means to wrap up or
hide so in data encapsulation different type of protocol layers are used to hide the specifications
and the personal information is called as data encapsulation. It is also called as the data hiding
because in this data is hiding and then transfer from one device to another with the help of
protocols layers.
The process of the data encapsulation has different steps at different layers of OSI model. These
steps of process of data encapsulation are as follows
The process of the data encapsulation initiates from the application layer of the OSI model and in
this layer it encapsulates the TCP header and then with the help of PDU communicates it with
the neighboring part. First of all the data present in the layer is converted for the transferring on
the network. The data is transfer to the transport layer for the sake of circuits that decides the
destination, it is called stream. After this stream broken and transport layer header in came into
being that take responsibility of controlling the attached data called as segment.
After the formation of the segment, all the responsibility is move onto the shoulders of the
networking layer that deals with the routing protocols of the OSI layer model such as IP. The
networking protocol layer attached its header to the segment and then transfers it to the DLL. In
the data link layer streams are built again and representing the host destination.
The role of the data link layer is that it receives the data packets from the networking layer
protocol and then place them on the communicational medium and another important job of DLL
is that it has to convert packets into frames, then MAC headers come in contact to assigning the
MAC address to the information and decides the destination, if the devices are not similar then it
will routed again.
Before placing the frames on the network, place them in the digital signals. Here physical layer
of the OSI model play its role to convert the 1s and 0s of the frame into the digital signals then it
is read by the local networking media.
Every programming has to be done on the basis of some reasons so, data encapsulation also have
some reasons which are listed below
In the early stages of development of the Internet Protocol,[1] network administrators interpreted an IP
address in two parts: network number portion and host number portion. The highest order octet
(most significant eight bits) in an address was designated as the network number and the remaining
bits were called the rest field or host identifier and were used for host numbering within a network.
This early method soon proved inadequate as additional networks developed that were independent
of the existing networks already designated by a network number. In 1981, the Internet addressing
specification was revised with the introduction of classful network architecture.[2]
Classful network design allowed for a larger number of individual network assignments and fine-
grained subnetwork design. The first three bits of the most significant octet of an IP address were
defined as the class of the address. Three classes (A, B, and C) were defined for
universal unicast addressing. Depending on the class derived, the network identification was based
on octet boundary segments of the entire address. Each class used successively additional octets in
the network identifier, thus reducing the possible number of hosts in the higher order classes
(B and C). The following table gives an overview of this now obsolete system.
16,777,216
A 0 8 24 128 (27) 0.0.0.0 127.255.255.255
(224)
16,384
B 10 16 16 65,536 (216) 128.0.0.0 191.255.255.255
(214)
2,097,152
C 110 24 8 256 (28) 192.0.0.0 223.255.255.255
(221)
Classful network design served its purpose in the startup stage of the Internet, but it
lacked scalability in the face of the rapid expansion of the network in the 1990s. The class system of
the address space was replaced with Classless Inter-Domain Routing (CIDR) in 1993. CIDR is
based on variable-length subnet masking (VLSM) to allow allocation and routing based on arbitrary-
length prefixes.
Today, remnants of classful network concepts function only in a limited scope as the default
configuration parameters of some network software and hardware components (e.g. netmask), and
in the technical jargon used in network administrators' discussions.
Private addresses
Early network design, when global end-to-end connectivity was envisioned for communications with
all Internet hosts, intended that IP addresses be uniquely assigned to a particular computer or
device. However, it was found that this was not always necessary as private networks developed
and public address space needed to be conserved.
Computers not connected to the Internet, such as factory machines that communicate only with each
other via TCP/IP, need not have globally unique IP addresses. Three non-overlapping ranges of
IPv4 addresses for private networks were reserved in RFC 1918
. These addresses are not routed on the Internet and thus their use need not be coordinated with
an IP address registry.
Today, when needed, such private networks typically connect to the Internet through network
address translation (NAT).
Any user may use any of the reserved blocks. Typically, a network administrator will divide a block
into subnets; for example, many home routers automatically use a default address range of
192.168.0.0 through 192.168.0.255 (192.168.0.0/24).
IP address classes
<< Back
Private IP Addresses
Class Private Networks Subnet Mask Address Range
A 10.0.0.0 255.0.0.0 10.0.0.0 - 10.255.255.255
B 172.16.0.0 - 172.31.0.0 255.240.0.0 172.16.0.0 - 172.31.255.255
C 192.168.0.0 255.255.0.0 192.168.0.0 - 192.168.255.255
IP
Class E 240.0.0.0 to 254.255.255.254 Reserved for future use, or Research and Development Purpose
Octet value: 8 8 8
192.168.1.3 - 254 Addresses beyond 3 are assigned to computers and devices on the network.
In IPv4 an address consists of 32 bits which limits the address space to 4294967296 (232) possible
unique addresses. IPv4 reserves some addresses for special purposes such as private
networks (~18 million addresses) or multicast addresses(~270 million addresses).
IPv4 addresses are canonically represented in dot-decimal notation, which consists of four decimal
numbers, each ranging from 0 to 255, separated by dots, e.g., 172.16.254.1. Each part represents a
group of 8 bits (octet) of the address. In some cases of technical writing, IPv4 addresses may be
presented in various hexadecimal, octal, or binary representations.
IPv6 addresses
Decomposition of an IPv6 address fromhexadecimal representation to its binary value.
The rapid exhaustion of IPv4 address space prompted the Internet Engineering Task Force (IETF) to
explore new technologies to expand the addressing capability in the Internet. The permanent
solution was deemed to be a redesign of the Internet Protocol itself. This new generation of the
Internet Protocol was eventually named Internet Protocol Version 6 (IPv6) in 1995.[3][4] The address
size was increased from 32 to 128 bits (16 octets), thus providing up to
2128 (approximately3.403×1038) addresses. This is deemed sufficient for the foreseeable future.
The intent of the new design was not to provide just a sufficient quantity of addresses, but also
redesign routing in the Internet by more efficient aggregation of subnetwork routing prefixes. This
resulted in slower growth of routing tables in routers. The smallest possible individual allocation is a
subnet for 264 hosts, which is the square of the size of the entire IPv4 Internet. At these levels, actual
address utilization rates will be small on any IPv6 network segment. The new design also provides
the opportunity to separate the addressing infrastructure of a network segment, i.e. the local
administration of the segment's available space, from the addressing prefix used to route traffic to
and from external networks. IPv6 has facilities that automatically change the routing prefix of entire
networks, should the global connectivity or the routing policy change, without requiring internal
redesign or manual renumbering.
The large number of IPv6 addresses allows large blocks to be assigned for specific purposes and,
where appropriate, to be aggregated for efficient routing. With a large address space, there is no
need to have complex address conservation methods as used in CIDR.
All modern desktop and enterprise server operating systems include native support for the IPv6
protocol, but it is not yet widely deployed in other devices, such as residential networking
routers, voice over IP (VoIP) and multimedia equipment, and network peripherals.