Thoughts on Naming and Referencing of Data Objects within Content Distribution Network Interconnection (CDNI) solutions
draft-jenkins-cdni-names-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Ben Niven-Jenkins | ||
| Last updated | 2011-02-08 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-jenkins-cdni-names-00.txt
https://www.ietf.org/archive/id/draft-jenkins-cdni-names-00.txt
Abstract
As part of the development of protocols and solutions for CDNI it will be necessary to agree on common mechanisms for how to identify and name the data objects that are to be interchanged between interconnected CDNs, as well as how to describe which policy should be used when doing so. This document presents some thoughts on the naming and referencing of data types/objects within a CDNI solution.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)