Fragment behavior is the NAT instance's capability to receive and translate fragments incoming from remote sources. fragmentNone(0) implies no capability to translate incoming fragments, so all received fragments are dropped. Each dropped fragment is counted in natv2InstanceFragmentDrops. fragmentInOrder(1) implies the ability to translate fragments only if they are received in order, so that in particular the header is in the first packet. If a fragment is received out of order, it is dropped and counted in natv2InstanceFragmentDrops. fragmentOutOfOrder(2), the capability REQUIRED by RFC 4787, REQ-14, implies the capability to translate fragments even when they arrive out of order, subject to a protective limit natv2InstanceLimitPendingFragments on total number of fragments awaiting the first fragment of the chain. If the implementation supports this capability, natv2InstanceFragmentDrops is incremented only when a new fragment arrives but is dropped because the limit on pending fragments has already been reached.