Ip – Confusion about data fragmentation/MTUs – why was it introduced in the first place

fragmentationiplayer2layer3mtu

I am currently studying networking as a part of my bachelors and I am a bit confused about why fragmentation/MTUs are necessary. In my lecture slides, it only says "Fragmenting if necessary" under the "Functions of the Network Layer" and when re-listening to the lecture recording, the lecturer does not really expand on it much. Our course textbook is Tanenbaum's "Computer networking" which also provides no extra information.

I read the Wikipedia article on MTUs and I now understand the core concept, however, I fail to understand why were fragmentation and MTUs introduced in the first place. Intuitively, I can understand how if there is a huge chunk of data and a small error occurs, you would have to re-send the whole enormous packet which is wasteful. Is this correct? And what are the other reasons why fragmentation is used? What would happen in a hypothetical network that does not fragment data/have MTUs – is it even possible for the physical layer to handle that?

Best Answer

One of the two basic functions for IPv4 is packet fragmentation (the other is addressing). IP is designed to send packets from one network to another network. Each network can have a different maximum packet size.

For example. the original serial WAN connections could have maximum packet sizes of greater than 4000 bytes, but ethernet specifies a maximum packet size of 1500 bytes. If a host on a network sends a 4000 byte packet to an ethernet network where the maximum packet size is 1500 bytes, without fragmentation, the router would need to simply drop the packet. With fragmentation, the router can fragment the packet into smaller packets that can be sent on the ethernet network.

RFC 791, Internet Protocol explains about fragmentation:

The internet protocol also provides for fragmentation and reassembly of long datagrams, if necessary, for transmission through "small packet" networks.

-and-

The internet protocol implements two basic functions: addressing and fragmentation.

-and-

The internet modules use fields in the internet header to fragment and reassemble internet datagrams when necessary for transmission through "small packet" networks.

-and-

In the routing of messages from one internet module to another, datagrams may need to traverse a network whose maximum packet size is smaller than the size of the datagram. To overcome this difficulty, a fragmentation mechanism is provided in the internet protocol.

and so on...

Remember that IPv4 was a government/academic experiment that escaped the lab and got out of control. It was never envisioned to be the Internet we have today. After seeing the strengths and weaknesses in IPv4, the IETF designed IPv6, which has eliminated packet fragmentation in the path (requiring the use of PMTUD to determine the smallest maximum packet size in the path prior to sending), among other improvements to IP.

Edit for your clarification of MTU:

The MTU was not "introduced" as you have implied. The MTU is a function of the maximum payload size of a layer-2 protocol. Each protocol must have a maximum payload size. For ethernet, it was determined that 1500 octets struck a good balance on the amount of data that can be transferred without monopolizing the medium. Other designers of layer-2 protocols make their own determinations as to the maximum payload size for a frame for their layer-2 protocols.

IP, as a layer-3 protocol (the payload of a layer-2 protocol), must simply live with the MTU of the layer-2 protocols used to carry it. IP has no idea which layer-2 protocol is carrying it, or which other layer-2 protocols may be used in the path to the destination of the IP packet.

Remember that IP was designed by a government program in conjunction with universities and the telco, but that program had nothing to do with the designs of the layer-2 protocols in use today. IP was designed to be carried by any layer-2 protocol.

Related Solutions

Ethernet – Why was the MTU size for ethernet frames calculated as 1500 bytes

The answer is in draft-ietf-isis-ext-eth-01, Sections 3-5. Ethernet uses the same two bytes different ways in the Ethernet II (DIX) and 802.3 encapsulations:

Ethernet II uses the first two bytes after the Ethernet source mac-address for a Type
802.3 uses those same two bytes for a Length field.

I'm including an annotated diagram below of each frame type, which shows exactly where the conflicting bytes are in the ethernet header:

RFC 894 (commonly known as Ethernet II frames) use these bytes for Type

    +----+----+------+------+-----+
    | DA | SA | Type | Data | FCS |
    +----+----+------+------+-----+
              ^^^^^^^^

    DA      Destination MAC Address (6 bytes)
    SA      Source MAC Address      (6 bytes)
    Type    Protocol Type           (2 bytes: >= 0x0600 or 1536 decimal)  <---
    Data    Protocol Data           (46 - 1500 bytes)
    FCS     Frame Checksum          (4 bytes)

IEEE 802.3 with 802.2 LLC / SNAP (used by Spanning-Tree, ISIS) use these bytes for Length

    +----+----+------+------+-----+
    | DA | SA | Len  | Data | FCS |
    +----+----+------+------+-----+
              ^^^^^^^^

    DA      Destination MAC Address (6 bytes)
    SA      Source MAC Address      (6 bytes)
    Len     Length of Data field    (2 bytes: <= 0x05DC or 1500 decimal)  <---
    Data    Protocol Data           (46 - 1500 bytes)
    FCS     Frame Checksum          (4 bytes)

Both Ethernet II and 802.3 encapsulations must be able to exist on the same link. If IEEE allowed Ethernet payloads to exceed 1536 bytes (0x600 hex), then it would be impossible to distinguish large 802.3 LLC or SNAP frames from Ethernet II frames; ethernet's Type values start at 0x600 hex.

EDIT:

I am including a link to pdf copies of the Ethernet Version 1 spec and Ethernet Version 2 spec, in case anyone is interested...

Ethernet – Why is the Ethernet data frame size limited to 1500 bytes

"Data transparency" in this context means that Ethernet doesn't care what kind of data it transports. You put any payload in a frame, send it to the destination and extract the exact same payload.

Initially, the maximum frame size was a trade-off between efficiency and latency. The larger a frame, the lower the overhead, the better the effiency. However, early Ethernet was a shared medium, so any frame in transit occupied the whole segment - the longer the frame, the longer the network was blocked and other senders had to wait. Additionally, early Ethernet NICs required fast local memory for buffering a frame. Ethernet was aiming to reduce prices, so then-expensive RAM had to be kept at a reasonable minimum.

When switches were introduced in the early 1990s, the maximum size had to be kept for compatibility reasons: a sender has no way to tell whether the frames it sends are going over a shared medium (anywhere) or whether they are switched at all times. Hardware buffers have to sized to maximum frame size as well and can't change on the fly.

Best Answer

Related Solutions

Ethernet – Why was the MTU size for ethernet frames calculated as 1500 bytes

Ethernet – Why is the Ethernet data frame size limited to 1500 bytes

Related Topic