• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

Advanced Search Include Citations
Advanced Search Include Citations

Comparing alternative approaches for networking of named objects in the future Internet,” in (2012)

by A Baid, T Vu, D Raychaudhuri
Venue:Proc. of NOMEN,
Add To MetaCart

Tools

Sorted by:
Results 1 - 5 of 5

A Survey of Information-Centric Networking Research

by George Xylomenos, Christopher N. Ververidis, Vasilios A. Siris, Nikos Fotiou, Christos Tsilopoulos, Xenofon Vasilakos, Konstantinos V. Katsaros, George C. Polyzos - PUBLISHED IN: COMMUNICATIONS SURVEYS AND TUTORIALS (TO APPEAR)
"... The current Internet architecture was founded upon a host-centric communication model, which was appropriate for coping with the needs of the early Internet users. Internet usage has evolved however, with most users mainly interested in accessing (vast amounts of) information, irrespective of its ph ..."
Abstract - Cited by 16 (2 self) - Add to MetaCart
The current Internet architecture was founded upon a host-centric communication model, which was appropriate for coping with the needs of the early Internet users. Internet usage has evolved however, with most users mainly interested in accessing (vast amounts of) information, irrespective of its physical location. This paradigm shift in the usage model of the Internet, along with the pressing needs for, among others, better security and mobility support, has led researchers into considering a radical change to the Internet architecture. In this direction, we have witnessed many research efforts investigating Information-Centric Networking (ICN) as a foundation upon which the Future Internet can be built. Our main aims in this survey are: (a) to identify the core functionalities of ICN architectures, (b) to describe the key ICN proposals in a tutorial manner, highlighting the similarities and differences among them with respect to those core functionalities, and (c) to identify the key weaknesses of ICN proposals and to outline the main unresolved research challenges in this area of networking research.
(Show Context)

Citation Context

...] project (see Figure 1), funded by the US Future Internet Architecture program, proposes a cleanslate Future Internet architecture with an emphasis on treating mobile devices as first-class citizens =-=[69]-=-. As a result, MobilityFirst provides detailed mechanisms to handle both mobility and wireless links, as well as multicast, multi-homing, innetwork caching and security. The basis of the MobilityFirst...

SNAMP: Secure namespace mapping to scale NDN forwarding

by Alexander Afanasyev, Cheng Yi, Lan Wang, Beichuan Zhang, Lixia Zhang - In Proc. of Global Internet Symposium , 2015
"... Abstract—Named Data Networking (NDN) is a proposed information-centric design for the future Internet architecture, where application names are directly used to route requests for data. This key component of the architecture raises concerns about scalability of the forwarding system in NDN network, ..."
Abstract - Cited by 4 (2 self) - Add to MetaCart
Abstract—Named Data Networking (NDN) is a proposed information-centric design for the future Internet architecture, where application names are directly used to route requests for data. This key component of the architecture raises concerns about scalability of the forwarding system in NDN network, i.e., how to keep the routing table sizes under control given unbounded nature of application data namespaces. In this paper we apply a well-known concept of Map-and-Encap to provide a simple and secure namespace mapping solution to the scalability problem. More specifically, whenever necessary, application data names can be mapped to a set of globally routable names that are used to retrieve the data. By including such sets in data requests, we are informing (more precisely, hinting) the forwarding system of the whereabouts of the requested data, and such hints can be used when routers do not know from where to retrieve the data using application data names alone. This solution enables NDN forwarding to scale with the Internet’s well-understood routing protocols and operational practice, while keeping all the benefits of the new NDN architecture. I.
(Show Context)

Citation Context

...r alignment between the desired application usages and the underlying data delivery model in general. However, one frequently raised concern about NDN is the scalability of its name-based forwarding (=-=[8]-=-, [9]). Given that the number of data names is unbounded, can one keep the size of name-based NDN forwarding information base (FIB) under control? Forwarding scalability concern is not new. Although I...

Scaling ndn routing: Old tale, new design

by Alexander Afanasyev , Cheng Yi , Lan Wang , Beichuan Zhang , Lixia Zhang , 2013
"... ABSTRACT The Named Data Networking (NDN) is a newly proposed design for future Internet architecture, however one commonly raised concern about NDN's feasibility is its routing scalability. In this paper we sketch out a design that makes the NDN routing scale as well as today's IP Interne ..."
Abstract - Cited by 2 (1 self) - Add to MetaCart
ABSTRACT The Named Data Networking (NDN) is a newly proposed design for future Internet architecture, however one commonly raised concern about NDN's feasibility is its routing scalability. In this paper we sketch out a design that makes the NDN routing scale as well as today's IP Internet, potentially significantly better. We apply the well understood concept of map-n-encap to the context of NDN so that only ISP name prefixes need to appear in the global routing table. More specifically, our design securely maps each application name to one or more ISP names where the named data resides, and encapsulates the ISP names in NDN's Interest packets to hint the forwarding system of the whereabouts of the requested Data.
(Show Context)

Citation Context

...r of new network architecture designs [1,2,3,4] have proposed to use name-based routing. In namebased routing, packets carry data names or data identifiers instead of host addresses, and routers forward packets based on their names or identifiers. Named Data Networking (NDN) [4] is one prominent example. By naming data explicitly and binding the name and data by a cryptographic signature, NDN provides a number of benefits including data security, in-network caching, and better alignment between applications and data delivery. However, one frequently raised concern is NDN’s routing scalability [5, 6]. If the number of data names is unbounded, how can NDN routing table scale? We observe that NDN’s routing scalability issue is not new; one could ask a similar question about IP. Although IP’s address space is finite (232 or 2128), it is larger than any of today’s router can hold. IP solves this problem by address aggregation. At the edge of the Internet, hosts and small networks get addresses from their access providers. Since addresses from the same provider can be aggregated into prefixes (i.e., these are provider-aggregatable or PA addresses), routing tables only need to store prefixes in...

Controller-based Routing Scheme for Named Data Network

by João Vitor Torres, Lyno Henrique, G. Ferraz, Otto Carlos M. B. Duarte
"... Abstract—Named Data Network (NDN) routing schemes must learn routes to named data locations, so routers know where to send interest packets. These routing schemes are based on IP routing schemes, therefore they inherit characteristics such as prefix dissemination and routing based prefix longest mat ..."
Abstract - Cited by 1 (0 self) - Add to MetaCart
Abstract—Named Data Network (NDN) routing schemes must learn routes to named data locations, so routers know where to send interest packets. These routing schemes are based on IP routing schemes, therefore they inherit characteristics such as prefix dissemination and routing based prefix longest match. As the amount of named data and non-aggregated prefixes increase, routers store more routes and exchange more control messages, which results in high control overhead and possible Forwarding Information Base explosion. We address these issues with a novel Controller-based Routing Scheme (CRoS) for NDN. CRoS introduces special controllers which have two main functions: i) acquire topology and calculate routes, and ii) store named data locations. Named data locations are registered in controllers. On interest packets to an unknown prefix, routers request controllers for installation of a new route. CRoS controllers implement distributed hash tables to distribute the storage of named data locations efficiently. Furthermore, as CRoS runs on top of the NDN, it preserves NDN features such congestion control, network problem detection and path diversity. I.
(Show Context)

Citation Context

...ory requirements andmessage exchange, mapping named data prefixes to a reduced set of flat identifiers and these identifiers to network addresses. It employs a DHT system to provide this indirection =-=[7]-=-. Some proposals also address content, but use a different approach based on a publisher-subscriber architecture [8]. Carzaniga et al. compares NDN on-demand content retrieval to subscription approach...

Comparing Alternative Approaches for Mobile Content Delivery in Information-Centric Networking

by Feixiong Zhang
"... Abstract—The information-centric networking (ICN) concept has been investigated to support mobile content delivery, in which content is distributed and requested directly through their names. Pervasive in-network caching is normally enabled in ICN to further facilitate mobile content delivery. Sever ..."
Abstract - Add to MetaCart
Abstract—The information-centric networking (ICN) concept has been investigated to support mobile content delivery, in which content is distributed and requested directly through their names. Pervasive in-network caching is normally enabled in ICN to further facilitate mobile content delivery. Several different architectures have been proposed to realize ICN. In this work, we present their common features and then compare different approaches for mobile content delivery in these architectures. Such comparison would greatly deepen our understanding of different design choices and help with future ICN research. I.
(Show Context)

Citation Context

...e sharing same ICN rationale, they differ from each other in how they realize name-based service, and how cached content is appropriately utilized by content requests. Some existing comparison of ICN =-=[6]-=- has investigated general aspects including routing table size, update overhead, and infrastructure requirements. In this work, we would conduct an in-depth comparison study of alternate approaches fo...

Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University