Project

General

Profile

Feature #4706

RDR packet format specification

Added by Junxiao Shi 5 months ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Start date:
Due date:
% Done:

100%

Estimated time:
3.00 h

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.


Related issues

Blocked by NDN Specifications - Task #4396: Provide canonical example for latest data retrieval without selectors in real-time applicationsClosed

Blocks ndn-cxx - Feature #4707: RDR reference implementationCode review

Blocks ndn-tools - Task #4556: ndncatchunks: stop using ChildSelector and ExcludeNew

History

#1 Updated by Junxiao Shi 5 months ago

  • Blocked by Task #4396: Provide canonical example for latest data retrieval without selectors in real-time applications added

#2 Updated by Junxiao Shi 5 months ago

#3 Updated by Junxiao Shi 5 months ago

  • Blocked by Feature #4577: Naming conventions: use typed name components instead of markers added

#4 Updated by Davide Pesavento 4 months ago

  • Blocks Task #4556: ndncatchunks: stop using ChildSelector and Exclude added

#5 Updated by Alex Afanasyev 4 months ago

  • Assignee changed from Spyros Mastorakis to Junxiao Shi

#6 Updated by Junxiao Shi 3 months ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

RDR rev1.

#7 Updated by Junxiao Shi 3 months ago

  • Blocked by deleted (Feature #4577: Naming conventions: use typed name components instead of markers)

#8 Updated by Chavoosh Ghasemi 3 months ago

Why there is "32" in the nameprefix of Interest and Data packets?

#9 Updated by Davide Pesavento 3 months ago

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.

#10 Updated by Chavoosh Ghasemi 3 months ago

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?

#11 Updated by Jeff Thompson 3 months ago

The content of a Link data packet is basically the same thing. Maybe you could use that.

https://github.com/named-data/ndn-cxx/blob/master/src/link.hpp

#12 Updated by Chavoosh Ghasemi 3 months ago

Jeff Thompson wrote:

The content of a Link data packet is basically the same thing. Maybe you could use that.

https://github.com/named-data/ndn-cxx/blob/master/src/link.hpp

Thanks for sharing the link, Jeff. It was so helpful.

#13 Updated by Junxiao Shi 3 months ago

  • Status changed from Resolved to Closed

RDR rev4 corrects a few typos. Closing.

Also available in: Atom PDF