Container Resolution System in ICN
draft-wang-icnrg-container-resolution-system-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Rong Wang , Chunfeng Yao, Zhefeng Yan | ||
| Last updated | 2013-08-22 (Latest revision 2013-02-18) | ||
| 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
We illustrate the architecture and mechanism of container resolution system, and to the protocol of resolving containers in ICN. The fundamental characters are:1)Use Interest and Data packet as the communication primitives, 2)Every routing node has FIB, CS, PIT tables to do packet routing and caching. Current NDN/CCN architecture does not require a resolution system. The routing is totally based on prefixes of content names, which causes scalability and mobility issues described in [Cisco-Name]. This draft addresses the aforementioned issues.
Authors
Rong Wang
Chunfeng Yao
Zhefeng Yan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)