Feature #4706
closed
RDR packet format specification
Added by Junxiao Shi over 6 years ago.
Updated about 6 years ago.
Description
Realtime Data Retrieval (RDR) protocol enables realtime applications to discover names of the latest data. It assumes neither infrastructure support (namely, centralized server) nor clock synchronization, and does not rely on Exclude selector deprecated in #4444.
Real-Time Data Retrieval in Named Data Networking published in HotICN'2018 introduces the design of RDR protocol.
This issue is to produce a recommended packet format specification for the RDR protocol.
Although RDR is an application protocol, having a recommended format and a reference implementation promotes its adoption.
- Blocked by Task #4396: Provide canonical example for latest data retrieval without selectors in real-time applications added
- Blocked by Feature #4577: Naming conventions: use typed name components instead of markers added
- Blocks Task #4556: ndncatchunks: stop using Selectors added
- Assignee changed from Spyros Mastorakis to Junxiao Shi
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Blocked by deleted (Feature #4577: Naming conventions: use typed name components instead of markers)
Why there is "32" in the nameprefix of Interest and Data packets?
Chavoosh Ghasemi wrote:
Why there is "32" in the nameprefix of Interest and Data packets?
It's a KeywordNameComponent and 32 is its TLV-TYPE, see NameComponentType.
I know that the content of metadata packet should include the full name of the content (including version number). But I do not know how to create TLV and add it to the payload. Can you refer me to any reference to learn how to implement TLV?
- Status changed from Resolved to Closed
RDR rev4 corrects a few typos. Closing.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Anonymous