NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Enjoy The TCP/IP Guide? Get the complete PDF!
The TCP/IP Guide

Google
Web TCP/IP Guide






Table Of Contents  The TCP/IP Guide
 9  TCP/IP Lower-Layer (Interface, Internet and Transport) Protocols (OSI Layers 2, 3 and 4)
      9  TCP/IP Internet Layer (OSI Network Layer) Protocols
           9  Internet Protocol (IP/IPv4, IPng/IPv6) and IP-Related Protocols (IP NAT, IPSec, Mobile IP)
                9  Internet Protocol Version 4 (IP, IPv4)

Previous Topic/Section
IP Datagram Options and Option Format
Previous Page
Pages in Current Topic/Section
1
Next Page
IP Datagram Size, the Maximum Transmission Unit (MTU), and Fragmentation Overview
Next Topic/Section

IP Datagram Size, Maximum Transmission Unit (MTU), Fragmentation and Reassembly

IP's main responsibility is to deliver data between internetworked devices. As we saw in the preceding section, this requires that data received from higher layers be encapsulated into IP datagrams for transmission. These datagrams are then passed down to the data link layer where they are sent over physical network links.

In order for this to work properly, each datagram must be small enough to fit within the frame format of the underlying technology. If the message is bigger than the maximum frame size of the underlying network, it may be necessary to break up an IP message into several datagrams, a process called fragmentation. The datagrams are then sent individually and reassembled into the original message.

The Internet Protocol is designed to manage datagram size, and to allow fragmentation and reassembly in a seamless manner. In this section I explore issues related to managing the size of IP datagrams. I start with an overview of datagram size issues and the important concept of a network's maximum transmission unit (MTU), discussing why fragmentation is necessary. I then describe the process by which IP messages to be transmitted are fragmented by the source device and possibly routers along the path to the destination, and then outline how they are reassembled by the recipient.

Background Information: Explaining fragmentation and reassembly requires some understanding of the basic format of IP datagrams and some of the fields they contain. If you haven't yet read the topic describing IP datagram general format you may wish to review it before proceeding here.


Quick navigation to subsections and regular topics in this section



Previous Topic/Section
IP Datagram Options and Option Format
Previous Page
Pages in Current Topic/Section
1
Next Page
IP Datagram Size, the Maximum Transmission Unit (MTU), and Fragmentation Overview
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.