[ English | Japanese ]
The Domain Name System (DNS) has been described in the literature as
the most successful distributed naming system that has ever been
designed. However, limitations, imposed by its fundamental design
premises are increasingly difficult to work around, particularly the
assumption that certain nodes are always reachable. Mobility and
transient connectivity are becoming the standard for nodes in the
Internet. In general, the DNS as implemented is constructed as a "softfail"
service, with authoritative node replicas, caching, etc. However,
changes to the DNS itself and the changes to the Internet infrastructure
are degrading the robustness and "reachability" of parts of the system at
the same time that client expectations about resolvability are rising.
This work documents how to eliminate the inherent reliance of DNS on
fixed third-party servers by using a solution I call Client Based Naming
(CBN), which operates optimally in fluid environments, including selforganizing
networks such as the Internet. These ideas question key
deployment decisions regarding the root context and service discovery.
To eliminate reliance on reachability, the re-implemented DNS uses
existing technologies in three new ways as follows:
Keywords: DNS, Mobility, Multicast, Ad-Hoc, Identity Management
Keio University, Graduate School of Media and Governance
MAUI Project
Ph.D. Dissertation
Back to Index Page
ACADEMIC YEAR
2013 (May 22nd, 2013)
NAME
MANNING, William C.
TITLE
Client Based Naming
ABSTRACT
These techniques, plus additional identity credentials, form the basis of a
globally persistent name that is usable inside and outside the DNS.
Persistent names are critical for service delivery since the nodes'
location (based on IP address) changes when the node or network is
moved in the Internet. Persistent names can be constructed using the
DNS namespace without the need to migrate to Distributed Hash tables
(DHT) or crypto-hash based names for resolving ambiguity or to retain a
persistent name. CBN is evaluated using simulation. Results indicate that
use of multicast transport provides robust service in topologies where
node mobility and transient connectivity dominate. Other research has
shown that multicast transport for DNS is a commercially viable tactic as
long as scoping is restricted to local scope. Concerns still remain about
ambiguous naming, resolution and robust crypto key distribution, but
this discourse lays out a path for future work.
CONTACT
To obtain the dissertation, please contact;
MANNING, William C. (bmanning at isi.edu)