| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
IP Message Fragmentation Process (Page 4 of 4) IP Header Flags Related to Fragmentation In addition to the fields above, there are a couple of flags in the IP header related to fragmentation. If a datagram containing options must be fragmented, some of the options may be copied to each of the fragments. This is controlled by the Copied flag in each option field. This flag can be set to 1 by a transmitting device to specify that a datagram not be fragmented in transit. This may be used in certain circumstances where the entire message must be delivered intact as pieces may not make sense. It may also be used if the destination device has a limited IP implementation and can't reassemble fragments, and is also used for testing the maximum transmission unit (MTU) of a link. Normally, however, devices don't care about fragmentation and this field is left at zero. What happens if a router encounters a datagram too large to pass over the next physical network but with the Don't Fragment bit set to 1? It can't fragment the datagram and it can't pass it along either, so it is stuck. It will generally drop the datagram, and then send back a special ICMP Destination Unreachable error message: Fragmentation Needed and Don't Fragment Bit Set. This is used in MTU Path Discovery as described in the preceding section.
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. |