File-Like ICN Collections (FLIC)
draft-irtf-icnrg-flic-07
| Document | Type |
Expired Internet-Draft
(icnrg RG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christian Tschudin , Christopher A. Wood , Marc Mosko , David R. Oran | ||
| Last updated | 2025-09-04 (Latest revision 2025-03-03) | ||
| RFC stream | Internet Research Task Force (IRTF) | ||
| Intended RFC status | Experimental | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | IRTF state | In RG Last Call | |
| Consensus boilerplate | Unknown | ||
| Document shepherd | (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
This document describes how to encode an application data objet into a structured _manifest_ using Information Centric Networking (ICN) data objects, creating a File-Like ICN Collection (FLIC). The manifest is an "index table" of objects that make up the manifest itself and the application data. It records the hash value (content object hash) of each item so a consumer using the manifest may request each piece by a complete hash name. The manifest is hierarchical and may be encoded into realtively small ICN objects to fit within network MTU sizes. FLIC has several methods to guide a consumer in constructing appropriate Interest names based on the manifest. It also supports encryption of the manifest data. FLIC may be used in CCNx or Named Data Networking, or other ICNs.
Authors
Christian Tschudin
Christopher A. Wood
Marc Mosko
David R. Oran
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)