2013 Fifth International Conference on Communication Systems and Networks (COMSNETS) 2013
DOI: 10.1109/comsnets.2013.6465579
|View full text |Cite
|
Sign up to set email alerts
|

Design requirements of a global name service for a mobility-centric, trustworthy internetwork

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0
1

Year Published

2013
2013
2019
2019

Publication Types

Select...
5
4

Relationship

3
6

Authors

Journals

citations
Cited by 19 publications
(9 citation statements)
references
References 21 publications
0
8
0
1
Order By: Relevance
“…In this paper, we consider MobilityFirst [3], [7], a mobility-centric architecture that supports large-scale, efficient and robust network services with mobility as the norm. In MobilityFirst, we associate every endpoint with a global unique identifier (GUID), which is decoupled from its network address or location, and rely on a dynamic global name resolution service (GNRS), such as those in [8], [9], [10], [11], to track and resolve the mapping between GUID and its network address(es). MobilityFirst aims to support smooth mobile content delivery exploiting real-time GNRS updates and queries.…”
Section: Introductionmentioning
confidence: 99%
“…In this paper, we consider MobilityFirst [3], [7], a mobility-centric architecture that supports large-scale, efficient and robust network services with mobility as the norm. In MobilityFirst, we associate every endpoint with a global unique identifier (GUID), which is decoupled from its network address or location, and rely on a dynamic global name resolution service (GNRS), such as those in [8], [9], [10], [11], to track and resolve the mapping between GUID and its network address(es). MobilityFirst aims to support smooth mobile content delivery exploiting real-time GNRS updates and queries.…”
Section: Introductionmentioning
confidence: 99%
“…A key implication of our findings is that name-based routing approaches in their puristic form may be better suited for content alone, but need to be augmented with addressingassisted approaches such as DNS, Mobile IP, or a nextgeneration name resolution service [49] in order to serve as a general-purpose replacement for the TCP/IP Internet. Our findings also show the important differences between device and content mobility, as well as the emerging importance of the strategy layer [28,55] in content-oriented architectures.…”
Section: Introductionmentioning
confidence: 93%
“…Several publications [10,11,12,13,14,15] discuss deploying DNS over an overlay network that uses a distributed hash table (DHT) to reduce the load on individual servers and thus provide higher scalability and better fault tolerance. These papers target the traditional DNS system in the Internet, and thus focus on planet-level scalability.…”
Section: Overlay Networkmentioning
confidence: 99%