IP fragmentation is the process of dividing large IP datagrams into smaller fragments to fit through network links with smaller Maximum Transmission Units (MTUs). While fragmentation is necessary when Path MTU Discovery fails, it introduces overhead, performance degradation, and potential reliability and security issues. IPv6 handles fragmentation differently by placing the responsibility on the source host and not allowing routers to fragment packets.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
9 views2 pages
Fragment I On
IP fragmentation is the process of dividing large IP datagrams into smaller fragments to fit through network links with smaller Maximum Transmission Units (MTUs). While fragmentation is necessary when Path MTU Discovery fails, it introduces overhead, performance degradation, and potential reliability and security issues. IPv6 handles fragmentation differently by placing the responsibility on the source host and not allowing routers to fragment packets.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2
You're likely asking about IP fragmentation.
Let's break down what that means in the context of
computer networking and the Internet Protocol (IP). IP Fragmentation Explained: IP fragmentation is the process of breaking down a single IP datagram (a packet of data) into smaller pieces, called fragments, so that the resulting fragments can pass through a network link with a smaller Maximum Transmission Unit (MTU). Why is Fragmentation Necessary? ● Maximum Transmission Unit (MTU): Every network link (e.g., Ethernet, Wi-Fi, PPP) has a maximum size of the data unit it can carry in a single frame. This is the MTU. ● Path MTU Discovery (PMTU): Ideally, the sending host should determine the smallest MTU along the entire path to the destination and send packets no larger than that. This process is called Path MTU Discovery (PMTU). ● When PMTU Fails: Sometimes, PMTU discovery fails (e.g., due to firewalls blocking ICMP messages used for PMTU). In such cases, if a router encounters a packet larger than the MTU of the next link in the path, it has two options: 1. Drop the packet: This can lead to retransmission and performance issues. 2. Fragment the packet: Break the packet into smaller fragments that fit within the MTU. How Fragmentation Works (IPv4): When an IPv4 packet is fragmented, the following fields in the IP header are used to manage the process: ● Identification: A 16-bit field that uniquely identifies the original IP datagram. All fragments of the same original datagram will have the same Identification value. ● Flags: A 3-bit field. The "Don't Fragment" (DF) flag indicates that the packet should not be fragmented. If a router encounters a packet with the DF flag set and it's too large for the next link's MTU, the router will drop the packet and typically send an ICMP "Fragmentation Needed and DF Set" message back to the sender. The "More Fragments" (MF) flag indicates that this is not the last fragment. The last fragment will have the MF flag set to 0. ● Fragment Offset: A 13-bit field that indicates the position of the fragment's data relative to the beginning of the original IP datagram. This allows the receiving host to reassemble the fragments in the correct order. The offset is measured in units of 8 bytes. Reassembly: The reassembly of IP fragments happens at the destination host, not at intermediate routers. The destination host uses the Identification field, Fragment Offset, and More Fragments flag to collect all the fragments belonging to the original datagram and put them back together in the correct order. The reassembled datagram is then passed to the upper-layer protocol (e.g., TCP or UDP). Fragmentation in IPv6: IPv6 handles fragmentation differently: ● Routers Don't Fragment: In IPv6, routers are not allowed to fragment packets. If an IPv6 packet is too large for a link's MTU, the router will drop the packet and send an ICMPv6 "Packet Too Big" message back to the source. ● Source Host Responsibility: The responsibility of fragmentation in IPv6 lies with the source host. The source host should perform Path MTU Discovery and send packets that fit within the smallest MTU along the path. If PMTU discovery fails or the source chooses to send a larger packet, it must fragment the packet itself before sending it. ● Fragmentation Header: IPv6 uses a separate Fragmentation Header to carry the information needed for reassembly (Identification, Fragment Offset, and a More Fragments flag). This keeps the base IPv6 header simpler. Drawbacks of Fragmentation: While fragmentation can be necessary in certain situations, it has several drawbacks: ● Increased Overhead: Each fragment has its own IP header, adding to the total overhead. ● Performance Degradation: Fragmentation and reassembly consume processing resources at both the fragmenting router (in IPv4) and the destination host. ● Reliability Issues: If even one fragment of an original datagram is lost, the entire original datagram is lost, requiring retransmission of all fragments. This can be particularly problematic on unreliable links. ● Security Risks: Fragments can be exploited for certain types of attacks. In summary, IP fragmentation is a mechanism to allow large IP datagrams to traverse network links with smaller MTUs. While it serves a purpose in ensuring deliverability in some scenarios, it's generally less efficient and can introduce reliability and security concerns. Modern networks and protocols increasingly rely on Path MTU Discovery to avoid fragmentation whenever possible.