Repo Protocol Specification » History » Revision 11
Revision 10 (Alex Afanasyev, 02/18/2014 09:27 PM) → Revision 11/136 (Shuo Chen, 02/19/2014 09:50 AM)
Repo Protocol Specification =========================== Repo is persistent storage of data objects model in NDN. The NDN repo protocol is a specification of repo operations including reading, insertion and deletion of data objects in repo. Repo semantics is based on [Command Interests](http://redmine.named-data.net/projects/nfd/wiki/Command_Interests) with signed commponents an the end of the name and basic common semantics of NDN. When some operation of repo including insertion and deletion of data objects is requested, a command starter interest is sent. The command starter interest is the interest as command of insertion and deletion and signed as form of command interest for access control. The repo will response the command with the data object. The repo protocol can be categorized in three sections of reading, insertion and deletion of data objects. ## Repo Reading Specification The repo could be viewed as the data container of the data objects. It will register some specific prefixes of data objects it holds into NFD (NDN Forwarding Deamon) and the Deamon). The prefix of data objects that repo will respond will following such semantics. ### Semantics of data objects that repo manages The name semantics is defined to have following components,: * ``<box of repo>`` refers to specific name of repo * ``%R`` refers to data objects * ``<data name>`` refers to specific name of data <box of repo> and <data name> can be divided by serveral continious ``/`` according to specific defination. For example, for ``<box of repo>`` as ``/ucla/cs/repo`` and ``<data name>`` as ``/vedio/Forrest Gump/s1/v1``, the data with such prefixes. object is defined as following: /ucla/cs/repo/%R/vedio/Forrest Gump/s1/v1 A standard interest with such semantics is used to fetch content from the repo. The repo will respond when the name of the interest matches the prefix it registered in NFD. If the content in repo matches the interests, it will respond with the data object. When the interest is not matched, it will not respond. The protocol is listed as bellow If there is a matching data object: Requester Repo | | | | | Interest | t1 |-------------------------->| | | | Data Object | t2 |<==========================| | | | | | | If there is no matching data object: Requester Repo | | | | | Interest | t1 |-------------------------->| | | | | | | ## Repo Insertion Specification Insertion specification is for some client and application to insert data objects into certain NDN repo. A command starter interest as insertion command will be sent to the repo. This command starter interest is a signed interest and will be validated with access control policy defined by the repo. When the interested is validated and name of the data is not existed in the repo. The repository will reponse with a data object containing OK status and start to send the interest to fetch the data to insert. ### Insertion command starter interest semantics The name semantics is defined to have following components: * ``<box of repo>`` refers to specific name of repo * ``insert`` ``%I`` refers to insert data objects * ``<data name>`` refers to specific name of data that will be inserted The folloing components are components of singed interest for access control: * ``<timestamp>`` * ``<random-value>`` * ``<SignatureInfo>`` * ``<SignatureValue>`` <box of repo> and <data name> can be divided by serveral continious ``/`` according to specific defination. For example, for ``<box of repo>`` as ``/ucla/cs/repo`` and ``<data name>`` as ``/vedio/Forrest Gump``, Gump/s1/v1``, the data object is defined as following: /ucla/cs/repo/insert/vedio/Forrest Gump/<timestamp>/<random-value>/<SignatureInfo>/<SignatureValue> /ucla/cs/repo/%R/vedio/Forrest Gump/s1/v1/<timestamp>/<random-value>/<SignatureInfo>/<SignatureValue> Protocol diagram 1. Requester sends insert command to repo. 2. Repo checks this insert command. 2.1 Repo validates the this command interest. If invalidated, a data object contained invalidated status code will be responded. 2.2 Repo checks the name of the interest. If a data with the name same with the name of the data in command interest exists in repo, this command interest is rejected. Requester Repo Data producer | | | | | | +---+ Insert command +---+ | | | --------------------> | | | +---+ | | | | | | | +---+ Confirm start | | | | | <==================== | | | +---+ Reject command +---+ | | (with status code) | | | +---+ Interest for Data +---+ | | | --------------------------> | | | +---+ | | | | | | | +---+ Data segment | | | | | <========================== | | | +---+ +---+ | | | | ~ ~ | ~ ~ | | | | +---+ Interest for Data +---+ | | | --------------------------> | | | +---+ | | | | | | | +---+ Data segment | | | | | <========================== | | | +---+ +---+ | | | | | | | ~ ~ | ~ ~ | | | | | | | | | +---+ Status interest +---+ | | | --------------------> | | | +---+ | | | | | | | +---+ Status response | | | | | <==================== | | | +---+ +---+ | | | | | | |