Networking named content
PARC1
01 Dec 2009-pp 1-12
TL;DR: Content-Centric Networking (CCN) is presented, which treats content as a primitive - decoupling location from identity, security and access, and retrieving content by name, using new approaches to routing named content.
Abstract: Network use has evolved to be dominated by content distribution and retrieval, while networking technology still speaks only of connections between hosts. Accessing content and services requires mapping from the what that users care about to the network's where. We present Content-Centric Networking (CCN) which treats content as a primitive - decoupling location from identity, security and access, and retrieving content by name. Using new approaches to routing named content, derived heavily from IP, we can simultaneously achieve scalability, security and performance. We implemented our architecture's basic features and demonstrate resilience and performance with secure file downloads and VoIP calls.
Citations
More filters
01 Sep 2012
TL;DR: A survey of technologies, applications and research challenges for Internetof-Things is presented, in which digital and physical entities can be linked by means of appropriate information and communication technologies to enable a whole new class of applications and services.
Abstract: The term ‘‘Internet-of-Things’’ is used as an umbrella keyword for covering various aspects related to the extension of the Internet and the Web into the physical realm, by means of the widespread deployment of spatially distributed devices with embedded identification, sensing and/or actuation capabilities. Internet-of-Things envisions a future in which digital and physical entities can be linked, by means of appropriate information and communication technologies, to enable a whole new class of applications and services. In this article, we present a survey of technologies, applications and research challenges for Internetof-Things.
3,172 citations
TL;DR: Content-Centric Networking (CCN) is presented which uses content chunks as a primitive---decoupling location from identity, security and access, and retrieving chunks of content by name, and simultaneously achieves scalability, security, and performance.
Abstract: Current network use is dominated by content distribution and retrieval yet current networking protocols are designed for conversations between hosts. Accessing content and services requires mapping from the what that users care about to the network's where. We present Content-Centric Networking (CCN) which uses content chunks as a primitive---decoupling location from identity, security and access, and retrieving chunks of content by name. Using new approaches to routing named content, derived from IP, CCN simultaneously achieves scalability, security, and performance. We describe our implementation of the architecture's basic features and demonstrate its performance and resilience with secure file downloads and VoIP calls.
3,122 citations
28 Jul 2014
TL;DR: The NDN project investigates Van Jacobson's proposed evolution from today's host-centric network architecture (IP) to a data-centricnetwork architecture (NDN), which has far-reaching implications for how the authors design, develop, deploy, and use networks and applications.
Abstract: Named Data Networking (NDN) is one of five projects funded by the U.S. National Science Foundation under its Future Internet Architecture Program. NDN has its roots in an earlier project, Content-Centric Networking (CCN), which Van Jacobson first publicly presented in 2006. The NDN project investigates Jacobson's proposed evolution from today's host-centric network architecture (IP) to a data-centric network architecture (NDN). This conceptually simple shift has far-reaching implications for how we design, develop, deploy, and use networks and applications. We describe the motivation and vision of this new architecture, and its basic components and operations. We also provide a snapshot of its current design, development status, and research challenges. More information about the project, including prototype implementations, publications, and annual reports, is available on named-data.net.
2,060 citations
TL;DR: The SDN architecture and the OpenFlow standard in particular are presented, current alternatives for implementation and testing of SDN-based protocols and services are discussed, current and future SDN applications are examined, and promising research directions based on the SDN paradigm are explored.
Abstract: The idea of programmable networks has recently re-gained considerable momentum due to the emergence of the Software-Defined Networking (SDN) paradigm. SDN, often referred to as a ''radical new idea in networking'', promises to dramatically simplify network management and enable innovation through network programmability. This paper surveys the state-of-the-art in programmable networks with an emphasis on SDN. We provide a historic perspective of programmable networks from early ideas to recent developments. Then we present the SDN architecture and the OpenFlow standard in particular, discuss current alternatives for implementation and testing of SDN-based protocols and services, examine current and future SDN applications, and explore promising research directions based on the SDN paradigm.
2,013 citations
TL;DR: This work compares and discusses design choices and features of proposed ICN architectures, focusing on the following main components: named data objects, naming and security, API, routing and transport, and caching.
Abstract: The information-centric networking (ICN) concept is a significant common approach of several future Internet research activities. The approach leverages in-network caching, multiparty communication through replication, and interaction models decoupling senders and receivers. The goal is to provide a network infrastructure service that is better suited to today?s use (in particular. content distribution and mobility) and more resilient to disruptions and failures. The ICN approach is being explored by a number of research projects. We compare and discuss design choices and features of proposed ICN architectures, focusing on the following main components: named data objects, naming and security, API, routing and transport, and caching. We also discuss the advantages of the ICN approach in general.
1,679 citations
References
More filters
Book•
01 Jan 1979
TL;DR: An automatic control system for a tube expander tool of the type having a hydraulically powered rotary tool which is advanced and retracted by a reversible linear motor to maintain a desired constant load and to prevent overloading.
Abstract: An automatic control system for a tube expander tool of the type having a hydraulically powered rotary tool which is advanced and retracted by a reversible linear motor. Operation of automatic cycling is initiated by a manual control whereas axial movement of the tool can be interrupted at any time by operating a hold control while rotation of the tool continues as long as necessary to iron out excess metal or to reposition the tube in the bore should this be desirable. The tool is maintained under constant load at all times by load sensor means in the tool advancing circuit and operable to vary the rate of tool advance to maintain a desired constant load and to prevent overloading. Accordingly, the rate of tool advance varies inversely as the load on the tool.
591 citations
"Networking named content" refers methods in this paper
...Though Data packets are designed to be individually verifiable, the computational cost of signature generation may be amortized across multiple packets through the use of aggregation techniques such as Merkle Hash Trees [27]....
[...]
02 Oct 1996
TL;DR: SDSI combines a simple public-key infrastructure design with a means of defining groups and issuing group-membership certificates, and its design emphasizes linked local name spaces rather than a hierarchical global name space.
Abstract: We propose a new distributed security infrastructure, called SDSI (pronounced “Sudsy”). SDSI combines a simple public-key infrastructure design with a means of defining groups and issuing group-membership certificates. SDSI’s groups provides simple, clear terminology for defining access-control lists and security policies. SDSI’s design emphasizes linked local name spaces rather than a hierarchical global name space.
589 citations
"Networking named content" refers background in this paper
...that of SDSI/SPKI [30, 9, 1], wherein identities, and corresponding keys form local namespaces that can be mapped directly onto CCN names – e....
[...]
01 Oct 1996
TL;DR: This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain (like a more general form of MX).
Abstract: This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain (like a more general form of MX).
462 citations
Additional excerpts
...net), DNS SRV[14], SLP[15], etc....
[...]
17 Aug 2008
TL;DR: The experiments show that SEATTLE efficiently handles network failures and host mobility, while reducing control overhead and state requirements by roughly two orders of magnitude compared with Ethernet bridging.
Abstract: IP networks today require massive effort to configure and manage. Ethernet is vastly simpler to manage, but does not scale beyond small local area networks. This paper describes an alternative network architecture called SEATTLE that achieves the best of both worlds: The scalability of IP combined with the simplicity of Ethernet. SEATTLE provides plug-and-play functionality via flat addressing, while ensuring scalability and efficiency through shortest-path routing and hash-based resolution of host information. In contrast to previous work on identity-based routing, SEATTLE ensures path predictability and stability, and simplifies network management. We performed a simulation study driven by real-world traffic traces and network topologies, and used Emulab to evaluate a prototype of our design based on the Click and XORP open-source routing platforms. Our experiments show that SEATTLE efficiently handles network failures and host mobility, while reducing control overhead and state requirements by roughly two orders of magnitude compared with Ethernet bridging.
425 citations
"Networking named content" refers methods in this paper
...SEATTLE [23] utilizes flat addressing with a one-hop DHT to provide a directory service with reactive address resolution and service discovery....
[...]
PARC1
TL;DR: In this paper, the authors present a detailed description of a prototype implementation of one such application (VoIP) in a content-based paradigm, and show how contentbased networking can offer advantages for the full range of Internet applications, if the architecture has certain key properties.
Abstract: A variety of proposals call for a new Internet architecture focused on retrieving content by name, but it has not been clear that any of these approaches are general enough to support Internet applications like real-time streaming or email. We present a detailed description of a prototype implementation of one such application -- Voice over IP (VoIP) -- in a content-based paradigm. This serves as a good example to show how content-based networking can offer advantages for the full range of Internet applications, if the architecture has certain key properties.
409 citations