Encapsulation and PDU Analysis in Networking
Uploaded by
ScribdTranslationsEncapsulation and PDU Analysis in Networking
Uploaded by
ScribdTranslationsUniversity of La Rochelle Master CCI
Networks
TD No. 2: Encapsulation and PDU
Exercise 1:
What is encapsulation?
Encapsulation consists of transporting data (PDU) of a given protocol inside structures.
(PDU) belonging to another protocol. In the OSI model, it is the insertion of data from the layer
superior in the data structure of the lower layer.
2. Decode the following Ethernet frame using the formats provided in the appendix (only give the
bold fields) :
0000 00 04 76 f0 fb b5 00 06 5b c2 f5 9e 08 00 45 00
0100 0100 0111 0110 1100 1100 0100 0000 0000 0100 0000 0111 1011 0110 1111 1100 0000 1010 1000 0000 0001 0111 1100 0000 1010 1000 .O..@.@..o......
0020 00 03 80 09 00 50 85 e6 67 33 03 6c 42 f4 80 18 .....P..[Link]...
0030 16 d0 78 f1 00 00 01 01 08 0a 00 09 62 11 0b 5a ..x.........b..Z
GET / HTTP/1.1 jCGET / HTTP/1.1
Connection: Ke ..Connection: Ke
ep-Alive User-A ep-Alive..User-A
get: Mozilla/5. gent: Mozilla/5.
0080 30 20 (compatible; K 0 (compatible; K
onqeror/2.2-11; Conqueror/2.2-11;
Linux Accept: Linux)..Accept:
0° text/*, image/j text/*, image/j
peg, image/png, peg, image/png
00d0 image/*, */* Ac image/*, */*..Ac
à cept-Encoding: x cept-Encoding: x
0f - gzpip, gzpip, ide -gzip, gzip, idea
NITTY Accept-Ch entity..Accept-Ch
Are you there: Any, utf- arset: Any, utf-
0120 38 2c 20 2a 0d 0a 41 63 63 65 70 74 2d 4c 61 6e 8, *..Accept-Lan
130 flag: fr, fr_FR guage: fr, fr_FR
0140 40 65 75 72 6f, en Host: @euro, en..Host:
0150 20 73 65 72 76 43 33 30 39 servC309....
Ethernet Frame IP Packet TCP Segment
Ethernet :
Destination address: 00 04 76 f0 fb b5
Source address: 00 06 5b c2 f5 9e
- Type: 00 80 → the content of the field "Information" is in IP format
Decoding the IP part:
- Version: 4 → we must use the format of version 4 of IP (another possibility: 6)
LETou Header Length: 5 → header size 5*4 bytes= 20 bytes
Service Type: we are not interested, we skip 1 byte
Total Length: 01 4f = 335 bytes - easily verifiable on the captured frame
Identification
Flags :
Relative position:
Lifetime: we are not interested, we skip 5 bytes
-Protocol: 06 → TCP, what follows the IP header is in TCP format (important for what follows)
Header checksum: not of interest, we skip 2 bytes
Source address: c0 a8 00 17 → [Link]
- Destination address: c0 a8 00 17 → [Link]
- Options :
Padding: there is none because the existing fields already represent 20 bytes, size specified by the 2nd.
champ
University of La Rochelle Master CCI
TPDU (segment) of the TCP Protocol:
- Port source: 80 09 → 32777 (is less than 1024, so not reserved, allocated by the system)
Recipient Port: 00 50 → 80 (is less than 1024, so reserved for a particular application)
the occurrence HTTP
Sequence number:
Acknowledgment of receipt: we are not interested, so we skip 8 bytes
Data Offset: 8*4octets = 32 octets → size of the header
Reserved:
Window
Checksum
Pointer for urgent data:
- Options :
Padding: we are not interested
3. In your opinion, what is the protocol carried within the TCP segment and what is the application that
Do I use it? In what form do the fields of this protocol present themselves?
HTTP because one of the TCP ports is an HTTP port (80). We can also see it in the data.
transmitted by TCP. This frame is sent from a web browser to a server to retrieve a
Web page. In the request, we observe the presence of various directives (defined by the protocol
HTTP) notably the browser used: Konqueror on Linux. These directives constitute the
various fields of the HTTP protocol message format. In addition to these directives (which are
optional), there is the command sent by the sender (here GET), which appears at the very beginning of the PDU
HTTP. The directives are in the form: "name: value". Thus, one can see:
Connection: Keep-Alive → request to keep the connection open with the server
application that uses HTTP
Accept: text/*, image… → types and formats of data accepted by the client
Exercise 2:
In a network based on the TCP/IP protocol stack model, an MDTP (Master) protocol is defined.
Data Transfer Protocol) from the application layer to transfer data between 2 machines. When a
the machine wants to transfer data using this protocol, it sends one (or more) datagrams
containing the data to be transferred to the destination machine. Thus, at the MDTP level, the protocol is
summarize into a monologue (unidirectional transmission of PDU). This protocol uses at the layer
UDP (User Datagram Protocol) is a connectionless protocol without acknowledgments.
What is the effectiveness of the transfer, knowing that:
the data to be transferred occupies 3 KB
The MDTP header has a fixed size of 60 bytes.
The UDP header has a fixed size of 8 bytes.
- The format of IP packets and Ethernet frames is provided in the appendix.
The IP protocol does not use its 'Options' field.
To calculate efficiency, we must calculate the total number of pieces of information circulating on the network all headers.
It is therefore necessary to determine the number of frames required.
Data size: Data = 3KB = 3072 bytes
PDU MDTP size (application PDU) = MDTP header + Data = 3132 bytes
The PDU MDTP must be transported by UDP TPDU (segments), which are encapsulated in NPDU
IP packets which in turn are carried by Ethernet LPDU (frames). Given that the frames
have a maximum size, packets and segments are also bounded.
Max Ethernet size = 1518 bytes including 18 bytes for control fields
→ maximum size of useful Ethernet data = 1500 bytes
→ max IP size = 1500 of which 20 bytes header
→ max useful IP data size = 1480 bytes
max UDP size = 1480 bytes including 8 bytes header
→ max useful UDP data size = 1472 bytes
→ we can only transport seg_u = 1472 bytes of MTDP at a time
University of La Rochelle Master CCI
max size of useful data in a segment
PDU IDTP / seg_u = 3132 / 1472 = 2.12, rounded to 3 because we need 2 filled frames
completely and a third frame to transport the little that remains.
To transmit data bytes, we additionally transmitted: 3 Ethernet headers, 3 IP headers, 3 UDP headers, 1 header
MDTP.
Total data = 3 x (18 + 20 + 8) + 60 + 3072 = 3270 bytes
Useful data = Data = 3072 bytes