IP Encapsulation, Fragmentation, and Reassembly - PowerPoint PPT Presentation

1 / 14
About This Presentation
Title:

IP Encapsulation, Fragmentation, and Reassembly

Description:

Termed Maximum Transmission Unit (MTU) If datagram larger, cannot be encapsulated ... In order for datagram to transit network with small MTU, must be fragmented ... – PowerPoint PPT presentation

Number of Views:190
Avg rating:3.0/5.0
Slides: 15
Provided by: elliot8
Category:

less

Transcript and Presenter's Notes

Title: IP Encapsulation, Fragmentation, and Reassembly


1
IP Encapsulation, Fragmentation, and Reassembly
2
Frames
  • Datagrams must travel inside of frames
  • Each network may well have different frame format
  • Especially when transiting WANs
  • Entire datagram encapsulated inside frame native
    to local network it is transiting
  • Network pays no attention to datagram

3
Encapsulation
4
Encapsulation Continued
  • Router translates next hop IP address into
    physical address
  • Each hop encapsulated
  • Datagram stored in router sans frame
  • Frames do not accumulate
  • Dont confuse frame destination address with
    datagrams destination address

5
(No Transcript)
6
MTU
  • Each network hardware has maximum frame size
  • Termed Maximum Transmission Unit (MTU)
  • If datagram larger, cannot be encapsulated

7
MTU Example
8
Fragmentation
  • In order for datagram to transit network with
    small MTU, must be fragmented
  • Datagram broken into parts (fragments) and each
    moved independently
  • Fragment has same form as other datagrams
  • Total length, flags, fragment offset changed

9
Fragmentation Continued
  • Routers do fragmentation
  • They know MTUs
  • Ultimate destination host does reassembly
  • Termed opaque fragmentation
  • Allows routes to change
  • Fragments can be fragmented
  • May have smaller and smaller MTUs
  • Reassembly unaffected

10
Fragmenting Fragments
11
Reassembly
  • Each original packet has unique identifier ID
    field in datagram header
  • Each fragment has copy
  • Each fragment also has offset as to where it was
    in original
  • Last fragment does not have More Fragments bit set

12
Reassembly Continued
  • Fragments can be lost
  • Cant wait forever for arrival
  • Timer started, when times out, fragments
    discarded
  • Cant ask for fragment resend as sender unaware
    of fragmentation
  • Routes (and therefore level of fragmentation)
    will change too

13
Important Header Fields for Fragmentation see
Figure 20.4 (page 324)
  • Flags
  • Flag telling if data-gram is a fragment
  • Flag telling if more fragments (more fragments
    bit)
  • Identification (ID) Field unique across all
    fragments of one data-gram
  • Fragment offset field

14
Questions
  • 21.2, 21.3, 21.5, 21.8, 21.9, 21.10
Write a Comment
User Comments (0)
About PowerShow.com