Internet Protocol and Datagram Fragmentation

The Internet Protocol (IP) serves as the primary network-layer host-to-host routing and delivery system of the TCP/IP suite. This curriculum guide covers the structural format of IPv4 packets and the exact mechanics of datagram fragmentation when transitioning across heterogeneous network links with differing transfer capacities.

1. Overview of the Internet Protocol (IP) and Datagram Structure

The Internet Protocol (IP) provides a best-effort, connectionless packet delivery system. This means that IP does not guarantee reliable delivery, error-free transit, or sequential arrival of packets; these higher-level guarantees are left to the transport layer (e.g., TCP).

Packets at the IP layer are formally called datagrams. An IP datagram is a variable-length packet made of a header and payload data. The standard header ranges from $20$ to $60$ bytes in length, with any space beyond the core 20 bytes utilized for protocol options.

text

+-----------------------------------------------------------+
|                       IP Datagram                         |
+-----------------------------+-----------------------------+
|      Header (20-60 B)       |      Payload (Data)         |
|  - Controls, Routing, Flags |  - Encapsulated segments    |
+-----------------------------+-----------------------------+

2. Understanding IP Header Fields

To understand how packets travel through an internetwork, we must analyze the fields contained within the standard IPv4 header. The protocol formats headers in $4$ -byte ( $32$ -bit) blocks.

text

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Version|  HLEN |    ToS/DS     |          Total Length         |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|         Identification        |Flags|      Fragment Offset    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|  Time-to-Live |    Protocol   |        Header Checksum        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                         Source IP Address                     |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                      Destination IP Address                   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                    Options (Variable, 0-40 B)                 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Version ( $4$ bits): Defines the IP version. For IPv4, this is binary 0100 ( $4$ ).
Header Length / HLEN ( $4$ bits): Since the header can contain variable options, this field defines the total header size in terms of $32$ -bit ( $4$ -byte) words. The minimum value is $5$ (meaning $5 \times 4 = 20$ bytes) and the maximum value is ( bytes).

3. The Need for Datagram Fragmentation (MTU)

An IP datagram can travel through highly diverse networking links (such as Ethernet, Wi-Fi, Frame Relay, or ATM) on its route from source to destination. Each underlying physical network layer enforces its own limit on the maximum size of a frame payload. This limitation is known as the Maximum Transmission Unit (MTU).

text

[Host] ---> (Ethernet: MTU 1500) ---> [Router] ---> (WAN: MTU 576) ---> [Host]

When a router receives a datagram that is larger than the outgoing network link's MTU, it must break the datagram down into smaller units. This process is called Fragmentation.

Only the payload data of the datagram is divided.
Each resulting fragment becomes an independent IP packet with its own newly generated header, but with a shared Identification number.
Reassembly of these fragments back into the original datagram is performed exclusively at the destination host, rather than at intermediate routers, to minimize computational overhead.

4. Mechanics of Fragmentation: Identification, Flags, and Offset

Three primary fields in the IP header orchestrate fragmentation and reassembly:

Identification

This 16-bit field guarantees that fragments of the same original datagram can be grouped together at the destination host. All fragments of a parent datagram will share the exact same Identification number.

Flags

A 3-bit field organized as follows:

Bit 0: Reserved (must be set to $0$ ).
Bit 1 (Don't Fragment - DF): If set to $1$ , the router is forbidden from fragmenting this packet. If the packet exceeds the link MTU, the router discards it and returns an ICMP "Destination Unreachable" error.
Bit 2 (More Fragments - M): If set to $1$ , it means more fragments of this datagram follow. If set to $0$ , it indicates this packet is either the final fragment or that the packet was never fragmented.

Fragment Offset

A 13-bit field representing where this fragment's data belongs in the original payload. Because the offset field is only $13$ bits while the maximum payload size is $65,535$ bytes, the offset cannot represent single-byte increments. Instead, it measures distance in units of 8-byte blocks (often called eighth-byte units or octets).

Thus, the actual byte offset of a fragment is calculated as: $\text{Byte Offset} = \text{Fragment Offset} \times 8$

Because of this mapping, the payload data size of every intermediate fragment must be a multiple of 8 bytes.

text

Original Datagram:
+-----------------------------------------------------------+
| Header (20B) |         Payload Data (0 to 3999)           | (Total Length = 4020B)
+-----------------------------------------------------------+
 
Divided into 3 Fragments over an MTU of 1500 bytes:
 
Fragment 1:
+-----------------------+
| Header (20B) | Data 0 | (Bytes 0-1399) [Total Length = 1420, M = 1, Offset = 0]
+-----------------------+
 
Fragment 2:
+-----------------------+
| Header (20B) | Data 1 | (Bytes 1400-2799) [Total Length = 1420, M = 1, Offset = 175]
+-----------------------+
 
Fragment 3:
+-----------------------+
| Header (20B) | Data 2 | (Bytes 2800-3999) [Total Length = 1220, M = 0, Offset = 350]
+-----------------------+

Note on Offset Calculations:

Fragment 1 starts at byte $0$ . Offset is $0 / 8 = 0$ .
Fragment 2 starts at byte $1400$ . Offset is $1400 / 8 = 175$ .
Fragment 3 starts at byte $2800$ . Offset is $2800 / 8 = 350$ .

5. Algorithmic Fragmentation and Reassembly Process

To programmatically simulate how a router handles the division of an IP payload given an arbitrary MTU constraint, we can utilize the following calculation script written in Python. This demonstrates the division of payloads into $8$ -byte aligned blocks.

python

def fragment_ip_packet(payload_size, header_size, mtu):
    """
    Simulates IP datagram fragmentation over a specific link MTU.
    """
    max_payload_per_fragment = mtu - header_size
    # Must be a multiple of 8 bytes for intermediate fragments
    aligned_payload_size = (max_payload_per_fragment // 8) * 8
    
    if aligned_payload_size <= 0:
        raise ValueError("MTU is too small to carry even a single 8-byte aligned payload.")
        
    fragments = []
    bytes_remaining = payload_size
    current_byte = 0
    
    while bytes_remaining > 0:
        # Last fragment does not need to be a multiple of 8 bytes
        if bytes_remaining <= max_payload_per_fragment:

This automated structure verifies that each sub-block is correctly aligned, ensuring that routers on subsequent network hops can continue to fragment packets down further if they encounter even narrower MTU paths down the line.

Summary

The Internet Protocol (IP) acts as a best-effort, connectionless layer-3 routing framework.
IP Datagrams consist of a $20$ -to- $60$ byte header containing critical delivery markers, followed by variable payload data up to $65,535$ total bytes.
The Maximum Transmission Unit (MTU) defines the limits of underlying link layers. Whenever a packet size exceeds this capacity, fragmentation must occur.
The Fragment Offset represents payload position in multiples of $8$ bytes. As a direct consequence, all intermediate fragment sizes must be divisible by $8$ .
Reassembly of fragmented packets is deferred entirely to the final destination host to prevent routing latencies.

Assessed progress

Internet Protocol and Datagram Fragmentation

Internet Protocol and Datagram Fragmentation

1. Overview of the Internet Protocol (IP) and Datagram Structure

2. Understanding IP Header Fields

3. The Need for Datagram Fragmentation (MTU)

4. Mechanics of Fragmentation: Identification, Flags, and Offset

Identification

Flags

Fragment Offset

5. Algorithmic Fragmentation and Reassembly Process

Summary

Key Concepts

IP Datagram Structure

Maximum Transmission Unit (MTU)

Header Length (HLEN)

Fragmentation Flags

Fragment Offset

Quick Check

Computer Networks

Computer Networks