# Patent

## Title
Filtering superfluous data fragments on a computer network

## Abstract

Methods and apparatus for controlling transmission of data units in a network. In one embodiment, a method of controlling transmission of data units in a network node includes receiving a fragment of a data unit. The method further includes determining at least one of (a) whether a prior fragment of the data unit has been dropped and (b) whether a subsequent fragment of the data unit is likely to be dropped. The method further includes at least one of (c) transmitting the received fragment of the data unit only if no prior data fragment of the data unit has been dropped and (d) transmitting the fragment of the data unit only if no subsequent fragment of the data unit is likely to be dropped.

## Background
CROSS-REFERENCE TO RELATED APPLICATION
This application claims the benefit of U.S. Provisional Patent Application No. 61/095,461, entitled “IP Reassembly Problem in Network Without Flow Control,” which was filed on Sep. 9, 2008, the entire disclosure of which is hereby incorporated by reference herein.


FIELD OF THE DISCLOSURE
The present disclosure relates generally to communication networks and, more particularly, to filtering superfluous data fragments on a computer network.
BACKGROUND
In communication networks, data units (e.g., IP packets) may be fragmented for various reasons. When fragmented data units are received, it may be necessary to efficiently reassemble the fragmented packets.
One problem associated with fragmentation is that loss of fragments can lead to inefficient use of resources. In particular, if a fragment of a data unit is lost during transmission across a computer network, different devices in the computer network may continue processing and forwarding other fragments of the transmitted data unit, even though such fragments are rendered superfluous (i.e., they will ultimately be dropped, e.g., by the target host, because they will not be able to reconstruct a complete data unit). As a result, target hosts and devices on the network may waste potentially valuable resources (e.g., computational resources, storage resources, and so on) processing superfluous fragments. Moreover, these superfluous fragments may needlessly consume bandwidth and contribute to network delay and congestion and potentially prevent important data from being received in a timely manner.
SUMMARY
The present disclosure provides methods and apparatus for controlling transmission of data units in a network.
In one embodiment, a method of controlling transmission of data units in a network node includes receiving a fragment of a data unit. The method further includes determining at least one of (a) whether a prior fragment of the data unit has been dropped and (b) whether a subsequent fragment of the data unit is likely to be dropped. The method further includes at least one of (c) transmitting the received fragment of the data unit only if no prior data fragment of the data unit has been dropped and (d) transmitting the received fragment of the data unit only if no subsequent fragment of the data unit is likely to be dropped.
In another embodiment, an apparatus includes at least one ingress interface to receive data units and at least one egress interface to transmit data units. The apparatus further includes a forwarding engine to forward data units received via the ingress interface to the egress interface. The forwarding engine includes a fragment filtering engine. The fragment filtering engine is configured to determine, in response to receiving a fragment of a data unit, at least one of (a) whether a prior fragment of the data unit has been dropped and (b) whether a subsequent fragment of the data unit is likely to be dropped. The fragment filtering engine is further configured to perform at least one of (c) drop the received fragment of the data unit if it is determined that the prior fragment of the data unit has been dropped and (d) drop the received fragment of the data unit if it is determined that the subsequent fragment of the data unit is likely to be dropped.
In another embodiment, a method of controlling transmission of data units includes receiving a fragment of a data unit. The method further includes determining whether other fragments of the data unit have been received. The method further includes transmitting the fragment of the data unit only if other fragments of the data unit have been received.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of an example computer network;
FIG. 2 is a simplified block diagram of an example network node that is adapted to filter superfluous data fragments;
FIG. 3 is a flow diagram of an example method of filtering superfluous data fragments;
FIG. 4 is a flow diagram of another example method of filtering superfluous data fragments; and
FIG. 5 is a flow diagram of yet another example method of filtering superfluous data fragments.



Like reference numbers and designations in the various drawings indicate like elements. Furthermore, when individual elements are designated by references numbers in the form Nn, these elements may be referred to in the collective by N. For example, FIG. 1 includes hosts 105a-c that may be referred to collectively as hosts 105.
DETAILED DESCRIPTION
FIG. 1 is a block diagram of an example computer network 100. The computer network 100 may include a number of hosts 105 coupled via a number of network nodes 110. Hosts 105 may be coupled to network nodes 110 via various kinds of network interfaces 120 (e.g., an Ethernet interface, a wireless interface, and so on). A given host 105 may be coupled to a network interface 120 via a direct communication link. A given host 105 may also be coupled to a network interface 120 via other network nodes 110 or systems, other networks (e.g., local area networks 130), etc.
The hosts 105 may be a variety of devices and/or systems, including personal computers, laptops, printers, copier systems, scanners, personal digital assistants (PDAs), wireless devices, fax machines, and so on. A given host 105 may act as a source host that transmits a communication and/or as a target host that receives the communication. The hosts 105 generally communicate via the computer network 100 by sending and receiving data in data units, e.g., packets, frames, datagrams, cells, and so on. The hosts 105 may communicate wirelessly (e.g., using radio signals), via wired links, or both.
The network nodes 110 generally facilitate communication between the hosts 105, as well as between other devices, systems, network segments, subnets, and so on. Network nodes 110 may be located at the edge of the computer network 100, or they may be part of a network backbone interconnecting different networks and nodes. It will be appreciated that the network nodes 110 described herein are not limited to any particular protocol layer or to a particular networking technology. Moreover, the network nodes 110 may operate simultaneously at multiple protocol layers, and may couple together networks of different types, including Ethernet, Fiber Channel, Asynchronous Transfer Mode (ATM) networks, wireless local area networks, and so on. Examples of network nodes 110 include hubs, repeaters, bridges, routers, firewalls, modems, wireless access points, and so on.
In some instances, in order to manage network traffic, the computer network 100, or portions of the computer network 100, may impose a maximum size for a data unit that the computer network 100, or a portion thereof, will support. This imposed maximum data unit size is commonly referred to as the Maximum Transmission Unit (MTU). The MTU may be based on a number of factors, including hardware capabilities of devices on the computer network 100, requirements of particular protocols and/or standards, Quality of Service (QoS) constraints, and so on. For example, a given network may impose an MTU to prevent large data units from monopolizing a transmission medium for a significant period of time and thus delaying transmission of other data units. An MTU may be fixed by a standard (e.g., Ethernet) or decided at connect time, for example.
In some embodiments, when a particular data unit exceeds the size of an MTU of the computer network, or portions thereof, the data unit may be fragmented into two or more fragments, where none of the fragments exceed the MTU, and the different fragments may be then treated as individual data units. For example, when a relatively large data unit arrives at an interface to a network with an MTU lower than the size of the data unit, the relatively large data unit may be divided into smaller fragments, and the individual fragments may pass through the interface as separate data units. As a result, in some instances, a flow of data through a given interface may include a mix of fragments of different data units. Consequently, different data units may efficiently share the interface. Larger individual packets can be prevented from blocking the interface for a long period of time, and overall latency may generally be reduced.
A particular data unit may exceed the size of an MTU of the computer network 100, or portions thereof (and thus require fragmentation), for a number of reasons. For example, a source host 105 may transmit data units of size specified by a certain protocol, and that protocol may specify relatively large data units (as compared to the capacities of the computer network 100 or portions thereof). Also, different protocols, such as tunneling protocols, may attach additional headers (e.g., tunnel headers) to data units, causing these data units to exceed an MTU of a network, even if the data unit would not exceed the MTU in the absence of the attached header.
Fragmentation of data units may be performed at various points in the computer network 100 and/or by various devices and systems. For example, fragmentation may be performed by a network node 110 when the network node 110 receives a relatively large data unit and determines that the received data unit needs to be forwarded over a network with a relatively small MTU (e.g., an MTU that is smaller than the size of the received data unit). Alternatively, or in addition, a source host 105 that initially transmits a data unit (and chooses the size of the data in accordance with a particular protocol) may fragment the data unit if, for example, the source host 105 is coupled to a subnet with an MTU that is smaller than the size of the data unit.
Furthermore, fragmentation of data units may be performed at multiple points in the computer network 100 and/or by multiple devices and systems. For example, a source host 105 that initially transmits a data unit over a subnet that has an MTU smaller than the size of the transmitted data unit may break the data unit into fragments that do not exceed the MTU of the subnet and then transmit the individual fragments separately. As the fragments travel across the computer network 100, the fragments themselves may be further fragmented into smaller fragments. For example, if a network node 110 receives a fragment, and the network node 110 determines that the received fragment needs to be forwarded over a subnet with an MTU that is smaller than the size of the fragment, the network node 110 may further break the fragment into smaller fragments.
Fragments that travel across the computer network 100 may be reassembled, e.g., back to the original data unit, at various points in the computer network 100 and/or by various network devices and systems. For example, fragments may be reassembled at their final destination (e.g., by a target host 105). Alternatively, or in addition, fragments may be reassembled at various, and by multiple, intermediate devices (e.g., network nodes 110) and/or systems.
In some implementations, when data units are fragmented, data specific to fragmentation may be added to the resulting fragments (e.g., to the headers of the resulting fragments) to enable later reassembly. For example, the header of a fragment may include data that identifies the source host 105 of the data unit. The header of a fragment may further include data that identifies the original data unit associated with the fragment. In some embodiments, one or more combinations of fields of a fragment header may be combined or otherwise used to form a unique identifier of the original data unit associated with the fragment.
The header of a fragment may also include data that identifies which portion of the data from the original data unit is carried in the fragment. In some embodiments, for example, a fragment of a given data unit may carry in its header the position (e.g., in bytes) of the fragment in the data field of the original data unit (sometimes referred to as “offset”). Additional information that may be carried in the header of a fragment may include the total number of fragments associated with the data unit, the size of the fragment, some sort of an indicator (e.g., a Boolean field) that the fragment is, in fact, a fragment of a larger data unit, and so on. Some or all of the information inside the headers of fragments may be used by devices (e.g., network nodes 110) and systems to reassemble the fragments, e.g., into a larger fragment or the original data unit.
One problem that may be associated with fragmentation of data units is that loss of fragments can lead to inefficient use of resources. In particular, if a fragment of a data unit transmitted from a source host to a destination host is lost during transmission across the computer network 100, different devices in the computer network 100 (and the destination host) may continue processing and forwarding other fragments of the transmitted data unit, even if the data unit will ultimately be dropped by the target host because of the lost fragment. As a result, the target host and devices in the computer network 100 may waste potentially valuable resources (e.g., computational resources, storage resources, and so on) processing superfluous fragments. Moreover, these superfluous fragments may needlessly consume bandwidth and contribute to network delay and congestion and potentially prevent important data from being received in a timely manner.
Loss of fragments (and data units in general) may be caused by a number of factors, including signal degradation over the network medium, oversaturated network links, corrupted packets rejected in-transit, faulty networking hardware, maligned system drivers or network applications, and so on. Another cause of fragment loss is incapacity of a network node 110 to process and/or forward fragments at the same rate as the network node 110 receives those fragments. For example, if a network node 110 receives fragments via a wired local area network (e.g., Ethernet) interface 120 and forwards these fragments via a wireless interface 120, the network node 110 may be receiving fragments at a faster rate than the network node 100 may be able to forward them. As a result, the network node 110 may drop some of the received fragments.
In order to use network resources more efficiently, a network node 110 may implement a fragment-filtering scheme to minimize the transmission of superfluous fragments. The fragment-filtering scheme may be implemented in a number of ways. Details of several example implementations are described below.
FIG. 2 is a simplified block diagram of an example network node 200 that is adapted to filter superfluous fragments and to minimize the transmission of such fragments. The network node 200 may be utilized in the computer network 100 as one or more of the network nodes 110, for example. It will be understood, however, that the computer network 100 may alternatively use one or more other network nodes different than the network node 200 and configured to filter superfluous fragments. In general, the computer network 100 may include many different types of network nodes 110, one or more of which may be configured to filter superfluous fragments.
The network node 200 includes one or more ingress interfaces 230 and one or more egress interfaces 240. The ingress interfaces 230 are generally for receiving data units, and the egress interfaces 240 are generally for transmitting data units. The ingress interfaces 230 and the egress interfaces 240 are coupled together via a forwarding engine 225, which generally transfers data units from the ingress interfaces 230 to appropriate egress interfaces 240, and which may perform additional data processing functions. The network node 200 also may include a central processing unit (CPU) 205 coupled to the forwarding engine 225. The CPU 205 may execute computer readable instructions stored in a memory 210 coupled to the CPU 205.
The forwarding engine 225 generally performs wire speed functions associated with transferring data units from ingress interfaces 230 to egress interfaces 240, whereas the CPU 205 generally performs functions that can tolerate higher latency. The memory 210 also may be coupled to the forwarding engine 225. The forwarding engine 225 may be implemented in hardware, e.g., on a single application specific integrated circuit (ASIC) coupled to the CPU 205. In other embodiments, other types of integrated circuits may be used such as a field programmable gate array (FPGA), a programmable logic array (PLA), a custom integrated circuit, etc. In other embodiments, the forwarding engine 225 may be implemented on multiple different integrated circuits that are coupled together.
The forwarding engine 225 includes a fragment filtering engine 220 generally configured to filter superfluous fragments and to minimize transmission of such fragments. Generally speaking, the fragment filtering engine 220 monitors incoming data fragments and drops data fragments if other data fragments associated with the same data unit have been dropped, or are likely to be dropped in the future. Operations of the fragment filtering engine 220 will subsequently be described in more detail.
FIG. 3 is a flow diagram illustrating an example method 300 that may be implemented by the filtering engine 220 to filter superfluous data fragments. For ease of explanation, FIG. 3 will be described with reference to FIGS. 1-2. It will be understood, however, that the method 300 may be utilized with systems and devices other than those illustrated in FIGS. 1-2.
Generally speaking, a filtering engine 220 operating in accordance with the method 300 in FIG. 3 may accumulate a certain number of the data fragments associated with a given data unit (e.g., a predetermined percentage) before forwarding any of the fragments associated with that data unit. More specifically, when the network node 200 receives a fragment of a data unit (block 310), the filtering engine 220 may determine whether a certain predetermined percentage (e.g., 90%) of other fragments of that data unit has been received (block 320) and only forward the new fragment (block 330) if that percentage of other fragments has been received (YES branch of block 320). In some embodiments, in order to significantly minimize the transmission of superfluous fragments, or to prevent any such transmission, the filtering engine 220 may forward newly received fragments only if, or when, all of the other fragments associated the same data unit (i.e., 100%) have been received.
If the network node 200 receives a fragment of a data unit (block 310), and the predetermined percentage (e.g., 90%) of other fragments of that data unit has not been received (NO branch of block 320), the filtering engine 220 may store the received fragment (e.g., in memory 210) and delay the forwarding of the fragment (block 340) to give other fragments some time to arrive. If the other fragments arrive within a certain (e.g., predefined) period of time (YES branch of block 350), then the received fragment (and all other fragments of the associated data unit) may be transmitted (block 330). However, if the other fragments do not arrive within a certain period of time (NO branch of block 350), the filtering engine 220 may drop the fragment (block 360), as well as other fragments of the associated data unit.
In order to implement the method 300 discussed in reference to FIG. 3, the filtering engine 220 may determine various attributes of the data unit associated with the fragment received in block 310. For example, in order to determine the percentage of fragments of that data unit that have been received, the filtering engine 220 may need to determine the total number of fragments that make up the data unit in question. Such information may be determined from the information in the header of the received fragment. For example, as discussed above, the header may include information about the total length (e.g., in bytes) of the data unit, the length of the header of the data unit, the MTU, the offset of the fragment, and so on. Thus, in one embodiment, the total number of fragments that make up the data unit associated with the received fragment may be calculated as the total length of the data unit (e.g., in bytes) divided by the difference of the MTU and the length of the header of the data unit.
FIG. 4 is a flow diagram illustrating another example method 400 the filtering engine 200 may use to filter superfluous data fragments. For ease of explanation, FIG. 4 will be described with reference to FIGS. 1-2. It will be understood, however, that the method 400 may be utilized with systems and devices other than those illustrated in FIGS. 1-2.
Generally speaking, a filtering engine 220 operating in accordance with the method 400 in FIG. 4 may keep track (e.g., in memory 210) of the fragments that the network node 200 drops and filter incoming fragments that are associated with the same data units. More specifically, when the filtering engine 220 receives a fragment of a particular data unit (block 410), the filtering engine 220 may determine whether any other fragments of that data unit have been dropped by the network node 200 (block 420) and only transmit the received fragment (block 430) if no other data fragment of the data unit has been dropped (NO branch of block 420). Otherwise, if at least one data fragment of the data unit has been dropped, the filtering engine 220 may drop the received fragment (block 440).
FIG. 5 is a flow diagram illustrating another example method 500 the filtering engine 220 may use to filter superfluous data fragments. For ease of explanation, FIG. 5 will be described with reference to FIGS. 1-2. It will be understood, however, that the method 500 may be utilized with systems and devices other than those illustrated in FIGS. 1-2.
Generally speaking, a filtering engine 220 operating in accordance with the method 500 in FIG. 5 may monitor the resources of the associated network node 200 and process and transmit a received fragment of a data unit only if the network node 200 has the resources to process and transmit other fragments of the same data unit. More specifically, when the filtering engine 220 receives a fragment of a data unit (block 510), the filtering engine 220 may first determine whether the received fragment is the first fragment of the data unit (block 520). This can be determined by looking at the information in the header of the received fragment. For instance, this can be determined by looking at the offset value discussed above.
If the received fragment is the first fragment of the data unit (YES branch of block 520), the filtering engine 220 may refrain from processing and transmitting the received fragment unless the network node 110 has enough resources to process and transmit other fragments of the data unit. Therefore, the filtering engine 220 may first check whether the network node 200 has the resources to process and transmit other fragments of the data unit (block 530). If so (YES branch of block 530), the filtering engine 220 may ultimately transmit the received fragment (block 560). Otherwise (NO branch of block 530), the filtering engine 220 may drop the received fragment (block 570).
In some embodiments, checking whether the network node 200 has the resources to process and transmit other fragments of the data unit (block 530) may include checking whether the network node 200 has the resources to process and transmit all the fragments of the data unit. However, in some embodiments checking whether the network node 200 has the resources to process and transmit other fragments of the data unit (block 530) may include checking whether the network node 200 has the resources to process and transmit a portion of the fragments of the data unit (e.g., a predefined percentage). For example, if the network node 200, under optimal conditions, has the resources to process and transmit all fragments of the data unit but only currently has the resources, for example, to process and transmit 90% of the fragments, the filtering engine 220 may nonetheless transmit the received fragment based on past performance history indicating that sufficient resources will likely become available before the network node 200 starts dropping fragments.
In some embodiments, checking whether the network node 200 has the resources to process and transmit other fragments of the data unit (block 530) may include checking whether the network node 200 has enough storage capacity (e.g., in memory 210) to temporarily store the other fragments of the data unit as the fragments are being transferred from an ingress interface 230 to an egress interface 240. Accordingly, the filtering engine 220 may, for example, attempt to allocate memory for storing all the fragments of the data unit. If the filtering engine 220 is able to allocate that memory, the filtering engine 220 may determine that the network node 200 has sufficient resources to process and transmit all the fragments of the data unit (YES branch of block 530). Otherwise, the filtering engine 220 may determine that the network node 200 does not have sufficient resources to process and transmit all fragments of the data unit (NO branch of block 530), and the filtering engine 220 may drop the received fragment (block 570).
If the filtering engine 220 determines that the network node 200 has the resources to process and transmit all the fragments of the data unit (YES branch of block 530), the filtering engine 220 may perform further operations in addition to transmitting the fragment (block 560). The filtering engine 220 may actually reserve the necessary resources (e.g., allocate memory) for the other fragments (block 540). The filtering engine 220 may further create a fragmentation context data structure for the data unit that generally includes fragmentation information about the data unit. Fragmentation information about the data unit may include one or more of: the number of fragments, the number of received and/or transmitted fragments, the size of fragments, the next expected fragment, and so on. Accordingly, the fragmentation context data structure may be useful to determine the status of a given data unit when the filtering engine 220 receives a new fragment for that data unit that is not the first fragment of that data unit.
More specifically, when the filtering engine 220 receives a new fragment of a data unit (block 510), and the filtering engine 220 determines (e.g., from the offset value in the header of the fragment) that the received fragment is not the first fragment of the data unit (NO branch of block 520), the filtering engine 220 may check if a fragmentation context data structure exists for that data unit (block 525). If a fragmentation context data structure does not exist (NO branch of block 525), the filtering engine 220 may interpret it as an indication that resources (e.g., space in memory) were not reserved previously for the fragments of the data unit, and that some of the fragments of the data unit might have been consequently dropped. As a result, the filtering engine 220 may drop the received fragment (block 570).
On the other hand, if a fragmentation context data structure does exist for the data unit associated with the received fragment (YES branch of block 525), the filtering engine 220 may interpret it as an indication that resources (e.g., space in memory) were reserved previously for the fragments of the data unit. As a result, the filtering engine 220 may ultimately transmit the received fragment (block 560).
In some embodiments, the filtering engine 220 may transmit the received fragment (block 560) only after performing further operations and/or after additional conditions have been met. In particular, the filtering engine 220 may check if the received fragment is the fragment that was expected (block 590). For example, if fragment N was the last received fragment, then fragment N+1 may be expected next. As explained above, the fragmentation context data structure may include information about which fragment is expected next, so the filtering engine 220 may use the fragmentation context data structure to determine whether the received fragment is, in fact, the fragment that was expected.
If the received fragment was expected (YES branch of block 590), then the filtering engine 220 may transmit the fragment (block 560) and update the fragmentation context data structure with information about a new expected fragment (e.g., N+2) and, potentially, other information (block 580). On the other hand, if the received fragment was not expected (NO branch of block 590), the filtering engine 220 may interpret the arrival of an unexpected fragment as an indication that the expected fragment was lost. As a result, the filtering engine 220 may drop the received fragment (block 570).
Although fragment-filtering techniques were described above with reference to the network node 200, these techniques may be utilized in other types of network devices such network nodes different than the network node 200, routers, network bridges, wireless access points, etc. Moreover, while the present invention has been described with reference to specific examples, which are intended to be illustrative only and not to be limiting of the invention, it will be apparent to those of ordinary skill in the art that changes, additions and/or deletions may be made to the disclosed embodiments without departing from the spirit and scope of the invention.

## Claims

1. A method of controlling transmission of data units in a network node, the method comprising:
receiving a fragment of a data unit, wherein the data unit has been previously fragmented into an ordered sequence of fragments;
determining whether the received fragment is a first fragment in the ordered sequence of fragments; and
when it is determined that the received fragment is the first fragment in the ordered sequence of fragments,
determining whether the network node has sufficient resources, as of the time when the first fragment is received, to process a predefined percentage of all fragments in the ordered sequence of fragments, and
dropping the first fragment when it is determined that the network node does not have sufficient resources, as of the time when the first fragment is received, to process the predefined percentage of all fragments in the ordered sequence of fragments.

2. The method of claim 1, further comprising:
when it is determined that the received fragment is the first fragment in the ordered sequence of fragments, creating a data structure corresponding to the data unit, wherein the data structure provides information regarding fragmentation of the data unit into the ordered sequence of fragments;
when it is determined that the received fragment is not the first fragment in the ordered sequence of fragments, determining whether the fragmentation data structure for the data unit was created prior to receiving the received fragment; and
dropping the received fragment when i) it is determined that the received fragment is not the first fragment in the ordered sequence of fragments and ii) it is determined that the data structure corresponding to the data unit was not created prior to receiving the received fragment.

3. The method of claim 1, further comprising:
keeping track of fragments in the ordered sequence of fragments dropped by the network node, if any;
when it is determined that the received fragment is not the first fragment in the ordered sequence of fragments,
determining whether a previous fragment in the ordered sequence of fragments was dropped by the network node, and
dropping the received fragment when it is determined that the previous fragment in the ordered sequence of fragments was dropped by the network node.

4. The method of claim 1, further comprising:
receiving, previous to receiving the received fragment, another fragment in the ordered sequence of fragments;
determining that the other fragment in the ordered sequence of fragments is an N-th fragment in the ordered sequence of fragments of the data unit, wherein N is an integer greater than zero;
determining whether the received fragment is the (N+1)-th fragment in the ordered sequence; and
dropping the received fragment when it is determined that the received fragment is not the (N+1)-th fragment in the ordered sequence.

5. The method of claim 1, further comprising:
determining whether a predetermined percentage of other fragments in the ordered sequence of fragments have been received by the network node within a predefined period of time;
transmitting the received fragment and other received fragments in the ordered sequence of fragments when it is determined that the predetermined percentage of other fragments in the ordered sequence of fragments have been received by the network node within the predefined period of time; and
dropping the received fragment, and other received fragments in the ordered sequence of fragments, if any, when it is determined that the predetermined percentage of other fragments in the ordered sequence of fragments have not been received by the network node within the predefined period of time.

6. The method of claim 5, wherein the predetermined percentage of fragments that have been received is 90%.

7. The method of claim 5, wherein the predetermined percentage of fragments that have been received is 100%.

8. The method of claim 1, wherein determining whether the network node has sufficient resources to process the predefined percentage of all fragments in the ordered sequence of fragments comprises:
attempting to allocate resources of the network node to process the predefined percentage of all fragments in the ordered sequence of fragments; and
when attempting to allocate resources of the network node to process the predefined percentage of all fragments in the ordered sequence of fragments fails, determining that the network node does not have sufficient resources to process the predefined percentage of all fragments in the ordered sequence of fragments.

9. The method of claim 1, wherein the predefined percentage of all fragments in the ordered sequence of fragments is 90%.

10. The method of claim 1, wherein the predefined percentage of all fragments in the ordered sequence of fragments is 100%.

11. An apparatus comprising:
at least one ingress interface configured to receive data units;
at least one egress interface configured to transmit data units; and
a forwarding engine configured to forward data units received via the at least one ingress interface to the at least one egress interface, the forwarding engine including a fragment filtering engine configured to
determine whether a received fragment is a first fragment of a data unit wherein the data unit has been previously fragmented into an ordered sequence of fragments, and
when it is determined that the received fragment is the first fragment in the ordered sequence of fragments,
determine whether the apparatus has sufficient resources, as of the time when the first fragment is received, to process a predefined percentage of all fragments in the ordered sequence of fragments, and
drop the first fragment when it is determined that the apparatus does not have sufficient resources, as of the time when the first fragment is received, to process the predefined percentage of all fragments in the ordered sequence of fragments.

12. The apparatus of claim 11, wherein the fragment filtering engine is configured to create, when it is determined that the received fragment is the first fragment in the ordered sequence of fragments, a data structure corresponding to the data unit, wherein the data structure provides information regarding fragmentation of the data unit into the ordered sequence of data fragments, and wherein the fragment filtering engine is configured to:
when it is determined that the received fragment is not the first fragment in the ordered sequence of fragments, determine whether the fragmentation data structure for the data unit was created prior to receiving the received fragment, and
drop the received fragment when i) it is determined that the received fragment is not the first fragment in the ordered sequence of fragments, and ii) it is determined that the fragmentation data structure corresponding to the data unit was not created prior to receiving the received fragment.

13. The apparatus of claim 11, wherein the fragment filtering engine is configured to:
keep track of fragments in the ordered sequence of fragments dropped by the apparatus, if any,
when it is determined that the received fragment is not the first fragment in the ordered sequence of fragments,
determine whether a previous fragment in the ordered sequence of fragments was dropped by the apparatus, and
drop the received fragment when it is determined that the previous fragment in the ordered sequence of fragments was dropped by the apparatus.

14. The apparatus of claim 11, wherein the fragment filtering engine is configured to:
determine that another fragment of the data unit received by the apparatus prior to receiving the received fragment is an N-th fragment in the ordered sequence of fragments of the data unit, wherein N is an integer greater than zero,
determine whether the received fragment is the (N+1)-th fragment in the ordered sequence, and
drop the received fragment when it is determined that the received fragment is not the (N+1)-th fragment in the ordered sequence.

15. The apparatus of claim 11, wherein the fragment filtering engine is configured to:
determine whether a predetermined percentage of other fragments in the ordered sequence of fragments have been received by the apparatus within a predefined period of time,
allow the received fragment and other received fragments in the ordered sequence of fragments to be transmitted via one or more of the at least one egress interface when it is determined that the predetermined percentage of fragments in the ordered sequence of fragments have been received by the apparatus within the predefined period of time, and
drop the received fragment, and other received fragments in the ordered sequence of fragments, if any, when it is determined that the predetermined percentage of fragments in the ordered sequence of fragments have not been received by the apparatus within the predefined period of time.

16. The apparatus of claim 15, wherein the predetermined percentage of fragments that have been received is 90%.

17. The apparatus of claim 11, wherein the fragment filtering engine is configured to:
attempt to allocate resources of the apparatus to process the predefined percentage of all fragments in the ordered sequence of fragments, and
when the attempt to allocate resources of the apparatus to process the predefined percentage of all fragments in the ordered sequence of fragments fails, determine that the apparatus does not have sufficient resources, as of the time when the first fragment is received, to process the predefined percentage of all fragments in the ordered sequence of fragments.

18. The apparatus of claim 11, wherein the predefined percentage of subsequent fragments of the data unit is 90%.