IDHOCNET: A Novel ID Centric Architecture for Ad Hoc Networks

Table 5

Comparison between IDHOCNET and IP based ad hoc networks.

Requirement	Existing ad hoc schemes	Proposed scheme	Merit over IP based networks
End point identification	Uses IP addresses as identifiers.	Supports identifiers like global telephone numbers and MAC addresses.	Identifiers like telephone numbers, mobile numbers can be used.
Name resolution	For naming support it requires the naming and name resolution services [9] for identification support.	Uses identifiers (IDs) for end point identification, no need for resolution requirement throughout network.	No overhead for name resolution thus saving network bandwidth.
IP address autoconfiguration	These schemes require an IP address autoconfiguration service [10–12] to run in the ad hoc network.	It uses private address map for resolving IP address autoconfiguration. The proposed scheme does not suffer from IP address conflicts.	No requirement to run an IP address autoconfiguration scheme thus saving network bandwidth.
Heterogeneous subnets	Special gateway nodes are required for communication between nodes belonging to different subnets.	IP address support is implemented using private address map managed by the node. Therefore each node can have its own subnet.	No requirements for special gateway nodes.
Uniformity	Different schemes for IP address autoconfiguration assume different roles by different nodes like root node, group leader [21], and proxy node [22].	All nodes have similar role in the architecture.	Provides design simplification due to similar role.
Multihop header compression	Simulation studies [35, 36] have been conducted for multihop ROHC in ad hoc contexts. However a practical multihop ROHC implementation does not exist.	Implements a multihop Robust Header Compression scheme.	Supports a practical multihop Robust Header Compression (ROHC) scheme which saves considerable amount of network bandwidth.