Et3003 sem2-1314-7 network layers iv (ipv4)
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Et3003 sem2-1314-7 network layers iv (ipv4)

  • 232 views
Uploaded on

IPv4

IPv4

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
232
On Slideshare
232
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
22
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Network Layer Part IV Computer Networks Tutun Juhana Telecommunication Engineering School of Electrical Engineering & Informatics Institut Teknologi Bandung 7
  • 2. INTERNET PROTOCOL VERSION 4 (IPV4)
  • 3. 3
  • 4. 4 This is why we need Total Length field
  • 5. 5
  • 6. 6
  • 7. 7
  • 8. FRAGMENTATION 8
  • 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 done only by the destination host 11
  • 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 • 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 not used
  • 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. 17 identification The last fragment the offset field is always relative to the original datagram
  • 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
  • 21. Format 21 type-length-value (TLV)
  • 22. Option Types 22 do not require the length or the data fields require the length or the data fields
  • 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-of- option 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 25 • Pointer field is an offset integer field containing the byte number of the first empty entry It points to the first available entry.
  • 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