Repo Protocol Specification » History » Revision 83
Revision 82 (Shuo Chen, 02/25/2014 01:46 PM) → Revision 83/136 (Shuo Chen, 02/25/2014 01:56 PM)
Repo Protocol Specification
===========================
A Repo supports the network by preserving content and responding to Interests requesting content that it holds. A Repo can exist in any node, and is recommended if applications in that node need to preserve data. 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 interest is sent. The command 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
Repo registers prefixes of data objects it holds into NDN fowarding deamon and the repo will respond the data with such prefixes.
A standard interest 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 |-------------------------->|
| |
| |
| |
### About Freshness
Solution to handle freshness by repo has not been clearly defined, so producer needs to take care of freshness when it puts things into repo, i.e. explicitly delete obsolete content. The mustbefresh selector will be ignored by repo when fetching content from repo or handling repo command by repo.
## Repo Command
For insertion, deletion and other operations of repo, these commands are encoded in the form of [sigend command interest](http://redmine.named-data.net/projects/nfd/wiki/Command_Interests). The semantics of repo command interest is as follows:
The name semantics is defined to have following components:
* ``<repo prefix>`` refers to specific prefix repo is listening
* ``<command verb>`` refers to the name of command
* ``<RepoCommandParameters>`` refers to parameters of repo command
The following components are components of singed interest for access control:
* ``<timestamp>``
* ``<random-value>``
* ``<SignatureInfo>``
* ``<SignatureValue>``
For prefix of repo /ucla/cs/repo/, the command will be defined as this:
/ucla/cs/repo/<command verb>/<RepoCommandParameters>/<timestamp>/<random-value>/<SignatureInfo>/<SignatureValue>
### RepoCommandParameters
RepoCommandParameters ::= REPOCOMMANDPARAMETERS-TYPE TLV-LENGTH
Name?
Selectors?
StartBlockId?
EndBlockId?
ProcessId?
Name ::= NAME-TYPE TLV-LENGTH NameComponent*
NameComponent ::= NAME-COMPONENT-TYPE TLV-LENGTH BYTE+
Selectors ::= SELECTORS-TYPE TLV-LENGTH
MinSuffixComponents?
MaxSuffixComponents?
PublisherPublicKeyLocator?
Exclude?
ChildSelector?
MinSuffixComponents ::= MIN-SUFFIX-COMPONENTS-TYPE TLV-LENGTH
nonNegativeInteger
MaxSuffixComponents ::= MAX-SUFFIX-COMPONENTS-TYPE TLV-LENGTH
nonNegativeInteger
PublisherPublicKeyLocator ::= KeyLocator
Exclude ::= EXCLUDE-TYPE TLV-LENGTH Any? (NameComponent (Any)?)+
Any ::= ANY-TYPE TLV-LENGTH(=0)
ChildSelector ::= CHILD-SELECTOR-TYPE TLV-LENGTH
nonNegativeInteger
StartBlockId ::= STARTBLOCKID-TYPE TLV-LENGTH
nonNegativeInteger
EndBlockId ::= ENDBLOCKID-TYPE TLV-LENGTH
nonNegativeInteger
ProcessId ::= PROCESSID-TYPE TLV-LENGTH
nonNegativeInteger
#### Name
Name in command parameter is TLV-encoded block and represents the name or prefix of the data repo will process. The definition and format of name section are the same as the [name section](http://named-data.net/doc/ndn-tlv/name.html#name) of NDN interest.
#### Repo Command Selectors
Repo command supports parts of interest selectors of interest to indicate which contents to process. The definition of standard NDN selectors is described in [NDN Selectors Doc](http://named-data.net/doc/ndn-tlv/interest.html#selectors). The concrete definitions of both standard NDN selectors and repo command selectors are the same.
The difference between standard NDN interest and Repo Deletion Command interest that, the standard NDN selectors just matches **one** data packet that conforms to the selector conditions, but repo command selectors would matches **any** data packets. For example, if Interest is expressed for /ndn/edu and Exclude specifies one name component ucla, in standard NDN interest, the data producers will first exclude all the data packets with prefix /ndn/edu but not /ndn/edu/ucla, and then just selects one data packet. In repo deletion command interest, it will select all the data packets with prefix /ndn/edu but not /ndn/edu/ucla. However, in repo insert command, the repo will fetch one data just like standard interest selectors.
Repo command supports parts of standard NDN interests including MinSuffixComponents, MaxSuffixComponents, PublisherPublicKeyLocator, Exclude, ChildSelector. If command contains other selectors, repo will ignore these not supported selectors. In addition, selectors are just supported in delete command. If other commands contains selectors, repo will ignore selectors when processing these commands.
The form of selectors is as follows:
Selectors ::= SELECTORS-TYPE TLV-LENGTH
MinSuffixComponents?
MaxSuffixComponents?
PublisherPublicKeyLocator?
Exclude?
ChildSelector?
MinSuffixComponents ::= MIN-SUFFIX-COMPONENTS-TYPE TLV-LENGTH
nonNegativeInteger
MaxSuffixComponents ::= MAX-SUFFIX-COMPONENTS-TYPE TLV-LENGTH
nonNegativeInteger
PublisherPublicKeyLocator ::= KeyLocator
Exclude ::= EXCLUDE-TYPE TLV-LENGTH Any? (NameComponent (Any)?)+
Any ::= ANY-TYPE TLV-LENGTH(=0)
ChildSelector ::= CHILD-SELECTOR-TYPE TLV-LENGTH
nonNegativeInteger
#### StartBlockId, EndBlockId
StartBlockId and EndBlockId are used to process segmented data. StartBlockId indicate the first segment number and EndBlockId indicate the last segment number. Repo will process segment data whose segment id between StartBlockId and EndBlockId. If StartBlockId is missing, the first segment id the repo process is 0; If EndBlockId is missing, this scenario is described in specific process in Repo Insertion Command section and Repo Deletion Command section.
#### Conflict of Selectors and StartBlockId, EndBlockId
Repo cannot process command with both selectors and StartBlockId, EndBlockId in RepoCommandParameter. If the RepoCommandParameter carries both, repo will ignore this command interest and return with error code of 405.
#### ProcessId
ProcessId is used by insertion and deletion check command to indicate specific insertion and deletion process. The ProcessId is fetched by repo command response of insertion and deletion command.
## Repo Command Response
Repo command response is the response data packet of repo command interest. The response contains statuscode to indicate the status of command process and other information. A TLV-encoded block called ``RepoCommandResponse`` is encoded in content of the data packet.
RepoCommandResponse ::= INSERTSTATUS-TYPE TLV-LENGTH
ProcessId?
StatusCode?
StartBlockId?
EndBlockId?
InsertNum?
DeleteNum?
ProcessId ::= PROCESSID-TYPE TLV-LENGTH
nonNegativeInteger
StatusCode ::= STATUSCODE-TYPE TLV-LENGTH
nonNegativeInteger
StartBlockId ::= STARTBLOCKID-TYPE TLV-LENGTH
nonNegativeInteger
EndBlockId ::= ENDBLOCKID-TYPE TLV-LENGTH
nonNegativeInteger
InsertNum ::= INSERTNUM-TYPE TLV-LENGTH
nonNegativeInteger
DeleteNum ::= DELETENUM-TYPE TLV-LENGTH
nonNegativeInteger
### ProcessId
ProcessId is a random number generated by repo to indicate the number of the command process. Client could use this ProcessId to check the status of specific command.
### StatusCode
StatusCode indicates the status of repo command process. The statuscodes of insert and deletion command are described in following insertion and deletion specification.
### StartBlockId, EndBlockId
StartBlockId and EndBlockId are the same as those of RepoCommandParameter. If either of those in RepoCommandParameter is missing, repo will set them as the Id known for now. For example, if StartBlockId is missing in RepoCommandParameter, StartBlockId in response will be set 0. If EndBlockId is missing in RepoCommandParameter, EndBlockId will be set null untill Repo get FinalBlockId in data packet. If FinalBlockId in returned data packet is less than EndBlockId, the EndBlockId will be set FinalBlockId.
### InsertNum, DeleteNum
InsertNum is used in reponse of insertion status check to indicate how many data packets have been successfully inserted into the repo. DeleteNum is used in response of deletion command and deletion check command. DeleteNum indicates how many data packets have been successfully inserted from repo.
## Repo Trust Model
The trust model of repo depends on people who deploy the repo service, such as PKI. Repo can specify their own verification policies, and data consumers can specify their own trust anchors. The NDN [FAQ](http://named-data.net/project/faq/#How_does_NDN8217s_8220trust_management8221_work) shows how NDN trust managment works.
## Repo Insertion Specification
Repo insertion command requests that the repo retrieve and store content. This command 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.
Segmented data insertion is also supported in the insertion protocol. Segmantation info is defined as a TLV-encoded SegmantationInfo block. If the content is segmented, the final segment id will be encoded in this block.
### Insertion command interest semantics
The name semantics is follows the format of the repo command. The <command verb> is defined as ``insert``.
For example, for ``<repo prefix>`` as ``/ucla/cs/repo``, the following is an example:
/ucla/cs/repo/insert/<RepoCommandParameters>/<timestamp>/<random-value>/<SignatureInfo>/<SignatureValue>
### Insertion status check
During the insertion progress, the requester could send insertion status check command to check the status of the insertion progress. This status check command is also signed interest. The semantics of insertion status check command is shown as follows:
<command verb> equals to ``insert check``. For example:
/ucla/cs/repo/insert check/<RepoCommandParameters>/<timestamp>/<random-value>/<SignatureInfo>/<SignatureValue>
### RepoCommandParameter
RepoCommandParameter of insertion and insertion check command follows that in Repo Command section. Name, Selectors, StartBlockId, EndBlockId are used in insertion. Name and ProcessId are used in insertion check command.
In insertion command, Name represents the name or prefix of data for repo to fetch. If selectors are set, repo will use these selectors to fetch the data. If StartBlockId or EndBlockId is set, the repo will retrieve segmented data with segment number between StartBlockId and EndBlockId. If Repo Insert Command carries both Selectors and StartBlockId, EndBlockId, repo would ignore it and response with statuscode of 405.
In insertion check command, Name represents name or prefix of data for repo to fetch. ProcessId is set by the RepoCommandResponse to indicate specified process.
### Insertatation status response
This insert status data object could be the response data object of both insert command and insert check command. It will follow the format of repo command response.
StatusCode indicates the status of insertion. InsertNum represents how many data has been intersted into the repo. StartBlockId and EndBlockId is the start and end segment id of data inserted. InsertNum is the how many data segments have been inserted. ProcessId indicates an ID of process, a random number gernerated by repo.
For insert cammand, status code will be set according to definition below, StartBlockId and EndBlockId will be set according to the insert command. If StartBlockId in RepoCommandParameter is missing, it will be set 0 in response. If EndBlockId is missing, it will not be set.
For insert check command, status code will be set according to definition below, StartBlockId and EndBlockId will be set according to the StartBlockId and EndBlockId that repo is using, insertnum will be set according to insertion progress. ProcessId is set according to the ID of process checked. If EndBlockId has not been decided, this EndBlockId will not be set in response.
StatusCode Definition:
``StatusCode`` | Description
-------------- | ----------------------------------------------
``100`` | The command is OK. can start to fetch the data
``200`` | All the data has been inserted
``300`` | This insertion is in progress
``401`` | This insertion check is invalidated
``404`` | No such this insertion is in progress
``505`` | status check command is not supported
### EndBlockId Missing Timeout
If StartBlockId presents but EndBlockId is missing, and returned data packets do not contain FinalBlockId, the repo will continuosly fetch the data. An EndBlockId missing timeout is set to prevent this ocassion. The repo will start a timer when StartBlockId presents but EndBlockId is missing. When timeout happens, repo will stop fetching data to store and end insert process. If an insert check command arrives during this insert process, the time of timer is set to 0. If data packet containing FinalBlockId arrives, this timeout timer will be dismissed.
### Protocol Process
1. start to authorize the command; if authorization does not fail immediately, go to step 3
2. send a negative response indicating authorization failure, and abort these steps
3. if StartBlockId or EndBlockId is missing, go to step 7
4. if either StartBlockId or EndBlockId is present, and one of supported selectors is present. send negative reponse back and abort steps.
5. if both StartBlockId and EndBlockId are present, and StartBlockId is less than or equal to EndBlockId, go to step 7
6. send a negative response indicating malformed command, and abort these steps
7. wait for authorization completion
8. if authorization fails, go to step 2
9. send a positive response indicating insert is in progress
10. if either StartBlockId or EndBlockId is present, go to step 16
11. start to retrieve Name with selectors in insert command
12. wait for retrieval completion
13. if retrieval fails, go to step 26
14. store retrieved Data packet
15. abort these steps
16. if StartBlockId is missing, set StartBlockId 0. If EndBlockId is missing, EndBlockId will be missing unless get FinalBlockId in comming data packets.
17. append StartBlockId to Name
18. start to retrieve Name
19. wait for retrieval completion
20. if retrieval fails, go to step 26
21. store retrieved Data packet
22. if retrieved Data packet contains FinalBlockId, and FinalBlockId is less than EndBlockId or EndBlockId is missing, let EndBlockId be FinalBlockId
23. if the last component of Name is greater than or equal to EndBlockId, abort these steps
24. increment the last component of Name
25. go to step 17
26. retrieve data with this data another 2 times. If these 2 retrieval both failes, abort these steps. if success, go to step 13
27. retrieve data with this data another 2 times. If these 2 retrieval both failes, abort these steps. if success, go to step 20
Implementation MAY pipeline the Interests.
### Repo command progress report
Implementation MAY publish a notification of status regarding insert progress. The process of status check is as follows:
1. start to authorize the insert status command
2. send a negative response indicating authorization failure, and abort these steps
3. start to check the progress of the insert with the data name in the command. If no such progress is found, go to 4. or go to 5.
4. reponse status with status code of 404
5. ckeck te status of insertion. return the status data content
### Protocol diagram:
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 | | |
| | <==================== | | |
+---+ +---+ |
| | |
| | |
## Repo Deletion Specification
Deletion of one content object or content objects under certain prefix are both supported in repo specification. Selectors are used to select multiple content objects. These selectors are different from conventional [selectors](http://named-data.net/doc/ndn-tlv/interest.html#selectors) of interest packet. The conventional selecors of interest would select one data packet of repo. Selecors of delete command will return any data packets which applies for these selectors.
### Deletion command interest semantics
Deletion command interest follows the format of the repo command. For example:
/ucla/cs/repo/delete/<RepoCommandParameters>/<timestamp>/<random-value>/<SignatureInfo>/<SignatureValue>
### Deletion Command Selectors
Deletion command selectors follows the [repo command selectors](http://redmine.named-data.net/projects/repo-ng/wiki/Repo_Protocol_Specification#Repo-Command-Selectors).
### Deletion status check
During the deletion progress, the requester could send deletion status check command to check the status of the deletion progress. This status check command is also signed interest. The semantics of deletion status check command follows the format of repo command. ``<command verb>`` equals to ``delete check``. For example:
/ucla/cs/repo/delete/<RepoCommandParameters>/<timestamp>/<random-value>/<SignatureInfo>/<SignatureValue>
### Deletion Check Command Selectors
Selectors are not supported. Repo will ignore selectors when processing deletion status check command.
### Deletion status response
This delete status data object could be the response data packet of both delete command and delete check command. The name of data packet is the same as that of command.The deletion status is enocoded as a TLV echoded block in content block in data packet. The TLV block format follows RepoCommandResponse.
StatusCode indicates the status of deletion. DeleteSum is the sum of the deletion. DeleteNum represents how many data has been deleted.
StatusCode Definition:
``StatusCode`` | Description
-------------- | --------------------------------------
``200`` | All the data has been deleted
``300`` | This deletion is in progress
``401`` | This deletion check is invalidated
``404`` | No such this deletion is in progress
``505`` | status check command is not supported
### Protocol process
1. start to authorize the command; if authorization does not fail immediately, go to step 3
2. send a negative response indicating authorization failure, and abort these steps
3. check whether selectors are presented. If selectors are presented, go to step 4, or select the data packet of the exact name of command. If some data is selected, go to step 6. If no data selected, go to step 5
4. select all the data packets that comforms to data name of the command and the selectors. If some data packets are selected, go to step 6. Or no data selected, go to step 5.
5. send a negative response and abort the delete transaction.
6. wait for authorization completion
7. if authorization fails, go to step 2
8. start to delete the selected data. If deletion success, return positive reponse, or return negative response and abort the deletion.
Implementation MAY publish a notification of status regarding delete progress. The process of status check is as follows:
1. start to authorize the delete status command
2. send a negative response indicating authorization failure, and abort these steps
3. start to check the progress of the delete with the data name in the command. If no such progress is found, go to 4. or go to 5.
4. reponse status with status code of 404
5. ckeck te status of delete. return the status data content
### Protocol diagram:
Requester Repo
| |
| |
+---+ Delete command +---+
| | --------------------> | |
+---+ +---+
| |
| |
| |
+---+ Status interest +---+
| | --------------------> | |
+---+ | |
| | |
+---+ Status response | |
| | <==================== | |
+---+ +---+
| |
| |
| |
+---+ Confirm Deletion +---+
| | <==================== | |
+---+ Reject command +---+
| (with status code) |
| |