MOSS: Gathering Names in Networks of Mobile Nodes

Abstract

Nodes in mobile ad hoc networks (MANETs) act as routers by exchanging routing information to determine initial routes and to update those routes to account for node movement and failure. This ability of MANETs to self-form and self-heal makes them ideal for scenarios that require rapid deployment in areas with limited network infrastructure. However, their dynamic nature makes it challenging to implement naming and location services, as well as other services that traditionally require a fixed infrastructure. A naming service is highly desirable in networks, especially in dynamic networks like MANETs, since it allows accessing network resources by fixed names instead of volatile addresses. This paper presents multicast onomastic search (MOSS), which is a technique for implementing a distributed DNS server in a MANET using multicast addresses. Upon entering a network, a MOSS-enabled node joins a multicast group responsible for resolving the node's name. The node can then respond to DNS queries for its name. MOSS allows a set of nodes in a MANET to provide a naming service that is resilient to node movement and reconfiguration. It also guarantees that, once routes have stabilized sufficiently, it is always possible to resolve the name of a node provided only that the node itself is reachable.

A survey and taxonomy of name systems in mobile ad hoc networks

“…This method is used in fully and partially distributed name systems. MOSS which is presented by Gottlieb et al (2008) is a multicast based name system. It allows a set of nodes to provide name service which is resilient to node movement and reconfiguration.…”

“…The eventual destination node will check its local repository and send back the matching resource descriptor. In other schemes such as MOSS (Gottlieb et al, 2008), the client uses the preconfigured mapping to find the multicast address associated with the domain of the target name and sends a standard DNS query to that address. Assuming that routing has sufficiently stabilized, the multicast DNS query will be forwarded to all nodes in the network that are members of the target's group.…”

“…Whenever ANS Cache timer expires, Timer-Thread checks if there are entries that are expired in ANS Cache and then invalidates them. Finally, some of the proposed schemes try to avoid caching overheads by simply not caching the bindings (Gottlieb et al, 2008).…”

“…(Jeong et al, 2004b) Multicast Unicast - Broadcast Unicast Do not register (Hu et al, 2005) Broadcast Unicast Do not register Broadcast Unicast Do not register Jeong and Park Kim First request: one multicastþ N unicast Zero Next requests: zero (Jeong et al, 2003) Multicast unicast - (Gottlieb et al, 2008) Multicast Unicast -Time to reach the conflict messages to the user. Time to total conflict resolution.…”

“…Request Response Unicast Unicast Just in one DNS Server (Gottlieb et al, 2008) Multicast Unicast (Jeong et al, 2004b) Unicast, multicast Shared with autoconfiguration system (Jeong et al, 2003) Unicast Unicast Distributed server (Morera and McAuley, 2005) Multicast Unicast LLMNR (Esibov et al, 2005) Multicast Unicast mDns…”