ICN Packet Format Design Requirements
draft-icn-packet-format-requirements-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alexander Afanasyev , Ravi Ravindran , Guoqiang Wang , Lan Wang , Beichuan Zhang , Lixia Zhang | ||
| Last updated | 2015-09-30 (Latest revision 2015-03-29) | ||
| 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
It is a great challenge to design the right packet format for the Information-Centric Networking (ICN), because this new architecture is still in its research stage. We do not have good prediction regarding either the technology advances or the application needs may involve in next 10 years and beyond. To minimize the danger of premature constraints in the packet format design, we believe it is important to first clearly identify the design requirements, so that we can use the requirements to guide the design effort. In this document we describe our understanding of the design requirements and their tradeoffs.
Authors
Alexander Afanasyev
Ravi Ravindran
Guoqiang Wang
Lan Wang
Beichuan Zhang
Lixia Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)