Netprog: OSI Reference Model

Networking
Netprog: OSI Reference Model

1
Network
“ ... communication system for connecting end-

systems”
End-systems a.k.a. “hosts”

PCs, workstations
dedicated computers
network components

2
Multiaccess vs. Point-to-point
n Multiaccess means shared medium.

– many end-systems share the same physical
communication resources (wire, frequency, ...)
– There must be some arbitration mechanism.
n Point-to-point
– only 2 systems involved
– no doubt about where data came from !
3
Multiaccess Point-to-point

4
LAN - Local Area Network
n connects computers that are physically

close together ( < 1 mile).
– high speed
– multi-access
n Technologies:
– Ethernet 10 Mbps, 100Mbps
– Token Ring 16 Mbps
– FDDI 100 Mbps
5
WAN - Wide Area Network
n connects computers that are physically far

apart. “long-haul network”.
– typically slower than a LAN.
– typically less reliable than a LAN.
– point-to-point
n Technologies:
– telephone lines
– Satellite communications
6
MAN - Metropolitan Area Network
n Larger than a LAN and smaller than a WAN

- example: campus-wide network
- multi-access network
n Technologies:
– coaxial cable
– microwave

7
Internetwork
n Connection of 2 or more distinct (possibly
dissimilar) networks.
n Requires some kind of network device to
facilitate the connection.
Net A Net B

8
OSI Reference Model
n Layered model:
7. Application
6. Presentation
5. Session
4. Transport
3. Network
2. Data Link
1. Physical
9
The Physical Layer
n Responsibility:
– transmission of raw bits over a communication
channel.
n Issues:
– mechanical and electrical interfaces
– time per bit
– distances

10
The Data Link Layer -

Data Link Control
n Responsibility:
– provide an error-free communication link
n Issues:
– framing (dividing data into chunks)
» header & trailer bits
– addressing
10110110101 01100010011 10110000001

11
The Data Link Layer -

The MAC sublayer
n Medium Access Control - needed by
mutiaccess networks.
n MAC provides DLC with “virtual wires” on

multiaccess networks.

12
The Network Layer
n Responsibilities:
– path selection between end-systems (routing).
– subnet flow control.
– fragmentation & reassembly
– translation between different network types.
n Issues:
– packet headers
– virtual circuits

13
The Transport Layer

n Responsibilities:
– provides virtual end-to-end links between peer
processes.
– end-to-end flow control
n Issues:
– headers
– error detection
– reliable communication

14
The Session Layer
n Responsibilities:
– establishes, manages, and terminates sessions
between applications.
– service location lookup
n Many protocol suites do not include a

session layer.

15
The Presentation Layer
n Responsibilities:
– data encryption
– data compression
– data conversion
n Many protocol suites do not include a
Presentation Layer.

16
The Application Layer
n Responsibilities:
– anything not provided by any of the other layers
n Issues:
– application level protocols
– appropriate selection of “type of service”

17
Layering & Headers

n Each layer needs to add some control
information to the data in order to do it’s job.
n This information is typically prepended to the
data before being given to the lower layer.
n Once the lower layers deliver the the data
and control information - the peer layer uses
the control information.

18
Headers
Process DATA Process
Transport H DATA Transport
Network H H DATA Network
Data Link H H H DATA Data Link

19
What are the headers?
Physical: no header - just a bunch of bits.
Data Link:
– address of the receiving endpoints
– address of the sending endpoint
– length of the data
– checksum.

20
Network layer header - examples
n protocol suite version n protocol

n type of service n header checksum
n length of the data n source network
n packet identifier address
n fragment number n destination network
n time to live address

21
Important Summary
n Data-Link: communication between

machines on the same network.
n Network: communication between machines
on possibly different networks.
n Transport: communication between
processes (running on machines on possibly
different networks).

22
Connecting Networks
n Repeater: physical layer
n Bridge: data link layer
n Router: network layer
n Gateway: network layer and above.

23
Repeater
n Copies bits from one network to another

n Does not look at any bits
n Allows the extension of a network beyond
physical length limitations
REPEATER

24
Bridge
n Copies frames from one network to another
n Can operate selectively - does not copy all
frames (must look at data-link headers).
n Extends the network beyond physical length
limitations.
BRIDGE

25
Router
n Copies packets from one network to another.
n Makes decisions about what route a packet
should take (looks at network headers).
ROUTER

26
Gateway
n Operates as a router
n Data conversions above the network layer.
n Conversions:
encapsulation - use an intermediate network
translation - connect different application protocols
encrpyption - could be done by a gateway

27
Encapsulation Example
Gateway Gateway
n Provides service connectivity even

though intermediate network does
not support protocols.

28
Translation
Gateway
n Translate from green protocol to brown protocol

29
Encryption gateway
Secure Secure
Encryption/Decryption
Network Network
Gateways
GW ? GW
?
?
Insecure Network

30
Hardware vs. Software
n Repeaters are typically hardware devices.

n Bridges can be implemented in hardware or
software.
n Routers & Gateways are typically implemented in
software so that they can be extended to handle
new protocols.
n Many workstations can operate as routers or
gateways.
31
Byte Ordering
n Different computer architectures use
different byte ordering to represent multibyte
values.
n 16 bit integer:
Low Byte Address A High Byte
High Byte Address A+1 Low Byte

32
Byte Ordering
Little-Endian Big-Endian
Low Byte High Byte High Byte Low Byte
Addr A Addr A+1 Addr A Addr A+1
IBM 80x86 IBM 370

DEC VAX Motorola 68000
DEC PDP-11 Sun

33
Byte Order and Networking
n Suppose a Big Endian machine sends a 16

bit integer with the value 2:
0000000000000010
n A Little Endian machine will think it got the

number 512:
0000001000000000

34
Network Byte Order
n Conversion of application-level data is left

up to the presentation layer.
n But hold on !!! How do lower level layers
communicate if they all represent values
differently ? (data length fields in headers)
n A fixed byte order is used (called network
byte order) for all control data.

35
Multiplexing
n “.. to combine many into one”.

n Many processes sharing a single network
interface.
n A single process could use multiple
protocols.
n More on this when we look at TCP/IP.

36
Modes of Service
n connection-oriented vs. connectionless

n sequencing
n error-control
n flow-control
n byte stream vs. message based
n full-duplex vs. half-duplex.

37
Connection-Oriented vs.
Connectionless Service
n A connection-oriented service includes the
establishment of a logical connection
between 2 processes.
– establish logical connection
– transfer data
– terminate connection.
n Connectionless services involve sending of
independent messages.
38
Sequencing
n Sequencing provides support for an order to

communications.
n A service that includes sequencing requires
that messages (or bytes) are received in the
same order they are sent.

39
Error Control
n Some services require error detection (it is

important to know when a transmission error
has occured).
n Checksums provide a simple error detection
mechanism.
n Error control sometimes involves notification
and retransmission.

40
Flow Control
n Flow control prevents the sending process

from overwhelming the receiving process.
n Flow control can be handled a variety of
ways - this is one of the major research
issues in the development of the next
generation of networks (ATM).

41
Byte Stream vs. Message
n Byte stream implies an ordered sequence of

bytes with no message boundaries.
n Message oriented services provide
communication service to chunks of data
called datagrams.

42
Full- vs. Half-Duplex
n Full-Duplex services support the transfer of

data in both directions.
n Half-Duplex services support the transfer of

data in a single direction.

43
End-to-End vs. Hop-toHop
n Many service modes/features such as flow

control and error control can be done either:
between endpoints of the communication.
-or-
between every 2 nodes on the path between the
endpoints.

44
End-to-End
Process A
Process B

45
Hop-by-Hop
Process A
Process B

46
Buffering
n Buffering can provide more efficient

communications.
n Buffering is most useful for byte stream
services.
Send Recv.
Process A Process B
Buffer Buffer

47
Addresses
n Each communication endpoint must have an

address.
n Consider 2 processes communicating over
an internet:
– the network must be specified
– the host (end-system) must be specified
– the process must be specified.

48
Addresses at Layers
n Physical Layer: no address necessary

n Data Link Layer - address must be able to
select any host on the network.
n Network Layer - address must be able to
provide information to enable routing.
n Transport Layer - address must identify the
destination process.
49
Broadcasts
n Many networks support the notion of

sending a message from one host to all
other hosts on the network.
n A special address called the “broadcast
address” is often used.
n Some popular network services are based
on broadcasting (YP/NIS, rup, rusers)

50

Netprog: OSI Reference Model

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Netprog: OSI Reference Model

Uploaded by

Copyright:

Available Formats

Networking