The Computer Networks

Summary
 Introduction to Computer Networks
 Network architecture (OSI model, TCP / IP)
 physical layer
 Data Link Layer
 The network layer
 The transport layer
 The application layer

2
 Role of the link layer
 Data Link Layer
 channel allocation
  Data Frame
 physical addressing
 Who is concerned ?
 Error management
 Detection?
 Correction ? LLC
MAC

Physical layer

3
 LLC and MAC
 The data link layer comprises two sublayers
 LLC: Logical Link Control
 Used to establish a logical link between the MAC layer and network layer
of the OSI model
 It’s role is to control the flow of data
 MAC: Media Access Control
 Format the frames according to the network access method
 Control network access and packet transmission errors
 Responsible for transfer data without errors between two computers
 Communicates directly with the network card

4
 MAC addresses
 Each station receives all data
 A transmitter of a frame?
 Recipient of a frame?
➢ Need MAC addresses: a source address and a destination address
 Adding a dispatch statement: Frame Header
 Destination Address
 Source Address

5
 MAC Address (2)
 physical address of an Ethernet card (Hardware address)
 Coded on 6 bytes
 3 bytes manufacturer, assigned by the IEEE
 3-byte serial number (ID number of the card)
 Each address is UNIQUE in the world
 The source address is always that of a single interface (unicast)
 The destination can be a unique address, group (multicast) or
broadcast (broadcast = FF-FF-FF-FF-FF-FF)

6
 Frame format: MAC Addresses

@ Destination @ Source Data

MAC addresses

7
 Recognition of the frames
 How to recognize the start of the frame?
 Presence of transient signals
 receiver synchronization
 Need a preamble
 7 bytes
 10101010
 Regular data → clock synchronization
 Do not transmit information
→ not embarrassing loss

8
 Frame Format: Preamble

Preamble @ Destination @ Source Data

9
 End of Preamble
 Receiving en route preamble
 Already started
 Since when ?
 Need to mark the end of the preamble
 Inserting a « Start Frame Delimitor » SFD
 1 byte
 10101011
 End of the preamble, start of data
 Follows the preamble
 Precedes the data

10
 Frame format: SFD

Preamble
SFD @ Destination @ Source Data

11
 Recognition of the frames (2)
 How to recognize the end of the frame?
 According to the code used (Ethernet II)
 Frame Length (802.3 Standard: standard Ethernet)

12
 The field « length / Type »
 Field of 2 bytes
 Ethernet II
 indicates the type of the level 3 protocol that is used to transmit
the message
 Examples (in hexadecimal)
 IP: 0800
 ARP 0806
 IEEE 802.3
 This field was redefined to contain the length in bytes of the
data field
 Since 1997, the IEEE standard incorporates both frame
formats

13
 Frame Format: Len / Type
Frame IEEE 802.3

Preamble SFD @ Destination @ Source Len Data

Ethernet II frame

Preamble SFD @ Destination @ Source Type Data

14
 Error management
 Presence of noise on the channel →adding noise to the
signal
 Reducible but inevitable
 Ability to edit data
 ➔error detection code
 Recalculation upon receipt
 If difference → modified data → destruction of the damaged
frame

15
 The FCS control field
 Frame Check Sequence
 Field of four bytes
 It validates the integrity of the frame to a bit close
 It uses a CRC (Cyclic Redundancy Check) that encompasses
all fields of the frame
 Thus, the receiving station can decide whether the frame is
correct and should be transmitted to the upper layer

16
 Frame format: FCS
802.3 Ethernet frame

Preamble SFD @ Destination @ Source Len Data FCS

Ethernet II frame

Preamble SFD @ Destination @ Source Type Data FCS

17
 frame format
802.3 Ethernet frame

Preamble SFD @ Destination @ Source Len Data FCS

7 bytes 1 6 6 2 4

Standard Ethernet frame

Preamble SFD @ Destination @ Source Type Data FCS

18
 The inter-frame time
 Inter Frame Space or Inter Frame Gap
 A machine can not transmit all frames. It has to transmit one
after the other
 The normalized inter-frame delay is 96-bit thus 9.6ms
(microseconds) to 10 Mbps
 Warning, for Gigabit Ethernet, the "space-time" were
extended

19
 Abstract about frame
 The layer 3 sends a data packet
 The MAC layer creates a frame with
 MAC Address Destination
 MAC Address Source
 Type / Data Length
 The data
 Calculation of FCS
 Adding Preamble, SFD and FCS to the frame
 Sending to the physical layer

20
 Access to the channel
 The problem
 Each machine can use channel
 No referee giving voice
 How not all talk at once?
 The solution
 CSMA: Carrier Sensing Multiple Access
 You do not interrupt communication
 We listen, we expect the end, and we chain
 "Civilized conversation"

21
 How the Network Card detects a
collision

 Before sending its data, EC1 checks that DI1 = 0

Collision !
• DTE2 sees the collision
• DTE1 sees nothing !

23
 How to do ?
 CSMA / CD
 CSMA with Collision Detection
 Each station checks its message
 If collision
 emission stop
 random wait
 Re-transmission

 This approach solves only half the problem ... when a

24
 Collision unnoticed
 In the example
 DTE2 sees the collision
 DTE1 sees nothing
 DTE2 retransmits the frame, since collision
 DTE1 receives a second copy !!!
 ➔ Avoiding discreet collisions at all costs
 Avoid too short frames
 Limit the length of the network

25
 Round-Trip-Delay
 This is the delay return

26
 The Ethernet solution
 The standard requires
 Round-Trip-Delay <50 ms
 10 Mbit/s, 50 ms  500 bits  62.5 bytes
 >64 bytes → Collision Detection guarantee
 Any frame must contain at least 72 bytes
 26 bytes of Layer 2 protocol
 46 bytes of data minimum
 If less than 46 bytes to send
 Padding
 Ex: ARP request = 28 bytes + 18 padding

27
 Response time
 The response time is the average waiting time between
sending a query and receiving the response
 It's about how users perceive the network

28
 MTU: Maximum Transfer Unit
 The MTU depends on the network
 It defines the maximum size (in bytes) of the packet or frame can be
transmitted at once
 For an Internet network, MTU = 576 bytes
 On an Ethernet network, MTU = 1500 bytes
 SLIP (Serial Line Internet Protocol) = 296 bytes
 The MTU therefore depends on the path taken by the message
 Definition of a "MTU path"
 The minimum MTU of each segment crossed: Min (MTU (segments))

29