Abstracted Network API for ICN
draft-hur-icnrg-abstracted-network-api-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Cinyoung Hur , JongHwan Kim , Hee Jung , Jeesook Eun , Woo-Jik Chun | ||
| Last updated | 2015-04-30 (Latest revision 2014-10-27) | ||
| 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
draft-hur-icnrg-abstracted-network-api-00.txt In information-centric networking (ICN), well designed API will play a pivotal role in adopting ICN to applications. Traditional network API – i.e., current Socket implementation - is coupled between applications and underlying protocols, so it is hard to change one without changing the other, thus it could be solved by redesigning the network API in a way that decouples application-specific functions from network specific functions. In this draft, we addressed the network API modeling issues which can be also applied to the design of ICN APIs and proposed iPlug and dSocket API which help injection of applications’ intent and hide underlying network specific mechanisms, respectively.
Authors
Cinyoung Hur
JongHwan Kim
Hee Jung
Jeesook Eun
Woo-Jik Chun
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)