Project

General

Profile

Actions
Copy link

Feature #4706

closed

RDR packet format specification

Added by Junxiao Shi over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Junxiao Shi
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 3 (0 open — 3 closed)

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

Actions
Blocks ndn-cxx - Feature #4707: RDR reference implementationClosedChavoosh Ghasemi

Actions
Blocks ndn-tools - Task #4556: ndncatchunks: stop using SelectorsClosedChavoosh Ghasemi

Actions
Actions
Copy link
 #1

Updated by Junxiao Shi over 5 years ago

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

Updated by Junxiao Shi over 5 years ago

Actions
Copy link
 #3

Updated by Junxiao Shi over 5 years ago

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

Updated by Davide Pesavento over 5 years ago

  • Blocks Task #4556: ndncatchunks: stop using Selectors added
Actions
Copy link
 #5

Updated by Alex Afanasyev over 5 years ago

  • Assignee changed from Spyros Mastorakis to Junxiao Shi
Actions
Copy link
 #6

Updated by Junxiao Shi over 5 years ago

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

RDR rev1.

Actions
Copy link
 #7

Updated by Junxiao Shi over 5 years ago

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

Updated by Chavoosh Ghasemi over 5 years ago

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

Actions
Copy link
 #9

Updated by Davide Pesavento over 5 years 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.

Actions
Copy link
 #10

Updated by Chavoosh Ghasemi over 5 years 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?

Actions
Copy link
 #11

Updated by Anonymous over 5 years 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

Actions
Copy link
 #12

Updated by Chavoosh Ghasemi over 5 years 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.

Actions
Copy link
 #13

Updated by Junxiao Shi over 5 years ago

  • Status changed from Resolved to Closed

RDR rev4 corrects a few typos. Closing.

Actions
Copy link

Also available in: Atom PDF