Network Layer Part 4
Download as PPTX, PDF•0 likes•716 views
This document provides information on Internet Protocol version 4 (IPv4) fragmentation and options. It discusses how a datagram may need to be divided into fragments to pass through networks with different maximum transfer unit (MTU) sizes. When fragmenting, the identification, flags, fragmentation offset, and total length fields are modified in each fragment while other header fields are copied. At the destination, fragments can be reassembled using the identification and offset fields. The document also describes various IP options like record route, loose/strict source routing, and timestamps. It explains the type-length-value format for options and checksum calculation.
Network Layer Part 4
- 1. 4 Tutun Juhana Telecommunication Engineering Network Layer (Part 4) School of Electrical Engineering & Informatics Institut Teknologi Bandung Computer Networks
- 2. INTERNET PROTOCOL VERSION 4 (IPV4)
- 3. 3
- 4. This is why we need Total Length field 4
- 5. 5
- 6. 6
- 7. 7
- 9. Maximum Transfer Unit (MTU) 9
- 10. • Maximum IP datagram length is 65,535 bytes • We might have to divide the datagram to make it possible to pass through different physical networks This is called fragmentation. 10
- 11. • When a datagram is fragmented, each fragment has its own header with most of the fields repeated, but some changed • A fragmented datagram may itself be fragmented if it encounters a network with an even smaller MTU (a datagram can be fragmented several times before it reaches the final destination) • A datagram can be fragmented by the source host or any router in the path • The reassembly of the datagram, however, is 11 done only by the destination host
- 12. • When a datagram is fragmented, required parts of the header must be copied by all fragments The option field may or may not be copied • The host or router that fragments a datagram must change the values of three fields: flags, fragmentation offset, and total length (The rest of the fields must be copied) • The value of the checksum must be recalculated regardless of fragmentation. 12
- 13. Fields Related to Fragmentation • Identification • Flags • Fragmentation offset 13
- 14. Identification • 16 bit • Identifies a datagram originating from the source host • The combination of the identification and source IP address must uniquely define a datagram as it leaves the source host. • When a datagram is fragmented, the value in the identification field is copied into all fragments all fragments have the same identification number, which is also the same as the original datagram • The identification number helps the destination in reassembling the datagram all fragments having the same identification value should be assembled into one datagram 14
- 15. Flags not used • D (Do not fragment) – ‘1’ : machine must not fragment the datagram – ‘0’ : datagram can be fragmented if necessary • M (More fragments) – ‘1’ : datagram is not the last datagram – ‘0’ : This is the last or only fragment 15
- 16. Fragmentation offset • This 13-bit field shows the relative position of this fragment with respect to the whole datagram. • Measured in units of 8 bytes 16
- 17. the offset field is always relative to the original datagram identification The last fragment 17
- 18. • Final destination host can reassemble the original datagram from the fragments received (if none of them is lost) using the following strategy: a. The first fragment has an offset field value of zero. b. Divide the length of the first fragment by 8. The second fragment has an offset value equal to that result. c. Divide the total length of the first and second fragment by 8. The third fragment has an offset value equal to that result. d. Continue the process. The last fragment has a more bit value of 0. 18
- 19. OPTIONS 19
- 20. • Are not required for a datagram – But all IP software implementations must be able to handle options if they are present in the header. • Can be used for network testing and debugging. 20
- 22. Option Types do not require the length or the data fields require the length or the data fields 22
- 23. No-Operation Option • 1-byte option used as a filler between options 23
- 24. End-of-Option Option • 1-byte option used for padding at the end of the option field. • It can only be used as the last option Only one end-ofoption option can be used After this option, the receiver looks for the payload data If more than 1 byte is needed to align the option field, some no-operation options must be used, followed by an end-of-option option 24
- 25. Record-Route Option • is used to record the Internet routers that handle the datagram • It can list up to nine router IP addresses • Pointer field is an offset integer field containing the byte number of the first empty entry It points to the first available entry. 25
- 26. 26
- 27. Strict-Source-Route Option • used by the source to predetermine a route for the datagram as it travels through the Internet 27
- 28. 28
- 29. Loose-Source-Route Option • similar to the strict source route, but it is more relaxed Each router in the list must be visited, but the datagram can visit other routers as well. 29
- 30. Timestamp • A timestamp option is used to record the time of datagram processing by a router • The time is expressed in milliseconds from midnight, Universal Time. 30
- 31. 31
- 32. 32
- 33. CHECKSUM 33
- 34. Checksum Calculation at the Sender • The packet is divided into k sections, each of n bits. • All sections are added together using one’s complement arithmetic. • The final result is complemented to make the checksum. 34
- 35. 35
- 36. Checksum in the IP Packet 36
- 37. 37