News & Analysis
Comment
digitalshaman
Packet watermarks were introduced to address these issues in the early 2000s; ...
LarryM99
The problem with the current network address approach is that it takes each ...
PARC hosts summit on content-centric nets
Rick Merritt
8/12/2011 12:46 AM EDT
PALO ALTO, Calif. – PARC, a Xerox subsidiary, will gather as many as 100 researchers in September for the first event focused on content-centric networking, a new direction for organizing Internet traffic. The approach promises greater security and faster connections to popular content but will require new protocols and changes in router chip and systems designs.
Content-centric networking represents a shift from today's focus on using network addresses to find content. Instead it proposes a protocol that specifically defines and tracks content. Backers say it represents an evolutionary change similar to IP forwarding.
"We think it's definitely a concept that will change how people design high performance hardware," said Jim Thornton, a principal engineer who leads a dozen researchers at PARC working in the area.
The idea is largely the brainchild of Van Jacobsen, an Internet pioneer who helped develop multicasting and trace route capabilities for Internet Protocol. About four years ago, Jacobsen brought the concept to PARC which has been gestating it ever since.
PARC won a National Science Foundation grant to develop the concept working with a handful of universities as part of the Named Data Network project started in 2010.
"They aim to provide an idea of the cost and complexity trade offs" of the concept, said Thornton. "The sense we have is this is doable, it won't kill us and forwarding hardware has always stepped up to the challenges new application demands," he said.
In a separate project in Europe, Alcatel-Lucent, Orange and French universities are working on similar ideas. "We know there are other companies beginning to look at this too, [but] in the router hardware community it's still early in the life cycle of these ideas," said Thornton.
PARC recently released open source code for testing content-centric networks. One goal of the September meeting is to gather researchers to share their work with the software. Their findings begin to shape the kind of content ID and router frameworks needed to make the concept work.
"We are trying to define and validate what you could think of as an Internet Protocol for content," said Thornton. "It's this kind of work with people experimenting with apps and use cases that will push toward the design of a core protocol," he said.
Content-centric networks hold the promise of pervasive caching of popular Web content—often far out to the network's edge--based on actual demand. Today caching is limited to content-distribution networks (CDNs) set up for content and network owners, typically set up near the network core.
The approach could ease the job of getting popular videos quickly to widely dispersed users. It would not eliminate CDNs, but it could open up new business models for how carriers, content owners and CDNs create new caching capabilities.
The new protocols also would enable new levels of security and privacy. Content packets could carry digital signatures which could authenticate authorized users and verify no one has tampered with the content—services of interest to a wide range of providers from banks to Hollywood studios.
To enable content-centric nets, data packets will need to encode new information identifying its data type and where it fits in a content hierarchy. Router chips would need to inspect packets for that information, add new state information based on it and store the results.
Additional logic could help track optimal paths to the nearest similar data, stored in local tables. Systems may be able to use existing buffer memory and statistical multiplexing techniques for holding and maintaining the look up tables, Thornton said.


grouts
8/15/2011 9:46 PM EDT
Content-centric networks should be a natural for any company to use for all their product design activities. The PARC announcement also strongly suggests the re-discovery of the use of hashed binary trees, which are the strongest data structures (read also of course files, networks, clouds, etc.), capable of organizing and providing immense amounts information, especially for hierarchical product and library design information. I believe you will find that NSA is also using this basic data and network paradigm for their huge huge collections of information. My own background here is that this is the approach we took at Honeywell Large Information Systems EDA hierarchical design data using what Honeywell called indexed-sequential files. We implemented a EDA database we called MUSER which was actively used by Honeywell / Bull from 1969 through 1997, and was only shut down due to the french Bull folks having to use some many off the shelf design tools. --Steve Grout
Sign in to Reply
DrQuine
8/16/2011 10:16 AM EDT
One challenge of content-centric networks is that low quality information may be more difficult to avoid. The current network address based approach helps to identify trusted sources and avoid spam.
Sign in to Reply
LarryM99
8/16/2011 1:42 PM EDT
The problem with the current network address approach is that it takes each packet at face value (This one says it came from google.com? Good enough for me!). The idea of integrating authentication is a real step forward, whether it is done in a content-centric approach or an overlay onto the current structure. This seems to be a clean-sheet-of-paper approach, which has technical advantages and huge logistical challenges. Step one: throw away all of your infrastructure. Step two: doesn't matter until you get people to do step one.
Larry M.
Sign in to Reply
digitalshaman
8/22/2011 1:32 PM EDT
Packet watermarks were introduced to address these issues in the early 2000s; but, Cisco and Juniper generally promoted the notion of "free" bandwidth and bandwidth allocation schemes limited to coarse estimates (MPLS, etc.). Packet watermarks also enable differential QoS at far higher efficiency in computational overhead and better management of "flow". The other push comes from search and poor notions of where the network (*your* network / infrastructure) starts. Innovation suffers when legacy models are not subject to "restart"!
Sign in to Reply