DMap: A Shared Hosting Scheme for Dynamic Identifier to Locator Mappings in the Global Internet

Vu, Tam; Baid, Akash; Zhang, Yanyong; Nguyen, Thu D.; Fukuyama, Junichiro; Martin, Richard P.; Raychaudhuri, Dipankar

doi:10.1109/icdcs.2012.50

Cited by 96 publications

(74 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For the GNRS service, two alternate designs were simultaneously prototyped. One design uses an in-network DHT to store GUIDaddress mappings (with multiple replicas for each mapping) where service instances are co-located with the routing fabric to minimize access latency [12]. The second design is a flexible overlay implementation, and optimizes service latencies by considering access locality and exerting fine-grained control over replica placement [13].…”

Section: Evaluation and Testbed Considerationsmentioning

confidence: 99%

Future internets escape the simulator

et al. 2015

Self Cite

View full text Add to dashboard Cite

Researchers worldwide are increasingly turning to future Internet and distributed cloud (FIDC) testbeds, where they can conduct networking, distributed computing, and cloud computation experiments in a distributed laboratory setting. This brief survey of FIDC testbeds and sample applications is intended to introduce important concepts and to present example applications to pique the interest of experimentalist researchers and educators who are potential users. These testbeds are exemplified by the GENI project, which spans over forty university campuses in the US, and the FIRE initiative in the EU. They operate by virtualizing both computational and networking resources, permitting experiments that are not possible in today's public Internet or commercial cloud services. By virtualizing computation, network, and storage resources, many researchers can work simultaneously and independently within a shared cyberinfrastructure environment and extend their reach to real end users. As a result, studies that were previously confined to analysis, simulation, or execution in a single researcher's laboratory are more often conducted as experiments in real or realistic environments. This trend brings clear benefits for experimental fidelity, as well as challenges for experiment design. Four specific use cases of experimental research in GENI and FIRE are examined, including CloudCast's cloud-based localized weather forecasting; MobilityFirst, a clean-slate future Internet architecture; NetServ, an architecture for in-network services; and a study of resilience in OpenFlow software defined networks. Educational applications of these testbeds are also discussed, as are future trends toward international federations of testbeds. The Internet Innovation ProblemStandardization of basic underlying protocols such as the Internet Protocol (IP) has enabled rapid growth and widespread adoption of the global Internet. However, standardization carries the attendant risks of reducing variability and slowing the pace of progress. Validation and deployment of potential innovations by researchers in networking, distributed computing, and cloud computing are often hampered by Internet ossification, the inertia associated with the accumulated mass of hardware, software, and protocols that constitute the global, public Internet [1]. Researchers simply can't develop, test, and deploy certain classes of important innovations into the Internet. In the best case, the experimental components and traffic would be ignored; in the worst case, they could disrupt the correct behavior of the Internet. Cloud computing researchers confront a similar dilemma. In order to maintain uniformity and efficiency in their data centers, commercial cloud providers generally do not provide "under the hood" controls that permit modification to the underlying network topology or protocols that comprise the cloud environment.A clear example of the challenge is apparent to anyone tracking the pace of adoption of IPv6, a relatively modest revamping of IP. Becaus...

show abstract

Section: Evaluation and Testbed Considerationsmentioning

confidence: 99%

Future internets escape the simulator

et al. 2015

Self Cite

View full text Add to dashboard Cite

show abstract

“…Details about the design, prototype, and evaluation of the GNRS can be found in [7]. A key feature, and one which is crucial to supporting the wide variety of vehicular applications, is the use of service flags in the API (and service identifier (SID) in the packet).…”

Section: A Overview Of Mobilityfirstmentioning

confidence: 99%

Enabling vehicular networking in the MobilityFirst future internet architecture

Baid

Mukherjee

et al. 2013

2013 IEEE 14th International Symposium on "A World of Wireless, Mobile and Multimedia Networks" (WoWMoM)

Self Cite

View full text Add to dashboard Cite

Abstract-Vehicular networking, both vehicle-to-vehicle (V2V)and vehicle-to-infrastructure (V2I), is an increasingly important usage scenario for future mobile Internet services. Radio technologies such as 3G/4G and WAVE/802.11p now enable vehicles to communicate with each other and connect to the Internet, but there is still the lack of a unifying network protocol architecture for delivery of services across both V2V and V2I modes. The MobilityFirst future Internet architecture, discussed in this paper, is a clean-slate protocol design in which the requirements of untethered nodes and dynamically formed networks are considered from the ground-up, making it particularly suitable for vehicular applications. Here we describe the vehicular networking specific features and protocol design details of the architecture and present evaluation results on performance and scalability.

show abstract

“…This concept of separating names from addresses has been proposed in earlier work, such as [10], [11] but is usually viewed as an overlay service above the network similar in spirit to DNS. The MF architecture aims to integrate a global name resolution service (GNRS) as a basic network-layer service which can be efficiently accessed both by end-user devices and in-network routers, base stations and access points [12]. This concept is illustrated in Figure 6 which shows the layering of functionality in the proposed MobilityFirst architecture.…”

Section: Mobilityfirst Future Internet Architecturementioning

confidence: 99%

“…That is, when a user sends packets directed to a particular identifier (GUID), the networking subsystem must quickly ascertain the set of locators (NAs) attached to the GUID and route the packets correspondingly. We address the challenge of providing a fast global name resolution service at Internet scale through a router DHT-based Direct Mapping (DMap) scheme for achieving a good balance between scalability, low update/query latency, consistency, availability and incremental deployment [12]. In order to perform the name resolution for a given GUID, DMap distributes the GUID→NA mappings amongst Internet routers using an in-network single-hop hashing technique which derives the address of the storage router directly from the GUID.…”

Section: A Dynamic Name-address Bindingsmentioning

confidence: 99%

“…In order to perform the name resolution for a given GUID, DMap distributes the GUID→NA mappings amongst Internet routers using an in-network single-hop hashing technique which derives the address of the storage router directly from the GUID. Through a detailed simulation study described in [12], we have shown that DMap achieves a 95th percentile round trip query response time of below 100ms ( Figure 7 presents the key query response time result) considered more than adequate for current and future mobility services [13], [14]. The dynamic binding of GUIDs to network addresses thus helps meet mobility and multihoming requirements.…”

Section: A Dynamic Name-address Bindingsmentioning

confidence: 99%

See 1 more Smart Citation

Wireless access considerations for the MobilityFirst future Internet architecture

Baid

Raychaudhuri

2012

2012 35th IEEE Sarnoff Symposium

Self Cite

View full text Add to dashboard Cite

Abstract-This paper presents an overview of wireless access considerations behind the design of the MobilityFirst clean-slate future Internet architecture. The MobilityFirst architecture is motivated by a historic shift of the Internet from the fixed host-server model to one in which access from mobile platforms becomes the norm. This implies the need for a future Internet architecture designed to handle the special needs of mobile/wireless access efficiently and at large scale. A number of key wireless access network requirements including user/network mobility, varying wireless link quality and disconnection, multi-homing, ad hoc networking, flexible autonomous system boundaries and spectrum coordination are identified along with a brief discussion of the implications for protocol design. This is followed by a summary of the MobilityFirst protocol stack based on separation of names and locators, global name resolution service (GNRS), storage-aware routing with hop-by-hop transport, integrated spectrum management, along with an enhanced edge-aware interdomain routing framework. Selected results from ongoing protocol design and evaluation work are given for key components such as the GNRS, storage-aware routing and spectrum coordination protocol.

show abstract

DMap: A Shared Hosting Scheme for Dynamic Identifier to Locator Mappings in the Global Internet

Cited by 96 publications

References 21 publications

Future internets escape the simulator

Future internets escape the simulator

Enabling vehicular networking in the MobilityFirst future internet architecture

Wireless access considerations for the MobilityFirst future Internet architecture

Contact Info

Product

Resources

About