Container Assisted Naming and Routing for ICN
draft-yao-icnrg-naming-routing-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Chunfeng Yao, Rong Wang , Yuanzhe Xuan, 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
In ICN (Information-centric network), everything is an identifiable object with a name, therefore the number of name prefixes is a few orders of magnitude higher than that in current BGP routing table. Towards scalable routing in ICN, we propose a name scheme, called container assisted naming. With this scheme, an object name consists of two components: a content name which uniquely specifies the object within certain scope, and one or more containers which define access relationships to the object. This document illustrates the concept of container and how it assists scalable routing in ICN.
Authors
Chunfeng Yao
Rong Wang
Yuanzhe Xuan
Zhefeng Yan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)