IP protocol suite extensions to support CONET Information Centric Networking
draft-detti-conet-ip-option-05
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Andrea Detti , Stefano Salsano , Nicola Blefari-Melazzi | ||
Last updated | 2013-12-22 (Latest revision 2013-06-20) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Information Centric Networking (ICN) paradigm shifts the focus of networking from providing connections between hosts to efficiently providing content to the users. The work on ICN has traditionally been performed looking at "clean-slate" solutions which aims to replace IP with a new paradigm. On the other hand, in this memo we propose an "integration" approach to Information Centric Networking, i.e. we extend the IP protocol suite by defining a new IP Protocol type (CONET). Then we propose two ways of carring ICN related information in IP packets, one uses a new IP Option (both for IPv4 and IPv6), the other one only relies on the IP payload. The ICN related information is used by network nodes and end nodes to support networking based on content rather than (or better in addition to) end-point addresses.
Authors
Andrea Detti
Stefano Salsano
Nicola Blefari-Melazzi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)