In order to understand the problem of IP address lookup, we need first to start with the IP address architecture.
The IPv4 IP address is 32 bit of zeroes and ones that is divided into 4 octets. Each octet consists of 8 bits that are separated by dots. For example, the IP address of Lancaster University website 10010100 01011000 00010001 00101011 corresponds in dotted-decimal notation to 188.8.131.52
IP addresses are hierarchical. Specifically, IP addresses consist of two-level hierarchy, usually referred to as a network part and a host part. The network top level part of an IP address identifies the network to which the host is attached; all hosts attached to the same network share the same network part in their IP address. The host bottom part then identifies each host uniquely on that particular network. The network part corresponds to the first left bits of the IP address, called the address prefix. We will write prefixes as bit strings of up to 32 bits in IPv4 followed by an asterisk (*). For example, the prefix 10010100* represents all the 224 addresses that begin with the bit pattern 10010100. Alternatively, prefixes can be indicated using the dotted-decimal notation, so the same prefix can be written as 184.108.40.206/8, where the number after the slash indicates the length of the prefix.
Since routing occurs at the network level to locate the destination network, routers only forward packets based on network level IP addresses. Thus, all hosts attached to the same network and share the same network part in their IP address can be stored in the router’s forwarding table by a single network IP address, known as address aggregation. An example of a router’s forwarding table is shown in Table 1. Each entry in the forwarding table contains a destination address prefix, next-hop IP address, and output interface number. The forwarding information is located by searching for the prefix that matches the corresponding bits of the destination address.
|Destination address prefix||Next-hop IP address||Output interface|
Table 1: “Router Forwarding Table Example”
The Internet addressing was first designed using a rather simple allocation scheme known as classful addressing. Basically, classful addressing defines three main different sizes of networks: A, B, or C.
Class A: The network part consists of 8 bits and the first octet value is between (0 and 127) which means the networks size can be up to 27 = 128 and the host part consists of (32 – 8 = 24 bits) which means these networks can support at max 224 – 2 hosts devices (i.e. two addresses are not usable the first one is the network address and the broadcast address).
Class B: The network part consists of 16 bits and the first octet value is between (128 and 191) which means the networks size can be up to 214 = 65536 and the host part consists of (32 – 16 = 16 bits) which means these networks can support at max 216 – 2 = 65534 hosts devices.
Class C: The network part consists of 24 bits and the first octet value is between (192-223) which means the networks size can be up to 221 and the host part consists of (32 – 24 = 8 bits) which means these networks can support at max 28 – 2 = 254 hosts devices.
It is obvious that the original scheme was inflexible and wasteful. For example if a company has 255 host devices, then a class C IP address won’t be sufficient. It needs to buy either class B or A. As a result, and a huge amount of IP addresses will not be used. Moreover, with the continues growth of internet IP address space was getting exhausted very rapidly. One possible work around was to give the allocate bundles of class C addresses instead of giving class B or A. This causes a massive growth of forwarding table entries.
Classless Inter-Domain Routing (CIDR) addressing
The CIDR addressing scheme was introduced in 1993 to remedy the inefficiencies of classful addressing. With CIDR, variable prefix length is allowed rather than constraining them to be 8, 16, or 24 bits long. This results in IP address space is better conserved. By using route summarization, different blocks of networks can be aggregated together to reduce the growth of forwarding tables. To understand how this works, consider the networks from 220.127.116.11/16 through 18.104.22.168/16 and in a router all these networks are reachable through the same ISP as shown in Fig. 1.
Fig. 1: “Prefix Aggregation Example”
The leftmost 12 bits of all the addresses in this range are the same (10101010 0000). Thus, these 16 networks can be aggregated into one route summary represented by the 12-bit prefix, which in decimal notation gives 22.214.171.124/12. Indicating the prefix length is necessary in decimal notation, because the same value may be associated with prefixes of different lengths; for instance, 126.96.36.199/12 (10101010 0000*) is different from 188.8.131.52/14 (10101010 000000*).
Address aggregation does not reduce entries in the router’s forwarding table for all cases. Consider the scenario where a customer owns the network 184.108.40.206/16 and changes its ISP, but does not want to renumber its network. Now, all the networks from 220.127.116.11/16 through 18.104.22.168/16 can be reached through the same ISP, except for the network 22.214.171.124/16. We cannot perform aggregation as before, and instead of only one entry, 16 entries need to be stored in the forwarding table. One solution is aggregating in spite of the exception networks and additionally storing entries for the exception networks. In this example, this will result in only two entries in the forwarding table: 126.96.36.199/12 and 188.8.131.52/16 (See table 1). However, now some addresses (i.e. 184.108.40.206) will match both entries because of the prefixes overlap. In order to always make the correct forwarding decision, routers need to do more than search for a prefix that matches. Since exceptions in the aggregations may exist, a router must find the most specific match, which is the longest matching prefix. In summary, the address lookup problem in routers requires searching the forwarding table for the longest prefix that matches the destination address of a packet.
Obviously, the longest prefix match is harder than the exact match used for class-based addressing because the destination address of an arriving packet does not carry with it the information to determine the length of the longest matching prefix. Hence, we need to search among the space of all prefix lengths, as well as the space of all prefixes of a given length.
Many algorithms have been proposed to address the longest prefix match problem. This web based tutorial provides a survey of these techniques. But before that, we introduce some performance metrics for the comparison of these lookup algorithms.
- Lookup Speed: The growth of link bandwidth requires faster IP lookups. For example, links running at 10 Gbps can carry 31.25 million packets per second (mpps) (assuming minimum sized 40-byte IP packets which is a TCP-acknowledgment packets). The amount of time that it takes for a lookup can be calculated as follows:
Lookup time = (40 bytes x 8bits/byte) / 10Gbps = 32 ns
That means the number of memory accesses is very crucial in determining the lookup speed.
- Storage Requirement: Small storage means fast memory access speed through cache memory and low power consumption. Therefore, the amount of memory consumed by the data structures of the algorithm is also important.
- Scalability: The ability of an algorithm to scale both in speed and memory in order to handle large forwarding tables is required. While core routers presently contain as many as 200,000 prefixes, it is expected to increase to 500,000 to 1 million prefixes with the possible use of host routes and multicast routes .
- Update Time: Currently, the core routers may receive a peak of a few hundred BGP (Border Gateway Protocol) updates per second. Thus, the route changes require updating the forwarding table data structure, in the order of milliseconds or less. These requirements are still several orders of magnitude less than the lookup speed requirements. Nevertheless, it is important for an algorithm to support incremental updates and should interfere little with normal lookup operations.
Unless otherwise specified, we use the sample forwarding table shown below as a running example for the different algorithms.
Table 2: “Prefix Table Example”
We also use the following three parameters:
N = Number of prefixes in a router’s forwarding table.
W = Length of the prefixes in bits (Maximum is 32 for IPv4 and 128 for IPv6).
S = Memory space required for each node.