2013
DOI: 10.1016/j.comcom.2013.01.014
|View full text |Cite
|
Sign up to set email alerts
|

Hierarchical DHT-based name resolution for information-centric networks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
46
0

Year Published

2013
2013
2017
2017

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 54 publications
(47 citation statements)
references
References 26 publications
1
46
0
Order By: Relevance
“…For our description, we represent the inter-domain hierarchy as a graph G(V, E). V is the set of nodes in the graph, with each node representing a distinct administrative domain or AS 4 . E is the set of edges in the graph, with each edge representing the inter-domain link that connects the corresponding domains.…”
Section: H-pastry Designmentioning
confidence: 99%
See 2 more Smart Citations
“…For our description, we represent the inter-domain hierarchy as a graph G(V, E). V is the set of nodes in the graph, with each node representing a distinct administrative domain or AS 4 . E is the set of edges in the graph, with each edge representing the inter-domain link that connects the corresponding domains.…”
Section: H-pastry Designmentioning
confidence: 99%
“…Dannewitz et al [4] proposed a hierarchical version of SkipNet, which achieves low resolution delays. In their design they consider resolution domains organized into a global, tree-like hierarchy topologically embedded in the underlying network.…”
Section: ) Impact Of Churnmentioning
confidence: 99%
See 1 more Smart Citation
“…Even though this information is obviously important for content providers (see Section II), it is hidden from them in most ICN designs. The reason is that user requests for content may be served by any intermediate node either through caching or multicast (i.e., CCN/NDN [5]), or it can be served by an ISP-operated name resolution system (i.e., DONA [9], PURSUIT [26], NetInf [27], COMET [23]). In both cases, the content provider is not involved in the name resolution procedure thus losing access to content access information.…”
Section: B Exposing Information Through Name Resolutionmentioning
confidence: 99%
“…To this end, we foresee two potential approaches. The first approach is tailored for architectures that decouple name resolution from routing and forwarding ( [9], [26], [27], [23]). This decoupling adheres to the "design for tussle" principle [29], thus enabling content providers to potentially establish an interface with the nameresolution system for logging purposes.…”
Section: B Exposing Information Through Name Resolutionmentioning
confidence: 99%